DE View packages

Product · Organize the project

AI Founder Kit

Put project context, decisions and next steps into one system — so you do not start from zero with AI agents every time.

A set of versioned Markdown templates that hold your project state — readable for you and for any AI tool.

Request access What is included?
  • One-time payment
  • No subscription
  • v1.x updates included
  • ZIP download after confirmed payment
  • Ready to use
Version 1.1.1 available Request access
  • One-time payment
  • No subscription
  • v1.x updates included
  • ZIP download after confirmed payment
  • Ready to use

The kit is a set of versioned Markdown files you add to your project — no account, no cloud. You download it as a ZIP after purchase and put it to work right away.

What you get, concretely

The building blocks for your project state.

Project context file

PROJECT_CONTEXT.md keeps goal, status, assumptions and open questions in one place — not scattered across chats.

Decisions & roadmap

FOUNDER_DECISIONS.md and a roadmap structure keep reasoned decisions outside the chat history.

Task & briefing templates

Scoped task templates with goal, scope and protected areas — so agents understand what they may change.

Status & handoffs

Handoff and status files let a new session or model continue instead of starting over.

Next-step file

Captures the one sensible next step — continue without a long run-up.

Local Markdown files

No account, no cloud. You drop the files into your project and use them with the AI tool you already have.

What it gives you

What changes in daily work.

  • Clearer decisions, because context and reasoning are preserved.
  • Less context loss between sessions and models.
  • Reusable project memory instead of scattered notes.
  • Better prompts and briefings, because the state is already structured.
  • One shared place instead of documents across five tools.

What it saves you

Where idle time disappears.

  • Saves setup and thinking time on every new work step.
  • Reduces rework and false starts caused by unclear context.
  • Cuts unnecessary tool and token loops from re-explaining.
  • Can save weeks of structure-building — but does not replace your decision.

Ready to structure your project?

One-time payment, no subscription, ZIP download after confirmed payment.

Request access Read the FAQ

Compare

One layer, the other, or both as one.

The Founder Kit runs the project. The Orchestrator Kit runs the AI team. The Operating System is the complete system that keeps both in sync.

Capability Founder Kit Orchestrator Kit AI Founder Operating System Complete system
Project context
Decisions and roadmap
Tasks and handoffs
Quality gates
AI role matrix
Model routing
Repo / worktree safety
Review and verification
Integrated end-to-end loop Bundle only
Sample project Bundle only
Typical setup 1 tool 1–2 tools 2–3 tools + Operator
Orchestration scope Project layer Coordination & routing End-to-end loop
Best for Running the project Coordinating the AI team Both, kept in sync
Current status Available Available Available
Founder Kit
Project context
Included
Decisions and roadmap
Included
Tasks and handoffs
Included
Quality gates
Included
AI role matrix
Not included
Model routing
Not included
Repo / worktree safety
Not included
Review and verification
Not included
Integrated end-to-end loop
Not included
Sample project
Not included
Typical setup
1 tool
Orchestration scope
Project layer
Best for
Running the project
Current status
Available
Orchestrator Kit
Project context
Not included
Decisions and roadmap
Not included
Tasks and handoffs
Shared
Quality gates
Partial
AI role matrix
Included
Model routing
Included
Repo / worktree safety
Included
Review and verification
Included
Integrated end-to-end loop
Not included
Sample project
Not included
Typical setup
1–2 tools
Orchestration scope
Coordination & routing
Best for
Coordinating the AI team
Current status
Available
Complete system AI Founder Operating System
Project context
Included
Decisions and roadmap
Included
Tasks and handoffs
Included
Quality gates
Included
AI role matrix
Included
Model routing
Included
Repo / worktree safety
Included
Review and verification
Included
Integrated end-to-end loop
Included
Sample project
Included
Typical setup
2–3 tools + Operator
Orchestration scope
End-to-end loop
Best for
Both, kept in sync
Current status
Available

The three workflow packages are available as version 1.1.1. AI Operator Bridge is a separate local tool package.

Every package works with one tool. The tool count is a recommendation, not a requirement.

The system around the package

AI Orchestrator is a founder/operator system

