Hub-and-spoke orchestrator for RULE 0.12 at project scale. SKILL.md
indexes 4 phase files: intake, fork-skeleton, parallel-exec, merge-
ceremony.
Flow:
Phase 1 — 1 free-text line (GOAL) + 1 batch of 5 AskUserQuestion
(type, theory, fanout, main-agent, DB mode).
Phase 2 — project/<slug> branch, kei-ledger fork root, theoretical
sub-agent spawn confirmation click.
Phase 3 — poll kei-ledger list --status running, aggregate
progress.json, steering click (continue / add / kill /
merge / pause).
Phase 4 — kei-ledger validate per bundle, per-branch merge verdict
click (merge --no-ff / squash / reject / defer), final
integration + NO-DOWNGRADE close click if any rejected /
deferred.
>=6 AskUserQuestion calls minimum (1 batch Phase 1 + 1 Phase 2 + 1
Phase 3 + >=2 per-branch Phase 4 + 1 close).
Constructor Pattern: SKILL.md 109 LOC, phase files 80-108 LOC each —
all under 150 LOC.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
3.4 KiB
3.4 KiB
Phase 2 — Fork Skeleton
Create the project branch, the root ledger entry, and the first
theoretical sub-agent spawn(s) per Phase 1's THEORY_PART choice.
2a — Project branch
Resolve PROJECT_BRANCH = project/<PROJECT_SLUG>.
Run (via Bash tool):
git fetch origin main
git checkout -b "$PROJECT_BRANCH" origin/main
Failure modes — emit a NO-DOWNGRADE recovery AskUserQuestion:
{
"questions": [
{
"question": "Branch creation failed — how to proceed?",
"header": "Recovery",
"multiSelect": false,
"options": [
{"label": "rename slug", "description": "Use a suffix (-v2, -alt) and retry"},
{"label": "reuse existing branch", "description": "Check out the existing branch and append this work"},
{"label": "abort project", "description": "Stop before touching the ledger"}
]
}
]
}
2b — Ledger root entry
Skip when DB_MODE == "file-only". Otherwise:
spec_sha=$(printf '%s' "$GOAL" | shasum -a 256 | cut -c1-16)
LEDGER_ID="project-${PROJECT_SLUG}-$(date +%s)"
kei-ledger init
kei-ledger fork "$LEDGER_ID" "$PROJECT_BRANCH" \
--parent main \
--spec-sha "$spec_sha"
Also write the root bundle under
.claude/agents/$LEDGER_ID/{spec.md, plan.md, progress.json, chatlog.md, handoffs.md, review.md}.
spec.md = GOAL + 5 Phase-1 answers; others start empty / scaffolded.
2c — Theoretical sub-agent spawn (AskUserQuestion, ONE)
Branch on THEORY_PART. Emit this confirmation click:
{
"questions": [
{
"question": "Confirm theoretical sub-agent fan-out (derived from Phase 1)?",
"header": "Spawn",
"multiSelect": true,
"options": [
{"label": "physics-deriver", "description": "Math derivation agent (only if THEORY_PART = math derivation)"},
{"label": "research sweep", "description": "Prior-art research sub-agent (only if THEORY_PART = prior-art research)"},
{"label": "architect", "description": "Architecture spec agent (only if THEORY_PART = architecture spec)"},
{"label": "paradigm-classifier", "description": "Observable classification per RULE 0.6 (only if THEORY_PART = paradigm analysis)"},
{"label": "skip theory", "description": "No theoretical sub-agent — straight to implementation fan-out"}
]
}
]
}
For each selected label (except skip theory):
- Derive
agent_id = <kind>-<ts>,agent_branch = project/$PROJECT_SLUG/agent-$agent_id git worktree add .claude/worktrees/$agent_id -b $agent_branch(when fanout > single)kei-ledger fork "$agent_id" "$agent_branch" --parent "$PROJECT_BRANCH" --spec-sha "$spec_sha"(skip if file-only)- Invoke the Agent tool with the matching
subagent_typeandisolation: "worktree"(theagent-fork-logger.shhook will emit a second fork row — OK, ledger de-duplicates by primary key and the hook attempt returns nonzero silently) - Append
{id, branch, kind}toSUB_AGENTS
Verify-criterion
git branch --show-currentreturns$PROJECT_BRANCH.kei-ledger list --status runningreturns ≥ 1 row whose id ==LEDGER_ID(unlessDB_MODE == "file-only").- Every entry in
SUB_AGENTShas a correspondingkei-ledger listrow withparent_branch == $PROJECT_BRANCH. - If any spawn failed: emit NO-DOWNGRADE recovery click (retry / skip / abort).