generate-prd

Drafting a product requirements document with clear acceptance criteria is handled through guided interactive Q&A and a 100-point rubric, which resolves requirement gaps before generating structured, testable PRD prose.

The 100-point rubric in product management documentation is a quality-scoring mechanism that enforces completeness and testability in PRDs, ensuring structured templates, decision logging, and repeatable quality control.

Yes, interactive Q&A resolves gaps before finalizing a PRD by iteratively asking clarifying questions, aligning stakeholder inputs, and ensuring requirements are fully defined before document generation.

Yes, generate-prd saves finished requirements documents to a local plan store by persisting the finalized PRD as a .prd.md file in a local directory such as ~/.cursor/plans/ to ensure traceability.

The best way to ensure traceability in product requirements documents is to enforce structured templates with decision logging and persist finalized files to a local plan store as .prd.md files, creating a repeatable quality control process.

You need a rubric-driven PRD template instead of a standard document when product development requires clear requirements, stakeholder alignment, and testable acceptance criteria to avoid time-consuming, error-prone drafting gaps.