/vt-d-specs-from-prd

Break down a PRD into implementation-sized feature briefs (specs) for development handoff

Plugin: vt-product-dev
Usage: /vt-d-specs-from-prd

---

/vt-d-specs-from-prd

Generate specs (feature briefs) from an approved PRD document.

Usage

/vt-d-specs-from-prd                 # Process PRD in current project
/vt-d-specs-from-prd --prd PATH      # Process specific PRD file
/vt-d-specs-from-prd --feature NAME  # Generate single feature brief

What It Does

1. Reads PRD.md and analyzes feature scope
2. Reads PID.md for technical constraints
3. Generates spec-0 (Project Setup):
4. Links to parent PRD
5. Tech stack from PID
6. Shared components and CI/CD
7. Generates spec-N for each feature:
8. Feature name and scope
9. User stories (from PRD)
10. Testable acceptance criteria
11. Prototype links (if exists)
12. Dependencies mapping
13. SpecKit-compatible format
14. Saves to [Project]/05-specs/

specs = SpecKit Bridge

specs are designed to bridge Knowledge Work to Development: - Each specs can be used directly as a SpecKit spec - Development team copies specs to specs/[N]-feature/spec.md - Run /vt-d-2-plan to start implementation

Output Structure

05-specs/
├── spec-0-project-setup.md
├── spec-1-feature-name.md
├── spec-2-feature-name.md
└── ...

Execution

Invoke the kw-specs skill: → Load skill from skills/vt-d-specs-from-prd/SKILL.md