@namch/agent-assistant 1.0.3 → 1.1.0

package/commands/ask/fast.md

@@ -17,17 +17,19 @@ execution-mode: execute
 
 **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. CORE.md — Identity, Laws, Routing
+2. PHASES.md — Phase Execution
+3. AGENTS.md — Tiered Execution
 
 **⛔ Do not run Phase 1 until all are loaded.** Follow **all** rules in those files; they override any conflicting instructions in this file.
 
+**Skills Resolution**: When delegating, load `SKILLS.md` on-demand. Fast variant uses matrix-only (no dynamic discovery for speed optimization).
+
 ---
 
 ## 🔀 TIERED EXECUTION PROTOCOL (MANDATORY)
 
-> **Reference**: `{RULES_PATH}/ADAPTIVE-EXECUTION.md`
+> **Reference: AGENTS.md (Tiered Execution)`
 
 ```yaml
 tiered_execution:

package/commands/ask/hard.md

@@ -17,17 +17,19 @@ execution-mode: execute
 
 **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. CORE.md — Identity, Laws, Routing
+2. PHASES.md — Phase Execution
+3. AGENTS.md — Tiered Execution
 
 **⛔ Do not run Phase 1 until all are loaded.** Follow **all** rules in those files; they override any conflicting instructions in this file.
 
+**Skills Resolution**: When delegating, load `SKILLS.md` on-demand for fitness calculation and dynamic discovery (hard/focus variants enable find-skills).
+
 ---
 
 ## 🔀 TIERED EXECUTION PROTOCOL (MANDATORY)
 
-> **Reference**: `{RULES_PATH}/ADAPTIVE-EXECUTION.md`
+> **Reference: AGENTS.md (Tiered Execution)`
 
 ```yaml
 tiered_execution:

package/commands/ask.md

@@ -16,9 +16,9 @@ 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. CORE.md — Identity, Laws, Routing  
+2. PHASES.md — Phase Execution  
+3. AGENTS.md — Tiered Execution  
 
 **⛔ 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.
 

package/commands/auto.md

@@ -16,9 +16,9 @@ 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. CORE.md — Identity, Laws, Routing  
+2. PHASES.md — Phase Execution  
+3. AGENTS.md — Tiered Execution  
 
 **⛔ 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.
 

package/commands/brainstorm/fast.md

@@ -17,17 +17,19 @@ execution-mode: execute
 
 **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. CORE.md — Identity, Laws, Routing
+2. PHASES.md — Phase Execution
+3. AGENTS.md — Tiered Execution
 
 **⛔ Do not run Phase 1 until all are loaded.** Follow **all** rules in those files; they override any conflicting instructions in this file.
 
+**Skills Resolution**: When delegating, load `SKILLS.md` on-demand. Fast variant uses matrix-only (no dynamic discovery for speed optimization).
+
 ---
 
 ## 🔀 TIERED EXECUTION PROTOCOL (MANDATORY)
 
-> **Reference**: `{RULES_PATH}/ADAPTIVE-EXECUTION.md`
+> **Reference: AGENTS.md (Tiered Execution)`
 
 ```yaml
 tiered_execution:

package/commands/brainstorm/hard.md

@@ -17,17 +17,19 @@ execution-mode: execute
 
 **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. CORE.md — Identity, Laws, Routing
+2. PHASES.md — Phase Execution
+3. AGENTS.md — Tiered Execution
 
 **⛔ Do not run Phase 1 until all are loaded.** Follow **all** rules in those files; they override any conflicting instructions in this file.
 
+**Skills Resolution**: When delegating, load `SKILLS.md` on-demand for fitness calculation and dynamic discovery (hard/focus variants enable find-skills).
+
 ---
 
 ## 🔀 TIERED EXECUTION PROTOCOL (MANDATORY)
 
-> **Reference**: `{RULES_PATH}/ADAPTIVE-EXECUTION.md`
+> **Reference: AGENTS.md (Tiered Execution)`
 
 ```yaml
 tiered_execution:

package/commands/brainstorm.md

@@ -16,9 +16,9 @@ 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. CORE.md — Identity, Laws, Routing  
+2. PHASES.md — Phase Execution  
+3. AGENTS.md — Tiered Execution  
 
 **⛔ 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.
 

package/commands/code/fast.md

@@ -17,17 +17,19 @@ execution-mode: execute
 
 **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. CORE.md — Identity, Laws, Routing
+2. PHASES.md — Phase Execution
+3. AGENTS.md — Tiered Execution
 
 **⛔ Do not run Phase 1 until all are loaded.** Follow **all** rules in those files; they override any conflicting instructions in this file.
 
+**Skills Resolution**: When delegating, load `SKILLS.md` on-demand. Fast variant uses matrix-only (no dynamic discovery for speed optimization).
+
 ---
 
 ## 🔀 TIERED EXECUTION PROTOCOL (MANDATORY)
 
-> **Reference**: `{RULES_PATH}/ADAPTIVE-EXECUTION.md`
+> **Reference: AGENTS.md (Tiered Execution)`
 
 ```yaml
 tiered_execution:

package/commands/code/focus.md

@@ -20,17 +20,39 @@ execution-mode: execute
 
 **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. CORE.md — Identity, Laws, Routing
+2. PHASES.md — Phase Execution
+3. AGENTS.md — Tiered Execution
 
 **⛔ Do not run Phase 1 until all are loaded.** Follow **all** rules in those files; they override any conflicting instructions in this file.
 
+**Skills Resolution**: When delegating, load `SKILLS.md` on-demand for fitness calculation and dynamic discovery (focus variant enables find-skills for superior skill matching).
+
+---
+
+## 📌 PLAN-ALREADY-PROVIDED: SKIP REDUNDANT PHASES
+
+**Before starting Phase 1**, resolve whether the user is **coding from an existing plan**. If yes, **do not** run research, scout, or brainstorm.
+
+### Detection
+
+- User message references a plan: e.g. `@plan`, `@PLAN-...`, path like `./reports/plans/PLAN-{name}.md`, or phrases like "according to plan", "follow the plan", "code from plan", "implement per plan".
+- Or a plan file already exists for this task at `./reports/plans/PLAN-{task}.md` (derive `{task}` from `$ARGUMENTS` or from the referenced file name).
+
+### Resolution
+
+1. **CHECK**: Does a valid plan file exist (user-provided path or `./reports/plans/PLAN-{task}.md`)?
+2. **IF YES**:
+   - **SKIP** Phase 1 (Requirements/Brainstorm), Phase 2 (Scout), Phase 3 (Planning).
+   - **ANNOUNCE**: "✅ Plan provided/found — skipping research, scout, and planning. Proceeding to implementation."
+   - **GO TO**: Strict Context Gate (automatic) → then Phase 4 (Implementation) → Phase 5 (Testing) → Phase 6 (Review).
+3. **IF NO**: Run phases in order: Phase 1 → 2 → 3 → Context Gate → 4 → 5 → 6.
+
 ---
 
 ## 🔀 TIERED EXECUTION PROTOCOL (MANDATORY)
 
-> **Reference**: `{RULES_PATH}/ADAPTIVE-EXECUTION.md`
+> **Reference: AGENTS.md (Tiered Execution)`
 
 ```yaml
 tiered_execution:
@@ -160,56 +182,30 @@ One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in
 
 ---
 
-## 🛡️ STRICT CONTEXT GATE — Automatic Context Optimization
+## 🛡️ CONTEXT GATE CHECKPOINT
 
-> **⚡ FOCUS MODE**: This checkpoint executes automatically. NO user input required.
+> **⛔ BLOCKING**: Load Context Gate protocol NOW before proceeding.
 >
-> **PURPOSE**: Prevent "context rot" by forcibly clearing noisy planning history.
-> This acts as a mandatory "firewall" between Planning and Implementation phases.
+> **LOAD**: `rules/CONTEXT-GATE.md` — Execute FOCUS MODE protocol
+>
+> This is a MANDATORY checkpoint. Cannot skip or bypass.
 
