Overview
Writes pre-implementation product specs on disk: product vision (PRD), feature behavior (FRD), technical design (TRD), user journeys, and UI specs (navigation flow, screen structure, view states). Recipes own doc-type rules; spec-contract.md is shared plumbing. Works wherever the agent can read and write repository files.
Agent workflow
Follow this skill when the user names it, or references a spec file under a marked docs root, to create or amend product specification markdown. Stop without application code unless the user explicitly asks in the same message.
Docs root: Locate via <docs-root>/index.md with the static Author signature UUID. If none exists, ask the user for an empty folder path, then initialize. See spec-contract.md → Resolve docs root.
Match one Recipes row; open exactly that reference. Each create recipe also covers amend when the target file already exists.
Recipes
| Intent | Example phrasing | Read |
|---|---|---|
| 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 |
Reference index
Contract
spec-contract.md — resolve root, layout, frontmatter, tiers, hub sync, create-or-amend.
| Doc | When to use |
|---|---|
| spec-contract.md | Docs root marker, paths, frontmatter, tiers, hub sync, create-or-amend |
| creating-prd.md | New or amend prd.md |
| creating-frd.md | New or amend features/<slug>/frd.md |
| creating-user-story.md | New or amend product or feature user-story.md |
| creating-trd.md | New or amend product or feature trd.md |
| creating-ui-specs.md | New or amend product or feature ui-specs.md (flow, structure, view states) |