@namch/agent-assistant 1.2.1 → 1.2.2

package/commands/plan/focus.md

@@ -128,59 +128,6 @@ Plan(s) MUST reference prior phases:
 
 ---
 
-## 🛡️ 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

package/commands/plan/hard.md

@@ -125,62 +125,6 @@ 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/team.md

@@ -308,28 +308,6 @@ FOR EACH requirement in BRAINSTORM-{task}.md:
 
 ---
 
-## 🛡️ VERIFICATION CHECKPOINT
-
-> **⛔ BLOCKING**: Load Context Gate protocol NOW before proceeding.
->
-> **LOAD**: `rules/CONTEXT-GATE.md` — Execute HARD MODE protocol
-
-```yaml
-context_gate_execution:
-  mode: "HARD (User Choice)"
-  trigger: "After Phase 4 completes with PASS"
-  protocol: "Follow rules/CONTEXT-GATE.md § HARD MODE"
-  variant_adjustments:
-    plan_file: "PLAN-{task}.md"
-    qa_report: "QA-PLAN-{task}.md"
-    mailbox: "MAILBOX-{date}.md contains full debate history"
-    remaining_action: "Hand off to implementation workflow"
-```
-
-**DO NOT present completion until user selects option.**
-
----
-
 ## ✅ COMPLETION
 
 ```markdown

package/commands/report/focus.md

@@ -65,58 +65,6 @@ One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in
 
 ---
 
-## 🛡️ FOCUS CONTEXT GATE — Automatic Context Optimization
-
-> **⚡ FOCUS MODE**: This checkpoint executes automatically. NO user input required.
->
-> **PURPOSE**: Ensure report is based ONLY on facts, not conversation hallucinations.
-> This acts as a mandatory "firewall" before analysis begins.
-
-### 🔒 AUTOMATIC EXECUTION (NO PROMPT)
-
-```yaml
-focus_context_gate:
-  mode: "AUTOMATIC - No user interaction"
-  behavior: "Force Clear context & Analyze"
-
-  execution:
-    1. ANNOUNCE: |
-      ## 🛡️ Focus Context Gate — Automatic
-
-      ✅ **Target Defined**: Analysis target identified.
-      🔒 **Focus Mode**: Automatically clearing context for objective analysis.
-
-      ⚡ Executing: **Clear context & Analyze**...
-
-    2. CONTEXT_DIRECTIVE: |
-      ╔══════════════════════════════════════════════════════════════════╗
-      ║  ⛔ MANDATORY CONTEXT RESET — FOCUS MODE                         ║
-      ╠══════════════════════════════════════════════════════════════════╣
-      ║  IGNORE: All previous chat assumptions, unverified claims,       ║
-      ║          and subjective contextual bias.                         ║
-      ║                                                                  ║
-      ║  SOLE SOURCE OF TRUTH: The actual Codebase and Documentation.    ║
-      ║                                                                  ║
-      ║  PROCEED: Begin Analysis phase with FRESH, OBJECTIVE mindset.    ║
-      ╚══════════════════════════════════════════════════════════════════╝
-
-    3. LOAD: Read specified target files as if seeing them for the first time
-
-    4. PROCEED: Start Phase 1 (Objective Analysis) immediately
-```
-
-### 📋 Post-Gate Status
-
-```markdown
-🔒 **Context Gate Passed**
-
-- Previous context: DISCARDED
-- Active context: Target files / codebase only
-- Mode: Fresh objective analysis
-
-Proceeding to Phase 1...
-```
-
 ---
 
 ## 🎭 Phase 1: RESEARCH (AUDIT CRITERIA)

package/commands/test/focus.md

@@ -65,29 +65,6 @@ One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in
 | Exit  | Strategy defined, test types identified |
 
 ---
-
-## 🛡️ CONTEXT GATE CHECKPOINT
-
-> **⛔ BLOCKING**: Load Context Gate protocol NOW before proceeding.
->
-> **LOAD**: `rules/CONTEXT-GATE.md` — Execute FOCUS MODE (Test variant)
->
-> This is a MANDATORY checkpoint. Cannot skip or bypass.
-
-### ⚡ EXECUTION
-
-```yaml
-context_gate_execution:
-  mode: "FOCUS (Automatic)"
-  trigger: "After Phase 1 (Test Strategy) completes"
-  protocol: "Follow rules/CONTEXT-GATE.md § FOCUS MODE § test_focus_variant"
-  
-  variant_adjustments:
-    plan_source: "Finalized test strategy from Phase 1"
-    remaining_phases: "Phase 2 → 3 → 4 → 5"
-```
-
-**DO NOT proceed to Phase 2 until Context Gate completes.**
 - Rejected approaches
 - Planning noise
 - Chat history

package/commands/test/hard.md

@@ -63,63 +63,6 @@ One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in
 
 ---
 
-## 🛡️ VERIFICATION CHECKPOINT — Context Optimization
-
-> **PURPOSE**: Prevent "context rot" by clearing strategy discussion before test execution.
-> 
-> Test strategy discussions may include rejected approaches that can confuse execution.
-> This checkpoint ensures clean handoff to test execution phases.
-
-### ⚡ OPTIONS (Present to User)
-
-```markdown
-## 🛡️ Context Optimization Checkpoint
-
-**Test Strategy Complete** — Strategy defined, ready for execution.
-
-**Choose how to proceed:**
-
-| Option | Action | Description |
-|--------|--------|-------------|
-| **1. 🚀 Clear context & Execute** | `RECOMMENDED` | Fresh start: Focus on strategy, ignore discussion history |
-| **2. ⏸️ Review Strategy** | `SAFE` | Clear context, show strategy summary, wait for approval |
-| **3. ⚠️ Continue (No Clear)** | `RISKY` | Keep full history (may affect test focus) |
-
-⏳ Awaiting selection...
-```
-
-### 🔄 EXECUTION BEHAVIOR
-
-```yaml
-option_1_clear_execute:
-  behavior: "RECOMMENDED - Clean execution"
-  steps:
-    1. ACKNOWLEDGE: "🚀 Context optimized. Executing test strategy."
-    2. CONTEXT_DIRECTIVE: |
-       ⛔ IGNORE strategy discussion and rejected approaches.
-## 🛡️ VERIFICATION CHECKPOINT
-
-> **⛔ BLOCKING**: Load Context Gate protocol NOW before proceeding.
->
-> **LOAD**: `rules/CONTEXT-GATE.md` — Execute HARD MODE (Test variant)
->
-> This is a MANDATORY checkpoint. Cannot skip or bypass.
-
-### ⚡ EXECUTION
-
-```yaml
-context_gate_execution:
-  mode: "HARD (User Choice)"
-  trigger: "After Phase 1 (Test Strategy) completes"
-  protocol: "Follow rules/CONTEXT-GATE.md § HARD MODE § test_hard_variant"
-  
-  variant_adjustments:
-    plan_source: "Finalized test strategy from Phase 1"
-    remaining_phases: "Phase 2 → 3 → 4 → 5"
-```
-
-**DO NOT proceed to Phase 2 until user selects option.**
-
 ---
 
 ## 🎭 Phase 2: DEPENDENCY MAPPING

