pm-write-spec

To generate a PRD from a feature idea, provide a problem statement to receive a structured feature specification including goals, non-goals, user stories, categorized requirements, and acceptance criteria. This clarifies scope and implementation-ready details for your team.

A feature specification should include a problem statement, goals, non-goals, categorized requirements with acceptance criteria, success metrics, and timeline considerations. Organizing requirements into Must-Have (P0), Nice-to-Have (P1), and Future (P2) ensures decision-friendly scoping.

Breaking down a large feature request involves converting the overarching idea into a PRD with categorized requirements and acceptance criteria. This process structures the ask into phased, testable delivery plans by defining clear non-goals and timeline considerations.

Yes, you can use Linear, Notion, and Figma context when scoping user stories. The specification generation process pulls related requirements and artifacts from these connected tools to provide context-driven scoping for your product discovery.

Defining success metrics and non-goals for product scoping requires starting with a user problem statement. The generated PRD explicitly separates goals from non-goals and establishes measurable success metrics to align engineering and stakeholder execution.