@namch/agent-assistant 1.3.0 → 1.3.1
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/CHANGELOG.md +11 -1
- package/agents/backend-engineer.md +3 -3
- package/agents/brainstormer.md +3 -3
- package/agents/business-analyst.md +3 -3
- package/agents/database-architect.md +3 -3
- package/agents/debugger.md +2 -2
- package/agents/designer.md +2 -2
- package/agents/devops-engineer.md +2 -2
- package/agents/docs-manager.md +23 -15
- package/agents/frontend-engineer.md +3 -3
- package/agents/game-engineer.md +3 -3
- package/agents/mobile-engineer.md +4 -4
- package/agents/performance-engineer.md +3 -3
- package/agents/planner.md +4 -4
- package/agents/project-manager.md +3 -3
- package/agents/researcher.md +3 -3
- package/agents/reviewer.md +3 -3
- package/agents/scouter.md +3 -3
- package/agents/security-engineer.md +3 -3
- package/agents/tech-lead.md +3 -3
- package/agents/tester.md +2 -2
- package/commands/docs/audit.md +554 -78
- package/commands/docs/business.md +392 -76
- package/commands/docs/core.md +573 -74
- package/commands/docs.md +62 -61
- package/documents/business/business-features/00-index.md +101 -0
- package/documents/business/business-features/01-feature-inventory.md +341 -0
- package/documents/business/business-features/02-prioritization-moscow.md +148 -0
- package/documents/business/business-features/03-feature-specifications.md +512 -0
- package/documents/business/business-features/04-dependencies-and-release-sequencing.md +313 -0
- package/documents/business/business-features/05-success-metrics.md +290 -0
- package/documents/business/business-glossary/00-index.md +89 -0
- package/documents/business/business-glossary/01-canonical-terms.md +428 -0
- package/documents/business/business-glossary/02-synonyms-and-deprecated-terms.md +180 -0
- package/documents/business/business-glossary/03-domain-entities-and-events.md +395 -0
- package/documents/business/business-glossary/04-api-term-mapping.md +173 -0
- package/documents/business/business-prd/00-index.md +107 -0
- package/documents/business/business-prd/01-executive-summary.md +131 -0
- package/documents/business/business-prd/02-problem-goals-and-scope.md +204 -0
- package/documents/business/business-prd/03-stakeholders-and-requirements.md +210 -0
- package/documents/business/business-prd/04-acceptance-risks-assumptions.md +246 -0
- package/documents/business/business-workflows/00-index.md +107 -0
- package/documents/business/business-workflows/01-actor-map.md +303 -0
- package/documents/business/business-workflows/02-workflow-catalog.md +252 -0
- package/documents/business/business-workflows/03-detailed-workflows.md +641 -0
- package/documents/business/business-workflows/04-decision-rules-and-exceptions.md +216 -0
- package/documents/business/business-workflows/05-sla-and-handoffs.md +253 -0
- package/documents/knowledge-architecture/00-index.md +159 -0
- package/documents/knowledge-architecture/01-system-overview.md +240 -0
- package/documents/knowledge-architecture/02-components.md +419 -0
- package/documents/knowledge-architecture/03-data-flow.md +369 -0
- package/documents/knowledge-architecture/04-design-patterns.md +498 -0
- package/documents/knowledge-architecture/05-decisions.md +410 -0
- package/documents/knowledge-domain/00-index.md +251 -0
- package/documents/knowledge-domain/01-entities.md +583 -0
- package/documents/knowledge-domain/02-database-schema.md +138 -0
- package/documents/knowledge-domain/03-api-contracts.md +479 -0
- package/documents/knowledge-domain/04-business-rules.md +555 -0
- package/documents/knowledge-overview/00-index.md +107 -0
- package/documents/knowledge-overview/01-project-identity.md +162 -0
- package/documents/knowledge-overview/02-tech-stack.md +119 -0
- package/documents/knowledge-overview/03-features.md +233 -0
- package/documents/knowledge-overview/04-getting-started.md +394 -0
- package/documents/knowledge-source-base/00-index.md +107 -0
- package/documents/knowledge-source-base/01-directory-structure.md +312 -0
- package/documents/knowledge-source-base/02-entry-points.md +346 -0
- package/documents/knowledge-source-base/03-key-modules.md +582 -0
- package/documents/knowledge-source-base/04-configuration.md +467 -0
- package/documents/knowledge-standards/00-index.md +129 -0
- package/documents/knowledge-standards/01-code-style.md +161 -0
- package/documents/knowledge-standards/02-conventions.md +255 -0
- package/documents/knowledge-standards/03-git-workflow.md +228 -0
- package/documents/knowledge-standards/04-testing-standards.md +175 -0
- package/package.json +1 -1
- package/rules/REFERENCE.md +10 -6
- package/skills/docs-audit/README.md +10 -8
- package/skills/docs-audit/SKILL.md +45 -41
- package/skills/docs-audit/references/scoring-framework.md +5 -5
- package/skills/docs-core/README.md +19 -14
- package/skills/docs-core/SKILL.md +189 -117
- package/skills/planning/references/codebase-understanding.md +5 -5
- package/documents/business/business-features.md +0 -894
- package/documents/business/business-glossary.md +0 -554
- package/documents/business/business-prd.md +0 -400
- package/documents/business/business-workflows.md +0 -713
- package/documents/knowledge-architecture.md +0 -621
- package/documents/knowledge-domain.md +0 -602
- package/documents/knowledge-overview.md +0 -316
- package/documents/knowledge-source-base.md +0 -581
- package/documents/knowledge-standards.md +0 -632
package/commands/docs.md
CHANGED
|
@@ -1,13 +1,13 @@
|
|
|
1
1
|
---
|
|
2
|
-
description: 📝 Docs
|
|
3
|
-
version: "
|
|
2
|
+
description: "📝 Docs - Full Documentation Suite (executes ALL sub-commands sequentially)"
|
|
3
|
+
version: "2.0"
|
|
4
4
|
category: documentation
|
|
5
5
|
execution-mode: execute
|
|
6
6
|
---
|
|
7
7
|
|
|
8
8
|
# /docs — Full Documentation Suite
|
|
9
9
|
|
|
10
|
-
> **MISSION**: Execute ALL documentation sub-commands **SEQUENTIALLY**. Only report "Done" when ALL
|
|
10
|
+
> **MISSION**: Execute ALL documentation sub-commands **SEQUENTIALLY**. Only report "Done" when ALL deliverables are created: 5 knowledge folders (26+ files) + 4 business folders (22+ files) + 4 audit folders (20+ files).
|
|
11
11
|
|
|
12
12
|
<scope>$ARGUMENTS</scope>
|
|
13
13
|
|
|
@@ -31,9 +31,9 @@ execution-mode: execute
|
|
|
31
31
|
>
|
|
32
32
|
> 1. You MUST execute each sub-command **IN ORDER**
|
|
33
33
|
> 2. You MUST wait for each sub-command to **COMPLETE** before starting next
|
|
34
|
-
> 3. You MUST create
|
|
34
|
+
> 3. You MUST create ALL deliverables across 3 sub-commands
|
|
35
35
|
> 4. You may **NOT** skip any sub-command
|
|
36
|
-
> 5. Report "Done" **ONLY** when all
|
|
36
|
+
> 5. Report "Done" **ONLY** when all deliverables exist
|
|
37
37
|
|
|
38
38
|
---
|
|
39
39
|
|
|
@@ -42,16 +42,17 @@ execution-mode: execute
|
|
|
42
42
|
```
|
|
43
43
|
┌─────────────────────────────────────────────────────────────────┐
|
|
44
44
|
│ STEP 1: Load & Execute /docs:core │
|
|
45
|
-
│ → Wait until ALL 5
|
|
46
|
-
│ →
|
|
47
|
-
│ →
|
|
45
|
+
│ → Wait until ALL 5 knowledge folders are created │
|
|
46
|
+
│ → Each folder: 00-index.md + numbered sub-files │
|
|
47
|
+
│ → Verify: knowledge-overview/, architecture/, domain/, │
|
|
48
|
+
│ → source-base/, standards/ │
|
|
48
49
|
├─────────────────────────────────────────────────────────────────┤
|
|
49
50
|
│ STEP 2: Load & Execute /docs:business │
|
|
50
|
-
│ → Wait until ALL 4 business
|
|
51
|
-
│ → Verify: business-prd
|
|
51
|
+
│ → Wait until ALL 4 business folders are created │
|
|
52
|
+
│ → Verify: business-prd/, features/, workflows/, glossary/ │
|
|
52
53
|
├─────────────────────────────────────────────────────────────────┤
|
|
53
54
|
│ STEP 3: Load & Execute /docs:audit │
|
|
54
|
-
│ → Wait until ALL 4 audit
|
|
55
|
+
│ → Wait until ALL 4 audit folders are created │
|
|
55
56
|
│ → Verify: audit-security, compliance, dataflow, │
|
|
56
57
|
│ recommendations │
|
|
57
58
|
└─────────────────────────────────────────────────────────────────┘
|
|
@@ -66,15 +67,15 @@ execution-mode: execute
|
|
|
66
67
|
| **Sub-Command** | `~/.{TOOL}/agent-assistant/commands/docs/core.md` |
|
|
67
68
|
| **Action** | **LOAD AND FOLLOW** the entire core.md workflow |
|
|
68
69
|
|
|
69
|
-
###
|
|
70
|
+
### Folders to be Created (v3.0 — folder-based):
|
|
70
71
|
|
|
71
|
-
- [ ] `./documents/knowledge-overview.md
|
|
72
|
-
- [ ] `./documents/knowledge-architecture.md
|
|
73
|
-
- [ ] `./documents/knowledge-domain.md
|
|
74
|
-
- [ ] `./documents/knowledge-source-base.md
|
|
75
|
-
- [ ] `./documents/knowledge-standards.md
|
|
72
|
+
- [ ] `./documents/knowledge-overview/` (00-index.md + 4 sub-files)
|
|
73
|
+
- [ ] `./documents/knowledge-architecture/` (00-index.md + 5 sub-files)
|
|
74
|
+
- [ ] `./documents/knowledge-domain/` (00-index.md + 4 sub-files)
|
|
75
|
+
- [ ] `./documents/knowledge-source-base/` (00-index.md + 4 sub-files)
|
|
76
|
+
- [ ] `./documents/knowledge-standards/` (00-index.md + 4 sub-files)
|
|
76
77
|
|
|
77
|
-
**⏸️ PAUSE HERE** — Do NOT proceed to Step 2 until all 5
|
|
78
|
+
**⏸️ PAUSE HERE** — Do NOT proceed to Step 2 until all 5 knowledge folders with sub-files exist.
|
|
78
79
|
|
|
79
80
|
---
|
|
80
81
|
|
|
@@ -85,14 +86,14 @@ execution-mode: execute
|
|
|
85
86
|
| **Sub-Command** | `~/.{TOOL}/agent-assistant/commands/docs/business.md` |
|
|
86
87
|
| **Action** | **LOAD AND FOLLOW** the entire business.md workflow |
|
|
87
88
|
|
|
88
|
-
###
|
|
89
|
+
### Folders to be Created (v4.0 — folder-based):
|
|
89
90
|
|
|
90
|
-
- [ ] `./documents/business/business-prd.md
|
|
91
|
-
- [ ] `./documents/business/business-features.md
|
|
92
|
-
- [ ] `./documents/business/business-workflows.md
|
|
93
|
-
- [ ] `./documents/business/business-glossary.md
|
|
91
|
+
- [ ] `./documents/business/business-prd/` (00-index.md + 4 sub-files)
|
|
92
|
+
- [ ] `./documents/business/business-features/` (00-index.md + 5 sub-files)
|
|
93
|
+
- [ ] `./documents/business/business-workflows/` (00-index.md + 5 sub-files)
|
|
94
|
+
- [ ] `./documents/business/business-glossary/` (00-index.md + 4 sub-files)
|
|
94
95
|
|
|
95
|
-
**⏸️ PAUSE HERE** — Do NOT proceed to Step 3 until all 4 business files exist.
|
|
96
|
+
**⏸️ PAUSE HERE** — Do NOT proceed to Step 3 until all 4 business folders with sub-files exist.
|
|
96
97
|
|
|
97
98
|
---
|
|
98
99
|
|
|
@@ -103,57 +104,57 @@ execution-mode: execute
|
|
|
103
104
|
| **Sub-Command** | `~/.{TOOL}/agent-assistant/commands/docs/audit.md` |
|
|
104
105
|
| **Action** | **LOAD AND FOLLOW** the entire audit.md workflow |
|
|
105
106
|
|
|
106
|
-
###
|
|
107
|
+
### Folders to be Created (v4.0 - folder-based):
|
|
107
108
|
|
|
108
|
-
- [ ] `./documents/audit/audit-security.md
|
|
109
|
-
- [ ] `./documents/audit/audit-compliance.md
|
|
110
|
-
- [ ] `./documents/audit/audit-dataflow.md
|
|
111
|
-
- [ ] `./documents/audit/audit-recommendations.md
|
|
109
|
+
- [ ] `./documents/audit/audit-security/` (00-index.md + 4 sub-files)
|
|
110
|
+
- [ ] `./documents/audit/audit-compliance/` (00-index.md + 4 sub-files)
|
|
111
|
+
- [ ] `./documents/audit/audit-dataflow/` (00-index.md + 4 sub-files)
|
|
112
|
+
- [ ] `./documents/audit/audit-recommendations/` (00-index.md + 4 sub-files)
|
|
112
113
|
|
|
113
114
|
---
|
|
114
115
|
|
|
115
116
|
## ✅ FINAL VERIFICATION (REQUIRED)
|
|
116
117
|
|
|
117
|
-
Before reporting "Done", verify
|
|
118
|
+
Before reporting "Done", verify ALL deliverables exist:
|
|
118
119
|
|
|
119
120
|
```
|
|
120
121
|
./documents/
|
|
121
|
-
├── Core (5 files)
|
|
122
|
-
│ ├── ✅ knowledge-overview
|
|
123
|
-
│ ├── ✅ knowledge-architecture
|
|
124
|
-
│ ├── ✅ knowledge-domain
|
|
125
|
-
│ ├── ✅ knowledge-source-base
|
|
126
|
-
│ └── ✅ knowledge-standards
|
|
127
|
-
├── Business (
|
|
128
|
-
│ ├── ✅ business-prd
|
|
129
|
-
│ ├── ✅ business-features
|
|
130
|
-
│ ├── ✅ business-workflows
|
|
131
|
-
│ └── ✅ business-glossary
|
|
132
|
-
└── Audit (4 files)
|
|
133
|
-
├── ✅ audit-security
|
|
134
|
-
├── ✅ audit-compliance
|
|
135
|
-
├── ✅ audit-dataflow
|
|
136
|
-
└── ✅ audit-recommendations
|
|
122
|
+
├── Core (5 folders, 26+ files)
|
|
123
|
+
│ ├── ✅ knowledge-overview/ (00-index + 01~04)
|
|
124
|
+
│ ├── ✅ knowledge-architecture/ (00-index + 01~05)
|
|
125
|
+
│ ├── ✅ knowledge-domain/ (00-index + 01~04)
|
|
126
|
+
│ ├── ✅ knowledge-source-base/ (00-index + 01~04)
|
|
127
|
+
│ └── ✅ knowledge-standards/ (00-index + 01~04)
|
|
128
|
+
├── Business (4 folders, 22+ files)
|
|
129
|
+
│ ├── ✅ business-prd/ (00-index + 01~04)
|
|
130
|
+
│ ├── ✅ business-features/ (00-index + 01~05)
|
|
131
|
+
│ ├── ✅ business-workflows/ (00-index + 01~05)
|
|
132
|
+
│ └── ✅ business-glossary/ (00-index + 01~04)
|
|
133
|
+
└── Audit (4 folders, 20+ files)
|
|
134
|
+
├── ✅ audit-security/ (00-index + 01~04)
|
|
135
|
+
├── ✅ audit-compliance/ (00-index + 01~04)
|
|
136
|
+
├── ✅ audit-dataflow/ (00-index + 01~04)
|
|
137
|
+
└── ✅ audit-recommendations/ (00-index + 01~04)
|
|
137
138
|
```
|
|
138
139
|
|
|
139
140
|
---
|
|
140
141
|
|
|
141
142
|
## 📊 COMPLETION OUTPUT
|
|
142
143
|
|
|
143
|
-
Only output this when ALL
|
|
144
|
+
Only output this when ALL deliverables are verified:
|
|
144
145
|
|
|
145
146
|
```markdown
|
|
146
147
|
## ✅ Full Documentation Suite Complete
|
|
147
148
|
|
|
148
|
-
### 📁 All
|
|
149
|
+
### 📁 All Documents Created
|
|
149
150
|
|
|
150
|
-
| Type |
|
|
151
|
-
| -------- |
|
|
152
|
-
| Core | overview, architecture, domain, source-base, standards | ✅ 5/5 |
|
|
153
|
-
| Business | prd, features, workflows, glossary
|
|
154
|
-
| Audit | security, compliance, dataflow, recommendations
|
|
151
|
+
| Type | Deliverables | Status |
|
|
152
|
+
| -------- | ----------------------------------------------------------- | -------- |
|
|
153
|
+
| Core | 5 knowledge folders (overview, architecture, domain, source-base, standards) | ✅ 5/5 folders |
|
|
154
|
+
| Business | 4 business folders (prd, features, workflows, glossary) | ✅ 4/4 folders |
|
|
155
|
+
| Audit | 4 audit folders (security, compliance, dataflow, recommendations) | ✅ 4/4 folders |
|
|
155
156
|
|
|
156
|
-
**Total: 13
|
|
157
|
+
**Total: 13 folders (68+ files) created in `./documents/`**
|
|
157
158
|
```
|
|
158
159
|
|
|
159
160
|
---
|
|
@@ -161,9 +162,9 @@ Only output this when ALL 13 files are verified:
|
|
|
161
162
|
## 🚫 FORBIDDEN
|
|
162
163
|
|
|
163
164
|
- ❌ Skipping any sub-command
|
|
164
|
-
- ❌ Creating partial
|
|
165
|
+
- ❌ Creating partial deliverables and reporting "Done"
|
|
165
166
|
- ❌ Executing sub-commands in parallel (must be sequential)
|
|
166
|
-
- ❌ Reporting "Done" before all
|
|
167
|
+
- ❌ Reporting "Done" before all deliverables exist
|
|
167
168
|
|
|
168
169
|
---
|
|
169
170
|
|
|
@@ -171,8 +172,8 @@ Only output this when ALL 13 files are verified:
|
|
|
171
172
|
|
|
172
173
|
If you need only ONE type:
|
|
173
174
|
|
|
174
|
-
| Route |
|
|
175
|
-
| ---------------- |
|
|
176
|
-
| `/docs:core` | 5 knowledge
|
|
177
|
-
| `/docs:business` | 4 business
|
|
178
|
-
| `/docs:audit` | 4 audit
|
|
175
|
+
| Route | Deliverables Created |
|
|
176
|
+
| ---------------- | ---------------------------------------------- |
|
|
177
|
+
| `/docs:core` | 5 knowledge folders with 00-index + sub-files |
|
|
178
|
+
| `/docs:business` | 4 business folders with 00-index + sub-files |
|
|
179
|
+
| `/docs:audit` | 4 audit folders with 00-index + sub-files |
|
|
@@ -0,0 +1,101 @@
|
|
|
1
|
+
# Agent Assistant — Business Features (MoSCoW)
|
|
2
|
+
|
|
3
|
+
> **Purpose**: Features summary, table of contents, key facts, cross-references, and known gaps for @namch/agent-assistant v1.3.0
|
|
4
|
+
> **Last Updated**: 2026-03-26
|
|
5
|
+
> **Generated By**: docs-business skill
|
|
6
|
+
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
## Quick Summary
|
|
10
|
+
|
|
11
|
+
This document set catalogs the **23 business features** of @namch/agent-assistant v1.3.0, classified using the MoSCoW prioritization framework. Features span the full product surface — from one-time global installation (BF-001) through autonomous execution (BF-020) — and map directly to 10 business goals (BG-001 through BG-010).
|
|
12
|
+
|
|
13
|
+
The MoSCoW breakdown is: **10 Must Have** (core orchestration, agents, commands, skills), **8 Should Have** (teams, error healing, dynamic discovery, debate), **5 Could Have** (deployment workflows, autonomous mode, reporting, plan short-circuit, CLI list). All 10 Must Have features shipped in v1.0.0. Should Have features landed across v1.0.3–v1.2.0. Could Have features are partially delivered (BF-019 in v1.2.0, BF-020–BF-022 in v1.0.4, BF-023 pending).
|
|
14
|
+
|
|
15
|
+
---
|
|
16
|
+
|
|
17
|
+
## Sub-Files
|
|
18
|
+
|
|
19
|
+
| # | File | Description |
|
|
20
|
+
|---|------|-------------|
|
|
21
|
+
| 1 | [01-feature-inventory.md](./01-feature-inventory.md) | Complete inventory of all 23 features (BF-001–BF-023) with descriptions and business value |
|
|
22
|
+
| 2 | [02-prioritization-moscow.md](./02-prioritization-moscow.md) | MoSCoW classification with rationale and dependency analysis |
|
|
23
|
+
| 3 | [03-feature-specifications.md](./03-feature-specifications.md) | Per-feature specifications: acceptance criteria (Given/When/Then), technical surface, dependencies |
|
|
24
|
+
| 4 | [04-dependencies-and-release-sequencing.md](./04-dependencies-and-release-sequencing.md) | Dependency graph (Mermaid), release history mapping, recommended rollout order |
|
|
25
|
+
| 5 | [05-success-metrics.md](./05-success-metrics.md) | KPIs per feature, baselines, targets, measurement approach |
|
|
26
|
+
|
|
27
|
+
---
|
|
28
|
+
|
|
29
|
+
## Key Facts
|
|
30
|
+
|
|
31
|
+
| Key | Value |
|
|
32
|
+
|-----|-------|
|
|
33
|
+
| Total Features | 23 (BF-001 through BF-023) |
|
|
34
|
+
| Must Have | 10 |
|
|
35
|
+
| Should Have | 8 |
|
|
36
|
+
| Could Have | 5 |
|
|
37
|
+
| Won't Have | 0 (this release) |
|
|
38
|
+
| Features Delivered | 22 of 23 |
|
|
39
|
+
| Features Pending | 1 (BF-023: CLI List Command) |
|
|
40
|
+
| Business Goals Covered | 10 of 10 (BG-001–BG-010) |
|
|
41
|
+
| First Feature Release | v1.0.0 (2026-01-26) |
|
|
42
|
+
| Latest Feature Release | v1.3.0 (2026-03-23) |
|
|
43
|
+
| Releases with Features | 6 (v1.0.0, v1.0.3, v1.0.4, v1.1.0, v1.2.0, v1.3.0) |
|
|
44
|
+
|
|
45
|
+
---
|
|
46
|
+
|
|
47
|
+
## Cross-References
|
|
48
|
+
|
|
49
|
+
### Knowledge Folders (docs-core)
|
|
50
|
+
|
|
51
|
+
| Folder | Relationship to Features |
|
|
52
|
+
|--------|--------------------------|
|
|
53
|
+
| [../knowledge-overview/](../knowledge-overview/) | Feature descriptions, capability counts, performance metrics — factual basis for BF inventory |
|
|
54
|
+
| [../knowledge-architecture/](../knowledge-architecture/) | System components, data flow, design patterns — informs technical surface per feature |
|
|
55
|
+
| [../knowledge-domain/](../knowledge-domain/) | Entities, business rules — domain context for feature specifications |
|
|
56
|
+
| [../knowledge-source-base/](../knowledge-source-base/) | Directory structure, key modules — evidence for file mappings in specifications |
|
|
57
|
+
| [../knowledge-standards/](../knowledge-standards/) | Code style, conventions — informs quality-related features (BF-012, BF-014) |
|
|
58
|
+
|
|
59
|
+
### Business Folders (docs-business)
|
|
60
|
+
|
|
61
|
+
| Folder | Relationship to Features |
|
|
62
|
+
|--------|--------------------------|
|
|
63
|
+
| [../business-prd/](../business-prd/) | PRD goals (BG-001–BG-010) and requirements (BR-001–BR-023) that features implement |
|
|
64
|
+
| business-features/ (this folder) | MoSCoW feature classification, specifications, dependencies, metrics |
|
|
65
|
+
| business-user-stories/ | User stories derived from these features |
|
|
66
|
+
| business-use-cases/ | Use case specifications exercising these features |
|
|
67
|
+
| business-glossary/ | Canonical terminology for feature descriptions |
|
|
68
|
+
|
|
69
|
+
### Source Documents
|
|
70
|
+
|
|
71
|
+
| Document | Relationship |
|
|
72
|
+
|----------|-------------|
|
|
73
|
+
| [../../reports/business-analysis/structured-business-pack.md](../../reports/business-analysis/structured-business-pack.md) | Primary source — features section with MoSCoW table and goal mappings |
|
|
74
|
+
| [../../CHANGELOG.md](../../CHANGELOG.md) | Release history — maps features to versions |
|
|
75
|
+
| [../../README.md](../../README.md) | Public feature descriptions and metrics |
|
|
76
|
+
| [../HSOL-ASSESSMENT.md](../HSOL-ASSESSMENT.md) | HSOL readiness — informs BF-007, BF-013, BF-014 metrics |
|
|
77
|
+
|
|
78
|
+
---
|
|
79
|
+
|
|
80
|
+
## Known Gaps
|
|
81
|
+
|
|
82
|
+
| Gap ID | Description | Impact | Mitigation |
|
|
83
|
+
|--------|-------------|--------|------------|
|
|
84
|
+
| GAP-F01 | Performance metrics (70% faster, 70% bug reduction, 85% token savings) are self-reported and unvalidated by independent testing | Success metrics for BF-003, BF-007, BF-008 rely on unverified baselines | Flag as "UNVALIDATED" in metrics; plan benchmark suite |
|
|
85
|
+
| GAP-F02 | BF-023 (CLI List Command) not yet implemented | Feature inventory shows 22/23 delivered | Low priority — Could Have classification; no business goal blocked |
|
|
86
|
+
| GAP-F03 | Dynamic skill discovery (BF-013) depends on external network and community skill registry that does not yet have a published API | BF-014 (Trust Progression) also blocked without functional discovery | Design offline fallback; define registry API contract |
|
|
87
|
+
| GAP-F04 | No formal A/B testing or telemetry to measure feature adoption rates | Cannot validate success metrics for adoption-related KPIs | Define measurement plan before v2.0 |
|
|
88
|
+
| GAP-F05 | Debate mechanism (BF-016) max rounds and convergence rates not benchmarked | Cannot confirm 3-round max is sufficient for all domains | Collect empirical data from `:team` variant usage |
|
|
89
|
+
|
|
90
|
+
---
|
|
91
|
+
|
|
92
|
+
## Evidence Sources
|
|
93
|
+
|
|
94
|
+
| Source | Path |
|
|
95
|
+
|--------|------|
|
|
96
|
+
| Structured Business Pack (features, goals, MoSCoW) | [../../reports/business-analysis/structured-business-pack.md](../../reports/business-analysis/structured-business-pack.md) |
|
|
97
|
+
| CHANGELOG (release history) | [../../CHANGELOG.md](../../CHANGELOG.md) |
|
|
98
|
+
| README (feature descriptions) | [../../README.md](../../README.md) |
|
|
99
|
+
| Knowledge overview — features | [../knowledge-overview/03-features.md](../knowledge-overview/03-features.md) |
|
|
100
|
+
| PRD — goals and scope | [../business-prd/02-problem-goals-and-scope.md](../business-prd/02-problem-goals-and-scope.md) |
|
|
101
|
+
| PRD — requirements | [../business-prd/03-stakeholders-and-requirements.md](../business-prd/03-stakeholders-and-requirements.md) |
|
|
@@ -0,0 +1,341 @@
|
|
|
1
|
+
# Agent Assistant — Feature Inventory
|
|
2
|
+
|
|
3
|
+
> **Purpose**: Complete inventory of all 23 business features (BF-001–BF-023) with descriptions, business value, and goal traceability
|
|
4
|
+
> **Parent**: [00-index.md](./00-index.md)
|
|
5
|
+
> **Last Updated**: 2026-03-26
|
|
6
|
+
> **Generated By**: docs-business skill
|
|
7
|
+
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
## Inventory Overview
|
|
11
|
+
|
|
12
|
+
| Metric | Count |
|
|
13
|
+
|--------|-------|
|
|
14
|
+
| Total Features | 23 |
|
|
15
|
+
| Must Have | 10 (BF-001–BF-010) |
|
|
16
|
+
| Should Have | 8 (BF-011–BF-018) |
|
|
17
|
+
| Could Have | 5 (BF-019–BF-023) |
|
|
18
|
+
| Delivered | 22 |
|
|
19
|
+
| Pending | 1 (BF-023) |
|
|
20
|
+
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
## Must Have Features (10)
|
|
24
|
+
|
|
25
|
+
### BF-001 — One-Time Global Installation
|
|
26
|
+
|
|
27
|
+
**Description**: The CLI installer copies all framework files (agents, commands, rules, skills, matrix-skills) into the AI tool's global configuration directory. Install once per platform — zero per-project configuration. Supports `install --all` for batch installation across all 5 platforms.
|
|
28
|
+
|
|
29
|
+
**Business Value**: Eliminates setup friction. Developers start using 21 agents and 1,430+ skills immediately on every project without any per-repository configuration. Reduces onboarding time to under 60 seconds.
|
|
30
|
+
|
|
31
|
+
**Goal Mapping**: BG-001 (Global setup)
|
|
32
|
+
|
|
33
|
+
**Key Files**: `cli/install.js`, `package.json` (npm scripts)
|
|
34
|
+
|
|
35
|
+
---
|
|
36
|
+
|
|
37
|
+
### BF-002 — Multi-Platform Support (5 Platforms)
|
|
38
|
+
|
|
39
|
+
**Description**: Identical agent definitions, commands, workflows, and skills work across Cursor, GitHub Copilot, Claude Code, Codex, and Antigravity/Gemini. Platform-specific path resolution and template variable replacement (`{TOOL}`, `{HOME}`) adapt the same source files for each platform's directory structure.
|
|
40
|
+
|
|
41
|
+
**Business Value**: Write once, orchestrate everywhere. Teams using different AI tools share the same agent intelligence and workflow quality. No vendor lock-in.
|
|
42
|
+
|
|
43
|
+
**Goal Mapping**: BG-002 (Multi-platform)
|
|
44
|
+
|
|
45
|
+
**Key Files**: `cli/install.js` (TOOLS config), `code-assistants/*/`, platform entry files (CURSOR.md, COPILOT.md, CLAUDE.md, CODEX.md, GEMINI.md)
|
|
46
|
+
|
|
47
|
+
---
|
|
48
|
+
|
|
49
|
+
### BF-003 — Orchestrator Pattern
|
|
50
|
+
|
|
51
|
+
**Description**: The AI assistant assumes the role of Orchestrator — it coordinates, delegates, and verifies but never implements directly. This is enforced by CORE.md loaded at session boot with mandatory prohibition statements and self-check protocol.
|
|
52
|
+
|
|
53
|
+
**Business Value**: Prevents the AI from producing unreviewed, unstructured code. Forces specialization, traceability, and quality gates on every task. Directly drives the 70% time-to-production improvement and 70% bug reduction.
|
|
54
|
+
|
|
55
|
+
**Goal Mapping**: BG-003 (Speed), BG-004 (Quality)
|
|
56
|
+
|
|
57
|
+
**Key Files**: `rules/CORE.md`, platform entry files
|
|
58
|
+
|
|
59
|
+
---
|
|
60
|
+
|
|
61
|
+
### BF-004 — 21 Specialist Agents
|
|
62
|
+
|
|
63
|
+
**Description**: Each agent is a Markdown file with a defined profile (role, expertise, cognitive anchor), directive (primary mission), protocol (how it executes), and constraints (what it must not do). Agents span implementation (4), architecture (2), quality (4), planning (3), and support (8) domains.
|
|
64
|
+
|
|
65
|
+
**Business Value**: Specialization produces higher-quality output than generic AI responses. Each agent's profile triggers HSOL skill injection, ensuring domain-relevant knowledge is loaded. Agent constraints prevent scope creep.
|
|
66
|
+
|
|
67
|
+
**Goal Mapping**: BG-004 (Quality)
|
|
68
|
+
|
|
69
|
+
**Key Files**: `agents/*.md` (21 files), `agents/teams/` (17 teams × 3 roles = 51 team agent files)
|
|
70
|
+
|
|
71
|
+
---
|
|
72
|
+
|
|
73
|
+
### BF-005 — 14 Structured Commands
|
|
74
|
+
|
|
75
|
+
**Description**: Commands are workflow definitions that orchestrate agent collaboration across phases. Each command file specifies the routing logic, phase sequence, agent assignments, and exit criteria. Categories: Build (`/cook`, `/code`, `/fix`), Quality (`/test`, `/review`, `/debug`), Plan (`/plan`, `/brainstorm`, `/design`), Docs (`/docs`), Report (`/report`), Deploy (`/deploy`), Inquiry (`/ask`), Auto (`/auto`).
|
|
76
|
+
|
|
77
|
+
**Business Value**: Standardized workflows eliminate ad-hoc prompting. Every task follows a proven sequence of specialist agents, ensuring consistent quality regardless of the user's prompt engineering skill.
|
|
78
|
+
|
|
79
|
+
**Goal Mapping**: BG-003 (Speed), BG-006 (Structured workflows)
|
|
80
|
+
|
|
81
|
+
**Key Files**: `commands/*.md` (14 files), `commands/*/` (variant subdirectories)
|
|
82
|
+
|
|
83
|
+
---
|
|
84
|
+
|
|
85
|
+
### BF-006 — 4 Variant Strategies
|
|
86
|
+
|
|
87
|
+
**Description**: Each command supports up to 4 variants controlling scope and rigor: `:fast` (2–3 agents, basic gates), `:hard` (5–8 agents, comprehensive gates including test/review/security), `:focus` (clean execution with context optimization), `:team` (adversarial Golden Triangle with debate mechanism).
|
|
88
|
+
|
|
89
|
+
**Business Value**: Right-sized workflows for every task. Simple fixes use `:fast` (seconds), production features use `:hard` (thorough), critical systems use `:team` (adversarial review). Token cost scales with complexity.
|
|
90
|
+
|
|
91
|
+
**Goal Mapping**: BG-003 (Speed), BG-006 (Structured workflows)
|
|
92
|
+
|
|
93
|
+
**Key Files**: `commands/cook/fast.md`, `commands/cook/hard.md`, `commands/cook/focus.md`, `commands/cook/team.md` (pattern repeated per command)
|
|
94
|
+
|
|
95
|
+
---
|
|
96
|
+
|
|
97
|
+
### BF-007 — Matrix Skill Discovery (HSOL)
|
|
98
|
+
|
|
99
|
+
**Description**: The Hybrid Skill Orchestration Layer automatically resolves and injects relevant skills based on the agent's profile and task context. Resolution algorithm: parse agent profile → load inherited domains from `matrix-skills/_index.yaml` → filter by relevance → apply priority thresholds → calculate fitness scores (semantic 35%, specificity 25%, trust 20%, freshness 10%, success 10%) → return sorted skill set. 1,430+ skills across 19 domains.
|
|
100
|
+
|
|
101
|
+
**Business Value**: Eliminates manual skill selection. Agents receive precisely the knowledge they need, reducing token waste (85% savings) and improving output relevance. Skills scale independently of agent count.
|
|
102
|
+
|
|
103
|
+
**Goal Mapping**: BG-005 (Token cost), BG-007 (Skill injection)
|
|
104
|
+
|
|
105
|
+
**Key Files**: `rules/SKILLS.md`, `matrix-skills/_index.yaml`, `matrix-skills/*.yaml` (19 domain files), `skills/` (1,430+ modules)
|
|
106
|
+
|
|
107
|
+
---
|
|
108
|
+
|
|
109
|
+
### BF-008 — Tiered Execution
|
|
110
|
+
|
|
111
|
+
**Description**: Two-tier execution model — TIER 1 uses `runSubagent` for isolated parallel execution when the platform supports it (Claude Code, Cursor Max mode). TIER 2 falls back to in-context agent embodiment when sub-agents are unavailable. TIER 1 is mandatory when available.
|
|
112
|
+
|
|
113
|
+
**Business Value**: Maximizes parallelism where supported (multiple agents working simultaneously), while ensuring universal compatibility. Reduces total execution time on capable platforms.
|
|
114
|
+
|
|
115
|
+
**Goal Mapping**: BG-003 (Speed), BG-005 (Token cost)
|
|
116
|
+
|
|
117
|
+
**Key Files**: `rules/CORE.md` (Tiered Execution section), `rules/AGENTS.md`
|
|
118
|
+
|
|
119
|
+
---
|
|
120
|
+
|
|
121
|
+
### BF-009 — 10 Orchestration Laws
|
|
122
|
+
|
|
123
|
+
**Description**: Formal governance rules constraining Orchestrator behavior: (L1) Single Point of Truth, (L2) Requirement Integrity, (L3) Phase Completion, (L4) Agent Specialization, (L5) Transparent Delegation, (L6) No Silent Failures, (L7) Skill Authority, (L8) Output Verification, (L9) Context Preservation, (L10) Minimal Intervention.
|
|
124
|
+
|
|
125
|
+
**Business Value**: Predictable, auditable behavior. Laws prevent common AI failures — scope drift, silent errors, context loss, unauthorized implementation. Every session is governed by the same rules.
|
|
126
|
+
|
|
127
|
+
**Goal Mapping**: BG-004 (Quality)
|
|
128
|
+
|
|
129
|
+
**Key Files**: `rules/CORE.md` (Laws section)
|
|
130
|
+
|
|
131
|
+
---
|
|
132
|
+
|
|
133
|
+
### BF-010 — Cognitive Anchoring
|
|
134
|
+
|
|
135
|
+
**Description**: Every agent file contains a cognitive anchor block — a structured identity section that reinforces the agent's role, expertise, and boundaries at the start of execution. This prevents role drift during long sessions.
|
|
136
|
+
|
|
137
|
+
**Business Value**: Agents maintain consistent behavior across extended conversations. Role-specific expertise is preserved even when context windows approach limits.
|
|
138
|
+
|
|
139
|
+
**Goal Mapping**: BG-004 (Quality)
|
|
140
|
+
|
|
141
|
+
**Key Files**: `agents/*.md` (cognitive anchor block in each), `AGENT-TEMPLATE.md`
|
|
142
|
+
|
|
143
|
+
---
|
|
144
|
+
|
|
145
|
+
## Should Have Features (8)
|
|
146
|
+
|
|
147
|
+
### BF-011 — 17 Domain Teams (Golden Triangle)
|
|
148
|
+
|
|
149
|
+
**Description**: Adversarial collaboration system with 17 specialized domain teams, each composed of 3 roles: Tech Lead (designs approach), Executor (implements), Reviewer (challenges). Teams span backend, frontend, fullstack, database, research, planning, QA, design, debug, devops, security, game, mobile, performance, docs, project, and report domains.
|
|
150
|
+
|
|
151
|
+
**Business Value**: Multiple expert perspectives on critical features. The adversarial model catches design flaws, implementation bugs, and edge cases that a single agent would miss. 51 team agents total.
|
|
152
|
+
|
|
153
|
+
**Goal Mapping**: BG-004 (Quality), BG-008 (Adversarial quality)
|
|
154
|
+
|
|
155
|
+
**Key Files**: `rules/TEAMS.md`, `agents/teams/*/` (17 directories × 3 files each)
|
|
156
|
+
|
|
157
|
+
---
|
|
158
|
+
|
|
159
|
+
### BF-012 — Error Self-Healing (E1–E4)
|
|
160
|
+
|
|
161
|
+
**Description**: Classified error recovery system — E1 (Warning: auto-retry), E2 (Recoverable: fallback strategy), E3 (Blocking: pause for user input), E4 (Critical: halt with diagnostics). No silent failures — every error is surfaced, classified, and handled according to its severity.
|
|
162
|
+
|
|
163
|
+
**Business Value**: Prevents cascading failures and invisible quality degradation. Users always know the state of execution. Recovery is automatic where safe, manual where necessary.
|
|
164
|
+
|
|
165
|
+
**Goal Mapping**: BG-004 (Quality)
|
|
166
|
+
|
|
167
|
+
**Key Files**: `rules/ERRORS.md`
|
|
168
|
+
|
|
169
|
+
---
|
|
170
|
+
|
|
171
|
+
### BF-013 — Dynamic Skill Discovery
|
|
172
|
+
|
|
173
|
+
**Description**: When the matrix fitness score falls below 0.8 for `:hard` or `:focus` variants, the `find-skills` mechanism can discover additional community skills at runtime. Discovered skills are registered in `matrix-skills/_dynamic.yaml`.
|
|
174
|
+
|
|
175
|
+
**Business Value**: Extends the framework's knowledge beyond the bundled 1,430 skills. Community contributions supplement gaps in niche or emerging domains without requiring a framework release.
|
|
176
|
+
|
|
177
|
+
**Goal Mapping**: BG-007 (Skill injection), BG-009 (Community ecosystem)
|
|
178
|
+
|
|
179
|
+
**Key Files**: `rules/SKILLS.md` (dynamic section), `matrix-skills/_dynamic.yaml`
|
|
180
|
+
|
|
181
|
+
---
|
|
182
|
+
|
|
183
|
+
### BF-014 — Trust Progression Lifecycle
|
|
184
|
+
|
|
185
|
+
**Description**: Dynamically discovered skills follow a trust lifecycle: NEW → EVALUATING → VALIDATED → PROMOTED. Skills are gated at each stage based on usage outcomes, preventing untested community skills from ranking alongside verified core skills.
|
|
186
|
+
|
|
187
|
+
**Business Value**: Balances openness (community skills welcome) with quality (untested skills don't override proven ones). Trust builds through demonstrated success, not popularity.
|
|
188
|
+
|
|
189
|
+
**Goal Mapping**: BG-007 (Skill injection), BG-009 (Community ecosystem)
|
|
190
|
+
|
|
191
|
+
**Key Files**: `rules/SKILLS.md` (trust section), `matrix-skills/_dynamic.yaml`
|
|
192
|
+
|
|
193
|
+
---
|
|
194
|
+
|
|
195
|
+
### BF-015 — Documentation Generation (/docs)
|
|
196
|
+
|
|
197
|
+
**Description**: The `/docs` command generates structured documentation across three categories: Core (5 folders: overview, architecture, domain, source-base, standards), Business (4 folders: PRD, user stories, use cases, glossary + features), and Audit (4 folders). Uses scouter for discovery, business-analyst for analysis, and docs-manager for authoring.
|
|
198
|
+
|
|
199
|
+
**Business Value**: Auto-generates comprehensive project documentation from source code and framework artifacts. Reduces documentation debt and ensures consistency across docs types.
|
|
200
|
+
|
|
201
|
+
**Goal Mapping**: BG-006 (Structured workflows), BG-010 (Auto-docs)
|
|
202
|
+
|
|
203
|
+
**Key Files**: `commands/docs.md`, `commands/docs/*.md`, `agents/docs-manager.md`, `agents/scouter.md`, `agents/business-analyst.md`
|
|
204
|
+
|
|
205
|
+
---
|
|
206
|
+
|
|
207
|
+
### BF-016 — Debate Mechanism (Mailbox)
|
|
208
|
+
|
|
209
|
+
**Description**: The `:team` variant uses an append-only mailbox (`./reports/{topic}/MAILBOX-{date}.md`) for inter-agent communication. Message types: TASK_ASSIGNMENT, SUBMISSION, REVIEW, DEFENSE, ARBITRATION, DECISION. Maximum 3 debate rounds before Tech Lead makes a binding arbitration decision.
|
|
210
|
+
|
|
211
|
+
**Business Value**: Traceable quality improvement. Every challenge, defense, and resolution is recorded. The 3-round limit prevents infinite loops while ensuring substantive review.
|
|
212
|
+
|
|
213
|
+
**Goal Mapping**: BG-008 (Adversarial quality)
|
|
214
|
+
|
|
215
|
+
**Key Files**: `rules/TEAMS.md` (mailbox section)
|
|
216
|
+
|
|
217
|
+
---
|
|
218
|
+
|
|
219
|
+
### BF-017 — Natural Language Command Detection
|
|
220
|
+
|
|
221
|
+
**Description**: The Orchestrator detects user intent from natural language and maps it to the correct command. Examples: "implement/build/create" → `/cook` or `/code`, "fix/bug" → `/fix`, "plan" → `/plan`. Routing logic is defined in CORE.md.
|
|
222
|
+
|
|
223
|
+
**Business Value**: Users do not need to memorize 14 commands and 54 variants. Natural language input is automatically routed to the correct workflow, lowering the learning curve.
|
|
224
|
+
|
|
225
|
+
**Goal Mapping**: BG-005 (Token cost)
|
|
226
|
+
|
|
227
|
+
**Key Files**: `rules/CORE.md` (command routing section)
|
|
228
|
+
|
|
229
|
+
---
|
|
230
|
+
|
|
231
|
+
### BF-018 — Language Compliance (L6)
|
|
232
|
+
|
|
233
|
+
**Description**: Responses are always in the user's language. Code, comments, and generated files are always in English. This is enforced as Law L6 in CORE.md and referenced in every platform entry file.
|
|
234
|
+
|
|
235
|
+
**Business Value**: International accessibility without sacrificing code consistency. Non-English speakers receive guidance in their language while all artifacts remain in English for team collaboration.
|
|
236
|
+
|
|
237
|
+
**Goal Mapping**: BG-004 (Quality)
|
|
238
|
+
|
|
239
|
+
**Key Files**: `rules/CORE.md` (Law L6)
|
|
240
|
+
|
|
241
|
+
---
|
|
242
|
+
|
|
243
|
+
## Could Have Features (5)
|
|
244
|
+
|
|
245
|
+
### BF-019 — Deployment Workflows (/deploy)
|
|
246
|
+
|
|
247
|
+
**Description**: The `/deploy` command provides 4 variants: `check` (pre-deployment validation), `preview` (staging deployment), `production` (production release), `rollback` (revert). Orchestrated by devops-engineer agent.
|
|
248
|
+
|
|
249
|
+
**Business Value**: Structured deployment reduces release risk. Validation steps catch issues before they reach production. Rollback provides a safety net.
|
|
250
|
+
|
|
251
|
+
**Goal Mapping**: BG-006 (Structured workflows)
|
|
252
|
+
|
|
253
|
+
**Key Files**: `commands/deploy.md`, `commands/deploy/*.md`, `agents/devops-engineer.md`
|
|
254
|
+
|
|
255
|
+
---
|
|
256
|
+
|
|
257
|
+
### BF-020 — Autonomous Execution (/auto)
|
|
258
|
+
|
|
259
|
+
**Description**: The `/auto` command enables self-routing execution without user pauses at phase boundaries. The tech-lead agent classifies the task and selects the appropriate command and variant automatically.
|
|
260
|
+
|
|
261
|
+
**Business Value**: Hands-off execution for confident users. The AI handles the full workflow from classification to delivery without interruption.
|
|
262
|
+
|
|
263
|
+
**Goal Mapping**: BG-006 (Structured workflows)
|
|
264
|
+
|
|
265
|
+
**Key Files**: `commands/auto.md`, `agents/tech-lead.md`
|
|
266
|
+
|
|
267
|
+
---
|
|
268
|
+
|
|
269
|
+
### BF-021 — Reporting System (/report)
|
|
270
|
+
|
|
271
|
+
**Description**: The `/report` command generates status reports, sprint summaries, and analysis documents. Uses the reporter agent for authoring and scouter for data gathering. Supports create, update, and template-based output modes.
|
|
272
|
+
|
|
273
|
+
**Business Value**: Automated project reporting reduces manual effort and ensures reports are grounded in actual project state rather than memory.
|
|
274
|
+
|
|
275
|
+
**Goal Mapping**: BG-006 (Structured workflows)
|
|
276
|
+
|
|
277
|
+
**Key Files**: `commands/report.md`, `commands/report/*.md`, `agents/reporter.md`, `agents/scouter.md`
|
|
278
|
+
|
|
279
|
+
---
|
|
280
|
+
|
|
281
|
+
### BF-022 — Plan Short-Circuit
|
|
282
|
+
|
|
283
|
+
**Description**: When the user references an existing plan (`@plan`, `@PLAN-...`, path to `PLAN-*.md`, or phrases like "follow the plan"), research/scout/brainstorm phases are skipped. Execution jumps directly to context optimization → implementation → test → review.
|
|
284
|
+
|
|
285
|
+
**Business Value**: Eliminates redundant research when planning is already complete. Reduces token cost and execution time for plan-driven development.
|
|
286
|
+
|
|
287
|
+
**Goal Mapping**: BG-003 (Speed)
|
|
288
|
+
|
|
289
|
+
**Key Files**: `commands/code.md` (routing), `commands/code/hard.md`, `commands/code/focus.md` (skip logic)
|
|
290
|
+
|
|
291
|
+
---
|
|
292
|
+
|
|
293
|
+
### BF-023 — CLI List Command
|
|
294
|
+
|
|
295
|
+
**Description**: A CLI command to show which platforms have agent-assistant installed, their versions, and installation status.
|
|
296
|
+
|
|
297
|
+
**Business Value**: Visibility into installation state across platforms. Useful for troubleshooting and verifying multi-platform setup.
|
|
298
|
+
|
|
299
|
+
**Goal Mapping**: BG-001 (Global setup)
|
|
300
|
+
|
|
301
|
+
**Key Files**: `cli/install.js` (planned addition)
|
|
302
|
+
|
|
303
|
+
**Status**: NOT YET IMPLEMENTED
|
|
304
|
+
|
|
305
|
+
---
|
|
306
|
+
|
|
307
|
+
## Business Goals → Features Traceability
|
|
308
|
+
|
|
309
|
+
| Goal | ID | Features |
|
|
310
|
+
|------|----|----------|
|
|
311
|
+
| Global setup | BG-001 | BF-001, BF-023 |
|
|
312
|
+
| Multi-platform | BG-002 | BF-002 |
|
|
313
|
+
| Speed | BG-003 | BF-003, BF-005, BF-006, BF-008, BF-022 |
|
|
314
|
+
| Quality | BG-004 | BF-003, BF-004, BF-009, BF-010, BF-011, BF-012, BF-018 |
|
|
315
|
+
| Token cost | BG-005 | BF-007, BF-008, BF-017 |
|
|
316
|
+
| Structured workflows | BG-006 | BF-005, BF-006, BF-015, BF-019, BF-020, BF-021 |
|
|
317
|
+
| Skill injection | BG-007 | BF-007, BF-013, BF-014 |
|
|
318
|
+
| Adversarial quality | BG-008 | BF-011, BF-016 |
|
|
319
|
+
| Community ecosystem | BG-009 | BF-013, BF-014 |
|
|
320
|
+
| Auto-docs | BG-010 | BF-015 |
|
|
321
|
+
|
|
322
|
+
---
|
|
323
|
+
|
|
324
|
+
## Evidence Sources
|
|
325
|
+
|
|
326
|
+
| Source | Path |
|
|
327
|
+
|--------|------|
|
|
328
|
+
| Structured Business Pack | [../../reports/business-analysis/structured-business-pack.md](../../reports/business-analysis/structured-business-pack.md) |
|
|
329
|
+
| Knowledge overview — features | [../knowledge-overview/03-features.md](../knowledge-overview/03-features.md) |
|
|
330
|
+
| CHANGELOG | [../../CHANGELOG.md](../../CHANGELOG.md) |
|
|
331
|
+
| README | [../../README.md](../../README.md) |
|
|
332
|
+
| CORE rules | [../../rules/CORE.md](../../rules/CORE.md) |
|
|
333
|
+
| SKILLS rules | [../../rules/SKILLS.md](../../rules/SKILLS.md) |
|
|
334
|
+
| TEAMS rules | [../../rules/TEAMS.md](../../rules/TEAMS.md) |
|
|
335
|
+
| ERRORS rules | [../../rules/ERRORS.md](../../rules/ERRORS.md) |
|
|
336
|
+
| AGENTS rules | [../../rules/AGENTS.md](../../rules/AGENTS.md) |
|
|
337
|
+
| CLI installer | [../../cli/install.js](../../cli/install.js) |
|
|
338
|
+
| Agent definitions | [../../agents/](../../agents/) |
|
|
339
|
+
| Commands | [../../commands/](../../commands/) |
|
|
340
|
+
| Matrix skills | [../../matrix-skills/](../../matrix-skills/) |
|
|
341
|
+
| HSOL Assessment | [../HSOL-ASSESSMENT.md](../HSOL-ASSESSMENT.md) |
|