@namch/agent-assistant 1.0.1 → 1.0.3

package/commands/design.md

@@ -16,9 +16,10 @@ execution-mode: router
 ## 🛑 PRE-FLIGHT (DO FIRST — BLOCKS EXECUTION)
 
 **LOAD now** (in order; path `./rules/` or `~/.{TOOL}/skills/agent-assistant/rules/`):
-1. ORCHESTRATION-LAWS.md  
-2. ADAPTIVE-EXECUTION.md  
-3. EXECUTION-PROTOCOL.md  
+
+1. ORCHESTRATION-LAWS.md
+2. ADAPTIVE-EXECUTION.md
+3. EXECUTION-PROTOCOL.md
 
 **⛔ Do not run any workflow phase until all are loaded.** Follow **all** rules in those files. Then run this file's ROUTING LOGIC, LOAD the chosen variant workflow, and execute it.
 
@@ -33,6 +34,9 @@ IF design is simple (component, quick mockup):
 IF design is complex (full feature, system):
   → Route to /design:hard
 
+IF design is complex AND clean implementation handoff is critical:
+  → Route to /design:focus
+
 IF unsure:
   → Default to /design:fast
 ```
@@ -41,10 +45,11 @@ IF unsure:
 
 ## AVAILABLE ROUTES
 
-| Route          | When to Use                        |
-| -------------- | ---------------------------------- |
-| `/design:fast` | Quick component design, simple UI  |
-| `/design:hard` | Full feature design, system design |
+| Route           | When to Use                                        |
+| --------------- | -------------------------------------------------- |
+| `/design:fast`  | Quick component design, simple UI                  |
+| `/design:hard`  | Full feature design, system design                 |
+| `/design:focus` | Full design with **enforced context optimization** |
 
 ---
 
@@ -59,6 +64,7 @@ IF unsure:
 
 1. ⚡ **Fast** → `/design:fast` — Quick design
 2. ⚡⚡⚡ **Hard** → `/design:hard` — Full design process
+3. 🎯 **Focus** → `/design:focus` — Full design with **automatic context clearing** (clean implementation handoff)
 
 ⏳ Awaiting selection...
 ```

package/commands/fix/focus.md

