cclaw-cli 0.34.0 → 0.34.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/README.md +43 -18
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -2,13 +2,15 @@
|
|
|
2
2
|
|
|
3
3
|
**Install once, ship every time.** cclaw is an installer-first workflow
|
|
4
4
|
runtime that gives your AI coding agent one inspectable path from idea to
|
|
5
|
-
shipped PR
|
|
5
|
+
shipped PR — **plus an automatic closeout chain** that turns every ship
|
|
6
|
+
into reusable knowledge:
|
|
6
7
|
|
|
7
|
-
> **brainstorm → scope → design → spec → plan → tdd → review → ship**
|
|
8
|
+
> **brainstorm → scope → design → spec → plan → tdd → review → ship**
|
|
9
|
+
> **↳ auto-closeout: retro → compound → archive** *(resumable, never manual)*
|
|
8
10
|
|
|
9
11
|
Every stage has real gates the agent cannot skip, every decision leaves a
|
|
10
|
-
file-backed audit trail, and the same
|
|
11
|
-
|
|
12
|
+
file-backed audit trail, and the same slash commands work across Claude
|
|
13
|
+
Code, Cursor, OpenCode, and OpenAI Codex.
|
|
12
14
|
|
|
13
15
|
You install cclaw **once** from the terminal, then everything happens
|
|
14
16
|
inside your harness — no hidden control plane, no background daemon, no
|
|
@@ -41,15 +43,28 @@ operational knobs to memorise.
|
|
|
41
43
|
│ │ │ │ │ │ │ │
|
|
42
44
|
▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼
|
|
43
45
|
01.md 02.md 03.md 04.md 05.md 06.md 07.md 08.md
|
|
44
|
-
│
|
|
45
|
-
└──── gates + subagents + knowledge capture
|
|
46
|
+
│ │
|
|
47
|
+
└──── gates + subagents + knowledge capture │
|
|
48
|
+
happen at every step │
|
|
49
|
+
▼
|
|
50
|
+
┌─────────────────────────┐
|
|
51
|
+
│ automatic closeout │
|
|
52
|
+
│ (resumable state │
|
|
53
|
+
│ machine, never manual)│
|
|
54
|
+
└────────────┬────────────┘
|
|
55
|
+
▼
|
|
56
|
+
retro ──► compound ──► archive
|
|
57
|
+
09.md (knowledge (runs/
|
|
58
|
+
promoted) <slug>/)
|
|
46
59
|
```
|
|
47
60
|
|
|
48
61
|
Every stage reads and writes real files under `.cclaw/`. `flow-state.json`
|
|
49
|
-
holds the single source of truth for "where are we"
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
62
|
+
holds the single source of truth for "where are we" — including
|
|
63
|
+
`closeout.shipSubstate` so a ship → retro → compound → archive chain
|
|
64
|
+
resumes at the exact step after any interruption. `knowledge.jsonl`
|
|
65
|
+
accumulates reusable lessons **throughout** the flow, not only at the
|
|
66
|
+
end; stage artifacts live under `.cclaw/artifacts/` until archive rolls
|
|
67
|
+
them into `.cclaw/runs/<date-slug>/`.
|
|
53
68
|
|
|
54
69
|
```
|
|
55
70
|
You ──► /cc <idea>
|
|
@@ -188,21 +203,31 @@ No magic. No ambiguity about where you are.
|
|
|
188
203
|
|
|
189
204
|
---
|
|
190
205
|
|
|
191
|
-
## The eight stages,
|
|
206
|
+
## The eight stages, the three tracks, and auto-closeout
|
|
192
207
|
|
|
193
|
-
cclaw has eight stages
|
|
194
|
-
|
|
208
|
+
cclaw has eight **critical-path** stages plus an automatic three-step
|
|
209
|
+
closeout chain (retro → compound → archive). A single prompt rarely needs
|
|
210
|
+
all eight critical-path stages, so `/cc` picks a **track** up front so
|
|
211
|
+
the flow matches the task.
|
|
195
212
|
|
|
196
|
-
| Track |
|
|
213
|
+
| Track | Critical path | Typical trigger |
|
|
197
214
|
|---|---|---|
|
|
198
215
|
| **quick** | `spec → tdd → review → ship` | `bug`, `hotfix`, `typo`, `rename`, `bump`, `docs only`, one-liners |
|
|
199
216
|
| **medium** | `brainstorm → spec → plan → tdd → review → ship` | `add endpoint`, `add field`, `extend existing`, `wire integration` |
|
|
200
217
|
| **standard** _(default)_ | all 8 stages | `new feature`, `refactor`, `migration`, `platform`, `schema`, `architecture` |
|
|
201
218
|
|
|
202
|
-
|
|
203
|
-
|
|
204
|
-
`
|
|
205
|
-
|
|
219
|
+
**Every track ends with the same auto-closeout chain.** Once ship
|
|
220
|
+
completes, `/cc-next` automatically drives
|
|
221
|
+
`retro → compound → archive` — with `closeout.shipSubstate` carrying the
|
|
222
|
+
exact step across sessions, so a crashed or backgrounded run resumes
|
|
223
|
+
without re-drafting retros or re-asking structured questions. See
|
|
224
|
+
[Ship and closeout](#ship-and-closeout--automatic-resumable).
|
|
225
|
+
|
|
226
|
+
Each critical-path stage produces a dated artifact under
|
|
227
|
+
`.cclaw/artifacts/`: `00-idea.md` (seed), `01-brainstorm.md` through
|
|
228
|
+
`08-ship.md`. Closeout adds `09-retro.md`; archive then rolls the whole
|
|
229
|
+
bundle into `.cclaw/runs/<YYYY-MM-DD-slug>/` and resets the active flow
|
|
230
|
+
for the next feature.
|
|
206
231
|
|
|
207
232
|
### Track heuristics are configurable
|
|
208
233
|
|