-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathllms.txt
More file actions
68 lines (53 loc) · 2.62 KB
/
Copy pathllms.txt
File metadata and controls
68 lines (53 loc) · 2.62 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
# forge
> Forge is a Claude Code plugin that adds structured planning, parallel
> execution in isolated git worktrees, deep validation with API contract
> checks, intelligent retry via a debugger agent, and cross-session memory
> for learned patterns. It turns a one-line objective into a validated
> dependency graph of modules, each executed, verified, and reviewed before
> being merged back.
## Install
```bash
claude plugin marketplace add TT-Wang/forge
claude plugin install forge@tt-wang-plugins
```
## Usage
```
/forge <objective> # full workflow: plan → execute → validate → learn
/forge-status # show plan progress, iteration state, memory
/forge-validate <module> # run validation for a specific module
```
## Architecture
- **Orchestrator skill** (`skills/forge/`) — top-level workflow
- **Agents** (`agents/`) — planner, worker, reviewer, debugger
- **MCP server** (`forge-mcp-server/`) — 7 tools: validate, validate_plan,
memory_recall, memory_save, iteration_state, forge_logs, session_state
- **`.forge/` directory** — per-project state: plans, iterations, logs,
session snapshots, project + global memory
## MCP tools
| Tool | Purpose |
|------|---------|
| `validate` | Run verify commands + contract checks against a worktree |
| `validate_plan` | DAG cycle detection, file-overlap warnings, schema checks |
| `memory_recall` | Search project + global memory |
| `memory_save` | Persist learned patterns (dedup by category+pattern) |
| `iteration_state` | Track per-run retry counts, scores, stagnation |
| `forge_logs` | Query structured JSONL logs (run/module/phase/severity) |
| `session_state` | Save/load orchestrator state for resumability |
## Defaults worth knowing
- Node.js ≥ 20, ESM-only, zero build step (`node index.mjs`)
- `validate`'s `cwd` arg redirects checks to a worker's worktree
- Iteration state is scoped per `runId` so module IDs don't collide across plans
- stdio-only MCP transport (no network surface)
- State writes are atomic (`tmp + rename`)
## Links
- Repo: https://github.com/TT-Wang/forge
- Issues: https://github.com/TT-Wang/forge/issues
- Changelog: https://github.com/TT-Wang/forge/blob/main/CHANGELOG.md
- Security policy: https://github.com/TT-Wang/forge/blob/main/SECURITY.md
- Contributing: https://github.com/TT-Wang/forge/blob/main/CONTRIBUTING.md
- License: MIT
## Companion project
- **memem** — https://github.com/TT-Wang/memem — persistent cross-session
memory for Claude Code. Recommended pairing: forge plans + executes,
memem remembers. Forge's `memory_save` patterns are readable by memem's
recall index, so learnings compound across runs.