PM Playbook

The problem

Vague product requirements lead to scope creep and missed deadlines. Product managers often struggle to quantify the impact of features or clearly communicate the trade-offs of their roadmap decisions.

What it does

• Evaluates new ideas using a weighted Market Pull Score to determine if a concept is worth pursuing.
• Generates concise, one-page PRDs that explicitly define scope fences and success metrics.
• Sequences roadmaps using a value-minus-effort calculation across Now, Next, and Later horizons.
• Constructs go-to-market plans focused on beachhead audiences and message spines.
• Builds post-launch signal dashboards to track retention, churn, and North Star metrics.

Why this beats prompting it yourself

General LLM prompts often produce "fluff" or generic business speak. This skill enforces a strict output discipline that requires every response to state assumptions, use concrete numbers, and name specific trade-offs, ensuring rigorous thinking rather than just text generation.

Use cases

• Writing a tight PRD for a new mobile search feature with clear in/out scope boundaries.
• Scoring three competing product ideas to see which one clears the Market Pull threshold.
• Planning a quarterly roadmap that accounts for team capacity and dependency webs.
• Designing a go-to-market strategy for a niche beachhead audience.

Known limitations

Requires a local Python environment to run the PRD scaffolding script. The PRD framework is strictly limited to one-page outputs.