Build Sequences
The product's core output: one base prompt plus an ordered set of follow-up prompts, each with a purpose, completion checks, and a lineage back to the approved understanding.
Why not one mega-prompt
A single prompt that describes an entire product asks a build tool to make hundreds of decisions at once. The tool fills gaps with defaults, features interfere with each other, and when the output is wrong there is no way to tell which part of the prompt caused it. Ordered prompts fix this by construction: each step carries a bounded amount of intent, lands on a working state, and gives you a checkpoint before the next step builds on it.
The base prompt (order 0)
Every Build Sequence starts with one complete base prompt at order 0. It establishes the product foundation — the core structure and the first working slice — phrased in the vocabulary of your chosen build target. The base prompt is free for every approved project, complete on its own, and never truncated.
Ordered follow-ups
After the base prompt come 2 to 12 follow-up prompts in a fixed order. Each one assumes the state the previous prompts produced and extends it — the order is not decorative, it is the dependency structure of your build. Every follow-up states its purpose, so you always know why a step exists before you paste it. Follow-ups are generated with the base prompt but stay withheld server-side until the project holds a license; Licenses and pricing has the exact boundary.
Completion checks
Each prompt includes checks you can perform before advancing: concrete observations about what should now exist or work. Run them. Advancing past a failed check compounds the failure into every later step, while catching it immediately keeps the fix small. The checks are what make the sequence a sequence rather than a pile of prompts.
Feature lineage
Every prompt maps to named features in the approved Build Understanding — the retain, modify, and add classifications you signed off on. That lineage runs in both directions: for any prompt you can see which approved features it implements, and for any approved feature you can see which step builds it. Nothing in the sequence is unaccounted for, and nothing approved is silently dropped. This is why approval is immutable — see The Build Understanding.
Working with a sequence
In the workspace you can copy each prompt, copy the whole sequence, export it as a text file, mark steps complete as you go — your progress is saved to the project, so the sequence reopens where you left off — and share a private link to the sequence. If your scope changes after approval, the sequence regenerates from a newly approved understanding rather than drifting. To choose the tool you will run it in, read Choosing a build target.