fable-sonnet-orchestrator-kit

Operating model for the main agent orchestrating development — GitHub issues as the todo list, Sonnet 4.6 max-effort executor fan-out via worktrees + PRs into main, code-gated review loop, sole-reviewer merging. Auto-injected every session by the SessionStart hook.

Maintain `handoff.md` at the meta-repo root as the single, curated, never-stale ROLLING MEMORY of the whole project — current development status AND every durable learned truth — so any brand-new agent with zero foreknowledge can fully take over. This is an ORCHESTRATOR-ONLY duty. Use it: (1) the moment a context compaction/summary/handoff is imminent — flush the live context window into handoff.md FIRST; (2) after any milestone, merge, decision, architecture change, or newly-learned gotcha that changes durable state; (3) at session start, to READ handoff.md before acting; (4) whenever asked to update/regenerate/fix the handoff. Core rule: ACCRETE + CURATE, never blind-overwrite — preserve durable truths, supersede only what is truly stale.

Operating procedure for the issue-triage subagent — a narrow GitHub-issue clerk that creates, merges, updates, or closes issues exactly as instructed, with context-efficient search and careful flag hygiene. Preloaded into the issue-triage agent; not for the main agent.

Operating procedure for the sonnet-executor subagent — resolve exactly ONE GitHub issue into one focused PR into main. Preloaded into the sonnet-executor agent; not for the main agent.