@namch/agent-assistant 1.3.0 → 1.3.2

package/code-assistants/codex-assistant/skills/agent-assistant-plan-focus/SKILL.md

@@ -1,18 +0,0 @@
----
-name: agent-assistant-plan-focus
-description: "🔒 Focused Plan — Research-backed planning with enforced context optimization. Use when user types /plan:focus."
----
-
-# /plan:focus
-
-> Activates Agent Assistant `/plan:focus` workflow.
-
-## Rules
-
-1. **Load first**: `~/.codex/skills/agent-assistant/rules/CORE.md` — follow all 10 Laws
-2. **Agents**: Spawn via Codex native multi-agent (`~/.codex/agents/`)
-3. **Skills**: Resolve from `~/.codex/skills/agent-assistant/matrix-skills/`
-
-## Workflow
-
-**Load and follow**: `~/.codex/skills/agent-assistant/commands/plan/focus.md`

package/code-assistants/codex-assistant/skills/agent-assistant-plan-focus/agents/openai.yaml

@@ -1,4 +0,0 @@
-display_name: "/plan:focus"
-short_description: "🔒 Focused Plan — Research-backed planning with enforced context optimization"
-brand_color: "#F59E0B"
-allow_implicit_invocation: true

package/code-assistants/codex-assistant/skills/agent-assistant-report-focus/SKILL.md

@@ -1,18 +0,0 @@
----
-name: agent-assistant-report-focus
-description: "🔒 Focused Report — Deep analysis with enforced context optimization. Use when user types /report:focus."
----
-
-# /report:focus
-
-> Activates Agent Assistant `/report:focus` workflow.
-
-## Rules
-
-1. **Load first**: `~/.codex/skills/agent-assistant/rules/CORE.md` — follow all 10 Laws
-2. **Agents**: Spawn via Codex native multi-agent (`~/.codex/agents/`)
-3. **Skills**: Resolve from `~/.codex/skills/agent-assistant/matrix-skills/`
-
-## Workflow
-
-**Load and follow**: `~/.codex/skills/agent-assistant/commands/report/focus.md`

package/code-assistants/codex-assistant/skills/agent-assistant-report-focus/agents/openai.yaml

@@ -1,4 +0,0 @@
-display_name: "/report:focus"
-short_description: "🔒 Focused Report — Deep analysis with enforced context optimization"
-brand_color: "#3B82F6"
-allow_implicit_invocation: true

package/code-assistants/codex-assistant/skills/agent-assistant-test-focus/SKILL.md

@@ -1,18 +0,0 @@
----
-name: agent-assistant-test-focus
-description: "🔒 Focused Test — Comprehensive QA with enforced context optimization. Use when user types /test:focus."
----
-
-# /test:focus
-
-> Activates Agent Assistant `/test:focus` workflow.
-
-## Rules
-
-1. **Load first**: `~/.codex/skills/agent-assistant/rules/CORE.md` — follow all 10 Laws
-2. **Agents**: Spawn via Codex native multi-agent (`~/.codex/agents/`)
-3. **Skills**: Resolve from `~/.codex/skills/agent-assistant/matrix-skills/`
-
-## Workflow
-
-**Load and follow**: `~/.codex/skills/agent-assistant/commands/test/focus.md`

package/code-assistants/codex-assistant/skills/agent-assistant-test-focus/agents/openai.yaml

@@ -1,4 +0,0 @@
-display_name: "/test:focus"
-short_description: "🔒 Focused Test — Comprehensive QA with enforced context optimization"
-brand_color: "#10B981"
-allow_implicit_invocation: true

package/commands/code/focus.md