@@ -0,0 +1,175 @@
+---
+description: 🔒 Focused Fix — Complete issue resolution with enforced context optimization
+version: "1.0"
+category: debugging
+execution-mode: execute
+---
+
+# /fix:focus — Focus Issue Resolution
+
+> **MISSION**: Full resolution workflow with **enforced context optimization**.
+>
+> This variant automatically clears context before implementation—no user prompt required.
+> Use when you want guaranteed clean fix implementation without context rot risk.
+
+<issue>$ARGUMENTS</issue>
+
+---
+
+## 🛑 PRE-FLIGHT (DO FIRST — BLOCKS PHASE 1)
+
+**LOAD now** (in order; path `./rules/` or `~/.{TOOL}/skills/agent-assistant/rules/`):
+
+1. ORCHESTRATION-LAWS.md
+2. ADAPTIVE-EXECUTION.md
+3. EXECUTION-PROTOCOL.md
+
+**⛔ Do not run Phase 1 until all are loaded.** Follow **all** rules in those files; they override any conflicting instructions in this file.
+
+---
+
+## 🔀 TIERED EXECUTION
+
+| Tier       | When               | Action                       |
+| ---------- | ------------------ | ---------------------------- |
+| **TIER 1** | runSubagent EXISTS | Invoke sub-agent (MANDATORY) |
+| **TIER 2** | Tool MISSING       | EMBODY agent file (FALLBACK) |
+
+**❌ Anti-Lazy**: Never use TIER 2 when TIER 1 tool available.
+
+---
+
+## 📁 DELIVERABLE FILES
+
+| Agent      | Output                                      |
+| ---------- | ------------------------------------------- |
+| debugger   | `./reports/debugs/DEBUG-{issue}.md`         |
+| researcher | `./reports/researchers/RESEARCH-{issue}.md` |
+
+All files in `./reports/` → English only.
+
+---
+
+## ⛔ INCREMENTAL EXECUTION (MANDATORY)
+
+One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in one reply. No batching (load only what each phase needs). **Within each phase:** when doing a part, output it in format so user sees what's happening (announce before doing). Format: rules/EXECUTION-PROTOCOL.md § Phase output structure.
+
+---
+
+## 🎭 Phase 1: DEEP ANALYSIS
+
+| Agent | `debugger`                                                       |
+| ----- | ---------------------------------------------------------------- |
+| Goal  | Full root cause analysis                                         |
+| Exit  | Root cause identified, impact assessed, failure chain documented |
+
+---
+
+## 🎭 Phase 2: RESEARCH
+
+| Agent | `researcher`                                   |
+| ----- | ---------------------------------------------- |
+| Goal  | Research solution patterns                     |
+| Exit  | Solutions researched, best approach identified |
+
+---
+
+## 🎭 Phase 3: FIX PLANNING
+
+| Agent | `planner`                         |
+| ----- | --------------------------------- |
+| Goal  | Create fix strategy with rollback |
+| Exit  | Plan created, rollback included   |
+
+---
+
+## 🛡️ STRICT CONTEXT GATE — Automatic Context Optimization
+
+> **⚡ FOCUS MODE**: This checkpoint executes automatically. NO user input required.
+>
+> **PURPOSE**: Prevent "context rot" by forcibly clearing noisy debugging/planning history.
+> This acts as a mandatory "firewall" between Planning and Implementation phases.
+
+### 🔒 AUTOMATIC EXECUTION (NO PROMPT)
+
+```yaml
+strict_context_gate:
+  mode: "AUTOMATIC - No user interaction"
+  behavior: "Force Clear context & Auto-Implement"
+
+  execution:
+    1. ANNOUNCE: |
+      ## 🛡️ Strict Context Gate — Automatic
+
+      ✅ **Fix Plan Complete**: Strategy defined with rollback.
+      🔒 **Focus Mode**: Automatically clearing context for implementation.
+
+      ⚡ Executing: **Clear context & Auto-Implement**...
+
+    2. CONTEXT_DIRECTIVE: |
+      ╔══════════════════════════════════════════════════════════════════╗
+      ║  ⛔ MANDATORY CONTEXT RESET — FOCUS MODE                         ║
+      ╠══════════════════════════════════════════════════════════════════╣
+      ║  IGNORE: All previous debugging hypotheses, failed attempts,     ║
+      ║          research explorations, and intermediate reasoning.      ║
+      ║                                                                  ║
+      ║  SOLE SOURCE OF TRUTH: Fix plan with rollback strategy.          ║
+      ║                                                                  ║
+      ║  PROCEED: Begin Implementation phase with FRESH context mindset. ║
+      ║           Treat this as a NEW conversation starting from Plan.   ║
+      ╚══════════════════════════════════════════════════════════════════╝
+
+    3. LOAD: Read Fix plan completely as if seeing it for the first time
+
+    4. PROCEED: Start Phase 4 (Implementation) immediately
+```
+
+### 📋 Post-Gate Status
+
+```markdown
+🔒 **Context Gate Passed**
+
+- Previous context: DISCARDED
+- Active context: Fix plan only
+- Mode: Fresh implementation start
+
+Proceeding to Implementation...
+```
+
+---
+
+## 🎭 Phase 4: IMPLEMENTATION
+
+| Agent | `tech-lead` → specialists           |
+| ----- | ----------------------------------- |
+| Goal  | Execute fix plan                    |
+| Exit  | Fix implemented, changes documented |
+
+---
+
+## 🎭 Phase 5: VALIDATION
+
+| Agent | `tester`                                  |
+| ----- | ----------------------------------------- |
+| Goal  | Comprehensive validation                  |
+| Exit  | Issue resolved, tests pass, no regression |
+
+---
+
+## 🎭 Phase 5.5: ROLLBACK VERIFICATION (IF CRITICAL)
+
+| Agent   | `devops-engineer`                                    |
+| ------- | ---------------------------------------------------- |
+| Trigger | Fix affects production or is critical                |
+| Goal    | Verify rollback plan                                 |
+| Exit    | Rollback documented, tested, recovery time estimated |
+
+---
+
+## COMPLETION
+
+Present fix report with:
+
+1. ✅ **Fixed** — Issue resolved (Focus Mode)
+2. 🧪 **Test** → `/test`
+3. 📝 **Docs** → `/docs:core`

package/commands/fix/hard.md

@@ -79,6 +79,63 @@ One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in
 
 ---
 
