prd

To generate a markdown product requirements document, provide a feature name and problem context. The skill drafts a comprehensive PRD structure in the __docs/prd directory, automatically splitting the content into an index file and per-feature sub-files for readability.

Yes, you can split a large PRD into multiple markdown files for parallel editing. The skill enforces a multi-file PRD structure, creating an index file alongside separate feature-specific files like overview.md, functional-reqs.md, and acceptance-criteria.md to enable concurrent collaboration.

A structured PRD for stakeholders should include a problem statement, goals, non-goals, functional requirements, acceptance criteria, non-functional requirements, success metrics, milestones, and sprint contracts. The skill uses a template to enforce this complete PRD skeleton consistently.

You do not need to manually provide a template file to automate PRD documentation. The skill internally references a template at references/template.md to derive the feature name and structure, generating the index file frontmatter and organizing the documentation automatically.

The best way to organize sprint contracts and milestones in PRD markdown files is by structuring them within a dedicated feature directory. The skill outputs an index file at __docs/prd/<feature-name>.md and uses sub-files to maintain traceability for milestones and sprint contracts.

Your generated PRD includes an index file and separate feature sub-files to ensure traceability and accessibility for stakeholders. This multi-file PRD structure organizes functional requirements and acceptance criteria into distinct markdown documents, enabling parallel editing and better content readability.