write-a-prd

You can create a product requirements document by running a guided interview to capture needs, scanning the codebase for context, and generating a template-driven PRD saved as a markdown file. This process validates scope and aligns modular design with business goals.

A template-driven PRD enforces a standardized documentation structure by extracting repository context to validate dependencies and scope. It maps interview-derived requirements to high-level module designs, outputting a structured markdown file for feature planning.

To draft a PRD for a new feature, execute the skill to start an interactive interview, allow it to explore your codebase, and outline modules. It automatically persists the resulting requirements document to docs/prd/<name>.md in your repository.

Yes, this approach works for validating scope and modular design planning by combining user constraints from interviews with automatic repository extraction. It generates high-level module sketches and interfaces that map directly to validated business requirements.

Yes, you can generate a PRD without manual formatting because the skill enforces a template-driven structure automatically. It captures interview-derived requirements and codebase insights, saving the finalized document directly to your repository's docs folder.

You should avoid an automated PRD generator when your software project lacks an accessible codebase for context extraction or when feature ideation requires no modular design planning. It is designed for capturing interview-derived requirements and validating dependencies within a repository.