Step 4 — Produce roadmap.md¶
The tech design told you how to build each feature. The roadmap tells you in what order.
This is a short step — you're not making new decisions here, you're sequencing the ones already made.
Before you run the prompt¶
Open a new chat. The roadmap needs a clean context — no memory of the tech-design conversation. You want the agent reading tech-design.md as a finished document, not continuing an open negotiation.
Select Claude Sonnet — this is a lightweight task, no deep reasoning needed.
The prompt¶
Read specs/tech-design.md and specs/brief.md.
Produce specs/roadmap.md — an ordered list of implementation features.
Rules:
- Order features so that each one builds on what came before. Earlier features should not depend on later ones.
- Each feature gets: a short name, one sentence describing what it delivers to the user, a status (`planned` / `in progress` / `done`), a one-line implementation summary (how it's built — reference the relevant decision from `specs/tech-design.md` and link to that section), and a one-line done-criteria (how you know it's complete).
- No implementation detail. No AL objects. No field names. Just what the feature is and when it's done.
- Keep it short. The roadmap is a queue, not a spec.
Implementation summaries don't need to be perfect
If some details in the implementation summary aren't 100% accurate at this stage, that's fine. We'll move feature by feature, and with each one we'll refine the implementation, updating both the roadmap and tech-design.md as we go. The roadmap is a living document, not a contract.
What to expect¶
The agent should return 6–8 features in a logical build order. A reasonable sequence follows the dependencies naturally: you can't book a car that doesn't exist, you can't pick up without a booking, you can't bill without a pickup.
If the order looks wrong — for example billing appears before booking — push back and ask why.
Commit when you're satisfied¶
The constitution is complete¶
You now have everything an agent needs to start building:
specs/brief.md— what the customer wantsspecs/tech-design.md— how to implement itspecs/roadmap.md— in what order One more thing before you build — you needAGENTS.md.