What problem does it solve?
It helps you convert vague product ideas and stakeholder needs into decision-ready PRDs, user stories with acceptance criteria, prioritization work, and roadmaps.
Core Features & Use Cases
- PRD formatting that matches context: Chooses an appropriate PRD style (e.g., Amazon PR/FAQ, Intercom Intermission, or Linear-style spec) based on team size, culture, and the decision the document must enable.
- Stakeholder alignment upfront: Builds a DACI (Driver/Approver/Contributors/Informed) matrix to clarify accountability and sign-off.
- Prioritization and planning tools: Applies RICE, WSJF, and Kano thinking to make tradeoffs explicit, then outputs a roadmap using the Now/Next/Later structure.
- Acceptance criteria you can execute: Writes requirements in Gherkin (Given/When/Then) so the outcomes are testable.
Example use case: You’re iterating on an existing feature and need cross-functional alignment with Engineering and Design; use the intake questions, select a PRD format, and produce a roadmap with prioritized initiatives and Gherkin acceptance criteria.
Quick Start
Use the product-manager skill to generate a PRD by asking the intake questions for product stage, team culture, the decision it must enable, the audience, and whether you need competitive context.