-### 🔒 AUTOMATIC EXECUTION (NO PROMPT)
+### ⚡ EXECUTION
 
 ```yaml
-strict_context_gate:
-  mode: "AUTOMATIC - No user interaction"
-  behavior: "Force Clear context & Auto-Implement"
-
-  execution:
-    1. ANNOUNCE: |
-      ## 🛡️ Strict Context Gate — Automatic
-
-      ✅ **Plan Complete**: `./reports/plans/PLAN-{task}.md`
-      🔒 **Focus Mode**: Automatically clearing context for implementation.
-
-      ⚡ Executing: **Clear context & Auto-Implement**...
-
-    2. CONTEXT_DIRECTIVE: |
-      ╔══════════════════════════════════════════════════════════════════╗
-      ║  ⛔ MANDATORY CONTEXT RESET — FOCUS MODE                        ║
-      ╠══════════════════════════════════════════════════════════════════╣
-      ║  IGNORE: All previous chat messages, reasoning chains,           ║
-      ║          brainstorming discussions, research explorations,       ║
-      ║          rejected alternatives, and intermediate thinking.       ║
-      ║                                                                  ║
-      ║  SOLE SOURCE OF TRUTH: `./reports/plans/PLAN-{task}.md`          ║
-      ║                                                                  ║
-      ║  PROCEED: Begin Implementation phase with FRESH context mindset. ║
-      ║           Treat this as a NEW conversation starting from Plan.   ║
-      ╚══════════════════════════════════════════════════════════════════╝
-
-    3. LOAD: Read Plan file completely as if seeing it for the first time
-
-    4. PROCEED: Start Phase 4 (Implementation) immediately
+context_gate_execution:
+  mode: "FOCUS (Automatic)"
+  trigger: "After Phase 3 (Planning) completes"
+  protocol: "Follow rules/CONTEXT-GATE.md § FOCUS MODE"
+  
+  variant_adjustments:
+    remaining_phases: "Phase 4 → 5 → 6"
+    plan_file: "./reports/plans/PLAN-{task}.md"
 ```
 
-### 📋 Post-Gate Status
-
-```markdown
-🔒 **Context Gate Passed**
+**DO NOT proceed to Phase 4 until Context Gate completes.**
 
-- Previous context: DISCARDED
-- Active context: Plan file only
-- Mode: Fresh implementation start
+Mode: Fresh implementation start
 
 Proceeding to Implementation...
 ```

package/commands/code/hard.md

@@ -17,17 +17,39 @@ execution-mode: execute
 
 **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. CORE.md — Identity, Laws, Routing
+2. PHASES.md — Phase Execution
+3. AGENTS.md — Tiered Execution
 
 **⛔ Do not run Phase 1 until all are loaded.** Follow **all** rules in those files; they override any conflicting instructions in this file.
 
+**Skills Resolution**: When delegating, load `SKILLS.md` on-demand for fitness calculation and dynamic discovery (hard/focus variants enable find-skills).
+
+---
+
+## 📌 PLAN-ALREADY-PROVIDED: SKIP REDUNDANT PHASES
+
+**Before starting Phase 1**, resolve whether the user is **coding from an existing plan**. If yes, **do not** run research, scout, or brainstorm.
+
+### Detection
+
+- User message references a plan: e.g. `@plan`, `@PLAN-...`, path like `./reports/plans/PLAN-{name}.md`, or phrases like "according to plan", "follow the plan", "code from plan", "implement per plan".
+- Or a plan file already exists for this task at `./reports/plans/PLAN-{task}.md` (derive `{task}` from `$ARGUMENTS` or from the referenced file name).
+
+### Resolution
+
+1. **CHECK**: Does a valid plan file exist (user-provided path or `./reports/plans/PLAN-{task}.md`)?
+2. **IF YES**:
+   - **SKIP** Phase 1 (Requirements/Brainstorm), Phase 2 (Scout), Phase 3 (Planning).
+   - **ANNOUNCE**: "✅ Plan provided/found — skipping research, scout, and planning. Proceeding to implementation."
+   - **GO TO**: Verification Checkpoint (Context Optimization) → then Phase 4 (Implementation) → Phase 5 (Testing) → Phase 6 (Review).
+3. **IF NO**: Run phases in order: Phase 1 → 2 → 3 → Checkpoint → 4 → 5 → 6.
+
 ---
 
 ## 🔀 TIERED EXECUTION PROTOCOL (MANDATORY)
 
