Requirements And Artifact Contract

Use this before writing or revising product requirement files or the artifact contract. Keep the active system prompt small; detailed file shapes live in references.

Core Workflow

1. Write user-facing requirements in product/README.md.
2. Write machine-readable requirements in product/requirements.json as a requirements map. Every item has value and source; allowed sources are user, default, and research.
3. Research and write a concrete first draft before asking the user anything. If specific product facts or choices remain open, use user.ask with purpose="prd_item_confirmation" for only those items, write the answers back, and repeat until no PRD questions remain.
4. Never ask the user to approve, reject, review, or revise the whole PRD. Record each structured answer with source="user"; keep agent defaults and researched facts distinguishable.
5. Write product/contract.json before CAD modeling.
6. Resolve every PRD and artifact-contract diagnostic. The PRD is ready when open_questions is empty and the artifact contract is valid.
7. Report the PRD written and ask whether to begin BOM, PCB, or CAD in ordinary final text. Stop the query unless its original scope explicitly requested later stages.

Revising A User Requirement

A requirement with source="user" belongs to the user. When downstream design work contradicts one, ask that single item with user.ask purpose="prd_change_confirmation" and factId equal to the requirement id. Apply the answer to the requirement or design as directed. The durable decision receipt and project Git history record the outcome; do not duplicate baselines, conflicts, or change logs inside the PRD. Never rewrite a user requirement merely so the built design passes.

References

• references/product-files.md - required fields, allowed values, examples, and handoff rules for PRD status and artifact contracts.