prd-writing

Drafting a PRD from initial requirements involves reading your ideas from docs/ideas/initial-requirements.md and applying a provided template. This ensures the final PRD conforms to standard structure, enforces frontmatter, and saves directly to docs/product-requirements.md.

When a PRD already exists at docs/product-requirements.md, you can update it by incorporating the existing structure while integrating new requirements. This maintains documentation hygiene and preserves the original document alignment.

The standard structure for a product requirements document requires specific frontmatter and a template-driven format covering product vision, scope, success criteria, and milestones. The finalized PRD is saved as docs/product-requirements.md.

Yes, you need initial requirements saved as a file before drafting a PRD. The workflow specifically reads scattered product ideas from docs/ideas/initial-requirements.md to synthesize them into the formal PRD template.

The best way to ensure PRD alignment with project documentation is to use a template-driven output that enforces linking to initial requirements. This maintains documentation hygiene and preserves existing structure when updating the docs/product-requirements.md file.