@@ -1,297 +0,0 @@
----
-description: 🔒 Focused Development — Full development cycle with enforced context optimization
-version: "1.0"
-category: engineering
-execution-mode: execute
----
-
-# /code:focus — Focus Development Cycle
-
-> **MISSION**: Execute complete development workflow with **enforced context optimization**.
->
-> This variant automatically clears context before implementation—no user prompt required.
-> Use when you want guaranteed clean implementation without context rot risk.
-
-<task>$ARGUMENTS</task>
-
----
-
-## 🛑 PRE-FLIGHT (DO FIRST — BLOCKS PHASE 1)
-
-**LOAD now** (in order; path `./rules/` or `~/.{TOOL}/skills/agent-assistant/rules/`):
-
-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/{topic}/plans/PLAN-{name}`, 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/{topic}/plans/PLAN-{task}` (derive `{task}` from `$ARGUMENTS` or from the referenced file name).
-
-### Resolution
-
-1. **CHECK**: Does a valid plan file exist (user-provided path or `./reports/{topic}/plans/PLAN-{task}`)?
-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**: Phase 4 (Implementation) → Phase 5 (Testing) → Phase 6 (Review).
-3. **IF NO**: Run phases in order: Phase 1 → 2 → 3 → 4 → 5 → 6.
-
----
-
-## 🔀 TIERED EXECUTION PROTOCOL (MANDATORY)
-
-> **Reference: AGENTS.md (Tiered Execution)`
-
-```yaml
-tiered_execution:
-  principle: "Sub-agent FIRST (Tier 1). EMBODY ONLY on system failure (Tier 2)."
-
-  tool_discovery: "Check runSubagent availability BEFORE first delegation"
-
-  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
-    - ✅ ALWAYS log justification for Tier 2 fallback
-```
-
----
-
-## ⚠️ CRITICAL: PHASE CONTINUITY RULES
-
-```yaml
-phase_continuity:
-  rule: "Each phase MUST reference and follow outputs from prior phases"
-
-  check_for_files:
-    - "./reports/{topic}/brainstorms/BRAINSTORM-{task}"
-    - "./reports/{topic}/scouts/SCOUT-{task}"
-    - "./reports/{topic}/plans/PLAN-{task}"
-
-  enforcement:
-    - Phase 3 (Planning) MUST incorporate Scout findings
-    - Phase 4 (Implementation) MUST follow the Plan file exactly
-    - Phase 5 (Testing) MUST verify all plan checkpoints
-    - If prior phase file missing → Agent MUST create it
-```
-
-All files in `./reports/{topic}/` → English only.
-**⚠️ Paths above = base names.** Small (≤ 150 lines) → create as `{name}.md`. Large (> 150 lines or ≥ 4 sections) → create as `{name}/` folder with `00-index.md` + `01-*.md`, `02-*.md` section files.
-
----
-
-## ⛔ 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 ANALYSIS
-
-| Attribute   | Value                             |
-| ----------- | --------------------------------- |
-| **Agent**   | `brainstormer`                    |
-| **Goal**    | Clarify requirements if ambiguous |
-| **Trigger** | If requirements unclear           |
-
-### ⚡ 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
-- [ ] Scope defined
-- [ ] Acceptance criteria established
-- [ ] **METHODOLOGY CHECK**: Output aligns with `brainstormer` Thinking Protocol
-
----
-
-## 🎭 Phase 2: CODEBASE ANALYSIS
-
-| Attribute | Value                         |
-| --------- | ----------------------------- |
-| **Agent** | `scouter`                     |
-| **Goal**  | Full codebase context mapping |
-
-### ⚡ 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:**
-
-- [ ] Architecture understood
-- [ ] Patterns documented
-- [ ] Integration points identified
-- [ ] **METHODOLOGY CHECK**: Output aligns with `scouter` Thinking Protocol
-
----
-
-## 🎭 Phase 3: IMPLEMENTATION PLANNING
-
-| Attribute | Value                      |
-| --------- | -------------------------- |
-| **Agent** | `planner`                  |
-| **Goal**  | Create implementation plan |
-
-### ⚡ TIERED EXECUTION
-
-**TIER 1 (MANDATORY when tool exists):**
-
-> Invoke runSubagent for `planner`. Context: ISOLATED.
-
-**TIER 2 (FALLBACK on system error only):**
-
-> Load `{AGENTS_PATH}/planner.md`
-> EMBODY [planner] — Requires logged system error justification.
-
-**Exit Criteria:**
-
-- [ ] Plan created
-- [ ] Steps defined
-- [ ] Risks identified
-- [ ] **METHODOLOGY CHECK**: Output aligns with `planner` Thinking Protocol
-
----
-
-Mode: Fresh implementation start
-
-Proceeding to Implementation...
-```
-
----
-
-## 🎭 Phase 4: IMPLEMENTATION
-
-| Attribute | Value                               |
-| --------- | ----------------------------------- |
-| **Agent** | `tech-lead` → routes to specialists |
-| **Goal**  | Execute plan with specialist agents |
-
-### ⚡ TIERED EXECUTION
-
-**TIER 1 (MANDATORY when tool exists):**
-
-> Invoke runSubagent for `tech-lead`. Context: ISOLATED.
-> Tech-lead will spawn specialist subagents as needed.
-
-**TIER 2 (FALLBACK on system error only):**
-
-> Load `{AGENTS_PATH}/tech-lead.md`
-> EMBODY [tech-lead] — Requires logged system error justification.
-> Then recursively EMBODY specialists as needed.
-
-### ⚡ FOCUS ADHERENCE DIRECTIVE
-
-```
-1. READ plan completely BEFORE any implementation
-2. FOR EACH plan step:
-   a. Implement EXACTLY as specified
-   b. Mark complete: `- [ ]` → `- [x]`
-3. IF deviation needed:
-   a. STOP
-   b. REQUEST Re-Planning
-   c. DO NOT proceed with own interpretation
-```
-
-**Exit Criteria:**
-
-- [ ] All plan steps executed
-- [ ] Code complete
-- [ ] Documentation updated
-- [ ] **Each plan step has corresponding implementation**
-- [ ] **No unauthorized deviations**
-- [ ] **METHODOLOGY CHECK**: Output aligns with `tech-lead` Thinking Protocol
-
----
-
-## 🎭 Phase 5: TESTING
-
-| Attribute | Value                 |
-| --------- | --------------------- |
-| **Agent** | `tester`              |
-| **Goal**  | Comprehensive testing |
-
-### ⚡ TIERED EXECUTION
-
-**TIER 1 (MANDATORY when tool exists):**
-
-> Invoke runSubagent for `tester`. Context: ISOLATED.
-
-**TIER 2 (FALLBACK on system error only):**
-
-> Load `{AGENTS_PATH}/tester.md`
-> EMBODY [tester] — Requires logged system error justification.
-
-**Exit Criteria:**
-
-- [ ] Tests written
-- [ ] All tests pass
-- [ ] Coverage adequate
-- [ ] **METHODOLOGY CHECK**: Output aligns with `tester` Thinking Protocol
-
----
-
-## 🎭 Phase 6: REVIEW
-
-| Attribute | Value               |
-| --------- | ------------------- |
-| **Agent** | `reviewer`          |
-| **Goal**  | Code quality review |
-
-### ⚡ 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:**
-
-- [ ] Code reviewed
-- [ ] Standards met
-- [ ] No blocking issues
-- [ ] **METHODOLOGY CHECK**: Output aligns with `reviewer` Thinking Protocol
-
----
-
-## COMPLETION
-
-Present implementation report with:
-
-1. ✅ **Done** — Feature complete (Focus Mode)
-2. 🚀 **Deploy** → `/deploy:preview`
-3. 📝 **Docs** → `/docs:core`

