harness-prd

To create a product requirements document with an auditable decision log, provide your product idea, target users, and rigor level to generate a structured PRD featuring stable FR IDs and a decision-log skeleton.

You can validate a PRD without rewriting by running it against a quality rubric, which produces a consolidated validation report with severity-ranked findings rather than modifying the original text.

To update an existing PRD and check for stakeholder alignment conflicts, input your change signal to extract modifications and automatically surface conflicts against prior decisions logged in the document.

You should specify hobby, internal, or launch rigor levels when drafting product requirements, which dictates the validation depth, stakeholder alignment strictness, and evidence required for your elicitation and authoring process.

You need a rubric-driven reviewer gate for product requirements when finalizing a document for launch, ensuring testable outcomes, glossary discipline, and YAML-frontmatter metadata meet quality standards before approval.

Yes, you can use elicitation to extract product requirements and evidence from rough ideas before authoring, establishing a structured discovery-to-finalize synthesis that feeds into the final PRD output.