Building Product Specifications
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 creating or amending 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) |
Templates
assets/index.mdassets/prd.mdassets/frd.mdassets/trd.mdassets/user-story.mdassets/ui-specs.md
1---2name: building-product-specifications3description: Creates and amends product specification markdown — PRD, FRD, TRD, user story, and UI specs (flow, screen structure, view states) — with consistent layout and frontmatter. Use when the user asks to draft or amend prd.md, frd.md, trd.md, user-story.md, or ui-specs.md at product or feature level — no code implementation.4---56# Building Product Specifications78## Overview910Writes 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](references/spec-contract.md) is shared plumbing. Works wherever the agent can read and write repository files.1112## Agent workflow1314Follow this skill when creating or amending product specification markdown. Stop without application code unless the user explicitly asks in the same message.1516**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](references/spec-contract.md) → **Resolve docs root**.1718Match one **Recipes** row; open exactly that reference. Each create recipe also covers amend when the target file already exists.1920### Recipes2122| Intent | Example phrasing | Read |23| --- | --- | --- |24| PRD | "Draft a PRD", "Update the product requirements" | [creating-prd.md](references/creating-prd.md) |25| FRD | "Write an FRD for checkout", "Amend the checkout FRD" | [creating-frd.md](references/creating-frd.md) |26| User story | "User stories for checkout", "Product user journeys" | [creating-user-story.md](references/creating-user-story.md) |27| TRD | "Technical design for checkout", "System architecture TRD" | [creating-trd.md](references/creating-trd.md) |28| UI specs | "UI specs for checkout", "Screen flow and structure", "View states for checkout" | [creating-ui-specs.md](references/creating-ui-specs.md) |2930## Reference index3132### Contract3334[spec-contract.md](references/spec-contract.md) — resolve root, layout, frontmatter, tiers, hub sync, create-or-amend.3536| Doc | When to use |37| --- | --- |38| [spec-contract.md](references/spec-contract.md) | Docs root marker, paths, frontmatter, tiers, hub sync, create-or-amend |39| [creating-prd.md](references/creating-prd.md) | New or amend `prd.md` |40| [creating-frd.md](references/creating-frd.md) | New or amend `features/<slug>/frd.md` |41| [creating-user-story.md](references/creating-user-story.md) | New or amend product or feature `user-story.md` |42| [creating-trd.md](references/creating-trd.md) | New or amend product or feature `trd.md` |43| [creating-ui-specs.md](references/creating-ui-specs.md) | New or amend product or feature `ui-specs.md` (flow, structure, view states) |4445## Templates4647- [`assets/index.md`](assets/index.md)48- [`assets/prd.md`](assets/prd.md)49- [`assets/frd.md`](assets/frd.md)50- [`assets/trd.md`](assets/trd.md)51- [`assets/user-story.md`](assets/user-story.md)52- [`assets/ui-specs.md`](assets/ui-specs.md)
cedmandocdoc