// PM Agent Team - Automated product discovery, strategy, and PRD generation. Runs PM analysis workflow to produce comprehensive PRD before PDCA Plan phase. Triggers: pm team, product discovery, PM analysis, PM 분석, 제품 기획, PMチーム, PM分析, 产品分析, PM-Analyse, PM análisis, analyse PM, analisi PM
View and change bkit automation settings. Shows current automation level, feature flags, trust score, and guardrail configuration. Use proactively when user asks about automation settings, trust level, or guardrails. Triggers: control, automation, settings, level, guardrail, trust, 제어, 자동화, 설정, 레벨, 가드레일, 신뢰도, 制御, 自動化, 設定, レベル, ガードレール, 控制, 自动化, 设置, 级别, 护栏, control, automatización, configuración, nivel, contrôle, automatisation, paramètres, niveau, Kontrolle, Automatisierung, Einstellungen, Stufe, controllo, automazione, impostazioni, livello Do NOT use for: deployment (use /deploy), code changes
Process multiple features or tasks in parallel. Batch execution of PDCA commands across features. Triggers: batch, parallel, bulk, multiple features, 배치, 병렬, 대량 처리, バッチ, 並列, 一括処理, 批量, 并行, 批处理, lote, paralelo, procesamiento masivo, lot, parallèle, traitement en masse, Stapel, parallel, Massenverarbeitung, batch, parallelo, elaborazione di massa
Run a prompt or command on a recurring interval. Useful for monitoring, polling, or periodic checks. Triggers: loop, recurring, interval, monitor, poll, cron, 반복, 주기적, 모니터링, ループ, 定期的, 監視, 循环, 定期, 监控, bucle, intervalo, monitorear, boucle, intervalle, surveiller, Schleife, Intervall, überwachen, ciclo, intervallo, monitorare
Install bkit output styles to your project or user directory. Copies output style files from bkit plugin to the appropriate location. Triggers: output style setup, install output style, setup style, 아웃풋 스타일 설치, 스타일 설정, 出力スタイル設定, スタイルインストール, 输出样式安装, 样式设置, instalar estilo, configurar estilo, installer le style, configurer le style, Stil installieren, Stil einrichten, installare stile, configurare stile
Plan Plus — Brainstorming-Enhanced PDCA Planning. Combines intent discovery from brainstorming methodology with PDCA's structured planning. Produces higher-quality Plan documents by exploring user intent, comparing alternatives, and validating incrementally. Triggers: plan-plus, brainstorm plan, enhanced plan, deep plan, 플랜플러스, 브레인스토밍, 심층 기획, プランプラス, ブレインストーミング, 深度计划, 头脑风暴, plan plus, planificación avanzada, plan plus, planification avancée, Plan Plus, erweiterte Planung, plan plus, pianificazione avanzata
Review changed code for reuse, quality, and efficiency, then fix any issues found. Use after PDCA Check >= 90% or when code review is needed. Triggers: simplify, clean code, refactor, reduce complexity, 간소화, 코드 정리, リファクタリング, コード整理, 简化, 代码清理, simplificar, simplifier, vereinfachen, semplificare
| name | pm-discovery |
| classification | H |
| description | PM Agent Team - Automated product discovery, strategy, and PRD generation. Runs PM analysis workflow to produce comprehensive PRD before PDCA Plan phase. Triggers: pm team, product discovery, PM analysis, PM 분석, 제품 기획, PMチーム, PM分析, 产品分析, PM-Analyse, PM análisis, analyse PM, analisi PM |
| user-invocable | false |
| allowed-tools | ["read_file","write_file","replace","glob","grep_search","google_web_search","web_fetch","tracker_create_task","tracker_update_task","tracker_list_tasks"] |
| agents | {"discovery":"pm-discovery","strategy":"pm-strategy","research":"pm-research","prd":"pm-prd","lead":"pm-lead"} |
| context | session |
| memory | project |
Automated product discovery, strategy analysis, and PRD generation. Produces a comprehensive PRD before the PDCA Plan phase begins.
The PM Agent Team applies 8 professional product management frameworks to systematically analyze a feature before implementation begins. This ensures that development is grounded in validated strategy rather than assumptions.
The following frameworks are applied across the 4-phase workflow:
| # | Framework | Phase | Purpose |
|---|---|---|---|
| 1 | Opportunity Solution Tree (OST) | Discovery | Map problem space systematically |
| 2 | Teresa Torres' Continuous Discovery | Discovery | Evidence-based opportunity identification |
| 3 | JTBD 6-Part Value Proposition | Strategy | Define who, why, and what progress |
| 4 | Lean Canvas | Strategy | Validate business model viability |
| 5 | User Personas (JTBD-based) | Research | Humanize target segments |
| 6 | Competitor Analysis Matrix | Research | Identify differentiation opportunities |
| 7 | TAM/SAM/SOM Dual Validation | Research | Size the market with confidence |
| 8 | Beachhead Segment + GTM (Moore) | PRD | Define go-to-market strategy |
Phase 1: Discovery (OST)
Desired Outcome → Opportunities → Solutions → Experiments
│
Phase 2: Strategy (VP + Lean Canvas)
JTBD 6-Part → Lean Canvas → Key Assumptions
│
Phase 3: Research (Personas + Competitors + Market)
3 Personas → 5 Competitors → TAM/SAM/SOM
│
Phase 4: PRD Synthesis
Beachhead → GTM → 8-Section PRD
│
Output: docs/00-pm/{feature}.prd.md
/pdca pm {feature-name}
This runs the full PM Team workflow for the specified feature and outputs
the PRD to docs/00-pm/{feature-name}.prd.md.
Individual phases can be triggered by mentioning relevant keywords:
The PM Team workflow is a pre-phase that feeds into the PDCA cycle:
PM Team → PRD
↓
PDCA Plan → references PRD for requirements
↓
PDCA Design → translates PRD into technical design
↓
PDCA Do → implements the design
↓
PDCA Check → verifies implementation against design
↓
PDCA Act → iterates until quality threshold met
After the PRD is generated, the PM lead agent guides the user to:
/pdca plan {feature} to begin the implementation cycledocs/
00-pm/
{feature}.prd.md # Complete PRD with all 4 phases
The PRD includes all analysis outputs in a single consolidated document:
| Agent | Role | Model | Temp |
|---|---|---|---|
| pm-lead | Orchestrates 4-phase workflow | gemini-3.1-pro | 0.3 |
| pm-discovery | OST analysis | gemini-3.1-pro | 0.5 |
| pm-strategy | JTBD + Lean Canvas | gemini-3.1-pro | 0.4 |
| pm-research | Personas + Competitors + Market | gemini-3.1-pro | 0.4 |
| pm-prd | PRD synthesis + Beachhead + GTM | gemini-3.1-pro | 0.3 |