-> **Reference**: `{RULES_PATH}/ADAPTIVE-EXECUTION.md`
+> **Reference: AGENTS.md (Tiered Execution)`
 
 ```yaml
 tiered_execution:
@@ -220,56 +242,29 @@ One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in
 > Long-running planning 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
+## 🛡️ VERIFICATION CHECKPOINT
 
-**Planning Complete** — Plan file created at: `./reports/plans/PLAN-{task}.md`
+> **⛔ BLOCKING**: Load Context Gate protocol NOW before proceeding.
+>
+> **LOAD**: `rules/CONTEXT-GATE.md` — Execute HARD MODE protocol
+>
+> This is a MANDATORY checkpoint. Cannot skip or bypass.
 
-**Choose how to proceed with implementation:**
-
-| Option | Action | Description |
-|--------|--------|-------------|
-| **1. 🚀 Clear context & Auto-Implement** | `RECOMMENDED` | Fresh start: Reload Plan file, ignore chat history, begin implementation 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
+### ⚡ EXECUTION
 
 ```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: `./reports/plans/PLAN-{task}.md` as SOLE SOURCE OF TRUTH.
-       ✅ PROCEED: Begin Phase 4 (Implementation) immediately.
-    3. LOAD: Read Plan file completely
-    4. 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: `./reports/plans/PLAN-{task}.md` as SOLE SOURCE OF TRUTH.
-    3. OUTPUT: "Ready for 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
-    3. MONITOR: Watch for signs of context confusion
+context_gate_execution:
+  mode: "HARD (User Choice)"
+  trigger: "After Phase 3 (Planning) completes"
+  protocol: "Follow rules/CONTEXT-GATE.md § HARD MODE"
+  
+  variant_adjustments:
+    plan_file: "./reports/plans/PLAN-{task}.md"
+    remaining_phases: "Phase 4 → 5 → 6"
 ```
 
+**DO NOT proceed to Phase 4 until user selects option.**
+
 ---
 
 ## 🎭 Phase 4: IMPLEMENTATION

package/commands/code.md

@@ -17,9 +17,9 @@ execution-mode: router
 
 **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. CORE.md — Identity, Laws, Routing
+2. PHASES.md — Phase Execution
+3. AGENTS.md — Tiered Execution
 
 **⛔ 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.
 
@@ -28,6 +28,9 @@ execution-mode: router
 ## ROUTING LOGIC
 
 ```
+IF user references an existing plan (@plan, @PLAN-..., path to PLAN-*.md, or "according to plan" / "follow the plan"):
+  → Route to /code:hard or /code:focus (workflow will SKIP research, scout, brainstorm and go straight to implementation)
+
 IF task is simple (clear requirements, single file):
   → Route to /code:fast
 

package/commands/cook/fast.md

@@ -17,12 +17,14 @@ execution-mode: execute
 
 **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. CORE.md — Identity, Laws, Routing
+2. PHASES.md — Phase Execution
+3. AGENTS.md — Tiered Execution
 
 **⛔ Do not run Phase 1 until all are loaded.** Follow **all** rules in those files; they override any conflicting instructions in this file.
 
+**Skills Resolution**: When delegating, load `SKILLS.md` on-demand. Fast variant uses matrix-only (no dynamic discovery for speed optimization).
+
 ---
 
 ## 🔀 TIERED EXECUTION

package/commands/cook/focus.md

@@ -20,17 +20,19 @@ execution-mode: execute
 
 **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. CORE.md — Identity, Laws, Routing
+2. PHASES.md — Phase Execution
+3. AGENTS.md — Tiered Execution
 
 **⛔ Do not run Phase 1 until all are loaded.** Follow **all** rules in those files; they override any conflicting instructions in this file.
 
+**Skills Resolution**: When delegating, load `SKILLS.md` on-demand for fitness calculation and dynamic discovery (focus variant enables find-skills for superior skill matching).
+
 ---
 
 ## 🔀 TIERED EXECUTION
 
-> Reference: `{RULES_PATH}/ADAPTIVE-EXECUTION.md`
+> Reference: AGENTS.md (Tiered Execution)`
 
 | Tier       | When                          | Action                       |
 | ---------- | ----------------------------- | ---------------------------- |
