What problem does it solve?
Creates a complete, traceable Product Requirements Document (PRD) through a disciplined, facilitator-led workflow that prevents ad-hoc drafting, lost context, and incomplete requirements. It enforces sequential step execution, just-in-time loading of step files, and explicit state tracking so teams do not skip critical discovery, validation, or compliance checks.
Core Features & Use Cases
- Step-file guided workflow: A strict sequence of step files (initialization, discovery, vision, executive summary, success criteria, journeys, domain, innovation, project-type, scoping, functional and non-functional requirements, polish, completion) that must be read and followed exactly.
- Stateful, append-only document building: Initializes a PRD from a template, tracks progress via frontmatter (stepsCompleted, inputDocuments), and appends validated content only with user approval.
- Discovery & classification tools: Supports document discovery, CSV-driven classification (project-types and domain-complexity), optional domain deep-dive and innovation exploration, and project-type-specific requirements.
- Use Case: A product manager starting a new PRD or resuming an incomplete one uses the skill to run structured discovery, draft the executive summary, derive success criteria, map journeys, synthesize FRs/NFRs, and produce a polished PRD ready for downstream work.
Quick Start
Ask the skill to create a new PRD by saying: Create a new PRD for Project X and follow the guided workflow.