meto-cli 0.7.6 → 0.8.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.
@@ -0,0 +1,94 @@
1
+ # Swarm Workflow — {{PROJECT_NAME}}
2
+
3
+ ## What is Swarm Mode
4
+
5
+ Each epic runs its own agent in parallel. Epic agents are scoped to their domain and cannot touch files owned by other epics. They report status every 3 completed tasks. The user stays in control at every checkpoint.
6
+
7
+ ---
8
+
9
+ ## Swarm vs Sprint
10
+
11
+ | | Sprint | Swarm |
12
+ |---|---|---|
13
+ | Tasks | One at a time, sequential | Parallel per epic |
14
+ | Agents | meto-developer (generic) | meto-epic-[id] (scoped) |
15
+ | Speed | Careful, deliberate | Faster on independent epics |
16
+ | Risk | Low | Medium — requires domain discipline |
17
+ | Best for | Solo, small scope, tight control | Multiple epics, independent domains |
18
+
19
+ ---
20
+
21
+ ## Starting a Swarm
22
+
23
+ 1. `@meto-pm` confirms all epics are defined in `epics.md`
24
+ 2. `@meto-pm` generates `ai/swarm/domain-map.md` — one domain per epic
25
+ 3. `@meto-pm` generates one `epic-agent.md` per epic in `.claude/agents/`
26
+ 4. `@meto-pm` initialises `ai/swarm/SWARM_AWARENESS.md` with active epic table
27
+ 5. User launches epic agents — one per epic, in separate Claude Code sessions
28
+
29
+ ---
30
+
31
+ ## Checkpoint Rhythm
32
+
33
+ ```
34
+ Epic agent picks task → implements → self-check → moves to testing
35
+ Repeat × 3
36
+ → Write checkpoint to SWARM_AWARENESS.md
37
+ → Surface status to user
38
+ → User runs: npx meto-cli status
39
+ → User reviews: continue / intervene / reassign
40
+ → Repeat
41
+ ```
42
+
43
+ A checkpoint is NOT a blocker — if status is `on-track` the agent continues automatically. Only `blocked` status requires user intervention.
44
+
45
+ ---
46
+
47
+ ## npx meto-cli status
48
+
49
+ Reads `ai/swarm/SWARM_AWARENESS.md` and prints a formatted terminal report:
50
+
51
+ ```
52
+ Last Swarm Checkpoint
53
+
54
+ Project: {{PROJECT_NAME}}
55
+ Duration: [start] – [latest checkpoint]
56
+
57
+ Epics Active:
58
+ - E1 · [name] [n] tasks done
59
+ - E2 · [name] [n] tasks in progress
60
+ - E3 · [name] blocked — [reason]
61
+ - E4 · [name] not started
62
+
63
+ Acceptance Criteria: [n] of [n] passed
64
+
65
+ Blockers:
66
+ - [EPIC_ID]: [description]
67
+
68
+ Next: [instruction to user]
69
+ ```
70
+
71
+ Run at any time — not only at checkpoints. Gives a live read of the swarm state.
72
+
73
+ ---
74
+
75
+ ## Conflict Resolution Protocol
76
+
77
+ 1. Epic agent detects it needs a file outside its domain
78
+ 2. Agent logs conflict in `SWARM_AWARENESS.md` under Shared File Conflicts
79
+ 3. Agent sets its status to `blocked`
80
+ 4. Agent pauses — does NOT proceed
81
+ 5. User runs `npx meto-cli status` — sees the blocker
82
+ 6. User resolves: assigns ownership or approves shared edit
83
+ 7. Agent continues only after user confirmation
84
+
85
+ ---
86
+
87
+ ## Ending a Swarm
88
+
89
+ A swarm ends when all epics reach 0 tasks in `tasks-todo.md` tagged to them and `@meto-tester` has signed off all items in `tasks-done.md`.
90
+
91
+ `@meto-pm` writes final swarm summary to `SWARM_AWARENESS.md`:
92
+ ```
93
+ SWARM COMPLETE | [date] | [n] epics | [n] tasks | [n/n] AC passed
94
+ ```