@namch/agent-assistant 1.0.1 → 1.0.3

package/commands/report/fast.md

@@ -0,0 +1,71 @@
+---
+description: ⚡ Fast Report — Quick status updates and summaries
+version: "1.0"
+category: documentation
+execution-mode: execute
+---
+
+# /report:fast — Quick Status Report
+
+> **MISSION**: Generate concise, actionable status reports and summaries.
+>
+> Use for daily standups, progress checks, and high-level overviews.
+> For **update existing files** or **generate from template**, use `/report:hard` or `/report:focus`.
+
+<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) |
+
+**❌ Anti-Lazy**: Never use TIER 2 when TIER 1 tool available.
+
+---
+
+## ⛔ 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: INFORMATION GATHERING
+
+| Agent | `reporter`                               |
+| ----- | ---------------------------------------- |
+| Goal  | Scan current state and recent activities |
+| Exit  | Progress summarized, key sources scanned |
+
+---
+
+## 🎭 Phase 2: REPORT GENERATION
+
+| Agent | `reporter`                                                                 |
+| ----- | -------------------------------------------------------------------------- |
+| Goal  | Infer intent; if **create report** → generate concise status report        |
+| Exit  | Report with Summary, Key Changes, Next Steps — or recommend `/report:hard`/`/report:focus` if user intent is update/template |
+
+---
+
+## COMPLETION
+
+Present report:
+
+1. ✅ **Report Ready** — Displayed in chat
+2. 📄 **Save?** → If user wants to save: `./reports/general/REPORT-status-{YYYY-MM-DD}.md`

package/commands/report/focus.md

@@ -0,0 +1,156 @@
+---
+description: 🔒 Focused Report — Deep analysis with enforced context optimization
+version: "1.0"
+category: documentation
+execution-mode: execute
+---
+
+# /report:focus — Focused Deep Analysis Report
+
+> **MISSION**: Generate verifiable, objective output with **enforced context optimization** — report, update, or template.
+
+> This variant automatically clears context before analysis—no user prompt required.
+> Use when you want a "clean slate" audit or unbiased analysis. Reporter chooses: **create report**, **update existing files**, or **generate from template** per user intent.
+
+<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) |
+
+**❌ Anti-Lazy**: Never use TIER 2 when TIER 1 tool available.
+
+---
+
+## 📁 DELIVERABLES (Reporter chooses from user intent)
+
+| User intent | Reporter output |
+| ----------- | ---------------- |
+| **Create report** | `./reports/general/REPORT-FOCUS-{date}.md` or path user asked |
+| **Update existing** | **Edit** related files; do **not** create new report unless also asked |
+| **From template** | File(s) matching user format/template |
+
+| Agent      | When creating report                             |
+| ---------- | ------------------------------------------------- |
+| researcher | (optional) verification checklist                 |
+| scouter    | (optional) evidence output                        |
+| reporter   | Per table above — create / update / from template |
+
+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.
+
+---
+
+## 🛡️ 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)
+
+| Agent  | `researcher`                                          |
+| ------ | ----------------------------------------------------- |
+| Goal   | Research audit/report criteria and what to verify     |
+| Exit   | Verification checklist and report criteria defined    |
+
+---
+
+## 🎭 Phase 2: EVIDENCE COLLECTION
+
+| Agent  | `scouter`                       |
+| ------ | ------------------------------- |
+| Goal   | Gather raw, verifiable evidence |
+| Exit   | Factual state documented, no assumptions              |
+
+---
+
+## 🎭 Phase 3: VERIFICATION & OUTPUT (create / update / from template)
+
+| Agent       | `reporter`                                                                 |
+| ----------- | -------------------------------------------------------------------------- |
+| Prerequisite| **USE** Phase 1 criteria + Phase 2 evidence only                            |
+| Goal        | From **user intent**: synthesize into (1) new report, (2) **updates** to existing files, or (3) file(s) from template |
+| Output      | **Create**: `./reports/general/REPORT-FOCUS-{date}.md`. **Update**: edit related files. **Template**: file(s) matching user format. |
+| Exit        | Deliverable matches intent; every claim cited when creating report.       |
+
+---
+
+## COMPLETION
+
+Deliverable per **user intent**:
+
+1. ✅ **Create report** → `./reports/general/REPORT-FOCUS-{date}.md` (or path user asked)
+2. ✅ **Update existing** → Related files edited; list what was updated
+3. ✅ **From template** → File(s) matching user format; list path(s)
+4. 🕵️ **Audit** → `/review:focus` (optional)