+## 🛡️ VERIFICATION CHECKPOINT — Context Optimization
+
+> **PURPOSE**: Prevent "context rot" by clearing noisy debugging/planning history before implementation.
+> 
+> Long-running analysis sessions fill context with noise that degrades code generation quality.
+> This checkpoint acts as a "firewall" between Planning and Implementation phases.
+
+### ⚡ OPTIONS (Present to User)
+
+```markdown
+## 🛡️ Context Optimization Checkpoint
+
+**Planning Complete** — Fix plan created with rollback strategy.
+
+**Choose how to proceed with implementation:**
+
+| Option | Action | Description |
+|--------|--------|-------------|
+| **1. 🚀 Clear context & Auto-Implement** | `RECOMMENDED` | Fresh start: Reload Plan, ignore chat history, begin fix immediately |
+| **2. ⏸️ Clear context & Manual** | `SAFE` | Clear context, reload Plan, pause for your command before coding |
+| **3. ⚠️ Continue (No Clear)** | `RISKY` | Proceed with full history attached (may cause hallucination) |
+
+⏳ Awaiting selection...
+```
+
+### 🔄 EXECUTION BEHAVIOR
+
+```yaml
+option_1_clear_auto_implement:
+  behavior: "RECOMMENDED - Simulate fresh start"
+  steps:
+    1. ACKNOWLEDGE: "🚀 Executing Clear context & Auto-Implement..."
+    2. CONTEXT_DIRECTIVE: |
+       ⛔ IGNORE all previous chat messages and reasoning chains.
+       ✅ RELOAD: Fix plan as SOLE SOURCE OF TRUTH.
+       ✅ PROCEED: Begin Phase 4 (Implementation) immediately.
+    3. EXECUTE: Start Implementation phase with fresh context mindset
+
+option_2_clear_manual:
+  behavior: "Clear and wait for explicit command"
+  steps:
+    1. ACKNOWLEDGE: "⏸️ Context cleared. Plan reloaded."
+    2. CONTEXT_DIRECTIVE: |
+       ⛔ IGNORE all previous chat messages and reasoning chains.
+       ✅ RELOAD: Fix plan as SOLE SOURCE OF TRUTH.
+    3. OUTPUT: "Ready for fix implementation. Type `/continue` or give specific instructions."
+    4. WAIT: For user command before proceeding
+
+option_3_continue_no_clear:
+  behavior: "Proceed with caution - context rot risk"
+  steps:
+    1. WARN: "⚠️ Continuing with full history. Higher hallucination risk."
+    2. PROCEED: Continue to Phase 4 with existing context
+```
+
+---
+
 ## 🎭 Phase 4: IMPLEMENTATION
 
 | Agent | `tech-lead` → specialists |

package/commands/fix.md

@@ -16,9 +16,10 @@ execution-mode: router
 ## 🛑 PRE-FLIGHT (DO FIRST — BLOCKS EXECUTION)
 
 **LOAD now** (in order; path `./rules/` or `~/.{TOOL}/skills/agent-assistant/rules/`):
-1. ORCHESTRATION-LAWS.md  
-2. ADAPTIVE-EXECUTION.md  
-3. EXECUTION-PROTOCOL.md  
+
+1. ORCHESTRATION-LAWS.md
+2. ADAPTIVE-EXECUTION.md
+3. EXECUTION-PROTOCOL.md
 
 **⛔ Do not run any workflow phase until all are loaded.** Follow **all** rules in those files. Then run this file's ROUTING LOGIC, LOAD the chosen variant workflow, and execute it.
 
@@ -33,6 +34,9 @@ IF issue is simple (clear cause, quick fix):
 IF issue is complex (research needed, multi-file):
   → Route to /fix:hard
 
+IF issue is complex AND context optimization is critical:
+  → Route to /fix:focus
+
 IF unsure:
   → Default to /fix:fast (escalate if needed)
 ```
@@ -41,10 +45,11 @@ IF unsure:
 
 ## AVAILABLE ROUTES
 
-| Route       | When to Use                     |
-| ----------- | ------------------------------- |
-| `/fix:fast` | Quick fixes, clear issues       |
-| `/fix:hard` | Complex issues, research needed |
+| Route        | When to Use                                           |
+| ------------ | ----------------------------------------------------- |
+| `/fix:fast`  | Quick fixes, clear issues                             |
+| `/fix:hard`  | Complex issues, research needed                       |
+| `/fix:focus` | Complex issues with **enforced context optimization** |
 
 ---
 
@@ -59,6 +64,7 @@ IF unsure:
 
 1. ⚡ **Fast** → `/fix:fast` — Quick fix
 2. ⚡⚡⚡ **Hard** → `/fix:hard` — Full resolution
+3. 🎯 **Focus** → `/fix:focus` — Full resolution with **automatic context clearing** (prevents hallucination)
 
 ⏳ Awaiting selection...
 ```

