prd-to-spec
Transform a PRD into a technical SPEC document — architecture, API design, data model, error handling, and implementation contracts. Triggers on: prd-to-spec, prd to spec, prd转spec, 需求转设计, 需求转规格, generate spec from prd, design from prd, 技术方案, 设计方案.
Profile →npx skills add smallnest/goal-workflow --skill prd-to-spec --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# prd-to-spec — PRD to Technical Specification Transform a Product Requirements Document (PRD) into a detailed technical SPEC that an engineer or AI agent can implement against. The PRD says *what* to build; the SPEC says *how* to build it. --- ## When to Use - A `/prd` has been generated and you need to bridge the gap to implementation - You want architecture decisions documented before coding starts - Multiple developers/agents will implement the feature and need a shared contract - You need to validate technical feasibility before committing to a PRD - You want to catch design issues early — before code is written --- ## The Job 1. **Locate PRD** — find or receive the PRD document 2. **Analyze context (optional)** — if a codebase exists, scan it to understand current architecture, patterns, and constraints 3. **Ask clarifying questions** — resolve technical ambiguities (max 3-5 questions) 4. **Generate SPEC** — produce a structured technical specification 5. **Review** — present to user for feedback and iteration 6. **Save** — write final SPEC to agreed location --- ## Step 1: Locate PRD Find the input PRD in one of these ways: ``` Provide the PRD to convert: A. File path (e.g.,
- When to Use
- The Job
- Step 1: Locate PRD
- Step 2: Analyze Context (Optional)
- Step 3: Clarifying Questions
- Step 4: SPEC Document Structure
- Step 5: Review & Iteration
- Step 6: Save
- Mapping Strategy: PRD → SPEC
- Quality Criteria
- Edge Cases & Fallback
- Anti-Patterns to Avoid
- Relationship to Other Skills
What does the prd-to-spec skill do?
Transform a PRD into a technical SPEC document — architecture, API design, data model, error handling, and implementation contracts. Triggers on: prd-to-spec, prd to spec, prd转spec, 需求转设计, 需求转规格, generate spec from prd, design from prd, 技术方案, 设计方案.
How do I install it?
Run `npx skills add smallnest/goal-workflow --skill prd-to-spec --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From smallnest/goal-workflow, a repository with 199 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.