Use case
Planned
Product spec
Turn an outcome into a product spec (stories, acceptance criteria, edge cases) as a reviewed artifact, not a doc written from scratch.
What it is
The stage, and what it produces
A product agent frames the problem and drafts the spec from your workspace context. It's a proposal, not a decision: a human reviews it, and once approved it becomes trusted context the rest of the run builds on.
In a run
How it works, step by step
- 01Frame the problem, the users and the definition of done
- 02Draft stories and acceptance criteria
- 03Surface edge cases and priorities
- 04A human reviews, edits or approves
Spec · Checkout Approved → Memory
- As a buyer, I can pay with a saved card
- AC: a declined card shows a retry path
- AC: idempotent on double-submit
- Edge: card expires mid-checkout
Illustrative - produced, reviewed and approved before the next step.
Works with
The parts of the platform it leans on
Where it stands. Approving a drafted spec - so it becomes context in Memory - ships today. Generating the full spec is part of the Planned orchestration.
Turn this stage into a governed output
Start with what ships today, and grow into the full run as it lands.