package/commands/cook/focus.md

@@ -1,209 +0,0 @@
----
-description: 🔒 Focused Feature — Complete development with enforced context optimization
-version: "1.0"
-category: engineering
-execution-mode: execute
----
-
-# /cook:focus — Focus Feature Development
-
-> **MISSION**: Full feature development with **enforced context optimization**.
->
-> This variant automatically clears context before implementation—no user prompt required.
-> Use when you want guaranteed clean implementation without context rot risk.
-
-<feature>$ARGUMENTS</feature>
-
----
-
-## 🛑 PRE-FLIGHT (DO FIRST — BLOCKS PHASE 1)
-
-**LOAD now** (in order; path `./rules/` or `~/.{TOOL}/skills/agent-assistant/rules/`):
-
-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: AGENTS.md (Tiered Execution)`
-
-| Tier       | When                          | Action                       |
-| ---------- | ----------------------------- | ---------------------------- |
-| **TIER 1** | runSubagent/Agent Tool EXISTS | Invoke sub-agent (MANDATORY) |
-| **TIER 2** | Tool MISSING or SYSTEM error  | EMBODY agent file (FALLBACK) |
-
-**❌ Anti-Lazy**: Never use TIER 2 when TIER 1 tool available.
-
----
-
-## 📁 DELIVERABLE FILES
-
-| Agent        | Output                                          |
-| ------------ | ----------------------------------------------- |
-| brainstormer | `./reports/{topic}/brainstorms/BRAINSTORM-{feature}` |
-| researcher   | `./reports/{topic}/researchers/RESEARCH-{feature}`   |
-| scouter      | `./reports/{topic}/scouts/SCOUT-{feature}`           |
-| designer     | `./reports/{topic}/designs/DESIGN-{feature}`         |
-| planner      | `./reports/{topic}/plans/PLAN-{feature}`             |
-
-All files in `./reports/{topic}/` → English only.
-**⚠️ Paths above = base names.** Small (≤ 150 lines) → create as `{name}.md`. Large (> 150 lines or ≥ 4 sections) → create as `{name}/` folder with `00-index.md` + `01-*.md`, `02-*.md` section files.
-
----
-
-## 🔗 PHASE DEPENDENCIES
-
-| Phase              | Requires               | Blocking    |
-| ------------------ | ---------------------- | ----------- |
-| P1: Brainstorm     | User request           | No          |
-| P2: Research       | User request           | No          |
-| P3: Scout          | User request           | No          |
-| P3.5: DB Design    | Data requirements      | Conditional |
-| P4: Design         | Scout findings         | Conditional |
-| P5: Planning       | RESEARCH + SCOUT files | **YES**     |
-| P5.5: Context Gate | **PLAN file**          | **AUTO**    |
-| P6: Implementation | **PLAN file**          | **YES**     |
-| P7: Testing        | PLAN + Code            | **YES**     |
-| P8: Review         | PLAN + Code + Tests    | **YES**     |
-
-**⛔ Blocking**: If input missing → STOP → Create it first → Resume
-
----
-
-## ⛔ 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/PHASES.md § Phase output structure.
-
----
-
-## 🎭 Phase 1: REQUIREMENTS CLARIFICATION
-
-| Agent | `brainstormer`                                                       |
-| ----- | -------------------------------------------------------------------- |
-| Goal  | Full requirements discovery                                          |
-| Exit  | Requirements clear, constraints identified, success criteria defined |
-
----
-
-## 🎭 Phase 2: RESEARCH
-
-| Agent | `researcher`                                                               |
-| ----- | -------------------------------------------------------------------------- |
-| Goal  | Research best practices and patterns                                       |
-| Exit  | Patterns researched, best practices identified, recommendations documented |
-
----
-
-## 🎭 Phase 3: CODEBASE ANALYSIS
-
-| Agent | `scouter`                                                               |
-| ----- | ----------------------------------------------------------------------- |
-| Goal  | Map architecture and integration points                                 |
-| Exit  | Architecture understood, integration points mapped, patterns documented |
-
----
-
-## 🎭 Phase 3.5: DATABASE DESIGN (IF DATA CHANGES)
-
-| Agent   | `database-architect`                                        |
-| ------- | ----------------------------------------------------------- |
-| Trigger | Feature involves database changes/migrations                |
-| Goal    | Schema design and data modeling                             |
-| Exit    | Schema designed, migrations planned, query patterns defined |
-
----
-
-## 🎭 Phase 4: DESIGN (IF UI NEEDED)
-
-| Agent   | `designer`                                            |
-| ------- | ----------------------------------------------------- |
-| Trigger | Feature has UI components                             |
-| Goal    | UI/UX design                                          |
-| Exit    | Design created, accessibility considered, specs ready |
-
----
-
-## 🎭 Phase 5: PLANNING
-
-| Agent        | `planner`                                           |
-| ------------ | --------------------------------------------------- |
-| Prerequisite | **READ** RESEARCH + SCOUT + DESIGN files            |
-| Goal         | Create detailed implementation plan                 |
-| Output       | `./reports/{topic}/plans/PLAN-{feature}`                 |
-| Exit         | Plan file created, phases defined, risks identified |
-
----
-
-## 🎭 Phase 6: IMPLEMENTATION
-
-| Agent        | `tech-lead` → routes to specialists                     |
-| ------------ | ------------------------------------------------------- |
-| Prerequisite | **READ and FOLLOW** `./reports/{topic}/plans/PLAN-{feature}` |
-| Goal         | Execute implementation plan                             |
-
-**FOCUS ADHERENCE:**
-
-```
-1. READ plan FIRST
-2. FOR EACH step:
-   - Implement EXACTLY as specified
-   - Mark step complete: [ ] → [x]
-3. IF step seems wrong:
-   - STOP → Document → Request Re-Planning
-   - DO NOT implement your own interpretation
-```
-
-| Exit | All plan phases complete, no unauthorized deviations |
-
----
-
-## 🎭 Phase 7: TESTING
-
-| Agent        | `tester`                     |
-| ------------ | ---------------------------- |
-| Prerequisite | **READ** PLAN + Code changes |
-| Goal         | Comprehensive testing        |
-
-**PLAN CHECKPOINT VERIFICATION:**
-
-```
-FOR EACH checkpoint in PLAN:
-  - Write test that verifies criteria
-  - Document: "Checkpoint X → Test Y"
-```
-
-| Exit | All tests pass, each plan checkpoint has test |
-
----
-
-## 🎭 Phase 8: REVIEW
-
-| Agent        | `reviewer`                       |
-| ------------ | -------------------------------- |
-| Prerequisite | **READ** PLAN + Code + Tests     |
-| Goal         | Quality review + Plan compliance |
-
-**REVIEW CHECKLIST:**
-
-- Does code implement plan specification?
-- Any unauthorized deviations?
-- All plan phases reflected in code?
-
-| Exit | Code matches plan intent, standards met, approved |
-
----
-
-## COMPLETION
-
-Present feature report with:
-
-1. ✅ **Done** — Feature complete (Focus Mode)
-2. 🚀 **Deploy** → `/deploy:preview`
-3. 📝 **Docs** → `/docs:core`

package/commands/debug/focus.md

@@ -1,103 +0,0 @@
----
-description: 🔒 Focused Debug — Deep investigation with enforced context optimization
-version: "1.0"
-category: debugging
-execution-mode: execute
----
-
-# /debug:focus — Focus Deep Investigation
-
-> **MISSION**: Thorough investigation with **enforced context optimization**.
->
-> This variant automatically clears context before fix handoff—no user prompt required.
-> Use when you want guaranteed clean fix handoff without hypothesis drift.
-
-<issue>$ARGUMENTS</issue>
-
----
-
-## 🛑 PRE-FLIGHT (DO FIRST — BLOCKS PHASE 1)
-
-**LOAD now** (in order; path `./rules/` or `~/.{TOOL}/skills/agent-assistant/rules/`):
-
-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
-
-| Tier       | When               | Action                       |
-| ---------- | ------------------ | ---------------------------- |
-| **TIER 1** | runSubagent EXISTS | Invoke sub-agent (MANDATORY) |
-| **TIER 2** | Tool MISSING       | EMBODY agent file (FALLBACK) |
-
----
-
-## 📁 DELIVERABLE FILES
-
-| Agent    | Output                              |
-| -------- | ----------------------------------- |
-| debugger | `./reports/{topic}/debugs/DEBUG-{issue}` |
-
-All files in `./reports/{topic}/` → English only.
-**⚠️ Paths above = base names.** Small (≤ 150 lines) → create as `{name}.md`. Large (> 150 lines or ≥ 4 sections) → create as `{name}/` folder with `00-index.md` + `01-*.md`, `02-*.md` section files.
-
----
-
-## ⛔ 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: INFORMATION GATHERING
-
-| Agent | `scouter`                                 |
-| ----- | ----------------------------------------- |
-| Goal  | Gather context and reproduction steps     |
-| Exit  | Context gathered, reproduction documented |
-
----
-
-## 🎭 Phase 2: HYPOTHESIS FORMATION
-
-| Agent | `debugger`                          |
-| ----- | ----------------------------------- |
-| Goal  | Form and rank hypotheses            |
-| Exit  | Hypotheses documented with evidence |
-
----
-
-## 🎭 Phase 3: ROOT CAUSE ANALYSIS
-
-| Agent  | `debugger`                                      |
-| ------ | ----------------------------------------------- |
-| Goal   | Deep investigation                              |
-| Output | `./reports/{topic}/debugs/DEBUG-{issue}`             |
-| Exit   | Root cause identified, failure chain documented |
-
----
-
-## 🎭 Phase 4: SOLUTION DESIGN
-
-| Agent | `planner`                               |
-| ----- | --------------------------------------- |
-| Goal  | Design fix strategy                     |
-| Exit  | Fix approach defined with rollback plan |
-
----
-
-## COMPLETION
-
-Present findings with:
-
-1. ✅ **Root Cause** — Identified (Focus Mode)
-2. 🔒 **Context Optimized** — Ready for focus fix
-3. 🔧 **Fix** → `/fix:focus`
-4. 📝 **Document** → `/docs:core`