prd

To create a product requirements document, invoke the guided discovery loop to gather requirements and automatically pass them through four role-based critics for structured critique. This ensures requirements are refined and aligned across teams before finalizing the PRD.

PRD lifecycle management is a centralized process that orchestrates creation, syncing, and amending of product requirements. It handles versioning by maintaining versioned artifacts with frontmatter metadata and tracking changes through an amendment log and decisions log.

To amend existing product requirements after implementation discoveries, use the dedicated amender component to update the document and automatically maintain an amendment log. This keeps the PRD synchronized with actual development findings while preserving version history.

Yes, you can sync PRDs to spec groups to maintain cross-team alignment and discover integration surfaces. This seamless spec-group linking ensures consistent governance and connects product requirements directly to downstream spec workflows.

No specific dependencies or external components are required to run this PRD workflow. It operates independently with a built-in writer, four critics, and an amender, enforcing a structured state machine and frontmatter metadata without external tool integrations.