product-playbook

Plan products or features using 22 PM frameworks across six execution modes.

24|1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/Kaminoikari/product-playbook --skill product-playbook
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-playbook
Source: https://github.com/Kaminoikari/product-playbook/tree/main
Command: npx skills add https://github.com/Kaminoikari/product-playbook --skill product-playbook

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Plan and strategize a product or feature using a structured suite of PM frameworks. This Skill provides a guided, multi-step approach to translate ideas into concrete plans, aligning stakeholders and enabling smooth handoffs from discovery to development.

Core Features & Use Cases

  • Six execution modes (Quick, Full, Revision, Build, Custom, Feature Extension) to fit different timelines and risk profiles.
  • 22 product management frameworks (JTBD, OST, PR-FAQ, North Star, etc.) spanning Discovery → Define → Develop → Deliver.
  • Change propagation engine that auto-updates downstream outputs when upstream assumptions or decisions change.
  • Smart file import/export and Dev handoff outputs to streamline documentation and handoffs to Claude Code.
  • Multi-format outputs (HTML reports, PDFs, DOCX, PPTX) and cross-session context persistence via .product-context.md.
  • Slash commands for Claude Code and natural-language prompts to drive the planning flow.
  • Built-in security considerations and risk assessment integrated into the handoff and documentation workflow.

Quick Start

Trigger the flow with a simple natural-language prompt: "I want to plan a product."

Frequently Asked Questions about product-playbook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a product using structured PM frameworks?

Product planning with PM frameworks involves using a structured suite of tools like JTBD, PR-FAQ, and North Star to translate ideas into concrete plans. This approach guides you through Discovery, Define, Develop, and Deliver stages to align stakeholders and enable smooth development handoffs.

What is the best way to structure product management handoff documentation?

Product management handoff documentation is best structured using smart document import/export and Dev handoff outputs. Generating multi-format reports like HTML, PDF, DOCX, and PPTX ensures development teams receive clear, actionable context directly from the planning phase.

Can I use JTBD and North Star frameworks together for feature planning?

JTBD and North Star frameworks can be used together for feature planning through a structured PM suite. Combining these 22 product management frameworks spans the entire product lifecycle, ensuring strategic alignment from initial discovery through final delivery.

How do you propagate changes across product planning documents?

Change propagation across product planning documents is handled by an auto-updating engine that modifies downstream outputs when upstream assumptions or decisions change. This ensures all framework artifacts remain consistent without requiring manual updates across separate files.

Does product planning with PR-FAQ work for both new products and feature extensions?

Product planning with PR-FAQ works for both new products and feature extensions by utilizing distinct execution modes. Six modes, including Quick, Full, Revision, Build, and Feature Extension, fit different timelines and risk profiles for comprehensive product strategy.

How do I maintain product context across multiple planning sessions?

Maintaining product context across multiple planning sessions requires cross-session context persistence. Saving state via a local context file allows you to pause and resume structured framework workflows without losing prior assumptions or strategic decisions.