Stats
Actions
Available In
Tags
Plugin
product-playbook
Plan, strategize, and document product features using structured PM frameworks — from quick JTBD discovery and MVP scoping to full PRD generation and dev handoff packages (CLAUDE.md, TASKS.md, ARCHITECTURE.md, PRD.md). Includes adversarial review agents that stress-test decisions before development begins.
What's Inside
Slash Commands8
Product Build
/product-build
Build Mode — Problem is known, skip Discovery, go straight to solution design and MVP planning
Product Dev
/product-dev
Generate Dev Handoff Package — Produces CLAUDE.md + TASKS.md + TICKETS.md + ARCHITECTURE.md + setup.sh, ready to start development in Claude Code
Product Feature
/product-feature
Feature Extension Mode — Add a single feature to an existing product in 4 streamlined steps
Product Full
/product-full
Full Mode Product Planning — Run 8 Core + up to 3 Optional steps (8–11 total) across the most relevant frameworks, producing deliverable planning documents
Product Prd
/product-prd
Generate PRD Engineering Package — Integrates PR-FAQ + MVP + User Story + Pre-mortem, including flowcharts, DB Schema, and UI Wireframes
Agents3
discovery-specialist
/discovery-specialist
PROACTIVELY use this subagent whenever the Product Playbook planning flow enters Discovery-related steps — Persona, JTBD (Jobs to Be Done), Opportunity Solution Tree (OST), User Journey Map, or Continuous Discovery. The specialist focuses exclusively on understanding users and their unmet needs, with deliberately no awareness of downstream frameworks like RICE, MVP, PRD, or GTM. Use it inside Full Mode S2-S6, Revision Mode S2-S4, Build Mode S2 (problem clarification), and Custom Mode whenever any discovery step is selected. The orchestrator should pass the user's product description, target audience, and any uploaded research materials. Reply in the same language as the orchestrator (English / 繁體中文 / 简体中文 / 日本語 / Español / 한국어).
pre-mortem-runner
/pre-mortem-runner
PROACTIVELY use this subagent whenever the Product Playbook flow reaches a Pre-mortem step — Full Mode S10 (after MVP scoping), Build Mode S4 (architecture-grounded risk), Revision Mode S8, and any Custom Mode flow that includes Pre-mortem. Also use whenever the user says "what could go wrong", "pre-mortem this", "find the failure modes", or asks for risk analysis on a product, feature, or strategy. The runner imagines the product has failed and works backwards to find why — 15+ failure scenarios with leading indicators, ranked by likelihood and impact. Reply in the same language as the orchestrator.
strategy-critic
/strategy-critic
PROACTIVELY use this subagent immediately after the user writes or revises any strategy artifact in the Product Playbook flow — Strategy Blocks (mission/vision/strategy hierarchy), Rumelt's Good Strategy Kernel (diagnosis / guiding policy / coherent action), DHM Model (Delight/Hard-to-copy/Margin-enhancing), or Empowered Teams charter (Marty Cagan). The critic exists to dismantle bad strategy before it propagates downstream. Trigger this in Full Mode S7-S9, Revision Mode S6-S7, and Custom Mode whenever a strategy framework is selected. Pass the strategy artifact verbatim. The critic will return a structured critique — no rewrites. Reply in the same language as the orchestrator.
Stats
Version1.2.12
Released
LanguagePython
Stars19
Copy clicks1
MaintenanceExcellent
LicenseMIT
Last Commit
Added
Available In
Safety Signals
Caution
Modifies files
Hook triggers on file write and edit operations
Tags
Technologies
Categories
