To Spec (ex To PRD, Claude Code skill)
Synthesises the current conversation into a PRD ready to publish to your issue tracker. The skill does NOT interview you (that's the job of /grill-me or /grill-with-docs upstream), it synthesises what Claude already knows. Sketches the modules to build, identifies 'deep modules' (simple interfaces, heavy encapsulated logic, testable in isolation), and asks you to validate which modules deserve tests. Output: a PRD using a strict template (Problem Statement, Solution, numbered User Stories, Implementation Decisions, Testing Decisions, Out of Scope) published to the issue tracker with `needs-triage` label.
Strengths
- No redundant interview: the skill consumes the conversational context already acquired (ideal after /grill-me)
- 'Deep module' concept built into the template, pushes towards testable interfaces
- Numbered and exhaustive user stories by default, no rushed "as a user I want X"
- Mandatory 'Out of Scope' section, clarifies what is NOT in the PRD before issue breakdown
Limitations
- Assumes the grilling phase has been done, poor output if context is thin
- Refuses file paths and code snippets in the PRD ('they may end up being outdated very quickly'), can frustrate if you want a very technical PRD
- Publishes directly to the issue tracker, no dry-run mode to review before push
Best for
- PM/PO who want a clean PRD 30 minutes after the scoping session, without having to write it
- Tech leads handling the spec→implementation handoff who want to identify deep modules early
- Teams practising PRD-driven development who want a unified format