building-product-specifications

Building Product Specifications

Setup

Item	Kind	Required	When	Done when	How
Root path	ask	required	All	spec-contract.md → Resolve docs root finds a root	Ask for the folder (default docs/); missing or empty → use it, else ask for another path; recorded as the root's location
Root marker	static	required	All	<docs-root>/index.md carries spec-contract.md → Author signature	Write index.md from assets/index.md

Workflow

1. Setup — for each Setup row whose When covers the request, in order: Done when holds → skip; user → stop and print its How when required, continue without it when optional; ask → fill what the request answers, ask the rest together in one message, record each answer; auto and static → run.
2. Contract — read spec-contract.md.
3. Recipe — match one Recipes row; open every doc in its Read column.

• Writes no application code unless the user asks for it in the same message.

Recipes

Intent	Example phrasing	Read
Set up	"Set up building-product-specifications", "Is building-product-specifications ready?"	Setup — run Workflow step 1 for every row, then report each row's state
PRD	"Draft a PRD", "Update the product requirements"	creating-prd.md
FRD	"Write an FRD for checkout", "Amend the checkout FRD"	creating-frd.md
User story	"User stories for checkout", "Product user journeys"	creating-user-story.md
TRD	"Technical design for checkout", "System architecture TRD"	creating-trd.md
UI specs	"UI specs for checkout", "Screen flow and structure", "View states for checkout"	creating-ui-specs.md