package/commands/report/hard.md

@@ -0,0 +1,112 @@
+---
+description: ⚡ Detailed Report — Comprehensive project analysis and documentation
+version: "1.0"
+category: documentation
+execution-mode: execute
+---
+
+# /report:hard — Comprehensive Project Report
+
+> **MISSION**: Generate detailed output for **any topic** — reports, doc updates, or template-based files.
+>
+> Use for: sprint reviews, technical docs, any-topic reports, updating existing files, or generating from user format/template.
+
+<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) |
+
+**❌ Anti-Lazy**: Never use TIER 2 when TIER 1 tool available.
+
+---
+
+## 📁 DELIVERABLES (Reporter chooses from user intent)
+
+| User intent | Reporter output |
+| ----------- | ---------------- |
+| **Create report** | New file: `./reports/general/REPORT-{type}-{date}.md` (or path user asks) |
+| **Update existing** | **Edit** related files (docs, README, etc.); do **not** create new report unless also asked |
+| **From template** | New file(s) matching user format/template (e.g. after scouting source) |
+
+| Agent      | Output (when creating)                          |
+| ---------- | ------------------------------------------------ |
+| researcher | `./reports/researchers/RESEARCH-{task}.md` (optional) |
+| scouter    | `./reports/scouts/SCOUT-{task}.md` (optional)    |
+| reporter   | Per table above — create report **or** update existing **or** generate from template |
+
+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: RESEARCH
+
+| Agent  | `researcher`                                                |
+| ------ | ---------------------------------------------------------- |
+| Goal   | Research report scope, audience, and best practices for project/technical reports |
+| Output | `./reports/researchers/RESEARCH-{task}.md` (optional)       |
+| Exit   | Report scope and criteria defined, templates identified   |
+
+---
+
+## 🎭 Phase 2: DEEP SCAN
+
+| Agent  | `scouter`                         |
+| ------ | --------------------------------- |
+| Goal   | Full codebase structural analysis |
+| Output | `./reports/scouts/SCOUT-{task}.md` |
+| Exit   | Architecture and recent changes documented                 |
+
+---
+
+## 🎭 Phase 3: DATA SYNTHESIS
+
+| Agent       | `reporter`                                      |
+| ----------- | ------------------------------------------------ |
+| Prerequisite| **READ** RESEARCH + SCOUT outputs if present     |
+| Goal        | Aggregate data from Scouter, Plans, and History; identify discrepancies and milestones |
+| Exit        | Data synthesized, gaps and milestones identified |
+
+---
+
+## 🎭 Phase 4: OUTPUT (create / update / from template)
+
+| Agent | `reporter`                                                                 |
+| ----- | --------------------------------------------------------------------------- |
+| Goal  | From **user intent**: (1) create new report, (2) **update** existing files, or (3) generate from template/format |
+| Output| **Create**: `./reports/general/REPORT-{type}-{date}.md` or path user asked. **Update**: edit related files. **Template**: file(s) matching user format. |
+| Exit  | Deliverable matches intent — report file, updated docs, or template-based file(s). |
+
+---
+
+## COMPLETION
+
+Deliverable per **user intent**:
+
+1. ✅ **Create report** → `./reports/general/REPORT-{type}-{date}.md` (or path user asked)
+2. ✅ **Update existing** → Related files edited; list what was updated
+3. ✅ **From template** → File(s) matching user format; list path(s)
+4. 📢 **Share** → `/internal-comms` (optional)

package/commands/report.md