package/commands/plan/focus.md

@@ -0,0 +1,190 @@
+---
+description: 🔒 Focused Plan — Research-backed planning with enforced context optimization
+version: "1.0"
+category: planning
+execution-mode: execute
+---
+
+# /plan:focus — Focus Comprehensive Planning
+
+> **MISSION**: Create thorough implementation plan with **enforced context optimization**.
+>
+> This variant automatically clears context before handoff—no user prompt required.
+> Use when you want guaranteed clean plan handoff without context rot risk.
+
+<task>$ARGUMENTS</task>
+
+---
+
+## 🛑 PRE-FLIGHT (DO FIRST — BLOCKS PHASE 1)
+
+**LOAD now** (in order; path `./rules/` or `~/.{TOOL}/skills/agent-assistant/rules/`):
+
+1. ORCHESTRATION-LAWS.md
+2. ADAPTIVE-EXECUTION.md
+3. EXECUTION-PROTOCOL.md
+
+**⛔ Do not run Phase 1 until all are loaded.** Follow **all** rules in those files; they override any conflicting instructions in this file.
+
+---
+
+## 🔀 TIERED EXECUTION
+
+| Tier       | When               | Action                       |
+| ---------- | ------------------ | ---------------------------- |
+| **TIER 1** | runSubagent EXISTS | Invoke sub-agent (MANDATORY) |
+| **TIER 2** | Tool MISSING       | EMBODY agent file (FALLBACK) |
+
+---
+
+## 📁 DELIVERABLE FILES
+
+| Agent      | Output                                                                                                                                                                   |
+| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| researcher | `./reports/researchers/RESEARCH-{task}.md`                                                                                                                               |
+| scouter    | `./reports/scouts/SCOUT-{task}.md`                                                                                                                                       |
+| planner    | **One** `./reports/plans/PLAN-{task}.md` **OR** multiple `./reports/plans/PLAN-{task}-phase1.md`, `PLAN-{task}-phase2.md`, … (see **Complexity & plan splitting** below) |
+
+**Plans are source of truth for implementation.** All files in `./reports/` → English only.
+
+---
+
+## 📐 COMPLEXITY & PLAN SPLITTING (MANDATORY FOR PLANNER)
+
+When the logical plan would have **> 3 phases** or **estimated effort > 3 days**, the planner **MUST** produce **multiple plan files** (one per executable phase or per milestone group), **not** one monolithic file.
+
+| Condition                  | Planner output                                                   |
+| -------------------------- | ---------------------------------------------------------------- |
+| ≤ 3 phases, ≤ 3 days       | **One** `PLAN-{task}.md`                                         |
+| > 3 phases **or** > 3 days | **Multiple** `PLAN-{task}-phase1.md`, `PLAN-{task}-phase2.md`, … |
+
+**Multi-plan rules:**
+
+- Naming: `PLAN-{task}-phase1.md`, `PLAN-{task}-phase2.md`, …
+- Order: Execute in numeric order; phase N starts only after phase N−1 is complete.
+- Each file: scope **only** that phase; Prerequisites state "Phase N−1 complete" (or prior deliverables); clear handoff to next file.
+- Index (optional): planner may add `PLAN-{task}-INDEX.md` listing phases and file names for navigation.
+
+---
+
+## ⛔ INCREMENTAL EXECUTION (MANDATORY)
+
+One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in one reply. No batching (load only what each phase needs). **Within each phase:** when doing a part, output it in format so user sees what's happening (announce before doing). Format: rules/EXECUTION-PROTOCOL.md § Phase output structure.
+
+---
+
+## 🎭 Phase 1: RESEARCH
+
+| Agent  | `researcher`                                  |
+| ------ | --------------------------------------------- |
+| Goal   | Research best practices and patterns          |
+| Output | `./reports/researchers/RESEARCH-{task}.md`    |
+| Exit   | Best practices identified, sources documented |
+
+---
+
+## 🎭 Phase 2: CODEBASE ANALYSIS
+
+| Agent  | `scouter`                                    |
+| ------ | -------------------------------------------- |
+| Goal   | Full architecture mapping                    |
+| Output | `./reports/scouts/SCOUT-{task}.md`           |
+| Exit   | Architecture understood, dependencies mapped |
+
+---
+
+## 🎭 Phase 3: DESIGN (IF UI NEEDED)
+
+| Agent   | `designer`                                        |
+| ------- | ------------------------------------------------- |
+| Trigger | Task involves UI/UX                               |
+| Goal    | Design approach input                             |
+| Exit    | Design approach defined, accessibility considered |
+
+---
+
+## 🎭 Phase 4: PLAN CREATION
+
+| Agent        | `planner`                                                                                                                   |
+| ------------ | --------------------------------------------------------------------------------------------------------------------------- |
+| Prerequisite | **READ** RESEARCH + SCOUT files (and DESIGN if Phase 3 ran)                                                                 |
+| Goal         | Create detailed implementation plan as **one file** or **multiple phase files** (see **Complexity & plan splitting** above) |
+| Output       | One `./reports/plans/PLAN-{task}.md` **or** multiple `./reports/plans/PLAN-{task}-phase1.md`, `PLAN-{task}-phase2.md`, …    |
+
+**Directive to planner:** If the task decomposes into **> 3 phases** or **> 3 days** effort, produce **multiple plan files** (one per phase/milestone), each executable in sequence. Otherwise produce a single `PLAN-{task}.md`.
+
+**CONSTRAINT INHERITANCE:**
+
+```
+Plan(s) MUST reference prior phases:
+- "Based on research finding R1..."
+- "Following pattern from Scout..."
+- "Per design decision D1..."
+```
+
+| Exit | One plan file **or** multiple phase plan files created; each has scope, prerequisites, tasks, exit criteria, risks, rollback; order and handoffs clear |
+
+---
+
+## 🛡️ STRICT CONTEXT GATE — Automatic Context Optimization
+
+> **⚡ FOCUS MODE**: This checkpoint executes automatically. NO user input required.
+>
+> **PURPOSE**: Prevent "context rot" by forcibly clearing noisy research/planning history.
+> This acts as a mandatory "firewall" before handoff to implementation workflows.
+
+### 🔒 AUTOMATIC EXECUTION (NO PROMPT)
+
+```yaml
+strict_context_gate:
+  mode: "AUTOMATIC - No user interaction"
+  behavior: "Force Clear context & Ready"
+
+  execution:
+    1. ANNOUNCE: |
+      ## 🛡️ Strict Context Gate — Automatic
+
+      ✅ **Plan Complete**: Plan file(s) created.
+      🔒 **Focus Mode**: Automatically clearing context for implementation handoff.
+
+      ⚡ Executing: **Clear context & Ready**...
+
+    2. CONTEXT_DIRECTIVE: |
+      ╔══════════════════════════════════════════════════════════════════╗
+      ║  ⛔ MANDATORY CONTEXT RESET — FOCUS MODE                         ║
+      ╠══════════════════════════════════════════════════════════════════╣
+      ║  IGNORE: All previous research discussions, exploration paths,   ║
+      ║          rejected alternatives, and intermediate reasoning.      ║
+      ║                                                                  ║
+      ║  SOLE SOURCE OF TRUTH: Plan file(s) in ./reports/plans/          ║
+      ║                                                                  ║
+      ║  HANDOFF: Plan is ready for `/code:focus` implementation.        ║
+      ║           Implementation should treat Plan as fresh context.     ║
+      ╚══════════════════════════════════════════════════════════════════╝
+
+    3. OUTPUT: Plan summary for user
+
+    4. PROCEED: To COMPLETION
+```
+
+### 📋 Post-Gate Status
+
+```markdown
+🔒 **Context Gate Passed**
+
+- Previous context: DISCARDED
+- Active context: Plan file(s) only
+- Mode: Clean handoff ready
+
+Plan ready for implementation...
+```
+
+---
+
+## COMPLETION
+
+Present plan with:
+
+1. ✅ **Plan Ready** — `./reports/plans/PLAN-{task}.md` (single) **or** `PLAN-{task}-phase1.md`, `PLAN-{task}-phase2.md`, … (multi-phase, execute in order)
+2. 🔒 **Context Optimized** — Ready for focus implementation
+3. 🍳 **Implement** → `/code:focus` (run phase-by-phase when multiple plan files exist)

