@namch/agent-assistant 1.3.1 → 1.3.2

package/commands/plan/focus.md

@@ -1,140 +0,0 @@
----
-description: 🔒 Focused Plan — Research-backed planning with enforced context optimization
-version: "1.0"
-category: planning
-execution-mode: execute
----
-
-# /plan:focus — Focus Comprehensive Planning
-
-> **MISSION**: Create thorough implementation plan with **enforced context optimization**.
->
-> This variant automatically clears context before handoff—no user prompt required.
-> Use when you want guaranteed clean plan handoff 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).
-
----
-
-## 🔀 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                                                                                                                                                                   |
-| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| researcher | `./reports/{topic}/researchers/RESEARCH-{task}`                                                                                                                               |
-| scouter    | `./reports/{topic}/scouts/SCOUT-{task}`                                                                                                                                       |
-| planner    | **One** `./reports/{topic}/plans/PLAN-{task}` **OR** multiple `./reports/{topic}/plans/PLAN-{task}-phase1`, `PLAN-{task}-phase2`, … (see **Complexity & plan splitting** below) |
-
-**Plans are source of truth for implementation.** 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.
-
----
-
-## 📐 COMPLEXITY & PLAN SPLITTING (MANDATORY FOR PLANNER)
-
-When the logical plan would have **> 3 phases** or **estimated effort > 3 days**, the planner **MUST** produce **multiple plan files** (one per executable phase or per milestone group), **not** one monolithic file.
-
-| Condition                  | Planner output                                                   |
-| -------------------------- | ---------------------------------------------------------------- |
-| ≤ 3 phases, ≤ 3 days       | **One** `PLAN-{task}.md`                                         |
-| > 3 phases **or** > 3 days | **Multiple** `PLAN-{task}-phase1.md`, `PLAN-{task}-phase2.md`, … |
-
-**Multi-plan rules:**
-
-- Naming: `PLAN-{task}-phase1.md`, `PLAN-{task}-phase2.md`, …
-- Order: Execute in numeric order; phase N starts only after phase N−1 is complete.
-- Each file: scope **only** that phase; Prerequisites state "Phase N−1 complete" (or prior deliverables); clear handoff to next file.
-- Index (optional): planner may add `PLAN-{task}-INDEX.md` listing phases and file names for navigation.
-
----
-
-## ⛔ 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: RESEARCH
-
-| Agent  | `researcher`                                  |
-| ------ | --------------------------------------------- |
-| Goal   | Research best practices and patterns          |
-| Output | `./reports/{topic}/researchers/RESEARCH-{task}`    |
-| Exit   | Best practices identified, sources documented |
-
----
-
-## 🎭 Phase 2: CODEBASE ANALYSIS
-
-| Agent  | `scouter`                                    |
-| ------ | -------------------------------------------- |
-| Goal   | Full architecture mapping                    |
-| Output | `./reports/{topic}/scouts/SCOUT-{task}`           |
-| Exit   | Architecture understood, dependencies mapped |
-
----
-
-## 🎭 Phase 3: DESIGN (IF UI NEEDED)
-
-| Agent   | `designer`                                        |
-| ------- | ------------------------------------------------- |
-| Trigger | Task involves UI/UX                               |
-| Goal    | Design approach input                             |
-| Exit    | Design approach defined, accessibility considered |
-
----
-
-## 🎭 Phase 4: PLAN CREATION
-
-| Agent        | `planner`                                                                                                                   |
-| ------------ | --------------------------------------------------------------------------------------------------------------------------- |
-| Prerequisite | **READ** RESEARCH + SCOUT files (and DESIGN if Phase 3 ran)                                                                 |
-| Goal         | Create detailed implementation plan as **one file** or **multiple phase files** (see **Complexity & plan splitting** above) |
-| Output       | One `./reports/{topic}/plans/PLAN-{task}` **or** multiple `./reports/{topic}/plans/PLAN-{task}-phase1`, `PLAN-{task}-phase2`, …    |
-
-**Directive to planner:** If the task decomposes into **> 3 phases** or **> 3 days** effort, produce **multiple plan files** (one per phase/milestone), each executable in sequence. Otherwise produce a single `PLAN-{task}.md`.
-
-**CONSTRAINT INHERITANCE:**
-
-```
-Plan(s) MUST reference prior phases:
-- "Based on research finding R1..."
-- "Following pattern from Scout..."
-- "Per design decision D1..."
-```
-
-| Exit | One plan file **or** multiple phase plan files created; each has scope, prerequisites, tasks, exit criteria, risks, rollback; order and handoffs clear |
-
----
-
----
-
-## COMPLETION
-
-Present plan with:
-
-1. ✅ **Plan Ready** — `./reports/{topic}/plans/PLAN-{task}` (single) **or** `PLAN-{task}-phase1`, `PLAN-{task}-phase2`, … (multi-phase, execute in order)
-2. 🔒 **Context Optimized** — Ready for focus implementation
-3. 🍳 **Implement** → `/code:focus` (run phase-by-phase when multiple plan files exist)

package/commands/report/focus.md

@@ -1,107 +0,0 @@
----
-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. 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.
-
----
-
-## 📁 DELIVERABLES (Reporter chooses from user intent)
-
-| User intent | Reporter output |
-| ----------- | ---------------- |
-| **Create report** | `./reports/{topic}/general/REPORT-FOCUS-{date}` 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/{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: 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/{topic}/general/REPORT-FOCUS-{date}`. **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/{topic}/general/REPORT-FOCUS-{date}` (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/test/focus.md

@@ -1,123 +0,0 @@
----
-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. 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) |
-
----
-
-## 📁 PLAN CHECKPOINT VERIFICATION
-
-```
-IF ./reports/{topic}/plans/PLAN-{scope} exists (.md file or folder):
-  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 |
-
----
-- Rejected approaches
-- Planning noise
-- Chat history
-
-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`