package/commands/test/team.md

@@ -148,13 +148,6 @@ Format: rules/PHASES.md § Phase output + rules/TEAMS.md § Golden Triangle Phas
 
 ---
 
-## 🛡️ VERIFICATION CHECKPOINT
-
-> **⛔ BLOCKING**: `rules/CONTEXT-GATE.md` — HARD MODE. Prevents context rot between planning and implementation.
-> Trigger: After Phase 2 completes. Plan file: `TEST-PLAN-{scope}.md`. Remaining: Phase 3 → 4.
-
-**DO NOT proceed to Phase 3 until user selects option.**
-
 ---
 
 ## 🎭 Phase 3: TEST IMPLEMENTATION — 🔺 GOLDEN TRIANGLE (CRITICAL)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@namch/agent-assistant",
-  "version": "1.2.1",
+  "version": "1.2.2",
   "description": "Multi-agent orchestration framework for AI coding assistants (Cursor, Copilot, Antigravity, Claude Code, Codex) with Hybrid Skill Orchestration Layer (HSOL).",
   "main": "cli/install.js",
   "bin": {

package/rules/TEAMS.md

@@ -417,7 +417,7 @@ IS task complex with multiple concerns (security + performance + correctness)?
 |---------|----------------|--------|------|
 | `:fast` | Single agent | 1 | Speed priority, simple tasks |
 | `:hard` | Single agent | 1 | Standard quality, focused tasks |
-| `:focus` | Single agent + context gate | 1 | Clean execution, noise reduction |
+| `:focus` | Single agent | 1 | Clean execution, noise reduction |
 | `:team` | Golden Triangle | 3 | Maximum quality, adversarial review, complex tasks |
 
 **⛔ Do NOT use `:team` for**: