Stop 3 of 6
Spec: agree on what you're building
You and your agent agree on SPEC.md: a plain description of what you're building, who it's for, and what's in and out.
≈ 30–60 minMilestone · Your first spec
What your agent will do
- A1Interviews you, one question at a time, each with a suggested answer you can accept or change.
- A2Writes
SPEC.md: a plain-language summary first, then the technical sections it needs. - A3Waits for your OK before planning anything. No code yet.
What you do
- Answer in your own words. “I don't know yet” is a fine answer: your agent will suggest one.
- Read
SPEC.md: click it in your agent's file list, or open Finder → Development → your project. - Reply OK, or say what to change. Your agent updates the spec until it matches your idea.
- Answer in your own words. “I don't know yet” is a fine answer: your agent will suggest one.
- Read
SPEC.md: click it in your agent's file list, or open File Explorer → Development → your project. - Reply OK, or say what to change. Your agent updates the spec until it matches your idea.
The ideas behind it
When something goes wrong
Your agent starts writing code before the spec is agreedSay: “Stop. Let's finish and agree on SPEC.md first.” More help →
The spec is full of words you don't understandAsk for the summary in plain words, with each term explained. More help →
You changed your mind about a featureNormal. Update
SPEC.md first, then the plan, then the code. More help →Quick check · 1 question
Why does your agent write SPEC.md before any code?
Copy for your agent
We're at the Spec stage. Read SPEC.md and tasks/todo.md and continue from where we left off.
Saved on this device only. No account needed.
Was this page helpful?