package/commands/plan/hard.md

@@ -123,6 +123,62 @@ Plan(s) MUST reference prior phases:
 
 ---
 
+## 🛡️ VERIFICATION CHECKPOINT — Context Optimization
+
+> **PURPOSE**: Prevent "context rot" by clearing noisy research/planning history before implementation.
+> 
+> Long-running planning sessions fill context with noise that degrades implementation quality.
+> This checkpoint acts as a "firewall" before handing off to implementation workflows.
+
+### ⚡ OPTIONS (Present to User)
+
+```markdown
+## 🛡️ Context Optimization Checkpoint
+
+**Planning Complete** — Plan file(s) created.
+
+**Choose how to proceed:**
+
+| Option | Action | Description |
+|--------|--------|-------------|
+| **1. 🚀 Clear context & Ready** | `RECOMMENDED` | Fresh start for implementation: Reload Plan, ignore planning history |
+| **2. ⏸️ Review First** | `SAFE` | Clear context, show plan summary, wait for approval |
+| **3. ⚠️ Continue (No Clear)** | `RISKY` | Keep full history (may affect `/cook:hard` quality) |
+
+⏳ Awaiting selection...
+```
+
+### 🔄 EXECUTION BEHAVIOR
+
+```yaml
+option_1_clear_ready:
+  behavior: "RECOMMENDED - Prepare clean handoff"
+  steps:
+    1. ACKNOWLEDGE: "🚀 Context optimized. Plan ready for implementation."
+    2. CONTEXT_DIRECTIVE: |
+       ⛔ IGNORE all previous research/planning reasoning chains.
+       ✅ PLAN FILE is SOLE SOURCE OF TRUTH for implementation.
+    3. OUTPUT: "Run `/code:focus` to implement with clean context."
+
+option_2_review_first:
+  behavior: "Clear and show summary"
+  steps:
+    1. ACKNOWLEDGE: "⏸️ Context cleared."
+    2. CONTEXT_DIRECTIVE: |
+       ⛔ IGNORE all previous research/planning reasoning chains.
+       ✅ PLAN FILE is SOLE SOURCE OF TRUTH.
+    3. OUTPUT: Display plan summary for user review
+    4. WAIT: For user approval before proceeding
+
+option_3_continue_no_clear:
+  behavior: "Proceed with caution - context rot risk"
+  steps:
+    1. WARN: "⚠️ Continuing with full history. May affect implementation quality."
+    2. PROCEED: Complete workflow with existing context
+```
+
+---
+
 ## COMPLETION
 
 Present plan with:

