@alxyrgin/agent-forge 3.0.0 → 3.2.0
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 +353 -118
- package/dist/index.js +262 -19
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
- package/templates/config/linear-mapping.json.ejs +27 -0
- package/templates/root/CLAUDE.md.ejs +2 -0
- package/templates/rules/linear-sync.md.ejs +65 -0
- package/templates/skills/core/complete-task/SKILL.md.ejs +17 -0
- package/templates/skills/core/done/SKILL.md.ejs +18 -0
- package/templates/skills/core/end-session/SKILL.md.ejs +18 -0
- package/templates/skills/core/plan/SKILL.md.ejs +9 -0
- package/templates/skills/core/take-task/SKILL.md.ejs +9 -0
- package/templates/skills/extra/decompose/SKILL.md.ejs +9 -0
- package/templates/skills/extra/sync-linear/SKILL.md.ejs +87 -0
package/README.md
CHANGED
|
@@ -1,8 +1,10 @@
|
|
|
1
1
|
# agent-forge
|
|
2
2
|
|
|
3
|
-
AI-driven Development Framework for Claude Code.
|
|
3
|
+
AI-driven Development Framework for Claude Code. Generates a complete development infrastructure with 20 specialized agents, quality gates, and TDD pipelines.
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
[](https://www.npmjs.com/package/@alxyrgin/agent-forge)
|
|
6
|
+
[](https://github.com/alxyrgin/agent-forge/blob/main/LICENSE)
|
|
7
|
+
[](https://nodejs.org)
|
|
6
8
|
|
|
7
9
|
## Quick Start
|
|
8
10
|
|
|
@@ -10,186 +12,419 @@ Scaffold a complete development infrastructure with Memory Bank, specialized age
|
|
|
10
12
|
npx @alxyrgin/agent-forge init
|
|
11
13
|
```
|
|
12
14
|
|
|
13
|
-
|
|
15
|
+
The interactive wizard asks for your project name, tech stack, team, and agent preset — then scaffolds the entire AI infrastructure in seconds. Start working immediately with `/start-session`.
|
|
14
16
|
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
- **`dev-infra/sessions/`** — Session logs
|
|
19
|
-
- **`dev-infra/tests/`** — Test structure (acceptance, PMI, results)
|
|
17
|
+
```bash
|
|
18
|
+
npx @alxyrgin/agent-forge init --yes # non-interactive, use defaults
|
|
19
|
+
```
|
|
20
20
|
|
|
21
|
-
##
|
|
21
|
+
## What Gets Generated
|
|
22
|
+
|
|
23
|
+
| Directory | Contents |
|
|
24
|
+
|-----------|----------|
|
|
25
|
+
| `.claude/CLAUDE.md` | Team Lead instructions — the orchestrator prompt |
|
|
26
|
+
| `.claude/agents/` | 5–20 specialized agents across 4 categories |
|
|
27
|
+
| `.claude/skills/` | 10–21 slash commands for development workflows |
|
|
28
|
+
| `.claude/rules/` | 8 development standards enforced automatically |
|
|
29
|
+
| `.claude/hooks/` | Git/tool hooks (protect-docs, stop hook) |
|
|
30
|
+
| `dev-infra/memory/` | 9 Memory Bank files for persistent context |
|
|
31
|
+
| `dev-infra/tasks/` | Task tracking system (`tasks.json`) |
|
|
32
|
+
| `dev-infra/sessions/` | Session logs |
|
|
33
|
+
| `dev-infra/tests/` | Test structure (acceptance criteria, PMI scenarios, results) |
|
|
34
|
+
|
|
35
|
+
## Architecture
|
|
36
|
+
|
|
37
|
+
The Team Lead (defined in `CLAUDE.md`) orchestrates four categories of specialized agents:
|
|
38
|
+
|
|
39
|
+
```mermaid
|
|
40
|
+
graph TD
|
|
41
|
+
subgraph "Orchestrator"
|
|
42
|
+
TL["Team Lead<br/>(CLAUDE.md)"]
|
|
43
|
+
end
|
|
44
|
+
|
|
45
|
+
subgraph "Pipeline — 8 agents"
|
|
46
|
+
analyst["analyst"]
|
|
47
|
+
architect["architect"]
|
|
48
|
+
skeptic["skeptic"]
|
|
49
|
+
developer["developer"]
|
|
50
|
+
tester["tester"]
|
|
51
|
+
inspector["inspector"]
|
|
52
|
+
reviewer["reviewer"]
|
|
53
|
+
planner["planner"]
|
|
54
|
+
end
|
|
55
|
+
|
|
56
|
+
subgraph "Planning — 4 agents"
|
|
57
|
+
researcher["researcher"]
|
|
58
|
+
interviewer["interviewer"]
|
|
59
|
+
validator["validator"]
|
|
60
|
+
decomposer["decomposer"]
|
|
61
|
+
end
|
|
62
|
+
|
|
63
|
+
subgraph "Security — 4 agents"
|
|
64
|
+
auditor["auditor"]
|
|
65
|
+
prompter["prompter"]
|
|
66
|
+
deployer["deployer"]
|
|
67
|
+
scaffolder["scaffolder"]
|
|
68
|
+
end
|
|
69
|
+
|
|
70
|
+
subgraph "Documentation — 4 agents"
|
|
71
|
+
librarian["librarian"]
|
|
72
|
+
writer["writer"]
|
|
73
|
+
gatekeeper["gatekeeper"]
|
|
74
|
+
verifier["verifier"]
|
|
75
|
+
end
|
|
76
|
+
|
|
77
|
+
TL --> analyst
|
|
78
|
+
TL --> researcher
|
|
79
|
+
TL --> auditor
|
|
80
|
+
TL --> librarian
|
|
81
|
+
|
|
82
|
+
analyst --> architect --> skeptic
|
|
83
|
+
developer <--> tester
|
|
84
|
+
tester --> inspector --> reviewer
|
|
85
|
+
```
|
|
22
86
|
|
|
23
|
-
|
|
87
|
+
Each agent has a defined role, a set of allowed tools, a model assignment, and structured JSON output with verdicts. The Team Lead reads each verdict and routes the pipeline accordingly.
|
|
24
88
|
|
|
25
|
-
|
|
89
|
+
## Pipelines
|
|
26
90
|
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
91
|
+
Every task is classified by size — **S**, **M**, or **L** — and routed through the appropriate pipeline. Larger tasks get more validation steps.
|
|
92
|
+
|
|
93
|
+
### S-Pipeline. Small tasks (1 file, < 50 lines)
|
|
94
|
+
|
|
95
|
+
```mermaid
|
|
96
|
+
graph LR
|
|
97
|
+
S1["checkpoint"] --> S2["developer"] --> S3["tester +<br/>inspector"] --> S4["quick-review"] --> S5["tech-debt"] --> S6["fixation"]
|
|
98
|
+
|
|
99
|
+
style S1 fill:#f0f0f0,stroke:#999
|
|
100
|
+
style S6 fill:#f0f0f0,stroke:#999
|
|
101
|
+
```
|
|
102
|
+
|
|
103
|
+
### M-Pipeline. Medium tasks (2–5 files, new module)
|
|
38
104
|
|
|
39
|
-
|
|
105
|
+
```mermaid
|
|
106
|
+
graph LR
|
|
107
|
+
M1["checkpoint"] --> M2["analyst"] --> M3["TDD RED"] --> M4["developer ↔<br/>tester +<br/>inspector"] --> M5["quality<br/>gates"] --> M6["reviewer"] --> M7["tech-debt"] --> M8["fixation"]
|
|
40
108
|
|
|
41
|
-
|
|
109
|
+
style M1 fill:#f0f0f0,stroke:#999
|
|
110
|
+
style M8 fill:#f0f0f0,stroke:#999
|
|
111
|
+
```
|
|
42
112
|
|
|
43
|
-
|
|
44
|
-
|----------|--------|-------|
|
|
45
|
-
| Pipeline | analyst, architect, skeptic, developer, tester, inspector, reviewer, planner | 8 |
|
|
46
|
-
| Planning | researcher, validator, interviewer, decomposer | 4 |
|
|
47
|
-
| Security | auditor, prompter, deployer, scaffolder | 4 |
|
|
48
|
-
| Documentation | librarian, writer, gatekeeper, verifier | 4 |
|
|
113
|
+
### L-Pipeline. Large tasks (6+ files, architecture changes)
|
|
49
114
|
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
- **full** (20 agents) — all categories
|
|
115
|
+
```mermaid
|
|
116
|
+
graph LR
|
|
117
|
+
L1["checkpoint"] --> L2["analyst"] --> L3["architect +<br/>reviewer<br/>(plan)"] --> L4["skeptic"] --> L5["TDD RED"] --> L6["developer ↔<br/>tester +<br/>inspector"] --> L7["quality<br/>gates"] --> L8["reviewer"] --> L9["tech-debt"] --> L10["fixation"]
|
|
54
118
|
|
|
55
|
-
|
|
119
|
+
style L1 fill:#f0f0f0,stroke:#999
|
|
120
|
+
style L10 fill:#f0f0f0,stroke:#999
|
|
121
|
+
```
|
|
56
122
|
|
|
57
|
-
|
|
123
|
+
Key pipeline features:
|
|
124
|
+
- **TDD RED phase** (M/L) — tester writes failing tests *before* developer writes code
|
|
125
|
+
- **Per-feature loops** (L) — developer and tester iterate on each feature independently
|
|
126
|
+
- **Inspector gate** — validates test quality after tester, before reviewer
|
|
127
|
+
- **Multi-round review** — reviewer runs up to 3 rounds; CRITICAL/HIGH issues go back to developer
|
|
128
|
+
- **Tech-debt is mandatory** for all sizes — never skipped
|
|
129
|
+
|
|
130
|
+
## Agent Presets
|
|
131
|
+
|
|
132
|
+
Three presets control how many agents are scaffolded:
|
|
133
|
+
|
|
134
|
+
| Preset | Agents | Skills | Best for |
|
|
135
|
+
|--------|--------|--------|----------|
|
|
136
|
+
| **minimal** | 5 | 10 | Solo developer, small projects |
|
|
137
|
+
| **core** (default) | 8 | 10 | Teams, production projects |
|
|
138
|
+
| **full** | 20 | 21 | Complex systems, enterprise |
|
|
139
|
+
|
|
140
|
+
### Preset coverage
|
|
141
|
+
|
|
142
|
+
| Agent | minimal | core | full |
|
|
143
|
+
|-------|:-------:|:----:|:----:|
|
|
144
|
+
| analyst | x | x | x |
|
|
145
|
+
| architect | | x | x |
|
|
146
|
+
| skeptic | | x | x |
|
|
147
|
+
| developer | x | x | x |
|
|
148
|
+
| tester | x | x | x |
|
|
149
|
+
| inspector | x | x | x |
|
|
150
|
+
| reviewer | x | x | x |
|
|
151
|
+
| planner | | x | x |
|
|
152
|
+
| researcher | | | x |
|
|
153
|
+
| interviewer | | | x |
|
|
154
|
+
| validator | | | x |
|
|
155
|
+
| decomposer | | | x |
|
|
156
|
+
| auditor | | | x |
|
|
157
|
+
| prompter | | | x |
|
|
158
|
+
| deployer | | | x |
|
|
159
|
+
| scaffolder | | | x |
|
|
160
|
+
| librarian | | | x |
|
|
161
|
+
| writer | | | x |
|
|
162
|
+
| gatekeeper | | | x |
|
|
163
|
+
| verifier | | | x |
|
|
164
|
+
|
|
165
|
+
## Agents
|
|
166
|
+
|
|
167
|
+
### Pipeline (8 agents)
|
|
168
|
+
|
|
169
|
+
Core development cycle — from analysis to code review.
|
|
170
|
+
|
|
171
|
+
| Agent | Description | Verdicts |
|
|
172
|
+
|-------|-------------|----------|
|
|
173
|
+
| **analyst** | Analyzes task requirements from documentation, extracts acceptance criteria and PMI scenarios | `COMPLETE`, `NEEDS_DISCOVERY` |
|
|
174
|
+
| **architect** | Designs module architecture — structure, API contracts, data schemas | `READY`, `NEEDS_INPUT` |
|
|
175
|
+
| **skeptic** | Reality checker — verifies plans against actual codebase, finds "mirages" (non-existent files, APIs, modules) | `PASS`, `PASS_WITH_WARNINGS`, `FAIL` |
|
|
176
|
+
| **developer** | Writes code following project patterns, makes failing TDD tests green | `DONE`, `BLOCKED` |
|
|
177
|
+
| **tester** | Parametric testing agent — unit, integration, acceptance, smoke. Supports TDD mode | `PASS`, `FAIL` |
|
|
178
|
+
| **inspector** | Validates test quality — coverage, naming, assertions, mocking, isolation, edge cases | `APPROVE`, `REQUEST_CHANGES` |
|
|
179
|
+
| **reviewer** | Code review with iterations and escalation. Modes: default, plan_review, quick | `APPROVE`, `REQUEST_CHANGES`, `ESCALATE` |
|
|
180
|
+
| **planner** | Project-level planning — milestones, tasks, dependencies, completeness validation | `VALID`, `ISSUES_FOUND` |
|
|
181
|
+
|
|
182
|
+
### Planning (4 agents)
|
|
183
|
+
|
|
184
|
+
Deep analysis and task decomposition. Available in the **full** preset.
|
|
185
|
+
|
|
186
|
+
| Agent | Description |
|
|
187
|
+
|-------|-------------|
|
|
188
|
+
| **researcher** | Codebase exploration — entry points, patterns, dependencies, integrations |
|
|
189
|
+
| **interviewer** | Structured discovery interview — 3 cycles (general, code-informed, edge cases) |
|
|
190
|
+
| **validator** | Specification validation — 4 modes: userspec, techspec, task, completeness |
|
|
191
|
+
| **decomposer** | Task decomposition — generates atomic tasks with TDD anchors, acceptance criteria, and verify steps |
|
|
192
|
+
|
|
193
|
+
### Security (4 agents)
|
|
194
|
+
|
|
195
|
+
Security audits and infrastructure review. Available in the **full** preset.
|
|
196
|
+
|
|
197
|
+
| Agent | Description |
|
|
198
|
+
|-------|-------------|
|
|
199
|
+
| **auditor** | Security analysis — OWASP Top 10, hardcoded secrets, threat modeling, access control |
|
|
200
|
+
| **prompter** | LLM prompt review — clarity, few-shot quality, output format, injection safety, token efficiency |
|
|
201
|
+
| **deployer** | CI/CD review — workflow correctness, secrets management, platform config, deploy scripts |
|
|
202
|
+
| **scaffolder** | Project infrastructure review — structure, Docker, pre-commit hooks, .gitignore, dependency management |
|
|
203
|
+
|
|
204
|
+
### Documentation (4 agents)
|
|
205
|
+
|
|
206
|
+
Documentation quality and deployment validation. Available in the **full** preset.
|
|
207
|
+
|
|
208
|
+
| Agent | Description |
|
|
209
|
+
|-------|-------------|
|
|
210
|
+
| **librarian** | Documentation review — completeness, freshness, absence of bloat, consistency |
|
|
211
|
+
| **writer** | Generates stakeholder-facing reports and internal documentation |
|
|
212
|
+
| **gatekeeper** | Pre-deploy QA — runs tests, verifies acceptance criteria, checks deferred criteria |
|
|
213
|
+
| **verifier** | Post-deploy QA — live environment verification, manual verification plans |
|
|
214
|
+
|
|
215
|
+
## Skills (Slash Commands)
|
|
216
|
+
|
|
217
|
+
### Core skills (all presets) — 10 commands
|
|
58
218
|
|
|
59
219
|
| Command | Description |
|
|
60
220
|
|---------|-------------|
|
|
61
|
-
| `/start-session` | Begin work
|
|
62
|
-
| `/end-session` | Save context, checkpoint, create session log, commit
|
|
221
|
+
| `/start-session` | Begin work — sync repo, check checkpoint, load context, show progress |
|
|
222
|
+
| `/end-session` | Save context, checkpoint, create session log, commit and push |
|
|
63
223
|
| `/take-task [id]` | Full development cycle with feature-size routing (S/M/L) |
|
|
64
224
|
| `/complete-task [id]` | Verify task, smoke test, update progress, clear checkpoint |
|
|
65
225
|
| `/status` | Show project status, deadlines, blockers |
|
|
66
|
-
| `/plan [mode]` | Plan
|
|
67
|
-
| `/review [file]` | Code review for file or task |
|
|
226
|
+
| `/plan [mode]` | Plan, replan, or validate tasks from documentation |
|
|
227
|
+
| `/review [file]` | Code review for a file or task |
|
|
68
228
|
| `/code [task]` | Direct code generation for a specific task |
|
|
69
229
|
| `/test [target]` | Run or generate tests for a target |
|
|
70
230
|
| `/done [id]` | Quick-complete a task with minimal ceremony |
|
|
71
231
|
|
|
72
|
-
|
|
232
|
+
### Extra skills (full preset only) — 11 commands
|
|
73
233
|
|
|
74
234
|
| Command | Description |
|
|
75
235
|
|---------|-------------|
|
|
76
236
|
| `/interview` | Structured discovery interview (3 cycles, completeness >= 85%) |
|
|
77
237
|
| `/audit-wave` | Comprehensive pre-milestone audit with GO/NO-GO verdict |
|
|
78
238
|
| `/write-report` | Generate non-technical progress report for stakeholders |
|
|
79
|
-
| `/dashboard` | Project dashboard
|
|
239
|
+
| `/dashboard` | Project dashboard — progress, health, tech debt, activity |
|
|
80
240
|
| `/skill-master [name]` | Create a new custom skill from template |
|
|
81
|
-
| `/decompose [task]` | Break down a task into subtasks |
|
|
241
|
+
| `/decompose [task]` | Break down a task into subtasks with TDD anchors |
|
|
82
242
|
| `/feature [name]` | Scaffold a new feature end-to-end |
|
|
83
243
|
| `/security [target]` | Run security analysis on a target |
|
|
84
244
|
| `/spec [feature]` | Generate specification for a feature |
|
|
85
245
|
| `/techspec [module]` | Generate technical specification for a module |
|
|
86
246
|
| `/prompts [agent]` | Manage and optimize agent prompts |
|
|
87
247
|
|
|
88
|
-
|
|
89
|
-
|
|
90
|
-
Tasks are automatically classified and routed through the appropriate pipeline:
|
|
91
|
-
|
|
92
|
-
| Size | Criteria | Steps |
|
|
93
|
-
|------|----------|-------|
|
|
94
|
-
| **S** | 1 file, < 50 lines | checkpoint → code → tester+inspector → quick-review → tech-debt → fixation (6 steps) |
|
|
95
|
-
| **M** | 2-5 files, new module | checkpoint → analysis → TDD(RED) → code+tester+inspector → review → tech-debt → fixation (8 steps) |
|
|
96
|
-
| **L** | 6+ files, architecture changes | full cycle with architect, skeptic, per-feature loops, inspector, multi-round review (10 steps) |
|
|
97
|
-
|
|
98
|
-
### Checkpoint System
|
|
248
|
+
## Rules
|
|
99
249
|
|
|
100
|
-
|
|
250
|
+
8 development standards that are loaded automatically and enforced across all agents:
|
|
101
251
|
|
|
102
|
-
|
|
103
|
-
|
|
104
|
-
-
|
|
105
|
-
|
|
106
|
-
|
|
252
|
+
| Rule | Purpose |
|
|
253
|
+
|------|---------|
|
|
254
|
+
| `commit-conventions` | Commit message format — `[type](scope): description` |
|
|
255
|
+
| `development-cycle` | Feature-size routing (S/M/L) and pipeline step definitions |
|
|
256
|
+
| `testing-standards` | Test coverage >= 80%, edge cases, access control testing |
|
|
257
|
+
| `shared-resources` | Singleton resource registry — no duplicate DB connections or API clients |
|
|
258
|
+
| `context-loading` | Just-in-time context loading — pass data, not file references |
|
|
259
|
+
| `agent-output-format` | JSON output standard for all agents with structured verdicts |
|
|
260
|
+
| `quality-gates` | Verdict-based routing between pipeline steps |
|
|
261
|
+
| `rollback-protocol` | Rollback procedures for failed deployments |
|
|
107
262
|
|
|
108
|
-
|
|
109
|
-
- **Stop hook** — Reminds to save checkpoint and run `/end-session` before exiting
|
|
263
|
+
## Quality Gates
|
|
110
264
|
|
|
111
|
-
|
|
265
|
+
Every agent returns a structured verdict. The Team Lead reads the verdict and routes the pipeline:
|
|
112
266
|
|
|
113
|
-
|
|
267
|
+
```mermaid
|
|
268
|
+
graph TD
|
|
269
|
+
A["Agent returns verdict"] --> B{"Verdict type?"}
|
|
270
|
+
B -->|"PASS / APPROVE / DONE"| C["Continue pipeline"]
|
|
271
|
+
B -->|"WARNINGS / ATTENTION"| D["Show to user,<br/>continue"]
|
|
272
|
+
B -->|"FAIL / BLOCKED"| E{"Retry count < 3?"}
|
|
273
|
+
E -->|"Yes"| F["Return to<br/>previous step"]
|
|
274
|
+
E -->|"No"| G["Escalate to user"]
|
|
275
|
+
F --> A
|
|
114
276
|
|
|
115
|
-
|
|
116
|
-
|
|
117
|
-
|
|
118
|
-
|
|
119
|
-
| `testing-standards` | Test coverage and quality requirements |
|
|
120
|
-
| `shared-resources` | Singleton resource registry and patterns |
|
|
121
|
-
| `context-loading` | Just-in-time context loading, anti-patterns |
|
|
122
|
-
| `agent-output-format` | JSON output standard for all agents |
|
|
123
|
-
| `quality-gates` | Verdict-based routing and quality checkpoints |
|
|
124
|
-
| `rollback-protocol` | Rollback procedures for failed deployments |
|
|
277
|
+
style C fill:#d4edda,stroke:#28a745
|
|
278
|
+
style D fill:#fff3cd,stroke:#ffc107
|
|
279
|
+
style G fill:#f8d7da,stroke:#dc3545
|
|
280
|
+
```
|
|
125
281
|
|
|
126
|
-
|
|
282
|
+
### Verdict matrix
|
|
283
|
+
|
|
284
|
+
```mermaid
|
|
285
|
+
graph LR
|
|
286
|
+
subgraph "Analysis"
|
|
287
|
+
A1["analyst"] -->|COMPLETE| A2["architect"]
|
|
288
|
+
A1 -->|NEEDS_DISCOVERY| A3["ask user"]
|
|
289
|
+
A3 --> A1
|
|
290
|
+
end
|
|
291
|
+
|
|
292
|
+
subgraph "Architecture"
|
|
293
|
+
A2 -->|READY| SK["skeptic"]
|
|
294
|
+
A2 -->|NEEDS_INPUT| A4["ask user"]
|
|
295
|
+
A4 --> A2
|
|
296
|
+
end
|
|
297
|
+
|
|
298
|
+
subgraph "Reality Check"
|
|
299
|
+
SK -->|PASS| DEV["developer"]
|
|
300
|
+
SK -->|FAIL| A2
|
|
301
|
+
end
|
|
302
|
+
|
|
303
|
+
subgraph "Code + Tests"
|
|
304
|
+
DEV -->|DONE| TST["tester"]
|
|
305
|
+
TST -->|PASS| INS["inspector"]
|
|
306
|
+
TST -->|FAIL| DEV
|
|
307
|
+
INS -->|APPROVE| REV["reviewer"]
|
|
308
|
+
INS -->|REQUEST_CHANGES| TST
|
|
309
|
+
end
|
|
310
|
+
|
|
311
|
+
subgraph "Review"
|
|
312
|
+
REV -->|APPROVE| FIN["finalize"]
|
|
313
|
+
REV -->|REQUEST_CHANGES| DEV
|
|
314
|
+
end
|
|
315
|
+
|
|
316
|
+
style FIN fill:#d4edda,stroke:#28a745
|
|
317
|
+
```
|
|
127
318
|
|
|
128
|
-
|
|
319
|
+
## CLI Commands
|
|
129
320
|
|
|
130
|
-
|
|
131
|
-
|--------|--------|--------|-------------|
|
|
132
|
-
| **minimal** | 5 | 10 | Essentials + inspector |
|
|
133
|
-
| **core** (default) | 8 | 10 | Full development pipeline |
|
|
134
|
-
| **full** | 20 | 21 | All categories + extra skills |
|
|
321
|
+
### `agent-forge init`
|
|
135
322
|
|
|
136
|
-
|
|
323
|
+
Initialize AI-driven development infrastructure in the current directory.
|
|
137
324
|
|
|
138
325
|
```bash
|
|
139
|
-
npx @alxyrgin/agent-forge init
|
|
326
|
+
npx @alxyrgin/agent-forge init # interactive setup
|
|
327
|
+
npx @alxyrgin/agent-forge init --yes # use defaults (TypeScript, core preset)
|
|
328
|
+
npx @alxyrgin/agent-forge init --overwrite # overwrite existing files
|
|
140
329
|
```
|
|
141
330
|
|
|
142
|
-
|
|
331
|
+
The wizard prompts for:
|
|
143
332
|
- Project name and description
|
|
144
|
-
- Technology stack (Python/TypeScript/Go/Rust)
|
|
333
|
+
- Technology stack (Python / TypeScript / Go / Rust)
|
|
145
334
|
- Framework and test framework
|
|
146
335
|
- Team members (names, roles, emails)
|
|
147
336
|
- Milestones (optional)
|
|
148
|
-
- Agent preset (core/full
|
|
149
|
-
- Commit style (standard/conventional)
|
|
337
|
+
- Agent preset (minimal / core / full)
|
|
338
|
+
- Commit style (standard / conventional)
|
|
339
|
+
|
|
340
|
+
### `agent-forge update`
|
|
150
341
|
|
|
151
|
-
|
|
342
|
+
Update framework files while preserving your data.
|
|
152
343
|
|
|
153
344
|
```bash
|
|
154
|
-
npx @alxyrgin/agent-forge
|
|
345
|
+
npx @alxyrgin/agent-forge update
|
|
155
346
|
```
|
|
156
347
|
|
|
157
|
-
|
|
348
|
+
**Overwritten** (updated to latest version):
|
|
349
|
+
- `.claude/CLAUDE.md`
|
|
350
|
+
- `.claude/agents/*`
|
|
351
|
+
- `.claude/skills/*`
|
|
352
|
+
- `.claude/rules/*`
|
|
353
|
+
- `.claude/hooks/*`
|
|
354
|
+
- `.claude/settings.json`
|
|
158
355
|
|
|
159
|
-
|
|
356
|
+
**Preserved** (your data stays intact):
|
|
357
|
+
- `dev-infra/memory/*` — your Memory Bank
|
|
358
|
+
- `dev-infra/tasks/*` — your task tracking
|
|
359
|
+
- `dev-infra/sessions/*` — your session logs
|
|
360
|
+
- `dev-infra/tests/*` — your test structure
|
|
160
361
|
|
|
161
|
-
|
|
362
|
+
### `agent-forge doctor`
|
|
162
363
|
|
|
163
|
-
|
|
164
|
-
- `--yes, -y` — skip prompts, use defaults
|
|
165
|
-
- `--overwrite` — overwrite existing files
|
|
364
|
+
Check integrity of the generated structure. Verifies that all expected files exist and are not empty.
|
|
166
365
|
|
|
167
|
-
|
|
366
|
+
```bash
|
|
367
|
+
npx @alxyrgin/agent-forge doctor
|
|
368
|
+
```
|
|
369
|
+
|
|
370
|
+
## Memory Bank
|
|
371
|
+
|
|
372
|
+
9 files that persist context across sessions. The Team Lead reads and updates these automatically.
|
|
373
|
+
|
|
374
|
+
| File | Purpose |
|
|
375
|
+
|------|---------|
|
|
376
|
+
| `active-context.md` | Current session state — what is done, what is next |
|
|
377
|
+
| `progress.md` | Milestone progress, task statuses |
|
|
378
|
+
| `project-brief.md` | Project overview, team, stack |
|
|
379
|
+
| `decisions.md` | Architectural Decision Records (ADR) |
|
|
380
|
+
| `tech-stack.md` | Technology stack details |
|
|
381
|
+
| `tech-debt.md` | Technical debt registry with lifecycle tracking (open / in_progress / resolved) |
|
|
382
|
+
| `patterns.md` | Code patterns and conventions |
|
|
383
|
+
| `troubleshooting.md` | Problem solutions log |
|
|
384
|
+
| `checkpoint.yml` | Recovery checkpoint for interrupted sessions |
|
|
168
385
|
|
|
169
|
-
|
|
386
|
+
### Checkpoint System
|
|
387
|
+
|
|
388
|
+
The checkpoint (`dev-infra/memory/checkpoint.yml`) enables recovery after session interruptions:
|
|
389
|
+
|
|
390
|
+
- **Automatic saving** — updated after each pipeline step
|
|
391
|
+
- **Recovery on start** — `/start-session` detects an active checkpoint and offers to resume
|
|
392
|
+
- **Cleanup on completion** — `/complete-task` clears the checkpoint
|
|
170
393
|
|
|
171
|
-
|
|
394
|
+
```mermaid
|
|
395
|
+
graph LR
|
|
396
|
+
A["Session interrupted"] --> B["checkpoint.yml<br/>saved automatically"]
|
|
397
|
+
B --> C["Next session:<br/>/start-session"]
|
|
398
|
+
C --> D{"Active<br/>checkpoint?"}
|
|
399
|
+
D -->|"Yes"| E["Offer to resume<br/>from last step"]
|
|
400
|
+
D -->|"No"| F["Fresh start"]
|
|
401
|
+
|
|
402
|
+
style B fill:#fff3cd,stroke:#ffc107
|
|
403
|
+
style E fill:#d4edda,stroke:#28a745
|
|
404
|
+
```
|
|
172
405
|
|
|
173
406
|
## Generated Structure
|
|
174
407
|
|
|
175
408
|
```
|
|
176
409
|
your-project/
|
|
177
410
|
├── .claude/
|
|
178
|
-
│ ├── CLAUDE.md
|
|
179
|
-
│ ├── settings.json
|
|
411
|
+
│ ├── CLAUDE.md # Team Lead instructions
|
|
412
|
+
│ ├── settings.json # Claude Code hooks and env
|
|
180
413
|
│ ├── hooks/
|
|
181
|
-
│ │ └── protect-docs.sh
|
|
182
|
-
│ ├── agents/
|
|
183
|
-
│ │ ├── pipeline/
|
|
184
|
-
│ │ │
|
|
185
|
-
│ │ ├── planning/
|
|
186
|
-
│ │ ├── security/
|
|
187
|
-
│ │ └── documentation/
|
|
188
|
-
│ ├── skills/
|
|
414
|
+
│ │ └── protect-docs.sh # PreToolUse hook — blocks edits in docs/
|
|
415
|
+
│ ├── agents/
|
|
416
|
+
│ │ ├── pipeline/ # analyst, architect, skeptic, developer,
|
|
417
|
+
│ │ │ # tester, inspector, reviewer, planner
|
|
418
|
+
│ │ ├── planning/ # researcher, validator, interviewer, decomposer
|
|
419
|
+
│ │ ├── security/ # auditor, prompter, deployer, scaffolder
|
|
420
|
+
│ │ └── documentation/ # librarian, writer, gatekeeper, verifier
|
|
421
|
+
│ ├── skills/
|
|
189
422
|
│ │ ├── start-session/SKILL.md
|
|
190
423
|
│ │ ├── take-task/SKILL.md
|
|
191
|
-
│ │
|
|
192
|
-
│
|
|
424
|
+
│ │ ├── code/SKILL.md
|
|
425
|
+
│ │ ├── test/SKILL.md
|
|
426
|
+
│ │ └── ... # 10–21 slash commands
|
|
427
|
+
│ └── rules/
|
|
193
428
|
│ ├── commit-conventions.md
|
|
194
429
|
│ ├── development-cycle.md
|
|
195
430
|
│ ├── testing-standards.md
|
|
@@ -199,19 +434,19 @@ your-project/
|
|
|
199
434
|
│ ├── quality-gates.md
|
|
200
435
|
│ └── rollback-protocol.md
|
|
201
436
|
├── dev-infra/
|
|
202
|
-
│ ├── memory/
|
|
437
|
+
│ ├── memory/ # 9 Memory Bank files
|
|
203
438
|
│ │ ├── active-context.md
|
|
204
439
|
│ │ ├── progress.md
|
|
205
440
|
│ │ ├── checkpoint.yml
|
|
206
441
|
│ │ └── ...
|
|
207
442
|
│ ├── tasks/
|
|
208
|
-
│ │ └── tasks.json
|
|
209
|
-
│ ├── sessions/
|
|
210
|
-
│ └── tests/
|
|
211
|
-
│ ├── acceptance/
|
|
212
|
-
│ ├── pmi/
|
|
213
|
-
│ └── results/
|
|
214
|
-
└── .claude-forge.json
|
|
443
|
+
│ │ └── tasks.json # Task tracking
|
|
444
|
+
│ ├── sessions/ # Session logs
|
|
445
|
+
│ └── tests/
|
|
446
|
+
│ ├── acceptance/ # Acceptance criteria
|
|
447
|
+
│ ├── pmi/ # PMI scenarios
|
|
448
|
+
│ └── results/ # Test results
|
|
449
|
+
└── .claude-forge.json # Manifest for doctor and update
|
|
215
450
|
```
|
|
216
451
|
|
|
217
452
|
## License
|