PRD overview
Chapter 01 · the spec every other chapter reads from.
The PRD is your project's engineering blueprint: what ships now and what waits, the architecture, every page, user journeys mapped decision by decision. It's the chapter every other one is built against. You describe what you want in plain language; an Architect agent drafts the complete spec; you edit it, refine it with AI, optionally run it past a panel of expert reviewers, and approve it. Approval snapshots the spec every other chapter reads from — which is why this chapter comes first.
How it works
A short intake conversation, then the spec streams in live, section by section while you watch (Environment fills from the project's env panel rather than streaming). Edit any line inline, ask Modus to refine a section, or send the whole document to a four-agent review. When it reads right, hit Approve — the Token Launcher unlocks, and the snapshot becomes the spec Design and Code build from.
What's in a PRD
Seven sections, each capturing one slice of the spec:
| Section | What it holds |
|---|---|
| Problem | The pain point, who it affects, why now |
| Users | 1–3 user personas |
| Scope | What's in v1, what's explicitly out |
| Architecture | Five canonical rows: persistence, backend, contracts, integrations, deploy target |
| Environment | Stack, hosts, and integrations (env vars) |
| Pages | The UI screens and what's on them |
| User journeys | How each persona moves through the pages to a goal |
Together they answer the only question that matters before you build: what exactly are we making, and for whom?
The workspace
Three panes, laid out so editing never breaks your flow:
- A subheader with your project title and the Review + Approve actions, always in reach.
- A content pane: one tab per section, edit inline.
- A chat panel alongside it (resize it, dock it left or right) that flips between Chat with the Architect and Review from the expert panel.
The lifecycle, in one line
Describe it → the spec drafts itself live → you edit and refine → optional expert review → Approve → the build unlocks.
Each step has its own page:
- Intake & drafting: how the spec gets written
- Editing the sections: the seven section editors
- Refine & review: AI refinement and the expert panel
- Approval: sign-off, snapshots, and unlocking