@namch/agent-assistant 1.3.1 → 1.3.2

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`

package/commands/design/focus.md

@@ -1,229 +0,0 @@
----
-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. 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: AGENTS.md (Tiered Execution)`
-
-```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/{topic}/researchers/RESEARCH-{request}"
-  scouter: "./reports/{topic}/scouts/SCOUT-{request}"
-  designer: "./reports/{topic}/designs/DESIGN-{request}" # MANDATORY OUTPUT
-
-enforcement:
-  - Design phase MUST create design file
-  - Design file is the deliverable for implementation phases
-```
-
-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 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
-
----
-
-## ❌ Discarded:
-- Design exploration noise
-- Rejected alternatives
-- Iteration history
-- Chat history
-
-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 complete (Focus Mode)
-2. 🔒 **Context Optimized** — Ready for focus implementation
-3. 💻 **Implement** → `/code:focus`
-4. 🔄 **Iterate** — Further refinement

package/commands/fix/focus.md

@@ -1,145 +0,0 @@
----
-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. 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) |
-
-**❌ Anti-Lazy**: Never use TIER 2 when TIER 1 tool available.
-
----
-
-## 📁 DELIVERABLE FILES
-
-| Agent      | Output                                      |
-| ---------- | ------------------------------------------- |
-| debugger   | `./reports/{topic}/debugs/DEBUG-{issue}`         |
-| researcher | `./reports/{topic}/researchers/RESEARCH-{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). Format: rules/PHASES.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   |
-
----
-
----
-
-## ✅ Reloaded:
-- User request (original issue verbatim)
-- Acceptance criteria (fix verification checkpoints)
-- Fix plan with rollback strategy
-- Remaining phases workflow
-- Implementation rules summary
-
-## ❌ Discarded:
-- Debugging hypotheses
-- Failed investigation attempts
-- Research explorations
-- Chat history noise
-
-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`