dev-prd

What problem does it solve?

Transforms a high-level product vision into a structured, actionable Product Requirements Document so teams can move from concept to development with clear scope, priorities, and measurable requirements. It reduces ambiguity around features, priorities, timelines, and non-functional constraints that typically slow down phase handoffs.

Core Features & Use Cases

• Automated PRD generation: Reads the vision and status files, consolidates personas, epics, functional and non-functional requirements, and outputs a single PRD file.
• Prioritization and planning: Produces MoSCoW prioritization, a 3–6 milestone timeline, and risk/mitigation sections to support roadmap and sprint planning.
• Operational integration: Writes specs/02-prd.md (800–1200 words), updates specs/_status.md to mark Phase 2 as completed, and appends a changelog entry; supports a --auto mode to skip interactive prompts.
• Use case: A PM running phase 2 of a Spec-Driven Development pipeline needs a complete PRD from the vision file with personas, prioritized features, and measurable NFRs to hand off to design and engineering.

Quick Start

Use dev-prd to generate a complete PRD from the current specs/01-vision.md and write the result to specs/02-prd.md.