@namch/agent-assistant 1.0.3 → 1.1.0

package/commands/cook/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
 
-> Reference: `{RULES_PATH}/ADAPTIVE-EXECUTION.md`
+> Reference: AGENTS.md (Tiered Execution)`
 
 | Tier       | When                          | Action                       |
 | ---------- | ----------------------------- | ---------------------------- |
@@ -72,7 +74,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.
 
 ---
 
@@ -134,63 +136,29 @@ One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in
 
 ---
 
-## 🛡️ VERIFICATION CHECKPOINT — Context Optimization
+## 🛡️ VERIFICATION CHECKPOINT
 
-> **PURPOSE**: Prevent "context rot" by clearing noisy planning history before implementation.
+> **⛔ BLOCKING**: Load Context Gate protocol NOW before proceeding.
 >
-> 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
-
-**Planning Complete** — Plan file created at: `./reports/plans/PLAN-{feature}.md`
-
-**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...
-```
+> **LOAD**: `rules/CONTEXT-GATE.md` — Execute HARD MODE protocol
+>
+> This is a MANDATORY checkpoint. Cannot skip or bypass.
 
-### 🔄 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-{feature}.md` as SOLE SOURCE OF TRUTH.
-      ✅ PROCEED: Begin Phase 6 (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-{feature}.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 6 with existing context
-    3. MONITOR: Watch for signs of context confusion
+context_gate_execution:
+  mode: "HARD (User Choice)"
+  trigger: "After Phase 5 (Planning) completes"
+  protocol: "Follow rules/CONTEXT-GATE.md § HARD MODE"
+  
+  variant_adjustments:
+    plan_file: "PLAN-{feature}.md"
+    remaining_phases: "Phase 6 → 7 → 8"
 ```
 
+**DO NOT proceed to Phase 6 until user selects option.**
+
 ---
 
 ## 🎭 Phase 6: IMPLEMENTATION

package/commands/cook.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.
 

package/commands/debug/fast.md

@@ -16,12 +16,14 @@ execution-mode: execute
 ## 🛑 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  
+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/debug/focus.md

@@ -20,12 +20,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 for fitness calculation and dynamic discovery (focus variant enables find-skills for superior skill matching).
+
 ---
 
 ## 🔀 TIERED EXECUTION
@@ -90,45 +92,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 (Debug variant)
 >
-> **PURPOSE**: Prevent "context rot" by forcibly clearing noisy debugging history.
-> This acts as a mandatory "firewall" before handoff to fix workflows.
+> 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 & Fix"
-
-  execution:
-    1. ANNOUNCE: |
-      ## 🛡️ Strict Context Gate — Automatic
-
-      ✅ **Debug Complete**: Root cause identified, fix strategy designed.
-      🔒 **Focus Mode**: Automatically clearing context for fix handoff.
-
-      ⚡ Executing: **Clear context & Fix**...
-
-    2. CONTEXT_DIRECTIVE: |
-      ╔══════════════════════════════════════════════════════════════════╗
-      ║  ⛔ MANDATORY CONTEXT RESET — FOCUS MODE                        ║
-      ╠══════════════════════════════════════════════════════════════════╣
-      ║  IGNORE: All debugging hypotheses, failed investigation paths,  ║
-      ║          rejected theories, and intermediate reasoning.         ║
-      ║                                                                  ║
-      ║  SOLE SOURCE OF TRUTH: Root cause + Fix strategy.               ║
-      ║                                                                  ║
-      ║  HANDOFF: Ready for `/fix:focus` implementation.               ║
-      ║           Fix should treat root cause as fresh context.         ║
-      ╚══════════════════════════════════════════════════════════════════╝
-
-    3. OUTPUT: Root cause + Fix strategy summary
-
-    4. PROCEED: To COMPLETION
+context_gate_execution:
+  mode: "FOCUS (Automatic)"
+  trigger: "After Phase 4 (Solution Design) completes"
+  protocol: "Follow rules/CONTEXT-GATE.md § FOCUS MODE § debug_focus_variant"
+  
+  variant_adjustments:
+    reload_type: "OUTPUT_ESSENTIAL_CONTEXT"
+    handoff_to: "/fix:focus"
+```
+
+**Note**: Debug outputs context for fix handoff, doesn't implement directly.
 ```
 
 ### 📋 Post-Gate Status
@@ -136,9 +121,19 @@ strict_context_gate:
 ```markdown
 🔒 **Context Gate Passed**
 
-- Previous context: DISCARDED
-- Active context: Root cause + Fix strategy only
-- Mode: Clean handoff ready
+## ✅ Output for Handoff:
+- User request (original issue verbatim)
+- Root cause summary with evidence
+- Fix strategy with rollback
+- Acceptance criteria for fix verification
+
+## ❌ Discarded:
+- Failed investigation hypotheses
+- Rejected theories
+- Debugging noise
+- Chat history
+
+Mode: Clean handoff ready
 
 Ready for fix implementation...
 ```

package/commands/debug/hard.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 for fitness calculation and dynamic discovery (hard/focus variants enable find-skills).
+
 ---
 
 ## 🔀 TIERED EXECUTION
@@ -122,22 +124,42 @@ option_1_clear_fix:
     2. CONTEXT_DIRECTIVE: |
        ⛔ IGNORE all debugging hypotheses and failed investigation paths.
        ✅ FIX STRATEGY is SOLE SOURCE OF TRUTH.
-    3. OUTPUT: "Run `/fix:focus` to implement with clean context."
-
-option_2_review_first:
-  behavior: "Clear and show summary"
-  steps:
-    1. ACKNOWLEDGE: "⏸️ Context cleared."
-    2. OUTPUT: Display root cause + fix strategy summary
-    3. WAIT: For user approval
+    3. OUTPUT_ESSENTIAL_CONTEXT: |
+       ## 📤 Essential Context for Fix Handoff
+       
+       Summarize these sections for `/fix:hard` to consume:
+       
+       1️⃣ **USER REQUEST (VERBATIM)**: 
+          - Quote the original issue description exactly as user stated
+          - This MUST be preserved for fix verification
+       
+       2️⃣ **ROOT CAUSE SUMMARY**:
+          - What is broken and why
+          - File(s) and line(s) involved
+          - Evidence that confirms root cause
+## 🛡️ VERIFICATION CHECKPOINT
+
+> **⛔ BLOCKING**: Load Context Gate protocol NOW before proceeding.
+>
+> **LOAD**: `rules/CONTEXT-GATE.md` — Execute HARD MODE (Debug variant)
+>
+> This is a MANDATORY checkpoint. Cannot skip or bypass.
+
+### ⚡ EXECUTION
 
-option_3_continue_no_clear:
-  behavior: "Proceed with caution"
-  steps:
-    1. WARN: "⚠️ Debug history retained. Watch for hypothesis drift."
-    2. PROCEED: Complete workflow with existing context
+```yaml
+context_gate_execution:
+  mode: "HARD (User Choice)"
+  trigger: "After Phase 4 (Solution Design) completes"
+  protocol: "Follow rules/CONTEXT-GATE.md § HARD MODE § debug_hard_variant"
+  
+  variant_adjustments:
+    output_type: "OUTPUT_ESSENTIAL_CONTEXT"
+    handoff_to: "/fix:hard"
 ```
 
+**Note**: Debug outputs context for fix handoff with user choice.
+
 ---
 
 ## COMPLETION

package/commands/debug.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/deploy/check.md

@@ -14,9 +14,9 @@ execution-mode: execute
 ## 🛑 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  
+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.
 
@@ -24,7 +24,7 @@ execution-mode: execute
 
 ## 🔀 TIERED EXECUTION PROTOCOL (MANDATORY)
 
-> **Reference**: `{RULES_PATH}/ADAPTIVE-EXECUTION.md`
+> **Reference: AGENTS.md (Tiered Execution)`
 
 ```yaml
 tiered_execution:

package/commands/deploy/preview.md

@@ -14,9 +14,9 @@ execution-mode: execute
 ## 🛑 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  
+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.
 
@@ -24,7 +24,7 @@ execution-mode: execute
 
 ## 🔀 TIERED EXECUTION PROTOCOL (MANDATORY)
 
-> **Reference**: `{RULES_PATH}/ADAPTIVE-EXECUTION.md`
+> **Reference: AGENTS.md (Tiered Execution)`
 
 ```yaml
 tiered_execution:

package/commands/deploy/production.md

@@ -14,9 +14,9 @@ execution-mode: execute
 ## 🛑 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  
+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.
 
@@ -24,7 +24,7 @@ execution-mode: execute
 
 ## 🔀 TIERED EXECUTION PROTOCOL (MANDATORY)
 
-> **Reference**: `{RULES_PATH}/ADAPTIVE-EXECUTION.md`
+> **Reference: AGENTS.md (Tiered Execution)`
 
 ```yaml
 tiered_execution:

package/commands/deploy/rollback.md

@@ -14,9 +14,9 @@ execution-mode: execute
 ## 🛑 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  
+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.
 
@@ -24,7 +24,7 @@ execution-mode: execute
 
 ## 🔀 TIERED EXECUTION PROTOCOL (MANDATORY)
 
-> **Reference**: `{RULES_PATH}/ADAPTIVE-EXECUTION.md`
+> **Reference: AGENTS.md (Tiered Execution)`
 
 ```yaml
 tiered_execution:

package/commands/deploy.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/design/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/design/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 PROTOCOL (MANDATORY)
 
-> **Reference**: `{RULES_PATH}/ADAPTIVE-EXECUTION.md`
+> **Reference: AGENTS.md (Tiered Execution)`
 
 ```yaml
 tiered_execution:
@@ -176,54 +178,36 @@ 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.
-> 
-> **PURPOSE**: Prevent "context rot" by forcibly clearing noisy design exploration history.
-> This acts as a mandatory "firewall" before review and implementation handoff.
+> **⛔ BLOCKING**: Load Context Gate protocol NOW before proceeding.
+>
+> **LOAD**: `rules/CONTEXT-GATE.md` — Execute FOCUS MODE (Design variant)
+>
+> 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 & Ready"
+context_gate_execution:
+  mode: "FOCUS (Automatic)"
+  trigger: "After Phase 4 (Design Creation) completes"
+  protocol: "Follow rules/CONTEXT-GATE.md § FOCUS MODE § design_focus_variant"
   
-  execution:
-    1. ANNOUNCE: |
-       ## 🛡️ Strict Context Gate — Automatic
-       
-       ✅ **Design Complete**: `./reports/designs/DESIGN-{request}.md`
-       🔒 **Focus Mode**: Automatically clearing context for review/implementation.
-       
-       ⚡ Executing: **Clear context & Ready**...
-    
-    2. CONTEXT_DIRECTIVE: |
-       ╔══════════════════════════════════════════════════════════════════╗
-       ║  ⛔ MANDATORY CONTEXT RESET — FOCUS  MODE                        ║
-       ╠══════════════════════════════════════════════════════════════════╣
-       ║  IGNORE: All design exploration, rejected alternatives,          ║
-       ║          iteration history, and intermediate reasoning.          ║
-       ║                                                                  ║
-       ║  SOLE SOURCE OF TRUTH: Design file in ./reports/designs/         ║
-       ║                                                                  ║
-       ║  PROCEED: Continue to Design Review with clean context.          ║
-       ║           Then handoff to implementation.                        ║
-       ╚══════════════════════════════════════════════════════════════════╝
-    
-    3. LOAD: Read Design file as if seeing it for the first time
-    
-    4. PROCEED: Continue to Phase 5 (Design Review)
+  variant_adjustments:
+    remaining_phases: "Phase 5 (Design Review) → Implementation Handoff"
+    deliverable_file: "./reports/designs/DESIGN-{request}.md"
 ```
 
-### 📋 Post-Gate Status
+**DO NOT proceed to Phase 5 until Context Gate completes.**
+
+## ❌ Discarded:
+- Design exploration noise
+- Rejected alternatives
+- Iteration history
+- Chat history
 
-```markdown
-🔒 **Context Gate Passed**
-- Previous context: DISCARDED
-- Active context: Design file only
-- Mode: Clean review start
+Mode: Clean review start
 
 Proceeding to Design Review...
 ```