pm-prd

To write a PRD from a feature idea, provide a brief description to generate a structured draft with required sections like Problem, Appetite, and Solution to align stakeholders. This reduces ambiguity by converting fuzzy concepts into formal requirements.

A falsification section in a product requirement document defines specific criteria to test and prove the feature concept wrong. It ensures testability and supports adversarial gating during the review process to validate product bets before development.

Yes, you can generate a Shape Up style pitch for software teams. The workflow supports standard PRD formats and Shape Up pitches, producing structured markdown files with frontmatter metadata and defined scope for startups and product organizations.

To define acceptance criteria and scope for a pitch, the system applies phase-driven guidance including clarifying questions and user research pull. This ensures the final write produces clear bets and strict boundaries for handoff.

The best way to structure roadmaps into formal product specs is to use a repeatable template that enforces required sections like Falsification, Scope, and Requirements. This generates a ready-for-handoff markdown file with proper frontmatter metadata.

Yes, you need prior context before drafting product requirement documents. The workflow uses a phase-driven approach that gathers user research and asks clarifying questions to ensure completeness and testability before generating the final PRD draft.