@namch/agent-assistant 1.0.2 → 1.0.4

package/commands/design/focus.md

@@ -0,0 +1,267 @@
+---
+description: 🔒 Focused Design — Complete design process with enforced context optimization
+version: "1.0"
+category: design
+execution-mode: execute
+---
+
+# /design:focus — Focus Full Design Process
+
+> **MISSION**: Execute complete design process with **enforced context optimization**.
+> 
+> This variant automatically clears context before implementation handoff—no user prompt required.
+> Use when you want guaranteed clean implementation handoff without design exploration noise.
+
+<request>$ARGUMENTS</request>
+
+---
+
+## 🛑 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 PROTOCOL (MANDATORY)
+
+> **Reference**: `{RULES_PATH}/ADAPTIVE-EXECUTION.md`
+
+```yaml
+tiered_execution:
+  principle: "Sub-agent FIRST (Tier 1). EMBODY ONLY on system failure (Tier 2)."
+  for_each_phase:
+    TIER_1_MANDATORY: "IF tool exists → MUST use SUB_AGENT_DELEGATION"
+    TIER_2_FALLBACK: "ONLY on system error—NOT complexity/preference/speed"
+  anti_lazy_fallback:
+    - ❌ NEVER use Tier 2 when Tier 1 tool is available
+    - ✅ ALWAYS attempt Tier 1 first when tool exists
+```
+
+---
+
+## ⚠️ CRITICAL: DELIVERABLE FILE RULES
+
+```yaml
+deliverable_files:
+  researcher: "./reports/researchers/RESEARCH-{request}.md"
+  scouter: "./reports/scouts/SCOUT-{request}.md"
+  designer: "./reports/designs/DESIGN-{request}.md" # MANDATORY OUTPUT
+
+enforcement:
+  - Design phase MUST create design file
+  - Design file is the deliverable for implementation phases
+```
+
+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).
+
+---
+
+## 🎭 Phase 1: REQUIREMENTS DISCOVERY
+
+| Attribute | Value                       |
+| --------- | --------------------------- |
+| **Agent** | `brainstormer`              |
+| **Goal**  | Clarify design requirements |
+
+### ⚡ TIERED EXECUTION
+
+**TIER 1 (MANDATORY when tool exists):**
+
+> Invoke runSubagent for `brainstormer`. Context: ISOLATED.
+
+**TIER 2 (FALLBACK on system error only):**
+
+> Load `{AGENTS_PATH}/brainstormer.md`
+> EMBODY [brainstormer] — Requires logged system error justification.
+
+**Exit Criteria:**
+
+- [ ] Requirements clear
+- [ ] User needs identified
+- [ ] Constraints documented
+- [ ] **METHODOLOGY CHECK**: Output aligns with `brainstormer` Thinking Protocol
+
+---
+
+## 🎭 Phase 2: RESEARCH
+
+| Attribute | Value                           |
+| --------- | ------------------------------- |
+| **Agent** | `researcher`                    |
+| **Goal**  | Research design patterns and UX |
+
+### ⚡ TIERED EXECUTION
+
+**TIER 1 (MANDATORY when tool exists):**
+
+> Invoke runSubagent for `researcher`. Context: ISOLATED.
+
+**TIER 2 (FALLBACK on system error only):**
+
+> Load `{AGENTS_PATH}/researcher.md`
+> EMBODY [researcher] — Requires logged system error justification.
+
+**Exit Criteria:**
+
+- [ ] Patterns researched
+- [ ] Best practices identified
+- [ ] **METHODOLOGY CHECK**: Output aligns with `researcher` Thinking Protocol
+
+---
+
+## 🎭 Phase 3: CODEBASE ANALYSIS
+
+| Attribute | Value                      |
+| --------- | -------------------------- |
+| **Agent** | `scouter`                  |
+| **Goal**  | Map existing design system |
+
+### ⚡ TIERED EXECUTION
+
+**TIER 1 (MANDATORY when tool exists):**
+
+> Invoke runSubagent for `scouter`. Context: ISOLATED.
+
+**TIER 2 (FALLBACK on system error only):**
+
+> Load `{AGENTS_PATH}/scouter.md`
+> EMBODY [scouter] — Requires logged system error justification.
+
+**Exit Criteria:**
+
+- [ ] Design system documented
+- [ ] Component inventory
+- [ ] Integration points
+- [ ] **METHODOLOGY CHECK**: Output aligns with `scouter` Thinking Protocol
+
+---
+
+## 🎭 Phase 4: DESIGN CREATION
+
+| Attribute | Value                  |
+| --------- | ---------------------- |
+| **Agent** | `designer`             |
+| **Goal**  | Full design with specs |
+
+### ⚡ TIERED EXECUTION
+
+**TIER 1 (MANDATORY when tool exists):**
+
+> Invoke runSubagent for `designer`. Context: ISOLATED.
+
+**TIER 2 (FALLBACK on system error only):**
+
+> Load `{AGENTS_PATH}/designer.md`
+> EMBODY [designer] — Requires logged system error justification.
+
+**Exit Criteria:**
+
+- [ ] Design complete
+- [ ] All states covered
+- [ ] Accessibility verified
+- [ ] Specs documented
+- [ ] **METHODOLOGY CHECK**: Output aligns with `designer` Thinking Protocol
+
+---
+
+## 🛡️ STRICT CONTEXT GATE — Automatic Context Optimization
+
+> **⚡ 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.
+
+### 🔒 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
+       
+       ✅ **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)
+```
+
+### 📋 Post-Gate Status
+
+```markdown
+🔒 **Context Gate Passed**
+- Previous context: DISCARDED
+- Active context: Design file only
+- Mode: Clean review start
+
+Proceeding to Design Review...
+```
+
+---
+
+## 🎭 Phase 5: DESIGN REVIEW
+
+| Attribute | Value                 |
+| --------- | --------------------- |
+| **Agent** | `reviewer`            |
+| **Goal**  | Review design quality |
+
+### ⚡ TIERED EXECUTION
+
+**TIER 1 (MANDATORY when tool exists):**
+
+> Invoke runSubagent for `reviewer`. Context: ISOLATED.
+
+**TIER 2 (FALLBACK on system error only):**
+
+> Load `{AGENTS_PATH}/reviewer.md`
+> EMBODY [reviewer] — Requires logged system error justification.
+
+**Exit Criteria:**
+
+- [ ] Design reviewed
+- [ ] Standards met
+- [ ] Approved
+- [ ] **METHODOLOGY CHECK**: Output aligns with `reviewer` Thinking Protocol
+
+---
+
+## COMPLETION
+
+Present design with:
+
+1. ✅ **Done** — Design approved (Focus Mode)
+2. 🔒 **Context Optimized** — Ready for focus implementation
+3. 💻 **Implement** → `/code:focus`
+4. 🔄 **Iterate** — Further refinement

package/commands/design/hard.md

@@ -173,6 +173,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 noisy design exploration history before implementation.
+> 
+> Design iterations and rejected alternatives fill context with noise.
+> This checkpoint acts as a "firewall" before handing off to implementation.
+
+### ⚡ OPTIONS (Present to User)
+
+```markdown
+## 🛡️ Context Optimization Checkpoint
+
+**Design Complete** — Design specs created at: `./reports/designs/DESIGN-{request}.md`
+
+**Choose how to proceed:**
+
+| Option | Action | Description |
+|--------|--------|-------------|
+| **1. 🚀 Clear context & Ready** | `RECOMMENDED` | Fresh start for implementation: Reload Design, ignore exploration history |
+| **2. ⏸️ Review First** | `SAFE` | Clear context, show design summary, wait for approval |
+| **3. ⚠️ Continue (No Clear)** | `RISKY` | Keep design history (may affect review quality) |
+
+⏳ Awaiting selection...
+```
+
+### 🔄 EXECUTION BEHAVIOR
+
+```yaml
+option_1_clear_ready:
+  behavior: "RECOMMENDED - Clean handoff"
+  steps:
+    1. ACKNOWLEDGE: "🚀 Context optimized. Design ready for review/implementation."
+    2. CONTEXT_DIRECTIVE: |
+       ⛔ IGNORE all design exploration and rejected alternatives.
+       ✅ DESIGN FILE is SOLE SOURCE OF TRUTH.
+    3. PROCEED: Continue to Design Review phase
+
+option_2_review_first:
+  behavior: "Clear and show summary"
+  steps:
+    1. ACKNOWLEDGE: "⏸️ Context cleared."
+    2. OUTPUT: Display design summary for user review
+    3. WAIT: For user approval
+
+option_3_continue_no_clear:
+  behavior: "Proceed with caution"
+  steps:
+    1. WARN: "⚠️ Design exploration history retained."
+    2. PROCEED: Continue to review with existing context
+```
+
+---
+
 ## 🎭 Phase 5: DESIGN REVIEW
 
 | Attribute | Value                 |

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...
 ```