Menu
Use during discuss-slice to synthesize conversation context into a formal PRD with user stories, implementation decisions, testing decisions, and exclusions.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when reviewing architecture decisions. C4 model, dependency inversion, hexagonal boundaries.
Use during discuss-slice and plan-slice to stress-test a spec or plan against domain vocabulary before approval.
Use during research-slice to build disposable experiments that answer technical uncertainty.
Use during project:init to scaffold repo-level agent configuration (CLAUDE.md, AGENTS.md, tracker labels).
Use when debugging. 4-phase investigation, root cause, minimal fix.
Use when implementing features/fixes. Iron law: ยฌโ production code without failing test.
| name | to-prd |
| description | Use during discuss-slice to synthesize conversation context into a formal PRD with user stories, implementation decisions, testing decisions, and exclusions. |
| version | 1.0.0 |
| tags | ["process","planning"] |
During discuss-slice, after the user has described the problem and the agent has explored the codebase. Synthesizes conversation context into a formal requirements document without further interrogation of the user.
Turn the current conversation context into a product requirements document scoped to the slice under discussion.
Grasp the repository's present condition:
CONTEXT.md or DOMAIN.mdIdentify principal components requiring creation or alteration. Prioritize "deep modules" โ units that encapsulate a lot of functionality in a simple, testable interface which rarely changes. Validate these components with the user and confirm where unit verification is desired.
Produce a PRD with the following sections:
Save the PRD as SPEC.md in the slice directory. Mark it as ready for planning.