| What you agree | Minimum | When the project needs expansion |
|---|---|---|
| Who it is for, why, boundaries | docs/product.md | Detailed scenarios in product-spec.md |
| Stages, current work, short decision, and evidence | One docs/plan.md | The plan preserves status and links to details |
| How the system is built | Short description in the right existing project section | architecture.md: current state separate from proposed |
| How screens look and work | “Interface” section in the same plan, with links to accepted graphics | Link to an existing design system; no second copy of rules |
| A durable choice and why | Briefly in the plan | decisions.md |
| How to run it | README.md | development.md |
| What was checked | Evidence in the plan | verification.md, with version and limits |
| How the agent should work | AGENTS.md: rules and links | Short instruction with links to documents |
Do not fill in these documents in advance. Ask the agent to record decisions during the conversation. For example, after agreeing “I do not need sign-in in the first version,” it should add that boundary to the product description. Its proposal does not become a decision until you agree it. If it moves details to a separate file, it leaves a link in the plan.