Not just templates, but one way of working: find work, prepare the AI task, check the result, remember the decision. Guides, agent briefings, QA and release routines — plus the local operator workflow the package is built around. Five building blocks that fit together.

  1. Founder Operating System

    The layer that keeps project and AI team in sync.

    • Decisions, scope and priorities in one traceable place.
    • A clear execution order instead of random prompting.
    • Context stays intact across sessions and models.

  2. Local Operator Bridge

    The core local tool: it does the operator work around your AI agents — not a web service on this page.

    • Prepares tasks, generates handoffs and reviews agent reports locally.
    • Detects protected areas and flags risky changes before you approve.
    • A copy-ready report for Claude or Codex instead of screenshot chaos.
    • Secrets stay local and are not copied into the report.

  3. Founder SEO Tool

    An SEO-first tool with an AI Answer Readiness module — the first workflow that feeds AI Bridge.

    • Standard SEO audit plus an AI Answer Block Scanner for definitions, steps and comparison/Q&A structure.
    • Gives priorities, before/after suggestions and a copy-paste handoff — exportable as an AI Bridge task.
    • No ranking promise — analysis and next steps, not a visibility score.

  4. Agent Briefing System

    Structured tasks for Claude, Codex and other agents.

    • Goal, scope, protected areas and acceptance criteria per task.
    • Protected files an agent must not touch.
    • QA and handoff reports instead of a vague “done”.

  5. Release & QA Workflow

    The routine before every step that goes outward.

    • Preflight and a protected diff before anything changes.
    • Live smoke checks after shipping.
    • No live money action without an explicit gate and your confirmation.

The Operator Bridge and Founder SEO Tool are part of the operator workflow around the package and support working with it — they are not files inside the product ZIP. Local tools run on your machine; this page explains the way of working.

View packages Read the FAQ

What you actually receive after buying

Included

  • Downloadable package files as a ZIP.
  • Markdown documents, templates, checklists and agent briefings.
  • Clear workflow instructions.

Not included

  • No subscription.
  • No cloud dashboard and no account.
  • No live credentials.
  • No automatic deployment.
  • No Operator Bridge app inside the ZIP.
  • No Founder SEO Tool app inside the ZIP.

The value is not just in files, but in the structure: tasks, decisions, QA and safe handoffs to agents.

System vs. download

The ZIP is what you buy and download today. The operator system is how the package is meant to be used. AI Operator Bridge is the core local tool that does the operator work around your AI agents; the Founder SEO Tool is the first connected workflow — it finds SEO work and turns it into an AI Bridge task. Future add-ons could package them separately.

View packages Read the FAQ

Why it is more than a template

A template is a starting point. This is a continuing system.

One tool is enough. No coding required. You fill in Markdown templates — with the AI tool you already use.

Templates give you blank structure. The AI Founder Kit holds living state: what was decided, what is in progress, what is verified, and what should happen next — so a new session, or a new model, continues instead of starting over.

What it answers

The questions a project keeps asking.

What is the AI Founder Kit?

A structured operating layer for the project itself — the files that hold what you are building, what was decided, and what to do next.

What problem does it solve?

Context, decisions and task history scatter across chats and get lost between sessions. The kit keeps them in one durable place.

How does a human start?

A START_HERE_FOR_HUMAN file explains where the project stands and the next best action — no archaeology required.

How does the AI start?

A START_HERE_FOR_AI file gives an agent its context, rules and priorities before it touches anything.

How are decisions saved?

A Founder Decision Log captures decisions that must not be lost, outside of chat history.

How do tasks and handoffs work?

Scoped task templates make work routable; handoff files preserve results across sessions and models.

Who is it for?

Solo founders and small teams running a real project with AI assistance who keep re-explaining their own context.

Who is it not for?

Anyone wanting a one-off prompt collection, or a finished SaaS dashboard — neither is what this is.

What is actually inside · v1.1.1

The real files you add to your project.

These are the exact filenames in version 1.1.1 — not screenshots of an app. The ZIP is delivered after confirmed payment; short, real excerpts are shown in the product proof below.

AI Founder Kit Organizes the project.

Entry points

  • START_HERE_FOR_HUMAN.md Where the project stands and the next best action.
  • START_HERE_FOR_AI.md The first file an agent reads — context, rules, priorities.

Project memory

  • PROJECT_CONTEXT.md What/who/why and the constraints that frame decisions.
  • PRODUCT_STRATEGY.md Positioning, scope and priorities.
  • FOUNDER_DECISIONS.md Append-only decision memory, kept out of chat history.

