PD Phase 5: specs¶
Deprecated
This phase has been removed from the product design workflow (SPEC-073). Spec generation is now handled by /vt-c-specs-from-prd, which generates implementation specs directly from the PRD.
The /vt-c-pd-5-specs command still works but redirects to /vt-c-specs-from-prd.
New workflow: /vt-c-pd-4-validate → /vt-c-pd-6-handoff → /vt-c-specs-from-prd → /vt-c-activate
Break the PRD into implementation-sized feature briefs (specs) for development handoff.
Command: /vt-c-pd-5-specs [--prd PATH | --feature NAME] (deprecated — use /vt-c-specs-from-prd instead)
When to use¶
After the prototype is validated. specs bridge the gap between a broad PRD and actionable development work. Each specs is sized for 1-2 sprints and follows a SpecKit-compatible format.
What happens¶
- PRD delta review -- Checks
03-PRD/PRD-DELTA.mdfor accumulated requirement changes from prototyping and validation. Offers to incorporate them into the PRD before generating specs. - PRD and PID loading -- Reads the full PRD and PID for features, priorities, tech stack, and constraints.
- Feature scope analysis -- Assesses complexity, identifies shared components, determines feature boundaries, and maps each feature to prototype sections.
- spec-0 generation -- Creates the project setup spec covering tech stack, shared components, CI/CD, and database schema.
- Feature specs generation -- For each PRD feature, creates a specs file with metadata (SPEC ID, parent PRD, prototype link, dependencies), user stories, acceptance criteria, technical specifications, and API endpoints.
- PRD update -- Populates the FB-Link column in PRD Section 4 to link each feature to its specs file.
Output¶
05-specs/spec-0-project-setup.md05-specs/spec-N-[feature-name].mdfor each feature- Updated PRD Section 4 with FB-Link column populated
- Dependency map between specs files
Quality gate¶
- All PRD features have corresponding specs
- Acceptance criteria defined for each
- SpecKit-compatible YAML frontmatter present
- Dependencies between specs mapped