Menu
Turn the current conversation into a PRD and write it to docs/prd/ — no interview, just synthesis of what you've already discussed.
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
Review staged/unstaged changes plus commits ahead of origin/main. Produces an HTML report in the OS temp dir, then grills the user with docs on findings.
Disciplined diagnosis loop for hard bugs. Use when the user reports a defect, says "diagnose"/"debug this", describes something broken/throwing/failing/slow, or wants to investigate a misbehavior. Grounds investigation in ADRs and CONTEXT.md so the gap between intended design and observed behavior is always clear. Handles code bugs, sensor-drift bugs, event-misfire bugs, and physical-world noise through a dedicated HITL iteration loop.
Break a plan, spec, or PRD into independently-grabbable implementation slices written as markdown files in docs/issues/ using tracer-bullet vertical slices.
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
| name | to-prd |
| description | Turn the current conversation into a PRD and write it to docs/prd/ — no interview, just synthesis of what you've already discussed. |
| disable-model-invocation | true |
This skill takes the current conversation context and codebase understanding and produces a PRD. Do NOT interview the user — just synthesize what you already know.
Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the PRD, and respect any ADRs in the area you're touching.
Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.
Check with the user that these seams match their expectations.
docs/prd/ as a markdown file. Derive the filename from the title: lowercase, hyphenated slug (e.g. docs/prd/mobile-check-deposit.md). Create the docs/prd/ directory lazily — only when the first PRD is needed.The problem that the user is facing, from the user's perspective.
The solution to the problem, from the user's perspective.
A LONG, numbered list of user stories. Each user story should be in the format of:
This list of user stories should be extremely extensive and cover all aspects of the feature.
A list of implementation decisions that were made. This can include:
Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.
Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it within the relevant decision and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.
A list of testing decisions that were made. Include:
A description of the things that are out of scope for this PRD.
Any further notes about the feature.