product-playbook 1.0.9 → 1.1.1

package/.claude-plugin/marketplace.json

@@ -7,7 +7,7 @@
     {
       "name": "product-playbook",
       "description": "MUST use when user wants to plan or strategize a product/feature. 22 PM frameworks, 6 modes, multi-language, from idea to dev handoff",
-      "version": "1.0.9",
+      "version": "1.1.1",
       "source": "./."
     }
   ]

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "product-playbook",
   "description": "MUST use when user wants to plan or strategize a product/feature. 22 PM frameworks, 6 modes, multi-language, from idea to dev handoff",
-  "version": "1.0.9",
+  "version": "1.1.1",
   "author": {
     "name": "Charles Chen"
   },

package/README.es.md

@@ -182,8 +182,8 @@ product-playbook/
 | Modo | Pasos | Duración | Ideal para |
 |------|-------|----------|-----------|
 | 🚀 **Modo Rápido** | 3 pasos | ~30 min | Validación rápida de ideas, preparación de pitch |
-| 📦 **Modo Completo** | 20 pasos | Varias horas | Planificación de nuevo producto, grandes renovaciones |
-| 🔄 **Modo Revisión** | 12 pasos | 1-2 horas | Iteración sobre productos existentes |
+| 📦 **Modo Completo** | 9–11 pasos (8 Core + 1 Journey Map por defecto ON + 2 Optional por defecto OFF) | 1-2 horas | Planificación de nuevo producto, grandes renovaciones |
+| 🔄 **Modo Revisión** | 6–8 pasos (6 Core + 2 Optional) | <1 hora | Iteración sobre productos existentes |
 | ✏️ **Modo Personalizado** | 4-16 pasos | Variable | Llenar vacíos específicos |
 | ⚡ **Modo Build** | 7 pasos | ~1 hora | El problema es conocido, ir directo a soluciones |
 | 🔧 **Expansión de Funcionalidades** | 4 pasos | ~30 min | Agregar una sola funcionalidad a un producto existente |
@@ -401,7 +401,7 @@ Comparando la calidad de respuesta entre "con guía del Skill" y "sin guía del
 
 - **Hard Gate de Autoevaluación de Calidad** (+100%): Si la IA critica proactivamente su propio output con estándares estrictos, señala brechas y exige mejoras después de completar un entregable — 0% de tasa de aprobación sin el Skill
 - **Context Bootstrap** (+100%): Si la IA recopila información foundacional del producto antes de comenzar a planificar, en lugar de saltar directamente a implementación técnica — completamente omitido sin el Skill
-- **Modo Expansión de Funcionalidades** (+83%): Si la IA reconoce escenarios de "agregar una funcionalidad a un producto existente" y activa un flujo simplificado de 4 pasos en lugar de los 7-12 pasos completos — sin el Skill, salta directamente a soluciones técnicas
+- **Modo Expansión de Funcionalidades** (+83%): Si la IA reconoce escenarios de "agregar una funcionalidad a un producto existente" y activa un flujo simplificado de 4 pasos en lugar de los 6-11 pasos completos — sin el Skill, salta directamente a soluciones técnicas
 - **Integración de Seguridad** (+75%): Si el handoff de desarrollo incluye arquitectura de seguridad, plantillas .gitignore y medidas de seguridad específicas de plataforma — sin el Skill, la seguridad se reduce a una tabla resumen
 
 > Ver [`evals/`](./evals/) para metodología detallada y datos.