Working state

  • PROJECT_STATUS.md The verified current state.
  • ACTIVE_TASKS.md Scoped tasks in flight, with allowed files and a definition of done.
  • ROADMAP.md Phased plan of now / next / later.
  • NEXT_BEST_ACTION.md A single, unambiguous next step.

Guard rails & history

  • QUALITY_GATES.md The bar a change must clear to be "done".
  • STOP_RULES.md Hard conditions under which work pauses instead of guessing.
  • HANDOFF_LOG.md Append-only timeline of completed work.
  • templates/ Task, handoff, decision, status, roadmap and QA report formats.

Check before you buy

What is in the package — shown with real files.

Real excerpts from version 1.1.1: which file you open first, what a short start gives you, how the files work together, and what is deliberately not included.

What you download

How you receive and use version 1.1.1 — no app, no account, no cloud.

Version
1.1.1
Product format
Digital ZIP archive
Contents
Markdown working files, templates and checklists; a completed sample project is included only in the bundle
Language of the product files
English — the site is bilingual, the kit files themselves are English
Requirements
A local project or repository and any editor; nothing to compile or install
Delivery
Download after confirmed payment plus an email with the access link
Account required
No — no cloud, no running online service
Subscription
No — a one-time purchase, no recurring fees or credits
Updates
All v1.x updates included; v2.0 is a separate product

What you open first

Three files are enough to start — in this order.

  1. START_HERE_FOR_HUMAN.md Ten minutes of orientation: how the kit runs and which start path fits you.
  2. PROJECT_CONTEXT.md The project core: what you build, for whom and with what goal — three fields are enough to start.
  3. NAVIGATION.md The router: from your situation to the right next file.

Result after the quick start Project goal, scope and a first clean agent task are set — a first usable base in about 15–25 minutes.

Real file excerpts

What a filled-in project context looks like.

PROJECT_CONTEXT.md Excerpt

Project
FeedbackPing — a lightweight feedback tool for appointment-based businesses
Primary goal
Ask one good question after each appointment and see the answers in one place
Current stage
Pre-launch — the first real-world test is next
Users
Small service businesses, e.g. a two-person bike repair shop
Constraints
One founder, a few evenings per week, running cost near zero
Protected areas
The data schema changes only with explicit approval
Definition of success
Setup in under five minutes; at least half of the prompts get an answer

Fictional sample project — no real people or companies.

The project context survives outside individual chats — every session and every AI tool starts from the same state.

From NAVIGATION.md — three ways in by how much time you have.

NAVIGATION.md Excerpt

## Three ways in (pick by how much time you have)

- 15-minute start — just get going safely: name the project, fill the top of PROJECT_CONTEXT.md, and prepare one small, safe task.

- 60-minute setup — a working project base: context, strategy, status, first roadmap items, quality gates, and the first task.

- Full method — keep running it: use the working loop for every task, and FILE_MAP.md for who owns which file.

Real excerpt · shortened for the preview · full file in the package.

How the files work together

  1. Context Fill PROJECT_CONTEXT.md: what, for whom, goal.
  2. Task ACTIVE_TASKS.md: one small, scoped task with a definition of done.
  3. Agent Hand over START_HERE_FOR_AI.md — the assistant plans first.
  4. Verify Check the plan and result against the definition of done.
  5. Next step NEXT_BEST_ACTION.md: record the one next action.

What is not included

So it is clear what you do yourself — nothing hidden.

  • No SaaS account and no running cloud platform
  • No automatic implementation by us
  • No personal consulting and no success guarantee
  • No API credits needed — a normal chat account is enough
Request access Compare all packages

Fit

Is it for you?

A good fit if…

  • You run a real project with AI help.
  • You lose context between sessions.
  • You want decisions and tasks to persist.

Not for you if…

  • You want a prompt collection.
  • You expect a hosted app or login today.
  • You want done-for-you content.

Updates

Version 1.1.1 with v1.x updates included.

Version 1.1.1 contains the project operating layer — START_HERE files, decision log, task and handoff system. v1.1.1 brings the one-tool and no-code entry to the front and refines the entry files. Existing buyers receive v1.1.1 via “restore access”; your own filled-in files stay usable — no migration required. Further v1.x updates for this package are included; no publication dates are promised.

Request access Compare all packages