@@ -0,0 +1,89 @@
+---
+description: 📝 Report Router — Multi-purpose reporting (create report, update docs, or generate from template)
+version: "1.0"
+category: documentation
+execution-mode: router
+---
+
+# /report — Reporting Router
+
+> **ROUTER DIRECTIVE**: Analyze reporting needs and route to appropriate reporting workflow.
+>
+> **MULTI-PURPOSE**: Report supports any topic and three output modes — create new report, update existing files, or generate from user template/format.
+
+<task>$ARGUMENTS</task>
+
+---
+
+## 🛑 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
+
+**⛔ 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.
+
+---
+
+## OUTPUT MODES (infer from user request)
+
+Reporter **infers** the mode from what the user asks for — no fixed phrase list. Choose by **intent**:
+
+| Mode | User intent | Reporter action |
+|------|-------------|-----------------|
+| **Create report** | User wants a **new** deliverable (report, summary, analysis, documentation). | Scout/synthesize → write **new** file under `./reports/` or path user specifies. |
+| **Update existing** | User wants **changes reflected in existing** files (docs, README, specs, etc.). | Scout → identify related files → **edit** those files. Do not create a new report unless also asked. |
+| **From template** | User provides a **format, template, or structure** to follow. | Use that format/structure → generate file(s) matching it (e.g. after scouting source). |
+
+**Topic-agnostic**: Subject is whatever the user asks for — infer from the request; not limited to status or technical only.
+
+---
+
+## ROUTING LOGIC
+
+```
+IF task is simple status update OR summary:
+  → Route to /report:fast
+
+IF task is comprehensive analysis OR deep dive OR any non-trivial topic (infer from request):
+  → Route to /report:hard
+
+IF task requires absolute context clarity OR "clean slate" analysis:
+  → Route to /report:focus
+
+IF user explicitly asks to UPDATE existing files (not create report):
+  → Still use /report:hard or /report:focus; reporter OUTPUT MODE = update existing files
+
+IF unsure:
+  → Default to /report:fast (escalate if needed)
+```
+
+---
+
+## AVAILABLE ROUTES
+
+| Route           | When to Use                                                                 |
+| --------------- | --------------------------------------------------------------------------- |
+| `/report:fast`  | Quick status updates, daily summaries                                       |
+| `/report:hard`  | Detailed analysis, any topic (algorithms, docs, changes), template-based  |
+| `/report:focus` | Deep analysis with **enforced context optimization**; update or create      |
+
+---
+
+## PRESENT OPTIONS
+
+```markdown
+## 📝 Reporting Mode Selection
+
+**Task**: [parsed task]
+
+**Choose workflow:**
+
+1. ⚡ **Fast** → `/report:fast` — Quick summary
+2. ⚡⚡⚡ **Hard** → `/report:hard` — Full analysis, any topic; create report **or** update existing files / use template
+3. 🎯 **Focus** → `/report:focus` — Deep analysis with **automatic context clearing**; create or update per task
+
+⏳ Awaiting selection...
+```

package/commands/test/focus.md

@@ -0,0 +1,165 @@
+---
+description: 🔒 Focused Test — Comprehensive QA with enforced context optimization
+version: "1.0"
+category: validation
+execution-mode: execute
+---
+
+# /test:focus — Focus Comprehensive Testing
+
+> **MISSION**: Full QA workflow with **enforced context optimization**.
+> 
+> This variant automatically clears context before test execution—no user prompt required.
+> Use when you want guaranteed focused test execution without strategy noise.
+
+<scope>$ARGUMENTS</scope>
+
+---
+
+## 🛑 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) |
+
+---
+
+## 📁 PLAN CHECKPOINT VERIFICATION
+
+```
+IF ./reports/plans/PLAN-{scope}.md exists:
+  1. READ plan completely
+  2. EXTRACT all checkpoints
+  3. FOR EACH checkpoint → Create test
+  4. OUTPUT: "Checkpoint Coverage: X/Y"
+```
+
+---
+
+## ⛔ 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).
+
+---
+
+## 🎭 Phase 1: TEST STRATEGY
+
+| Agent | `tester`                                |
+| ----- | --------------------------------------- |
+| Goal  | Design test strategy                    |
+| Exit  | Strategy defined, test types identified |
+
+---
+
+## 🛡️ STRICT CONTEXT GATE — Automatic Context Optimization
+
+> **⚡ FOCUS MODE**: This checkpoint executes automatically. NO user input required.
+> 
+> **PURPOSE**: Prevent "context rot" by forcibly clearing strategy discussion noise.
+> This acts as a mandatory "firewall" before test execution phases.
+
+### 🔒 AUTOMATIC EXECUTION (NO PROMPT)
+
+```yaml
+strict_context_gate:
+  mode: "AUTOMATIC - No user interaction"
+  behavior: "Force Clear context & Execute"
+  
+  execution:
+    1. ANNOUNCE: |
+       ## 🛡️ Strict Context Gate — Automatic
+       
+       ✅ **Test Strategy Complete**: Strategy defined, test types identified.
+       🔒 **Focus Mode**: Automatically clearing context for test execution.
+       
+       ⚡ Executing: **Clear context & Execute**...
+    
+    2. CONTEXT_DIRECTIVE: |
+       ╔══════════════════════════════════════════════════════════════════╗
+       ║  ⛔ MANDATORY CONTEXT RESET — FOCUS MODE                         ║
+       ╠══════════════════════════════════════════════════════════════════╣
+       ║  IGNORE: All strategy discussions, rejected approaches,          ║
+       ║          and intermediate test planning reasoning.               ║
+       ║                                                                  ║
+       ║  SOLE SOURCE OF TRUTH: Finalized test strategy.                  ║
+       ║                                                                  ║
+       ║  PROCEED: Execute test phases with FRESH context mindset.        ║
+       ║           Focus purely on test execution and verification.       ║
+       ╚══════════════════════════════════════════════════════════════════╝
+    
+    3. LOAD: Finalized test strategy as if seeing it for the first time
+    
+    4. PROCEED: Start Phase 2 (Dependency Mapping) immediately
+```
+
+### 📋 Post-Gate Status
+
+```markdown
+🔒 **Context Gate Passed**
+- Previous context: DISCARDED
+- Active context: Test strategy only
+- Mode: Fresh execution start
+
+Proceeding to Test Execution...
+```
+
+---
+
+## 🎭 Phase 2: DEPENDENCY MAPPING
+
+| Agent | `scouter`                              |
+| ----- | -------------------------------------- |
+| Goal  | Map test dependencies                  |
+| Exit  | Dependencies mapped, environment ready |
+
+---
+
+## 🎭 Phase 3: TEST EXECUTION
+
+| Agent        | `tester`                                                        |
+| ------------ | --------------------------------------------------------------- |
+| Prerequisite | READ PLAN file if exists                                        |
+| Goal         | Run full test suite                                             |
+| Exit         | All tests run, coverage measured, checkpoint mapping documented |
+
+---
+
+## 🎭 Phase 4: FAILURE ANALYSIS (IF FAILURES)
+
+| Agent   | `debugger`             |
+| ------- | ---------------------- |
+| Trigger | If failures exist      |
+| Goal    | Analyze failures       |
+| Exit    | Root causes identified |
+
+---
+
+## 🎭 Phase 5: QUALITY GATES
+
+| Agent | `tester`                          |
+| ----- | --------------------------------- |
+| Goal  | Verify quality gates              |
+| Exit  | All gates pass, coverage adequate |
+
+---
+
+## COMPLETION
+
+Present test report with:
+
+1. ✅ **Pass** — All tests green (Focus Mode)
+2. 🔧 **Fix** → `/fix:fast`
+3. 📝 **Review** → `/review`