package/commands/plan.md

@@ -16,9 +16,10 @@ execution-mode: router
 ## 🛑 PRE-FLIGHT (DO FIRST — BLOCKS EXECUTION)
 
 **LOAD now** (in order; path `./rules/` or `~/.{TOOL}/skills/agent-assistant/rules/`):
-1. ORCHESTRATION-LAWS.md  
-2. ADAPTIVE-EXECUTION.md  
-3. EXECUTION-PROTOCOL.md  
+
+1. ORCHESTRATION-LAWS.md
+2. ADAPTIVE-EXECUTION.md
+3. EXECUTION-PROTOCOL.md
 
 **⛔ Do not run any workflow phase until all are loaded.** Follow **all** rules in those files. Then run this file's ROUTING LOGIC, LOAD the chosen variant (e.g. plan/hard.md), and execute it.
 
@@ -33,6 +34,9 @@ IF task is clear (known approach, codebase-only):
 IF task is complex (research needed, architectural):
   → Route to /plan:hard
 
+IF task is complex AND clean implementation handoff is critical:
+  → Route to /plan:focus
+
 IF unsure:
   → Default to /plan:fast
 ```
@@ -41,10 +45,11 @@ IF unsure:
 
 ## AVAILABLE ROUTES
 
-| Route        | When to Use                     |
-| ------------ | ------------------------------- |
-| `/plan:fast` | Quick planning without research |
-| `/plan:hard` | Full planning with research     |
+| Route         | When to Use                                          |
+| ------------- | ---------------------------------------------------- |
+| `/plan:fast`  | Quick planning without research                      |
+| `/plan:hard`  | Full planning with research                          |
+| `/plan:focus` | Full planning with **enforced context optimization** |
 
 ---
 
@@ -59,6 +64,7 @@ IF unsure:
 
 1. ⚡ **Fast** → `/plan:fast` — Quick plan
 2. ⚡⚡⚡ **Hard** → `/plan:hard` — Full research-backed plan
+3. 🎯 **Focus** → `/plan:focus` — Full plan with **automatic context clearing** (clean implementation handoff)
 
 ⏳ Awaiting selection...
 ```