@@ -428,7 +428,7 @@ cp -r product-playbook/commands/* ~/.claude/commands/
 | Comando | Descripción |
 |---------|-------------|
 | `/product-quick <descripción>` | Modo Rápido — recorre JTBD → PR-FAQ → North Star en menos de 30 min |
-| `/product-full <descripción>` | Modo Completo — plan de producto completo de 20 pasos |
+| `/product-full <descripción>` | Modo Completo — plan de producto completo (9–11 pasos; Journey Map por defecto ON) |
 | `/product-revision <descripción>` | Modo Revisión — iterar y optimizar un producto existente |
 | `/product-build <descripción>` | Modo Build — omitir Discovery, ir directo a soluciones |
 | `/product-feature <descripción>` | Modo Extensión — añade una funcionalidad a un producto existente (4 pasos) |

package/README.ja.md

@@ -183,8 +183,8 @@ product-playbook/
 | モード | ステップ | 所要時間 | 最適な用途 |
 |------|-------|----------|----------|
 | 🚀 **クイックモード** | 3ステップ | 約30分 | 迅速なアイデア検証、ピッチ準備 |
-| 📦 **フルモード** | 20ステップ | 数時間 | 新プロダクト企画、大規模リニューアル |
-| 🔄 **リビジョンモード** | 12ステップ | 1-2時間 | 既存プロダクトの改善 |
+| 📦 **フルモード** | 9–11ステップ（8 Core + 1 デフォルト ON Journey Map + 2 デフォルト OFF Optional） | 1-2時間 | 新プロダクト企画、大規模リニューアル |
+| 🔄 **リビジョンモード** | 6–8ステップ（6 Core + 2 Optional） | <1時間 | 既存プロダクトの改善 |
 | ✏️ **カスタムモード** | 4-16ステップ | 場合による | 特定のギャップを埋める |
 | ⚡ **ビルドモード** | 7ステップ | 約1時間 | 問題は既知、ソリューションに直行 |
 | 🔧 **機能拡張** | 4ステップ | 約30分 | 既存プロダクトに単一機能を追加 |
@@ -402,7 +402,7 @@ Claude Codeは自動的に：
 
 - **品質セルフチェック ハードゲート**（+100%）：AIが成果物完成後に厳格な基準で自発的に自身の出力を批評し、ギャップを指摘し、改善を求めるかどうか — スキルなしでは合格率0%
 - **Context Bootstrap**（+100%）：AIが企画を始める前に基礎的なプロダクト情報を収集するか、それとも技術的実装にすぐ飛び込むか — スキルなしでは完全にスキップ
-- **機能拡張モード**（+83%）：AIが「既存プロダクトへの機能追加」シナリオを認識し、フルの7-12ステップではなく効率化された4ステップフローを起動するか — スキルなしでは技術ソリューションに直行
+- **機能拡張モード**（+83%）：AIが「既存プロダクトへの機能追加」シナリオを認識し、フルの6-11ステップではなく効率化された4ステップフローを起動するか — スキルなしでは技術ソリューションに直行
 - **セキュリティ統合**（+75%）：開発ハンドオフにセキュリティアーキテクチャ、.gitignoreテンプレート、プラットフォーム固有のセキュリティ対策が含まれるか — スキルなしではセキュリティは単一のサマリー表に縮小
 
 > 詳細な方法論とデータは[`evals/`](./evals/)を参照。
@@ -429,7 +429,7 @@ cp -r product-playbook/commands/* ~/.claude/commands/
 | コマンド | 説明 |
 |---------|-------------|
 | `/product-quick <説明>` | クイックモード — JTBD → PR-FAQ → North Starを30分以内で実行 |
-| `/product-full <説明>` | フルモード — 20ステップの完全なプロダクト企画 |
+| `/product-full <説明>` | フルモード — 完全なプロダクト企画（9–11ステップ；Journey Map デフォルト ON） |
 | `/product-revision <説明>` | リビジョンモード — 既存プロダクトの改善と最適化 |
 | `/product-build <説明>` | ビルドモード — ディスカバリーをスキップ、ソリューションに直行 |
 | `/product-feature <説明>` | 機能拡張モード — 既存プロダクトに単一機能を追加（4ステップ） |

package/README.ko.md

@@ -182,8 +182,8 @@ product-playbook/
 | 모드 | 단계 | 소요 시간 | 적합한 경우 |
 |------|------|---------|-----------|
 | 🚀 **퀵 모드** | 3단계 | ~30분 | 빠른 아이디어 검증, 피칭 준비 |
-| 📦 **풀 모드** | 20단계 | 수 시간 | 신규 제품 기획, 대규모 개편 |
-| 🔄 **리비전 모드** | 12단계 | 1-2시간 | 기존 제품 반복 개선 |
+| 📦 **풀 모드** | 9–11단계 (8 Core + 1 기본 ON Journey Map + 2 기본 OFF Optional) | 1-2시간 | 신규 제품 기획, 대규모 개편 |
+| 🔄 **리비전 모드** | 6–8단계 (6 Core + 2 Optional) | <1시간 | 기존 제품 반복 개선 |
 | ✏️ **커스텀 모드** | 4-16단계 | 다양 | 특정 부분 보완 |
 | ⚡ **빌드 모드** | 7단계 | ~1시간 | 문제가 명확한 경우, 솔루션으로 바로 |
 | 🔧 **기능 확장** | 4단계 | ~30분 | 기존 제품에 단일 기능 추가 |
@@ -401,7 +401,7 @@ Claude Code가 자동으로:
 
 - **품질 자체 점검 하드 게이트** (+100%): AI가 납품물 완성 후 엄격한 기준으로 자체 산출물을 비판하고, 갭을 지적하며, 개선을 요구하는지 여부 — 스킬 없이는 0% 통과율
 - **Context Bootstrap** (+100%): AI가 기획을 시작하기 전에 기초 제품 정보를 수집하는지, 기술 구현으로 바로 뛰어들지 않는지 — 스킬 없이는 완전히 건너뜀
-- **기능 확장 모드** (+83%): AI가 "기존 제품에 기능 추가" 시나리오를 인식하고 전체 7-12단계 대신 간소화된 4단계 플로우를 활성화하는지 — 스킬 없이는 기술 솔루션으로 바로 점프
+- **기능 확장 모드** (+83%): AI가 "기존 제품에 기능 추가" 시나리오를 인식하고 전체 6-11단계 대신 간소화된 4단계 플로우를 활성화하는지 — 스킬 없이는 기술 솔루션으로 바로 점프
 - **보안 통합** (+75%): 개발 핸드오프에 보안 아키텍처, .gitignore 템플릿, 플랫폼별 보안 조치가 포함되는지 — 스킬 없이는 보안이 단일 요약 테이블로 축소
 
 > 상세한 방법론과 데이터는 [`evals/`](./evals/)를 참조하세요.
@@ -428,7 +428,7 @@ cp -r product-playbook/commands/* ~/.claude/commands/
 | 명령 | 설명 |
 |------|------|
 | `/product-quick <설명>` | 퀵 모드 — JTBD → PR-FAQ → North Star를 30분 이내 실행 |
-| `/product-full <설명>` | 풀 모드 — 완전한 20단계 제품 기획 |
+| `/product-full <설명>` | 풀 모드 — 완전한 제품 기획 (9–11단계; Journey Map 기본 ON) |
 | `/product-revision <설명>` | 리비전 모드 — 기존 제품 반복 최적화 |
 | `/product-build <설명>` | 빌드 모드 — 디스커버리 건너뛰고 솔루션으로 바로 |
 | `/product-feature <설명>` | 기능 확장 모드 — 기존 제품에 단일 기능 추가 (4단계) |

package/README.md

@@ -182,8 +182,8 @@ product-playbook/
 | Mode | Steps | Duration | Best for |
 |------|-------|----------|----------|
 | 🚀 **Quick Mode** | 3 steps | ~30 min | Rapid idea validation, pitch prep |
-| 📦 **Full Mode** | 20 steps | Several hours | New product planning, major revamps |
-| 🔄 **Revision Mode** | 12 steps | 1-2 hours | Iterating on existing products |
+| 📦 **Full Mode** | 9–11 steps (8 Core + 1 Default-ON Journey Map + 2 Default-OFF Optionals) | 1-2 hours | New product planning, major revamps |
+| 🔄 **Revision Mode** | 6–8 steps (6 Core + 2 Optional) | <1 hour | Iterating on existing products |
 | ✏️ **Custom Mode** | 4-16 steps | Varies | Filling specific gaps |
 | ⚡ **Build Mode** | 7 steps | ~1 hour | Problem is known, jump to solutions |
 | 🔧 **Feature Expansion** | 4 steps | ~30 min | Adding a single feature to an existing product |
@@ -401,7 +401,7 @@ By comparing response quality between "with Skill guidance" and "without Skill g
 
 - **Quality Self-check Hard Gate** (+100%): Whether the AI proactively critiques its own output with strict standards, flags gaps, and demands improvement after completing a deliverable — 0% pass rate without the Skill
 - **Context Bootstrap** (+100%): Whether the AI collects foundational product information before starting to plan, rather than jumping straight into technical implementation — completely skipped without the Skill
-- **Feature Expansion Mode** (+83%): Whether the AI recognizes "adding a feature to an existing product" scenarios and activates a streamlined 4-step flow instead of the full 7-12 steps — without the Skill, it jumps straight to technical solutions
+- **Feature Expansion Mode** (+83%): Whether the AI recognizes "adding a feature to an existing product" scenarios and activates a streamlined 4-step flow instead of the full 6-11 steps — without the Skill, it jumps straight to technical solutions
 - **Security Integration** (+75%): Whether the dev handoff includes security architecture, .gitignore templates, and platform-specific security measures — without the Skill, security is reduced to a single summary table
 
 > See [`evals/`](./evals/) for detailed methodology and data.
@@ -428,7 +428,7 @@ cp -r product-playbook/commands/* ~/.claude/commands/
 | Command | Description |
 |---------|-------------|
 | `/product-quick <description>` | Quick Mode — run through JTBD → PR-FAQ → North Star in under 30 min |
-| `/product-full <description>` | Full Mode — complete 20-step product plan |
+| `/product-full <description>` | Full Mode — comprehensive plan (9–11 steps; Journey Map default ON) |
 | `/product-revision <description>` | Revision Mode — iterate and optimize an existing product |
 | `/product-build <description>` | Build Mode — skip Discovery, jump straight to solutions |
 | `/product-feature <description>` | Feature Extension — add a single feature to an existing product (4 steps) |

package/README.zh-CN.md

@@ -182,8 +182,8 @@ product-playbook/
 | 模式 | 步骤数 | 耗时 | 适合情境 |
 |------|--------|------|---------|
 | 🚀 **快速模式** | 3 步 | ~30 分钟 | 快速验证想法、准备简报 |
-| 📦 **完整模式** | 20 步 | 数小时 | 新产品规划、重大改版 |
-| 🔄 **改版模式** | 12 步 | 1-2 小时 | 既有产品改版优化 |
+| 📦 **完整模式** | 9–11 步(8 Core + 1 预设启用 Journey Map + 2 预设停用 Optional) | 1-2 小时 | 新产品规划、重大改版 |
+| 🔄 **改版模式** | 6–8 步(6 Core + 2 Optional) | <1 小时 | 既有产品改版优化 |
 | ✏️ **自订模式** | 4-16 步 | 依选择 | 补足特定环节 |
 | ⚡ **直接实作** | 7 步 | ~1 小时 | 问题已知，直接进解法 |
 | 🔧 **功能扩充** | 4 步 | ~30 分钟 | 既有产品加单一功能 |
@@ -401,7 +401,7 @@ Claude Code 会自动：
 
 - **品质自检 Hard Gate**（+100%）：AI 在完成产出后，是否会主动以严格标准批判自己的输出、标记不足并要求改进——无 Skill 时通过率为 0%
 - **Context Bootstrap**（+100%）：首次使用时是否会先收集产品基础资讯再开始规划，而非直接跳入技术实作——无 Skill 时完全跳过此步骤
-- **功能扩充模式**（+83%）：是否能识别「在既有产品上加功能」的场景，启用 4 步精简流程而非完整 7-12 步——无 Skill 时直接输出技术方案
+- **功能扩充模式**(+83%):是否能识别「在既有产品上加功能」的场景,启用 4 步精简流程而非完整 6-11 步——无 Skill 时直接输出技术方案
 - **安全性整合**（+75%）：开发交接包是否包含安全架构、.gitignore 模板、平台特定安全措施——无 Skill 时安全性仅占一个简表
 
 > 详细评测方法与数据见 [`evals/`](./evals/) 目录。
@@ -428,7 +428,7 @@ cp -r product-playbook/commands/* ~/.claude/commands/
 | 指令 | 说明 |
 |------|------|
 | `/product-quick <描述>` | 快速模式 — 30 分钟内跑完 JTBD → PR-FAQ → North Star |
-| `/product-full <描述>` | 完整模式 — 完整 20 步产品企划 |
+| `/product-full <描述>` | 完整模式 — 完整产品企划(9–11 步;Journey Map 预设启用) |
 | `/product-revision <描述>` | 改版模式 — 既有产品改版优化 |
 | `/product-build <描述>` | 直接实作模式 — 跳过 Discovery，直接进解法 |
 | `/product-feature <描述>` | 功能扩展模式 — 在现有产品新增单一功能（4 步） |

package/README.zh-TW.md

@@ -182,8 +182,8 @@ product-playbook/
 | 模式 | 步驟數 | 耗時 | 適合情境 |
 |------|--------|------|---------|
 | 🚀 **快速模式** | 3 步 | ~30 分鐘 | 快速驗證想法、準備簡報 |
-| 📦 **完整模式** | 20 步 | 數小時 | 新產品規劃、重大改版 |
-| 🔄 **改版模式** | 12 步 | 1-2 小時 | 既有產品改版優化 |
+| 📦 **完整模式** | 9–11 步(8 Core + 1 預設啟用 Journey Map + 2 預設停用 Optional) | 1-2 小時 | 新產品規劃、重大改版 |
+| 🔄 **改版模式** | 6–8 步(6 Core + 2 Optional) | <1 小時 | 既有產品改版優化 |
 | ✏️ **自訂模式** | 4-16 步 | 依選擇 | 補足特定環節 |
 | ⚡ **直接實作** | 7 步 | ~1 小時 | 問題已知，直接進解法 |
 | 🔧 **功能擴充** | 4 步 | ~30 分鐘 | 既有產品加單一功能 |
@@ -401,7 +401,7 @@ Claude Code 會自動：
 
 - **品質自檢 Hard Gate**（+100%）：AI 在完成產出後，是否會主動以嚴格標準批判自己的輸出、標記不足並要求改進——無 Skill 時通過率為 0%
 - **Context Bootstrap**（+100%）：首次使用時是否會先收集產品基礎資訊再開始規劃，而非直接跳入技術實作——無 Skill 時完全跳過此步驟
-- **功能擴充模式**（+83%）：是否能識別「在既有產品上加功能」的場景，啟用 4 步精簡流程而非完整 7-12 步——無 Skill 時直接輸出技術方案
+- **功能擴充模式**(+83%):是否能識別「在既有產品上加功能」的場景,啟用 4 步精簡流程而非完整 6-11 步——無 Skill 時直接輸出技術方案
 - **安全性整合**（+75%）：開發交接包是否包含安全架構、.gitignore 模板、平台特定安全措施——無 Skill 時安全性僅佔一個簡表
 
 > 詳細評測方法與數據見 [`evals/`](./evals/) 目錄。
@@ -428,7 +428,7 @@ cp -r product-playbook/commands/* ~/.claude/commands/
 | 指令 | 說明 |
 |------|------|
 | `/product-quick <描述>` | 快速模式 — 30 分鐘內跑完 JTBD → PR-FAQ → North Star |
-| `/product-full <描述>` | 完整模式 — 完整 20 步產品企劃 |
+| `/product-full <描述>` | 完整模式 — 完整產品企劃(9–11 步;Journey Map 預設啟用) |
 | `/product-revision <描述>` | 改版模式 — 既有產品改版優化 |
 | `/product-build <描述>` | 直接實作模式 — 跳過 Discovery，直接進解法 |
 | `/product-feature <描述>` | 功能擴充模式 — 在既有產品新增單一功能（4 步） |

package/SKILL.md

@@ -47,8 +47,8 @@ When the user triggers this skill, use a **progressive confirmation** approach
 Select a mode (enter a number or name), or just tell me about your product and I'll recommend the best mode:
 
 1. 🚀 **Quick Mode** — 3 steps, ~30 min (JTBD → PR-FAQ → North Star)
-2. 📦 **Full Mode** — 20 steps, comprehensive planning document
-3. 🔄 **Revision Mode** — 12 steps, optimize existing product
+2. 📦 **Full Mode** — 9–11 steps (8 Core + 1 Default-ON Journey + 2 Default-OFF Optionals; 8 if flow is too simple to map), comprehensive planning document
+3. 🔄 **Revision Mode** — 6–8 steps (6 Core + 2 Optional), optimize existing product
 4. ✏️ **Custom Mode** — Choose your own framework combination
 5. ⚡ **Build Mode** — 7 steps, skip Discovery, go straight to solution
 6. 🔧 **Feature Extension Mode** — 4 steps, add a feature to existing product
@@ -84,17 +84,17 @@ Who is this plan primarily for?
 | Mode | Description | Fixed Outputs | Best For |
 |------|-------------|---------------|----------|
 | 🚀 **Quick Mode** | Actionable direction in 30 min; three fixed steps, no skipping | ① JTBD Statement ② PR-FAQ ③ North Star Metric | Quick alignment, idea validation, preparing a pitch |
-| 📦 **Full Mode** | Run through all frameworks; produce a deliverable plan | All frameworks (see step sequence) | New product planning, major revamps |
-| 🔄 **Revision Mode** | Optimize an existing product with user data and a feature baseline | Current state analysis → Pain point synthesis → Solution → Validation | Feature revamps, UX optimization, product repositioning |
+| 📦 **Full Mode** | 8 Core + 1 Default-ON Journey Map + 2 Default-OFF Optionals; produces a deliverable plan | Strategy → Persona → **Journey Map (default ON)** → JTBD → Pain+HMW+Ranking → PR-FAQ → Solution Evaluation → MVP → North Star (+ optional Positioning, PMF/GTM/Validation) | New product planning, major revamps |
+| 🔄 **Revision Mode** | 6 Core steps + 2 Optional, baseline-aware | Current state + JTBD re-validation → Pain points → Pain+HMW+Ranking (+optional Positioning) → PR-FAQ (+optional Pre-mortem) → MVP → North Star + Validation | Feature revamps, UX optimization, product repositioning |
 | ✏️ **Custom Mode** | Choose your own framework combination or completeness level | User-specified | Filling in specific gaps |
 | ⚡ **Build Mode** | Skip Discovery, go straight to solutions | PR-FAQ + Pre-mortem + GEM/RICE + MVP + North Star | Problem is known; need fast execution |
 | 🔧 **Feature Extension Mode** | Add a single feature to an existing product; streamlined 4-step flow | Problem + Context → Three parallel solutions + AI recommendation → Risk assessment → Execution scope | Adding features to an existing product; clear feature requirements |
 
 ### 📊 Completeness Levels (Custom Mode only)
 
-**🔴 Low (Lean)**: JTBD Statement → One HMW → PR-FAQ → North Star (any step can be swapped)
-**🟡 Medium (Standard)**: Persona + JTBD → Pain Points + HMW + Positioning → Parallel Solutions + MVP → North Star + PMF + Product Spec Summary
-**🟢 High (Comprehensive)**: Medium + Journey Map + OST + Strategy Blocks + RICE + Pre-mortem + Hypothesis Validation
+**🔴 Low (Lean — 4 steps)**: JTBD Statement → One HMW → PR-FAQ → North Star (any step can be swapped)
+**🟡 Medium (Standard — 8 or 9 steps)**: Persona → **(Journey Map auto-inserted unless flow is too simple)** → JTBD → Pain+HMW+Ranking → Positioning → PR-FAQ → Solution Evaluation → MVP → North Star
+**🟢 High (Comprehensive — 11 steps)**: Standard + Strategy Diagnosis + **Journey Map (bundled with Persona, default ON)** + PMF/GTM/BM/Validation
 
 ### 👥 Target Audience
 
@@ -130,6 +130,23 @@ When product context read/write is triggered, read `references/rules-context.md`
 
 When the user asks to list frameworks or uses supplementary commands, read `references/rules-commands.md`.
 
+**For any mode that contains Optional steps (Full / Revision / Comprehensive Custom), read `references/rules-optional-trigger.md` for trigger conditions, the Persona-Journey bundling rule, and the Phase Decision Point output format.**
+
+---
+
+## 🔗 Global Rule: Persona-Journey Bundling
+
+**Whenever a mode includes a Persona step, Journey Map is included by DEFAULT in the very next step.** Persona defines Who; Journey Map describes the journey Who experiences. This applies equally to 0-to-1 and existing products — the relevant variable is whether the user's Job spans multiple stages, not whether the product already exists. (Teresa Torres, Indi Young, and Amazon Working Backwards all treat Journey Map as essential during 0-to-1.)
+
+Skip Journey Map only when one of the following holds:
+1. **Single interaction point** — the Job is solved by a single API call, single button, backend service, or pure config tool
+2. **Flow is only 1–2 steps** — too short for stage transitions; Journey Map degenerates into a list
+3. **User explicitly requests skip** — e.g., "skip Journey Map"
+
+When skipping, surface the decision rather than silently dropping it: *"Persona is complete. Based on context ([single interaction point / flow has only N steps]), Journey Map is being skipped. Reply 'add journey' to add it back."*
+
+Full skip logic, Custom Mode conditional insert behavior, and Phase Decision Point format live in `references/rules-optional-trigger.md`.
+
 ---
 
 ## Startup Flow

package/commands/product-full.md

@@ -1,5 +1,5 @@
 ---
-description: Full Mode Product Planning — Run through all 20 steps across every framework, producing deliverable planning documents
+description: Full Mode Product Planning — Run 8 Core + up to 3 Optional steps (8–11 total) across the most relevant frameworks, producing deliverable planning documents
 argument-hint: <product description>
 ---
 
@@ -10,4 +10,4 @@ When executing each step, load the corresponding reference files as indicated in
 Execution mode: Full Mode
 Product description: $ARGUMENTS
 
-Follow the step sequence in rules-full.md (S1 → S20). First confirm the product type (B2B/B2C) and target audience, then begin the first step. Display a progress indicator at each step.
+Follow the step sequence in rules-full.md (S1 → S11, with Optional steps gated by triggers in rules-optional-trigger.md). First confirm the product type (B2B/B2C) and target audience, then begin the first step. Render a Phase Decision Point block before any phase that contains Optional steps, and display a progress indicator at each step.

package/commands/product-revision.md

@@ -10,4 +10,4 @@ When executing each step, load the corresponding reference files as indicated in
 Execution mode: Revision Mode
 Product description: $ARGUMENTS
 
-Follow the step sequence in rules-revision.md (S1 → S12). S1 will proactively ask about existing product metrics (DAU/MAU, retention rate, key user feedback, etc.). Display a progress indicator at each step.
+Follow the step sequence in rules-revision.md (S1 → S8, with Optional steps gated by triggers in rules-optional-trigger.md). S1 will proactively ask about existing product metrics (DAU/MAU, retention rate, key user feedback, etc.). Render a Phase Decision Point block before any phase that contains Optional steps, and display a progress indicator at each step.

package/i18n/en/SKILL.md

@@ -47,8 +47,8 @@ When the user triggers this skill, use a **progressive confirmation** approach
 Select a mode (enter a number or name), or just tell me about your product and I'll recommend the best mode:
 
 1. 🚀 **Quick Mode** — 3 steps, ~30 min (JTBD → PR-FAQ → North Star)
-2. 📦 **Full Mode** — 20 steps, comprehensive planning document
-3. 🔄 **Revision Mode** — 12 steps, optimize existing product
+2. 📦 **Full Mode** — 9–11 steps (8 Core + 1 Default-ON Journey + 2 Default-OFF Optionals; 8 if flow is too simple to map), comprehensive planning document
+3. 🔄 **Revision Mode** — 6–8 steps (6 Core + 2 Optional), optimize existing product
 4. ✏️ **Custom Mode** — Choose your own framework combination
 5. ⚡ **Build Mode** — 7 steps, skip Discovery, go straight to solution
 6. 🔧 **Feature Extension Mode** — 4 steps, add a feature to existing product
@@ -84,17 +84,17 @@ Who is this plan primarily for?
 | Mode | Description | Fixed Outputs | Best For |
 |------|-------------|---------------|----------|
 | 🚀 **Quick Mode** | Actionable direction in 30 min; three fixed steps, no skipping | ① JTBD Statement ② PR-FAQ ③ North Star Metric | Quick alignment, idea validation, preparing a pitch |
-| 📦 **Full Mode** | Run through all frameworks; produce a deliverable plan | All frameworks (see step sequence) | New product planning, major revamps |
-| 🔄 **Revision Mode** | Optimize an existing product with user data and a feature baseline | Current state analysis → Pain point synthesis → Solution → Validation | Feature revamps, UX optimization, product repositioning |
+| 📦 **Full Mode** | 8 Core + 1 Default-ON Journey Map + 2 Default-OFF Optionals; produces a deliverable plan | Strategy → Persona → **Journey Map (default ON)** → JTBD → Pain+HMW+Ranking → PR-FAQ → Solution Evaluation → MVP → North Star (+ optional Positioning, PMF/GTM/Validation) | New product planning, major revamps |
+| 🔄 **Revision Mode** | 6 Core steps + 2 Optional, baseline-aware | Current state + JTBD re-validation → Pain points → Pain+HMW+Ranking (+optional Positioning) → PR-FAQ (+optional Pre-mortem) → MVP → North Star + Validation | Feature revamps, UX optimization, product repositioning |
 | ✏️ **Custom Mode** | Choose your own framework combination or completeness level | User-specified | Filling in specific gaps |
 | ⚡ **Build Mode** | Skip Discovery, go straight to solutions | PR-FAQ + Pre-mortem + GEM/RICE + MVP + North Star | Problem is known; need fast execution |
 | 🔧 **Feature Extension Mode** | Add a single feature to an existing product; streamlined 4-step flow | Problem + Context → Three parallel solutions + AI recommendation → Risk assessment → Execution scope | Adding features to an existing product; clear feature requirements |
 
 ### 📊 Completeness Levels (Custom Mode only)
 
-**🔴 Low (Lean)**: JTBD Statement → One HMW → PR-FAQ → North Star (any step can be swapped)
-**🟡 Medium (Standard)**: Persona + JTBD → Pain Points + HMW + Positioning → Parallel Solutions + MVP → North Star + PMF + Product Spec Summary
-**🟢 High (Comprehensive)**: Medium + Journey Map + OST + Strategy Blocks + RICE + Pre-mortem + Hypothesis Validation
+**🔴 Low (Lean — 4 steps)**: JTBD Statement → One HMW → PR-FAQ → North Star (any step can be swapped)
+**🟡 Medium (Standard — 8 or 9 steps)**: Persona → **(Journey Map auto-inserted unless flow is too simple)** → JTBD → Pain+HMW+Ranking → Positioning → PR-FAQ → Solution Evaluation → MVP → North Star
+**🟢 High (Comprehensive — 11 steps)**: Standard + Strategy Diagnosis + **Journey Map (bundled with Persona, default ON)** + PMF/GTM/BM/Validation
 
 ### 👥 Target Audience
 
@@ -128,6 +128,23 @@ After confirming the product type, read `references/rules-product-type.md` for B
 
 When product context read/write is triggered, read `references/rules-context.md` for context accumulation rules.
 
+**For any mode that contains Optional steps (Full / Revision / Comprehensive Custom), read `references/rules-optional-trigger.md` for trigger conditions, the Persona-Journey bundling rule, and the Phase Decision Point output format.**
+
+---
+
+## 🔗 Global Rule: Persona-Journey Bundling
+
+**Whenever a mode includes a Persona step, Journey Map is included by DEFAULT in the very next step.** Persona defines Who; Journey Map describes the journey Who experiences. This applies equally to 0-to-1 and existing products — the relevant variable is whether the user's Job spans multiple stages, not whether the product already exists. (Teresa Torres, Indi Young, and Amazon Working Backwards all treat Journey Map as essential during 0-to-1.)
+
+Skip Journey Map only when one of the following holds:
+1. **Single interaction point** — the Job is solved by a single API call, single button, backend service, or pure config tool
+2. **Flow is only 1–2 steps** — too short for stage transitions; Journey Map degenerates into a list
+3. **User explicitly requests skip** — e.g., "skip Journey Map"
+
+When skipping, surface the decision rather than silently dropping it: *"Persona is complete. Based on context ([single interaction point / flow has only N steps]), Journey Map is being skipped. Reply 'add journey' to add it back."*
+
+Full skip logic, Custom Mode conditional insert behavior, and Phase Decision Point format live in `references/rules-optional-trigger.md`.
+
 When the user asks to list frameworks or uses supplementary commands, read `references/rules-commands.md`.
 
 ---

package/i18n/en/commands/product-full.md

@@ -1,5 +1,5 @@
 ---
-description: Full Mode Product Planning — Run through all 20 steps across every framework, producing deliverable planning documents
+description: Full Mode Product Planning — Run 8 Core + up to 3 Optional steps (8–11 total) across the most relevant frameworks, producing deliverable planning documents
 argument-hint: <product description>
 ---
 
@@ -10,4 +10,4 @@ When executing each step, load the corresponding reference files as indicated in
 Execution mode: Full Mode
 Product description: $ARGUMENTS
 
-Follow the step sequence in rules-full.md (S1 → S20). First confirm the product type (B2B/B2C) and target audience, then begin the first step. Display a progress indicator at each step.
+Follow the step sequence in rules-full.md (S1 → S11, with Optional steps gated by triggers in rules-optional-trigger.md). First confirm the product type (B2B/B2C) and target audience, then begin the first step. Render a Phase Decision Point block before any phase that contains Optional steps, and display a progress indicator at each step.

package/i18n/en/commands/product-revision.md

@@ -10,4 +10,4 @@ When executing each step, load the corresponding reference files as indicated in
 Execution mode: Revision Mode
 Product description: $ARGUMENTS
 
-Follow the step sequence in rules-revision.md (S1 → S12). S1 will proactively ask about existing product metrics (DAU/MAU, retention rate, key user feedback, etc.). Display a progress indicator at each step.
+Follow the step sequence in rules-revision.md (S1 → S8, with Optional steps gated by triggers in rules-optional-trigger.md). S1 will proactively ask about existing product metrics (DAU/MAU, retention rate, key user feedback, etc.). Render a Phase Decision Point block before any phase that contains Optional steps, and display a progress indicator at each step.

package/i18n/en/references/rules-custom.md

@@ -1,63 +1,77 @@
 # ✏️ Custom Mode Step Sequence
 
-> This file is the authoritative step definition for Custom Mode. Loaded by the SKILL.md core dispatcher.
+> Authoritative step definition for Custom Mode. Dispatched from SKILL.md.
 
-Based on the user's selected completeness level:
+Choose a completeness level (or hand-pick steps):
 
-## 🔴 Low (Lean) — 4 Steps
+## 🔴 Lean — 4 steps
 
 ```
-S1. JTBD statement → load references/02b-jtbd.md
-S2. One HMW → load references/03-define.md → 2.3
-S3. PR-FAQ → load references/04a-prfaq.md
-S4. North Star → load references/05a-northstar-aha.md
-(Any step can be swapped by the user for a different framework)
+S1. JTBD Statement → references/02b-jtbd.md
+S2. One HMW → references/03-define.md
+S3. PR-FAQ → references/04a-prfaq.md
+S4. North Star → references/05a-northstar-aha.md
+(Any step can be swapped by the user for a different framework.)
 ────
-Final Output → Product spec summary (unexecuted fields marked "Not executed")
+Final output → Product Spec Summary (unexecuted fields marked "not run")
 ```
 
-## 🟡 Medium (Standard) — 10 Steps
+## 🟡 Standard — 8 steps (auto-expands to 9 when Journey Map is needed)
+
+> An 8-step subset of Full Mode: Full Core minus Strategy Diagnosis, plus Positioning. Standard users typically need market positioning earlier than deep strategy diagnosis, hence the swap.
+>
+> **Persona-Journey Conditional Insert**: After completing S1 (Persona), the AI runs the Persona-Journey evaluation per `rules-optional-trigger.md` Section 2. If skip conditions do NOT hold (i.e., the Job spans multiple stages), AI **proactively inserts Journey Map as S1.5**, making this a 9-step run. User can reply `-journey` to revert to 8 steps. If skip conditions hold (single interaction point / flow ≤2 steps), silently skip and disclose at final output.
 
 ```
-S1.  Persona Table + Persona Card → load references/02a-persona.md
-S2.  JTBD Analysis → load references/02b-jtbd.md
-S3.  Pain Point Summary Table → load references/03-define.md
-S4.  HMW Question Reframing → load references/03-define.md
-S5.  April Dunford Positioning → load references/03-define.md
-S6.  PR-FAQ → load references/04a-prfaq.md
-S7.  Parallel Solutions + MVP + Not Doing List → load references/04b-solutions.md + references/04c-mvp.md
-S8.  North Star + Three-Layer Signals + Aha Moment → load references/05a-northstar-aha.md
-S9.  PMF Level Assessment → load references/05b-pmf-gtm.md
-S10. Product Spec Summary → load references/05c-validation-spec.md
+S1.   Persona (Table + Cards) → references/02a-persona.md
+S1.5  User Journey Map [Inserted by default; skip only when situation is too simple]
+      → references/02c-ost-journey.md
+S2.   JTBD Analysis → references/02b-jtbd.md
+S3.   Pain Points + HMW + Opportunity Ranking → references/03-define.md
+S4.   April Dunford Positioning → references/03-define.md
+S5.   PR-FAQ → references/04a-prfaq.md
+S6.   Solution Evaluation (Parallel + Pre-mortem + GEM + RICE) → references/04b-solutions.md
+S7.   MVP + Not Doing List → references/04c-mvp.md
+S8.   North Star + Three-Layer Signals + Aha Moment → references/05a-northstar-aha.md
 ```
 
-## 🟢 High (Comprehensive) — 16 Steps
+## 🟢 Comprehensive — 11 steps
+
+> Full Mode Core + all Default-OFF Optionals triggered (Positioning + PMF/GTM/BM/Validation). **S2 Persona is immediately followed by S3 User Journey Map** per the Persona-Journey bundling rule. S3 may be skipped if the situation is genuinely simple — reply `-S3` after Persona to revert to 10 steps.
 
 ```
-S1.  Strategy Blocks + Rumelt → load references/01-strategy.md
-S2.  Persona Table + Persona Card → load references/02a-persona.md
-S3.  JTBD Analysis → load references/02b-jtbd.md
-S4.  OST Opportunity Solution Tree → load references/02c-ost-journey.md
-S5.  User Journey Map → load references/02c-ost-journey.md
-S6.  Pain Point Summary Table → load references/03-define.md
-S7.  HMW + April Dunford Positioning → load references/03-define.md
-S8.  Opportunity Assessment Table → load references/03-define.md
-S9.  PR-FAQ → load references/04a-prfaq.md
-S10. Parallel Prototypes → load references/04b-solutions.md
-S11. Pre-mortem → load references/04b-solutions.md
-S12. GEM + RICE → load references/04b-solutions.md
-S13. MVP + Not Doing List → load references/04c-mvp.md
-S14. North Star + Three-Layer Signals + Aha Moment → load references/05a-northstar-aha.md
-S15. Hypothesis Validation Plan → load references/05c-validation-spec.md
-S16. Product Spec Summary → load references/05c-validation-spec.md
+S1.  Strategy Diagnosis → references/00-opportunity-check.md + references/01-strategy.md
+S2.  Persona (Table + Cards) → references/02a-persona.md
+S3.  User Journey Map → references/02c-ost-journey.md   ← bundled with S2 (default ON)
+S4.  JTBD Analysis → references/02b-jtbd.md
+S5.  Pain Points + HMW + Opportunity Ranking → references/03-define.md
+S6.  April Dunford Positioning → references/03-define.md
+S7.  PR-FAQ → references/04a-prfaq.md
+S8.  Solution Evaluation (Parallel + Pre-mortem + GEM + RICE) → references/04b-solutions.md
+S9.  MVP + Not Doing List → references/04c-mvp.md
+S10. North Star + Three-Layer Signals + Aha Moment → references/05a-northstar-aha.md
+S11. PMF + GTM + BM + Hypothesis Validation Plan → references/05b-pmf-gtm.md + references/05c-validation-spec.md
 ```
 
-## Reference Loading Rules
+## Reference Loading Rule
+
+Load each reference file ONLY when entering its corresponding step (do not pre-load all references). Each step has its reference path annotated above.
+
+## Persona-Journey Bundling
+
+Per `references/rules-optional-trigger.md` Sections 2 and 6, whenever a Custom preset includes a Persona step, Journey Map is **default ON**:
+
+- **Comprehensive**: Journey Map is hard-coded as S3 (already in the sequence above). User may reply `-S3` after Persona to skip.
+- **Standard**: Journey Map is auto-inserted as **S1.5** when skip conditions don't hold (multi-stage Job). When the situation is too simple (single interaction point, flow ≤2 steps, user requests skip), Journey Map is silently skipped and disclosed at final output.
+- **Lean**: No Persona step, so this rule does not apply.
 
-When entering each step, only load the corresponding reference file (do not pre-load all files). Each step above has its reference path annotated.
+Skip conditions (any one holds → skip Journey):
+1. Single interaction point (API, single button, backend service, config tool)
+2. Flow has only 1–2 steps
+3. User explicitly requests skip
 
 ## Final Output Format
 
-**Product Spec Summary** (only integrates completed steps; unexecuted fields are marked "Not executed")
+**Product Spec Summary** (only integrates completed steps; unexecuted fields marked "not run").
 
-Upon completion, execute end-of-flow rules per `references/rules-end-of-flow.md`.
+After completion, follow `references/rules-end-of-flow.md` for end-of-flow rules.

package/i18n/en/references/rules-end-of-flow.md

@@ -23,7 +23,7 @@ Before generating the final integrated output, scan ALL completed steps and veri
 1. JTBD ↔ PR-FAQ: Does the PR-FAQ address the same problem as the JTBD statement?
 2. PR-FAQ ↔ North Star: Does the North Star measure the outcome the PR-FAQ promises?
 
-**📦 Full Mode** (20 steps — check all 7):
+**📦 Full Mode** (9–11 steps, 8 Core + 1 Default-ON + 2 Optional — check all 7):
 1. Target User — same persona referenced across JTBD, Positioning, PR-FAQ, and North Star?
 2. Core Problem / JTBD — PR-FAQ addresses the same problem? MVP solves it?
 3. Positioning — reflected in PR-FAQ headline and solution direction?
@@ -32,7 +32,7 @@ Before generating the final integrated output, scan ALL completed steps and veri
 6. North Star Metric — measures JTBD outcome? Achievable with MVP scope?
 7. Pre-mortem Risks — still relevant given final solution and MVP?
 
-**🔄 Revision Mode** (12 steps — check 4):
+**🔄 Revision Mode** (6–8 steps, 6 Core + 2 Optional — check 4):
 1. Existing JTBD ↔ Pain Points ↔ Positioning: consistent after re-evaluation?
 2. PR-FAQ ↔ MVP Scope: revision scope matches what PR-FAQ describes?
 3. North Star ↔ Before/After: metric comparison is logical?