@namch/agent-assistant 1.0.2 → 1.0.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +24 -9
- package/agents/reporter.md +177 -0
- package/code-assistants/antigravity-assistant/AntigravityGlobal.agent.md +3 -1
- package/code-assistants/antigravity-assistant/GEMINI.md +2 -0
- package/code-assistants/copilot-assistant/agent-assistant.agent.md +5 -0
- package/code-assistants/cursor-assistant/rules/agent-assistant.mdc +3 -1
- package/commands/code/focus.md +323 -0
- package/commands/code/hard.md +59 -0
- package/commands/code.md +13 -7
- package/commands/cook/focus.md +262 -0
- package/commands/cook/hard.md +59 -0
- package/commands/cook.md +13 -7
- package/commands/debug/focus.md +155 -0
- package/commands/debug/hard.md +53 -0
- package/commands/debug.md +9 -4
- package/commands/design/focus.md +267 -0
- package/commands/design/hard.md +53 -0
- package/commands/design.md +13 -7
- package/commands/fix/focus.md +175 -0
- package/commands/fix/hard.md +57 -0
- package/commands/fix.md +13 -7
- package/commands/plan/focus.md +190 -0
- package/commands/plan/hard.md +56 -0
- package/commands/plan.md +13 -7
- package/commands/report/fast.md +71 -0
- package/commands/report/focus.md +156 -0
- package/commands/report/hard.md +112 -0
- package/commands/report.md +89 -0
- package/commands/test/focus.md +165 -0
- package/commands/test/hard.md +53 -0
- package/commands/test.md +9 -4
- package/documents/business/business-features.md +1 -1
- package/documents/business/business-glossary.md +9 -8
- package/documents/business/business-prd.md +8 -8
- package/documents/knowledge-architecture.md +1 -1
- package/documents/knowledge-domain.md +5 -4
- package/documents/knowledge-overview.md +7 -6
- package/documents/knowledge-source-base.md +9 -9
- package/package.json +1 -1
- package/rules/AGENT-RULES.md +2 -1
- package/rules/BOOTSTRAP.md +3 -0
- package/rules/QUICK-REFERENCE.md +8 -0
|
@@ -0,0 +1,112 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: ⚡ Detailed Report — Comprehensive project analysis and documentation
|
|
3
|
+
version: "1.0"
|
|
4
|
+
category: documentation
|
|
5
|
+
execution-mode: execute
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
# /report:hard — Comprehensive Project Report
|
|
9
|
+
|
|
10
|
+
> **MISSION**: Generate detailed output for **any topic** — reports, doc updates, or template-based files.
|
|
11
|
+
>
|
|
12
|
+
> Use for: sprint reviews, technical docs, any-topic reports, updating existing files, or generating from user format/template.
|
|
13
|
+
|
|
14
|
+
<task>$ARGUMENTS</task>
|
|
15
|
+
|
|
16
|
+
---
|
|
17
|
+
|
|
18
|
+
## 🛑 PRE-FLIGHT (DO FIRST — BLOCKS PHASE 1)
|
|
19
|
+
|
|
20
|
+
**LOAD now** (in order; path `./rules/` or `~/.{TOOL}/skills/agent-assistant/rules/`):
|
|
21
|
+
|
|
22
|
+
1. ORCHESTRATION-LAWS.md
|
|
23
|
+
2. ADAPTIVE-EXECUTION.md
|
|
24
|
+
3. EXECUTION-PROTOCOL.md
|
|
25
|
+
|
|
26
|
+
**⛔ Do not run Phase 1 until all are loaded.** Follow **all** rules in those files; they override any conflicting instructions in this file.
|
|
27
|
+
|
|
28
|
+
---
|
|
29
|
+
|
|
30
|
+
## 🔀 TIERED EXECUTION
|
|
31
|
+
|
|
32
|
+
| Tier | When | Action |
|
|
33
|
+
| ---------- | ------------------ | ---------------------------- |
|
|
34
|
+
| **TIER 1** | runSubagent EXISTS | Invoke sub-agent (MANDATORY) |
|
|
35
|
+
| **TIER 2** | Tool MISSING | EMBODY agent file (FALLBACK) |
|
|
36
|
+
|
|
37
|
+
**❌ Anti-Lazy**: Never use TIER 2 when TIER 1 tool available.
|
|
38
|
+
|
|
39
|
+
---
|
|
40
|
+
|
|
41
|
+
## 📁 DELIVERABLES (Reporter chooses from user intent)
|
|
42
|
+
|
|
43
|
+
| User intent | Reporter output |
|
|
44
|
+
| ----------- | ---------------- |
|
|
45
|
+
| **Create report** | New file: `./reports/general/REPORT-{type}-{date}.md` (or path user asks) |
|
|
46
|
+
| **Update existing** | **Edit** related files (docs, README, etc.); do **not** create new report unless also asked |
|
|
47
|
+
| **From template** | New file(s) matching user format/template (e.g. after scouting source) |
|
|
48
|
+
|
|
49
|
+
| Agent | Output (when creating) |
|
|
50
|
+
| ---------- | ------------------------------------------------ |
|
|
51
|
+
| researcher | `./reports/researchers/RESEARCH-{task}.md` (optional) |
|
|
52
|
+
| scouter | `./reports/scouts/SCOUT-{task}.md` (optional) |
|
|
53
|
+
| reporter | Per table above — create report **or** update existing **or** generate from template |
|
|
54
|
+
|
|
55
|
+
All files in `./reports/` → English only.
|
|
56
|
+
|
|
57
|
+
---
|
|
58
|
+
|
|
59
|
+
## ⛔ INCREMENTAL EXECUTION (MANDATORY)
|
|
60
|
+
|
|
61
|
+
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.
|
|
62
|
+
|
|
63
|
+
---
|
|
64
|
+
|
|
65
|
+
## 🎭 Phase 1: RESEARCH
|
|
66
|
+
|
|
67
|
+
| Agent | `researcher` |
|
|
68
|
+
| ------ | ---------------------------------------------------------- |
|
|
69
|
+
| Goal | Research report scope, audience, and best practices for project/technical reports |
|
|
70
|
+
| Output | `./reports/researchers/RESEARCH-{task}.md` (optional) |
|
|
71
|
+
| Exit | Report scope and criteria defined, templates identified |
|
|
72
|
+
|
|
73
|
+
---
|
|
74
|
+
|
|
75
|
+
## 🎭 Phase 2: DEEP SCAN
|
|
76
|
+
|
|
77
|
+
| Agent | `scouter` |
|
|
78
|
+
| ------ | --------------------------------- |
|
|
79
|
+
| Goal | Full codebase structural analysis |
|
|
80
|
+
| Output | `./reports/scouts/SCOUT-{task}.md` |
|
|
81
|
+
| Exit | Architecture and recent changes documented |
|
|
82
|
+
|
|
83
|
+
---
|
|
84
|
+
|
|
85
|
+
## 🎭 Phase 3: DATA SYNTHESIS
|
|
86
|
+
|
|
87
|
+
| Agent | `reporter` |
|
|
88
|
+
| ----------- | ------------------------------------------------ |
|
|
89
|
+
| Prerequisite| **READ** RESEARCH + SCOUT outputs if present |
|
|
90
|
+
| Goal | Aggregate data from Scouter, Plans, and History; identify discrepancies and milestones |
|
|
91
|
+
| Exit | Data synthesized, gaps and milestones identified |
|
|
92
|
+
|
|
93
|
+
---
|
|
94
|
+
|
|
95
|
+
## 🎭 Phase 4: OUTPUT (create / update / from template)
|
|
96
|
+
|
|
97
|
+
| Agent | `reporter` |
|
|
98
|
+
| ----- | --------------------------------------------------------------------------- |
|
|
99
|
+
| Goal | From **user intent**: (1) create new report, (2) **update** existing files, or (3) generate from template/format |
|
|
100
|
+
| Output| **Create**: `./reports/general/REPORT-{type}-{date}.md` or path user asked. **Update**: edit related files. **Template**: file(s) matching user format. |
|
|
101
|
+
| Exit | Deliverable matches intent — report file, updated docs, or template-based file(s). |
|
|
102
|
+
|
|
103
|
+
---
|
|
104
|
+
|
|
105
|
+
## COMPLETION
|
|
106
|
+
|
|
107
|
+
Deliverable per **user intent**:
|
|
108
|
+
|
|
109
|
+
1. ✅ **Create report** → `./reports/general/REPORT-{type}-{date}.md` (or path user asked)
|
|
110
|
+
2. ✅ **Update existing** → Related files edited; list what was updated
|
|
111
|
+
3. ✅ **From template** → File(s) matching user format; list path(s)
|
|
112
|
+
4. 📢 **Share** → `/internal-comms` (optional)
|
|
@@ -0,0 +1,89 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: 📝 Report Router — Multi-purpose reporting (create report, update docs, or generate from template)
|
|
3
|
+
version: "1.0"
|
|
4
|
+
category: documentation
|
|
5
|
+
execution-mode: router
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
# /report — Reporting Router
|
|
9
|
+
|
|
10
|
+
> **ROUTER DIRECTIVE**: Analyze reporting needs and route to appropriate reporting workflow.
|
|
11
|
+
>
|
|
12
|
+
> **MULTI-PURPOSE**: Report supports any topic and three output modes — create new report, update existing files, or generate from user template/format.
|
|
13
|
+
|
|
14
|
+
<task>$ARGUMENTS</task>
|
|
15
|
+
|
|
16
|
+
---
|
|
17
|
+
|
|
18
|
+
## 🛑 PRE-FLIGHT (DO FIRST — BLOCKS EXECUTION)
|
|
19
|
+
|
|
20
|
+
**LOAD now** (in order; path `./rules/` or `~/.{TOOL}/skills/agent-assistant/rules/`):
|
|
21
|
+
|
|
22
|
+
1. ORCHESTRATION-LAWS.md
|
|
23
|
+
2. ADAPTIVE-EXECUTION.md
|
|
24
|
+
3. EXECUTION-PROTOCOL.md
|
|
25
|
+
|
|
26
|
+
**⛔ 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.
|
|
27
|
+
|
|
28
|
+
---
|
|
29
|
+
|
|
30
|
+
## OUTPUT MODES (infer from user request)
|
|
31
|
+
|
|
32
|
+
Reporter **infers** the mode from what the user asks for — no fixed phrase list. Choose by **intent**:
|
|
33
|
+
|
|
34
|
+
| Mode | User intent | Reporter action |
|
|
35
|
+
|------|-------------|-----------------|
|
|
36
|
+
| **Create report** | User wants a **new** deliverable (report, summary, analysis, documentation). | Scout/synthesize → write **new** file under `./reports/` or path user specifies. |
|
|
37
|
+
| **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. |
|
|
38
|
+
| **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). |
|
|
39
|
+
|
|
40
|
+
**Topic-agnostic**: Subject is whatever the user asks for — infer from the request; not limited to status or technical only.
|
|
41
|
+
|
|
42
|
+
---
|
|
43
|
+
|
|
44
|
+
## ROUTING LOGIC
|
|
45
|
+
|
|
46
|
+
```
|
|
47
|
+
IF task is simple status update OR summary:
|
|
48
|
+
→ Route to /report:fast
|
|
49
|
+
|
|
50
|
+
IF task is comprehensive analysis OR deep dive OR any non-trivial topic (infer from request):
|
|
51
|
+
→ Route to /report:hard
|
|
52
|
+
|
|
53
|
+
IF task requires absolute context clarity OR "clean slate" analysis:
|
|
54
|
+
→ Route to /report:focus
|
|
55
|
+
|
|
56
|
+
IF user explicitly asks to UPDATE existing files (not create report):
|
|
57
|
+
→ Still use /report:hard or /report:focus; reporter OUTPUT MODE = update existing files
|
|
58
|
+
|
|
59
|
+
IF unsure:
|
|
60
|
+
→ Default to /report:fast (escalate if needed)
|
|
61
|
+
```
|
|
62
|
+
|
|
63
|
+
---
|
|
64
|
+
|
|
65
|
+
## AVAILABLE ROUTES
|
|
66
|
+
|
|
67
|
+
| Route | When to Use |
|
|
68
|
+
| --------------- | --------------------------------------------------------------------------- |
|
|
69
|
+
| `/report:fast` | Quick status updates, daily summaries |
|
|
70
|
+
| `/report:hard` | Detailed analysis, any topic (algorithms, docs, changes), template-based |
|
|
71
|
+
| `/report:focus` | Deep analysis with **enforced context optimization**; update or create |
|
|
72
|
+
|
|
73
|
+
---
|
|
74
|
+
|
|
75
|
+
## PRESENT OPTIONS
|
|
76
|
+
|
|
77
|
+
```markdown
|
|
78
|
+
## 📝 Reporting Mode Selection
|
|
79
|
+
|
|
80
|
+
**Task**: [parsed task]
|
|
81
|
+
|
|
82
|
+
**Choose workflow:**
|
|
83
|
+
|
|
84
|
+
1. ⚡ **Fast** → `/report:fast` — Quick summary
|
|
85
|
+
2. ⚡⚡⚡ **Hard** → `/report:hard` — Full analysis, any topic; create report **or** update existing files / use template
|
|
86
|
+
3. 🎯 **Focus** → `/report:focus` — Deep analysis with **automatic context clearing**; create or update per task
|
|
87
|
+
|
|
88
|
+
⏳ Awaiting selection...
|
|
89
|
+
```
|
|
@@ -0,0 +1,165 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: 🔒 Focused Test — Comprehensive QA with enforced context optimization
|
|
3
|
+
version: "1.0"
|
|
4
|
+
category: validation
|
|
5
|
+
execution-mode: execute
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
# /test:focus — Focus Comprehensive Testing
|
|
9
|
+
|
|
10
|
+
> **MISSION**: Full QA workflow with **enforced context optimization**.
|
|
11
|
+
>
|
|
12
|
+
> This variant automatically clears context before test execution—no user prompt required.
|
|
13
|
+
> Use when you want guaranteed focused test execution without strategy noise.
|
|
14
|
+
|
|
15
|
+
<scope>$ARGUMENTS</scope>
|
|
16
|
+
|
|
17
|
+
---
|
|
18
|
+
|
|
19
|
+
## 🛑 PRE-FLIGHT (DO FIRST — BLOCKS PHASE 1)
|
|
20
|
+
|
|
21
|
+
**LOAD now** (in order; path `./rules/` or `~/.{TOOL}/skills/agent-assistant/rules/`):
|
|
22
|
+
|
|
23
|
+
1. ORCHESTRATION-LAWS.md
|
|
24
|
+
2. ADAPTIVE-EXECUTION.md
|
|
25
|
+
3. EXECUTION-PROTOCOL.md
|
|
26
|
+
|
|
27
|
+
**⛔ Do not run Phase 1 until all are loaded.** Follow **all** rules in those files; they override any conflicting instructions in this file.
|
|
28
|
+
|
|
29
|
+
---
|
|
30
|
+
|
|
31
|
+
## 🔀 TIERED EXECUTION
|
|
32
|
+
|
|
33
|
+
| Tier | When | Action |
|
|
34
|
+
| ---------- | ------------------ | ---------------------------- |
|
|
35
|
+
| **TIER 1** | runSubagent EXISTS | Invoke sub-agent (MANDATORY) |
|
|
36
|
+
| **TIER 2** | Tool MISSING | EMBODY agent file (FALLBACK) |
|
|
37
|
+
|
|
38
|
+
---
|
|
39
|
+
|
|
40
|
+
## 📁 PLAN CHECKPOINT VERIFICATION
|
|
41
|
+
|
|
42
|
+
```
|
|
43
|
+
IF ./reports/plans/PLAN-{scope}.md exists:
|
|
44
|
+
1. READ plan completely
|
|
45
|
+
2. EXTRACT all checkpoints
|
|
46
|
+
3. FOR EACH checkpoint → Create test
|
|
47
|
+
4. OUTPUT: "Checkpoint Coverage: X/Y"
|
|
48
|
+
```
|
|
49
|
+
|
|
50
|
+
---
|
|
51
|
+
|
|
52
|
+
## ⛔ INCREMENTAL EXECUTION (MANDATORY)
|
|
53
|
+
|
|
54
|
+
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).
|
|
55
|
+
|
|
56
|
+
---
|
|
57
|
+
|
|
58
|
+
## 🎭 Phase 1: TEST STRATEGY
|
|
59
|
+
|
|
60
|
+
| Agent | `tester` |
|
|
61
|
+
| ----- | --------------------------------------- |
|
|
62
|
+
| Goal | Design test strategy |
|
|
63
|
+
| Exit | Strategy defined, test types identified |
|
|
64
|
+
|
|
65
|
+
---
|
|
66
|
+
|
|
67
|
+
## 🛡️ STRICT CONTEXT GATE — Automatic Context Optimization
|
|
68
|
+
|
|
69
|
+
> **⚡ FOCUS MODE**: This checkpoint executes automatically. NO user input required.
|
|
70
|
+
>
|
|
71
|
+
> **PURPOSE**: Prevent "context rot" by forcibly clearing strategy discussion noise.
|
|
72
|
+
> This acts as a mandatory "firewall" before test execution phases.
|
|
73
|
+
|
|
74
|
+
### 🔒 AUTOMATIC EXECUTION (NO PROMPT)
|
|
75
|
+
|
|
76
|
+
```yaml
|
|
77
|
+
strict_context_gate:
|
|
78
|
+
mode: "AUTOMATIC - No user interaction"
|
|
79
|
+
behavior: "Force Clear context & Execute"
|
|
80
|
+
|
|
81
|
+
execution:
|
|
82
|
+
1. ANNOUNCE: |
|
|
83
|
+
## 🛡️ Strict Context Gate — Automatic
|
|
84
|
+
|
|
85
|
+
✅ **Test Strategy Complete**: Strategy defined, test types identified.
|
|
86
|
+
🔒 **Focus Mode**: Automatically clearing context for test execution.
|
|
87
|
+
|
|
88
|
+
⚡ Executing: **Clear context & Execute**...
|
|
89
|
+
|
|
90
|
+
2. CONTEXT_DIRECTIVE: |
|
|
91
|
+
╔══════════════════════════════════════════════════════════════════╗
|
|
92
|
+
║ ⛔ MANDATORY CONTEXT RESET — FOCUS MODE ║
|
|
93
|
+
╠══════════════════════════════════════════════════════════════════╣
|
|
94
|
+
║ IGNORE: All strategy discussions, rejected approaches, ║
|
|
95
|
+
║ and intermediate test planning reasoning. ║
|
|
96
|
+
║ ║
|
|
97
|
+
║ SOLE SOURCE OF TRUTH: Finalized test strategy. ║
|
|
98
|
+
║ ║
|
|
99
|
+
║ PROCEED: Execute test phases with FRESH context mindset. ║
|
|
100
|
+
║ Focus purely on test execution and verification. ║
|
|
101
|
+
╚══════════════════════════════════════════════════════════════════╝
|
|
102
|
+
|
|
103
|
+
3. LOAD: Finalized test strategy as if seeing it for the first time
|
|
104
|
+
|
|
105
|
+
4. PROCEED: Start Phase 2 (Dependency Mapping) immediately
|
|
106
|
+
```
|
|
107
|
+
|
|
108
|
+
### 📋 Post-Gate Status
|
|
109
|
+
|
|
110
|
+
```markdown
|
|
111
|
+
🔒 **Context Gate Passed**
|
|
112
|
+
- Previous context: DISCARDED
|
|
113
|
+
- Active context: Test strategy only
|
|
114
|
+
- Mode: Fresh execution start
|
|
115
|
+
|
|
116
|
+
Proceeding to Test Execution...
|
|
117
|
+
```
|
|
118
|
+
|
|
119
|
+
---
|
|
120
|
+
|
|
121
|
+
## 🎭 Phase 2: DEPENDENCY MAPPING
|
|
122
|
+
|
|
123
|
+
| Agent | `scouter` |
|
|
124
|
+
| ----- | -------------------------------------- |
|
|
125
|
+
| Goal | Map test dependencies |
|
|
126
|
+
| Exit | Dependencies mapped, environment ready |
|
|
127
|
+
|
|
128
|
+
---
|
|
129
|
+
|
|
130
|
+
## 🎭 Phase 3: TEST EXECUTION
|
|
131
|
+
|
|
132
|
+
| Agent | `tester` |
|
|
133
|
+
| ------------ | --------------------------------------------------------------- |
|
|
134
|
+
| Prerequisite | READ PLAN file if exists |
|
|
135
|
+
| Goal | Run full test suite |
|
|
136
|
+
| Exit | All tests run, coverage measured, checkpoint mapping documented |
|
|
137
|
+
|
|
138
|
+
---
|
|
139
|
+
|
|
140
|
+
## 🎭 Phase 4: FAILURE ANALYSIS (IF FAILURES)
|
|
141
|
+
|
|
142
|
+
| Agent | `debugger` |
|
|
143
|
+
| ------- | ---------------------- |
|
|
144
|
+
| Trigger | If failures exist |
|
|
145
|
+
| Goal | Analyze failures |
|
|
146
|
+
| Exit | Root causes identified |
|
|
147
|
+
|
|
148
|
+
---
|
|
149
|
+
|
|
150
|
+
## 🎭 Phase 5: QUALITY GATES
|
|
151
|
+
|
|
152
|
+
| Agent | `tester` |
|
|
153
|
+
| ----- | --------------------------------- |
|
|
154
|
+
| Goal | Verify quality gates |
|
|
155
|
+
| Exit | All gates pass, coverage adequate |
|
|
156
|
+
|
|
157
|
+
---
|
|
158
|
+
|
|
159
|
+
## COMPLETION
|
|
160
|
+
|
|
161
|
+
Present test report with:
|
|
162
|
+
|
|
163
|
+
1. ✅ **Pass** — All tests green (Focus Mode)
|
|
164
|
+
2. 🔧 **Fix** → `/fix:fast`
|
|
165
|
+
3. 📝 **Review** → `/review`
|
package/commands/test/hard.md
CHANGED
|
@@ -61,6 +61,59 @@ One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in
|
|
|
61
61
|
|
|
62
62
|
---
|
|
63
63
|
|
|
64
|
+
## 🛡️ VERIFICATION CHECKPOINT — Context Optimization
|
|
65
|
+
|
|
66
|
+
> **PURPOSE**: Prevent "context rot" by clearing strategy discussion before test execution.
|
|
67
|
+
>
|
|
68
|
+
> Test strategy discussions may include rejected approaches that can confuse execution.
|
|
69
|
+
> This checkpoint ensures clean handoff to test execution phases.
|
|
70
|
+
|
|
71
|
+
### ⚡ OPTIONS (Present to User)
|
|
72
|
+
|
|
73
|
+
```markdown
|
|
74
|
+
## 🛡️ Context Optimization Checkpoint
|
|
75
|
+
|
|
76
|
+
**Test Strategy Complete** — Strategy defined, ready for execution.
|
|
77
|
+
|
|
78
|
+
**Choose how to proceed:**
|
|
79
|
+
|
|
80
|
+
| Option | Action | Description |
|
|
81
|
+
|--------|--------|-------------|
|
|
82
|
+
| **1. 🚀 Clear context & Execute** | `RECOMMENDED` | Fresh start: Focus on strategy, ignore discussion history |
|
|
83
|
+
| **2. ⏸️ Review Strategy** | `SAFE` | Clear context, show strategy summary, wait for approval |
|
|
84
|
+
| **3. ⚠️ Continue (No Clear)** | `RISKY` | Keep full history (may affect test focus) |
|
|
85
|
+
|
|
86
|
+
⏳ Awaiting selection...
|
|
87
|
+
```
|
|
88
|
+
|
|
89
|
+
### 🔄 EXECUTION BEHAVIOR
|
|
90
|
+
|
|
91
|
+
```yaml
|
|
92
|
+
option_1_clear_execute:
|
|
93
|
+
behavior: "RECOMMENDED - Clean execution"
|
|
94
|
+
steps:
|
|
95
|
+
1. ACKNOWLEDGE: "🚀 Context optimized. Executing test strategy."
|
|
96
|
+
2. CONTEXT_DIRECTIVE: |
|
|
97
|
+
⛔ IGNORE strategy discussion and rejected approaches.
|
|
98
|
+
✅ FINALIZED STRATEGY is SOLE SOURCE OF TRUTH.
|
|
99
|
+
3. PROCEED: Continue to test execution phases
|
|
100
|
+
|
|
101
|
+
option_2_review_strategy:
|
|
102
|
+
behavior: "Clear and show summary"
|
|
103
|
+
steps:
|
|
104
|
+
1. ACKNOWLEDGE: "⏸️ Context cleared."
|
|
105
|
+
2. OUTPUT: Display strategy summary
|
|
106
|
+
3. WAIT: For user approval
|
|
107
|
+
|
|
108
|
+
option_3_continue_no_clear:
|
|
109
|
+
behavior: "Proceed with caution"
|
|
110
|
+
steps:
|
|
111
|
+
1. WARN: "⚠️ Discussion history retained."
|
|
112
|
+
2. PROCEED: Continue with existing context
|
|
113
|
+
```
|
|
114
|
+
|
|
115
|
+
---
|
|
116
|
+
|
|
64
117
|
## 🎭 Phase 2: DEPENDENCY MAPPING
|
|
65
118
|
|
|
66
119
|
| Agent | `scouter` |
|
package/commands/test.md
CHANGED
|
@@ -33,6 +33,9 @@ IF scope is limited (unit tests, quick check):
|
|
|
33
33
|
IF scope is comprehensive (full suite, E2E):
|
|
34
34
|
→ Route to /test:hard
|
|
35
35
|
|
|
36
|
+
IF scope is comprehensive AND clean execution focus is critical:
|
|
37
|
+
→ Route to /test:focus
|
|
38
|
+
|
|
36
39
|
IF unsure:
|
|
37
40
|
→ Default to /test:fast
|
|
38
41
|
```
|
|
@@ -41,10 +44,11 @@ IF unsure:
|
|
|
41
44
|
|
|
42
45
|
## AVAILABLE ROUTES
|
|
43
46
|
|
|
44
|
-
| Route
|
|
45
|
-
|
|
|
46
|
-
| `/test:fast`
|
|
47
|
-
| `/test:hard`
|
|
47
|
+
| Route | When to Use |
|
|
48
|
+
| -------------- | -------------------------------------------------- |
|
|
49
|
+
| `/test:fast` | Quick tests, unit tests |
|
|
50
|
+
| `/test:hard` | Full test suite, E2E |
|
|
51
|
+
| `/test:focus` | Full testing with **enforced context optimization** |
|
|
48
52
|
|
|
49
53
|
---
|
|
50
54
|
|
|
@@ -59,6 +63,7 @@ IF unsure:
|
|
|
59
63
|
|
|
60
64
|
1. ⚡ **Fast** → `/test:fast` — Quick tests
|
|
61
65
|
2. ⚡⚡⚡ **Hard** → `/test:hard` — Comprehensive testing
|
|
66
|
+
3. 🔒 **Focus** → `/test:focus` — Comprehensive testing with **automatic context clearing** (focused execution)
|
|
62
67
|
|
|
63
68
|
⏳ Awaiting selection...
|
|
64
69
|
```
|
|
@@ -14,7 +14,7 @@ Agent Assistant provides a comprehensive feature set organized into six categori
|
|
|
14
14
|
| Category | Feature Count | Description |
|
|
15
15
|
|----------|---------------|-------------|
|
|
16
16
|
| Specialist Agents | 20 | Domain expert personas |
|
|
17
|
-
| Command Workflows |
|
|
17
|
+
| Command Workflows | 50+ | Development workflow automations (incl. /report, focus variant) |
|
|
18
18
|
| Domain Skills | 310+ | On-demand knowledge modules |
|
|
19
19
|
| Quality Gates | 5 | Automated verification checkpoints |
|
|
20
20
|
| Orchestration Rules | 8 | Governance and coordination protocols |
|
|
@@ -40,7 +40,7 @@ A **slash-prefixed workflow trigger** that initiates a structured development pr
|
|
|
40
40
|
| With variant | `/cook:hard` |
|
|
41
41
|
| With argument | `/cook:hard "implement OAuth"` |
|
|
42
42
|
|
|
43
|
-
**Available Commands**: `/cook`, `/fix`, `/plan`, `/test`, `/review`, `/debug`, `/design`, `/docs`, `/deploy`, `/ask`, `/auto`, `/brainstorm`, `/code`
|
|
43
|
+
**Available Commands**: `/cook`, `/fix`, `/plan`, `/test`, `/review`, `/debug`, `/design`, `/docs`, `/report`, `/deploy`, `/ask`, `/auto`, `/brainstorm`, `/code`
|
|
44
44
|
|
|
45
45
|
---
|
|
46
46
|
|
|
@@ -477,16 +477,17 @@ A **document specifying** what a product should do, including features, requirem
|
|
|
477
477
|
|
|
478
478
|
| Command | Purpose | Variants |
|
|
479
479
|
|---------|---------|----------|
|
|
480
|
-
| `/cook` | Implement features | `:fast`, `:hard` |
|
|
481
|
-
| `/code` | Generate code snippets | `:fast`, `:hard` |
|
|
482
|
-
| `/fix` | Fix bugs | `:fast`, `:hard` |
|
|
483
|
-
| `/test` | Generate tests | `:fast`, `:hard` |
|
|
480
|
+
| `/cook` | Implement features | `:fast`, `:hard`, `:focus` |
|
|
481
|
+
| `/code` | Generate code snippets | `:fast`, `:hard`, `:focus` |
|
|
482
|
+
| `/fix` | Fix bugs | `:fast`, `:hard`, `:focus` |
|
|
483
|
+
| `/test` | Generate tests | `:fast`, `:hard`, `:focus` |
|
|
484
484
|
| `/review` | Code review | `:fast`, `:hard` |
|
|
485
|
-
| `/debug` | Debug issues | `:fast`, `:hard` |
|
|
486
|
-
| `/plan` | Create implementation plans | `:fast`, `:hard` |
|
|
485
|
+
| `/debug` | Debug issues | `:fast`, `:hard`, `:focus` |
|
|
486
|
+
| `/plan` | Create implementation plans | `:fast`, `:hard`, `:focus` |
|
|
487
487
|
| `/brainstorm` | Discover requirements | `:fast`, `:hard` |
|
|
488
|
-
| `/design` | UI/UX design | `:fast`, `:hard` |
|
|
488
|
+
| `/design` | UI/UX design | `:fast`, `:hard`, `:focus` |
|
|
489
489
|
| `/docs` | Generate documentation | `:core`, `:business`, `:audit` |
|
|
490
|
+
| `/report` | Create/update reports, summaries | `:fast`, `:hard`, `:focus` |
|
|
490
491
|
| `/deploy` | Deployment operations | `:check`, `:preview`, `:production`, `:rollback` |
|
|
491
492
|
| `/ask` | Q&A about codebase | `:fast`, `:hard` |
|
|
492
493
|
| `/auto` | Auto-detect best command | — |
|
|
@@ -11,7 +11,7 @@
|
|
|
11
11
|
|
|
12
12
|
### 1.1 Product Overview
|
|
13
13
|
|
|
14
|
-
**Agent Assistant** is an open-source multi-agent orchestration framework that transforms a single AI coding assistant into a coordinated team of
|
|
14
|
+
**Agent Assistant** is an open-source multi-agent orchestration framework that transforms a single AI coding assistant into a coordinated team of 21 specialist agents. It provides structured workflows, quality gates, and 310+ domain skills for production-grade AI-assisted software development.
|
|
15
15
|
|
|
16
16
|
### 1.2 Vision Statement
|
|
17
17
|
|
|
@@ -19,7 +19,7 @@
|
|
|
19
19
|
|
|
20
20
|
### 1.3 Mission Statement
|
|
21
21
|
|
|
22
|
-
> **"To democratize software engineering excellence by orchestrating AI coding assistants into a cohesive team of
|
|
22
|
+
> **"To democratize software engineering excellence by orchestrating AI coding assistants into a cohesive team of 21 specialist agents, enabling developers to ship faster, safer, and more consistently through repeatable workflows and automated quality verification."**
|
|
23
23
|
|
|
24
24
|
### 1.4 Key Metrics
|
|
25
25
|
|
|
@@ -135,7 +135,7 @@ AI coding assistants are powerful but unstructured. Developers use AI tools in a
|
|
|
135
135
|
|
|
136
136
|
| ID | Requirement | Priority | Status |
|
|
137
137
|
|----|-------------|----------|--------|
|
|
138
|
-
| FR-001.1 | System SHALL support
|
|
138
|
+
| FR-001.1 | System SHALL support 21 specialist agents | Must-Have | ✅ Complete |
|
|
139
139
|
| FR-001.2 | System SHALL route tasks to appropriate agents | Must-Have | ✅ Complete |
|
|
140
140
|
| FR-001.3 | System SHALL support tiered execution (sub-agent + embody) | Must-Have | ✅ Complete |
|
|
141
141
|
| FR-001.4 | System SHALL enforce orchestration laws | Must-Have | ✅ Complete |
|
|
@@ -145,7 +145,7 @@ AI coding assistants are powerful but unstructured. Developers use AI tools in a
|
|
|
145
145
|
|
|
146
146
|
| ID | Requirement | Priority | Status |
|
|
147
147
|
|----|-------------|----------|--------|
|
|
148
|
-
| FR-002.1 | System SHALL support
|
|
148
|
+
| FR-002.1 | System SHALL support 50+ command workflows | Must-Have | ✅ Complete |
|
|
149
149
|
| FR-002.2 | System SHALL support workflow variants (:fast, :hard) | Must-Have | ✅ Complete |
|
|
150
150
|
| FR-002.3 | System SHALL execute phases sequentially | Must-Have | ✅ Complete |
|
|
151
151
|
| FR-002.4 | System SHALL verify exit criteria before phase transition | Must-Have | ✅ Complete |
|
|
@@ -284,8 +284,8 @@ AI coding assistants are powerful but unstructured. Developers use AI tools in a
|
|
|
284
284
|
|
|
285
285
|
| Feature | Description | Status |
|
|
286
286
|
|---------|-------------|--------|
|
|
287
|
-
|
|
|
288
|
-
| Core Command Workflows | /cook, /fix, /plan, etc. | ✅ Complete |
|
|
287
|
+
| 21 Specialist Agents | Domain experts | ✅ Complete |
|
|
288
|
+
| Core Command Workflows | /cook, /fix, /plan, /report, etc. | ✅ Complete |
|
|
289
289
|
| Quality Gates | 5 automated gates | ✅ Complete |
|
|
290
290
|
| Matrix Skill Discovery | 310+ skills | ✅ Complete |
|
|
291
291
|
| Multi-Tool Support | 4 AI tools | ✅ Complete |
|
|
@@ -324,8 +324,8 @@ AI coding assistants are powerful but unstructured. Developers use AI tools in a
|
|
|
324
324
|
|
|
325
325
|
| Feature | Status |
|
|
326
326
|
|---------|--------|
|
|
327
|
-
|
|
|
328
|
-
|
|
|
327
|
+
| 21 Specialist Agents | ✅ |
|
|
328
|
+
| 50+ Command Workflows | ✅ |
|
|
329
329
|
| 310+ Domain Skills | ✅ |
|
|
330
330
|
| Matrix Skill Discovery | ✅ |
|
|
331
331
|
| Multi-Tool Support | ✅ |
|
|
@@ -41,7 +41,7 @@ Agent Assistant is a **multi-agent orchestration framework** that transforms a s
|
|
|
41
41
|
└─────────────────┬─────────────────┘
|
|
42
42
|
▼
|
|
43
43
|
┌─────────────────────────────────────────────────────────────────────────────┐
|
|
44
|
-
│ SPECIALIST AGENTS (
|
|
44
|
+
│ SPECIALIST AGENTS (21) │
|
|
45
45
|
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
|
|
46
46
|
│ │ tech-lead │ │ backend- │ │ frontend- │ │ security- │ ... │
|
|
47
47
|
│ │ │ │ engineer │ │ engineer │ │ engineer │ │
|
|
@@ -11,7 +11,7 @@ Agent Assistant operates in the domain of **AI-assisted software development orc
|
|
|
11
11
|
```
|
|
12
12
|
┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐
|
|
13
13
|
│ AGENTS │────▶│ COMMANDS │────▶│ SKILLS │
|
|
14
|
-
│ (
|
|
14
|
+
│ (21 entities) │ │ (50+ entities) │ │ (310+ entities) │
|
|
15
15
|
└─────────────────┘ └─────────────────┘ └─────────────────┘
|
|
16
16
|
│ │ │
|
|
17
17
|
▼ ▼ ▼
|
|
@@ -123,13 +123,14 @@ execution-mode: string # "execute" | "router"
|
|
|
123
123
|
|
|
124
124
|
| Command | Description | Variants | Category |
|
|
125
125
|
|---------|-------------|----------|----------|
|
|
126
|
-
| `/cook` | Implement features | `:fast`, `:hard` | development |
|
|
126
|
+
| `/cook` | Implement features | `:fast`, `:hard`, `:focus` | development |
|
|
127
127
|
| `/code` | Write code snippets | `:fast`, `:hard` | development |
|
|
128
|
-
| `/fix` | Fix bugs and refactor | `:fast`, `:hard` | development |
|
|
128
|
+
| `/fix` | Fix bugs and refactor | `:fast`, `:hard`, `:focus` | development |
|
|
129
129
|
| `/test` | Generate tests | `:fast`, `:hard` | quality |
|
|
130
130
|
| `/review` | Code review | `:fast`, `:hard` | quality |
|
|
131
131
|
| `/debug` | Systematic debugging | `:fast`, `:hard` | quality |
|
|
132
|
-
| `/plan` | Implementation planning | `:fast`, `:hard` | planning |
|
|
132
|
+
| `/plan` | Implementation planning | `:fast`, `:hard`, `:focus` | planning |
|
|
133
|
+
| `/report` | Create/update reports, summaries | `:fast`, `:hard`, `:focus` | documentation |
|
|
133
134
|
| `/brainstorm` | Requirements discovery | `:fast`, `:hard` | planning |
|
|
134
135
|
| `/design` | UI/UX design | `:fast`, `:hard` | planning |
|
|
135
136
|
| `/docs` | Documentation | `:core`, `:business`, `:audit` | documentation |
|
|
@@ -19,7 +19,7 @@
|
|
|
19
19
|
|
|
20
20
|
## 2. Purpose and Mission
|
|
21
21
|
|
|
22
|
-
Agent Assistant transforms a single AI coding assistant into a **coordinated team of
|
|
22
|
+
Agent Assistant transforms a single AI coding assistant into a **coordinated team of 21 specialist agents** with structured workflows, quality gates, and 310+ domain skills.
|
|
23
23
|
|
|
24
24
|
### Core Value Proposition
|
|
25
25
|
|
|
@@ -35,7 +35,7 @@ With Agent Assistant:
|
|
|
35
35
|
|
|
36
36
|
| Benefit | Description |
|
|
37
37
|
| ------------------ | ----------------------------------------------------- |
|
|
38
|
-
| **Specialization** |
|
|
38
|
+
| **Specialization** | 21 domain expert agents instead of one generalist |
|
|
39
39
|
| **Consistency** | Shared rules, skills, and conventions across all work |
|
|
40
40
|
| **Quality** | Built-in test, review, and security workflows |
|
|
41
41
|
| **Efficiency** | 85% token cost reduction through targeted expertise |
|
|
@@ -47,8 +47,8 @@ With Agent Assistant:
|
|
|
47
47
|
|
|
48
48
|
| Metric | Count | Description |
|
|
49
49
|
| ----------------- | ----- | ---------------------------------------------------------- |
|
|
50
|
-
| Specialist Agents |
|
|
51
|
-
| Command Workflows |
|
|
50
|
+
| Specialist Agents | 21 | Domain experts (backend, frontend, security, tester, reporter, etc.) |
|
|
51
|
+
| Command Workflows | 50+ | Development workflows (/cook, /fix, /plan, /report, /deploy, etc.; variants: fast, hard, focus) |
|
|
52
52
|
| Domain Skills | 310 | On-demand knowledge (React, APIs, databases, DevOps, AI/ML, Security, etc.) |
|
|
53
53
|
| Matrix Domains | 19 | Skill categories (backend, frontend, security, ai-ml, etc.) |
|
|
54
54
|
| Quality Gates | 5 | Compile, lint, test, security, review |
|
|
@@ -200,7 +200,7 @@ Then try development commands:
|
|
|
200
200
|
|
|
201
201
|
## 7. Key Features
|
|
202
202
|
|
|
203
|
-
### 7.1
|
|
203
|
+
### 7.1 21 Specialist Agents
|
|
204
204
|
|
|
205
205
|
| Category | Agents |
|
|
206
206
|
| ------------------ | ------------------------------------------------------------------- |
|
|
@@ -214,7 +214,7 @@ Then try development commands:
|
|
|
214
214
|
| **Design** | designer |
|
|
215
215
|
| **Management** | project-manager |
|
|
216
216
|
|
|
217
|
-
### 7.2
|
|
217
|
+
### 7.2 50+ Command Workflows
|
|
218
218
|
|
|
219
219
|
| Category | Commands |
|
|
220
220
|
| ----------------- | ---------------------------------------------------------------------------- |
|
|
@@ -222,6 +222,7 @@ Then try development commands:
|
|
|
222
222
|
| **Quality** | `/test`, `/review`, `/debug` |
|
|
223
223
|
| **Planning** | `/plan`, `/brainstorm`, `/design` |
|
|
224
224
|
| **Documentation** | `/docs:core`, `/docs:business`, `/docs:audit` |
|
|
225
|
+
| **Report** | `/report:fast`, `/report:hard`, `/report:focus` |
|
|
225
226
|
| **Deployment** | `/deploy:check`, `/deploy:preview`, `/deploy:production`, `/deploy:rollback` |
|
|
226
227
|
| **Utility** | `/ask`, `/auto` |
|
|
227
228
|
|