package/commands/test/hard.md

@@ -61,6 +61,59 @@ 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.
+       ✅ FINALIZED STRATEGY is SOLE SOURCE OF TRUTH.
+    3. PROCEED: Continue to test execution phases
+
+option_2_review_strategy:
+  behavior: "Clear and show summary"
+  steps:
+    1. ACKNOWLEDGE: "⏸️ Context cleared."
+    2. OUTPUT: Display strategy summary
+    3. WAIT: For user approval
+
+option_3_continue_no_clear:
+  behavior: "Proceed with caution"
+  steps:
+    1. WARN: "⚠️ Discussion history retained."
+    2. PROCEED: Continue with existing context
+```
+
+---
+
 ## 🎭 Phase 2: DEPENDENCY MAPPING
 
 | Agent | `scouter`                              |

package/commands/test.md

@@ -33,6 +33,9 @@ IF scope is limited (unit tests, quick check):
 IF scope is comprehensive (full suite, E2E):
   → Route to /test:hard
 
+IF scope is comprehensive AND clean execution focus is critical:
+  → Route to /test:focus
+
 IF unsure:
   → Default to /test:fast
 ```
@@ -41,10 +44,11 @@ IF unsure:
 
 ## AVAILABLE ROUTES
 
-| Route        | When to Use             |
-| ------------ | ----------------------- |
-| `/test:fast` | Quick tests, unit tests |
-| `/test:hard` | Full test suite, E2E    |
+| Route          | When to Use                                        |
+| -------------- | -------------------------------------------------- |
+| `/test:fast`   | Quick tests, unit tests                            |
+| `/test:hard`   | Full test suite, E2E                               |
+| `/test:focus` | Full testing with **enforced context optimization** |
 
 ---
 
@@ -59,6 +63,7 @@ IF unsure:
 
 1. ⚡ **Fast** → `/test:fast` — Quick tests
 2. ⚡⚡⚡ **Hard** → `/test:hard` — Comprehensive testing
+3. 🔒 **Focus** → `/test:focus` — Comprehensive testing with **automatic context clearing** (focused execution)
 
 ⏳ Awaiting selection...
 ```