@@ -76,7 +78,7 @@ 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.
+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/PHASES.md § Phase output structure.
 
 ---
 
@@ -138,59 +140,28 @@ One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in
 
 ---
 
-## 🛡️ STRICT CONTEXT GATE — Automatic Context Optimization
+## 🛡️ CONTEXT GATE CHECKPOINT
 
-> **⚡ FOCUS MODE**: This checkpoint executes automatically. NO user input required.
+> **⛔ BLOCKING**: Load Context Gate protocol NOW before proceeding.
+>
+> **LOAD**: `rules/CONTEXT-GATE.md` — Execute FOCUS MODE protocol
 >
-> **PURPOSE**: Prevent "context rot" by forcibly clearing noisy planning history.
-> This acts as a mandatory "firewall" between Planning and Implementation phases.
+> This is a MANDATORY checkpoint. Cannot skip or bypass.
 
-### 🔒 AUTOMATIC EXECUTION (NO PROMPT)
+### ⚡ EXECUTION
 
 ```yaml
-strict_context_gate:
-  mode: "AUTOMATIC - No user interaction"
-  behavior: "Force Clear context & Auto-Implement"
-
-  execution:
-    1. ANNOUNCE: |
-      ## 🛡️ Strict Context Gate — Automatic
-
-      ✅ **Plan Complete**: `./reports/plans/PLAN-{feature}.md`
-      🔒 **Focus Mode**: Automatically clearing context for implementation.
-
-      ⚡ Executing: **Clear context & Auto-Implement**...
-
-    2. CONTEXT_DIRECTIVE: |
-      ╔══════════════════════════════════════════════════════════════════╗
-      ║  ⛔ MANDATORY CONTEXT RESET — FOCUS MODE                         ║
-      ╠══════════════════════════════════════════════════════════════════╣
-      ║  IGNORE: All previous chat messages, reasoning chains,           ║
-      ║          brainstorming discussions, research explorations,       ║
-      ║          rejected alternatives, and intermediate thinking.       ║
-      ║                                                                  ║
-      ║  SOLE SOURCE OF TRUTH: `./reports/plans/PLAN-{feature}.md`       ║
-      ║                                                                  ║
-      ║  PROCEED: Begin Implementation phase with FRESH context mindset. ║
-      ║           Treat this as a NEW conversation starting from Plan.   ║
-      ╚══════════════════════════════════════════════════════════════════╝
-
-    3. LOAD: Read Plan file completely as if seeing it for the first time
-
-    4. PROCEED: Start Phase 6 (Implementation) immediately
+context_gate_execution:
+  mode: "FOCUS (Automatic)"
+  trigger: "After Phase 5 (Planning) completes"
+  protocol: "Follow rules/CONTEXT-GATE.md § FOCUS MODE"
+  
+  variant_adjustments:
+    remaining_phases: "Phase 6 → 7 → 8"
+    plan_file: "./reports/plans/PLAN-{feature}.md"
 ```
 
-### 📋 Post-Gate Status
-
-```markdown
-🔒 **Context Gate Passed**
-
-- Previous context: DISCARDED
-- Active context: Plan file only
-- Mode: Fresh implementation start
-
-Proceeding to Implementation...
-```
+**DO NOT proceed to Phase 6 until Context Gate completes.**
 
 ---