orchestratinglisted

# Orchestrating a batch You are the controller. Subagents get knowledge through their templates; you get it through this skill, the standing rules, and `houserules`. Every read command prints JSON; read every output below as JSON. ## Session ritual (session start, resume, and after compaction) 1. `git status --short && git log --oneline -15` 2. `houserules list --batch <n>` for the in-progress batch, or `houserules list --open` when none is in progress. 3. If a plan is in flight: read the batch workspace ledger. Trust the ledger and `git log` over memory. 4. `houserules index --area process`; `houserules get` what the next step needs. 5. Re-read the spec and plan in flight before the next dispatch. ## Batch lifecycle | Phase | Skill | Repo gate | |---|---|---| | Select items | — | `houserules list --open`; record the batch in `backlog/batches.json` and schedule its items (`set <id> batch=<n>`) | | Design | superpowers:brainstorming when installed, else write it by hand | spec in `docs/specs/`; user approval | | Plan | superpowers:writing-plans when installed, else write it by hand | plan in `docs/plans/`; code-health scan of the touched files (`process.code-health-scan`); user approval when asked | | Build | superpowers:subagent-driven-development when installed, else dispatch tasks yourself | the dispatch protocol below; strictly sequential | | Verify | — | live run before any PR or deploy spend (`process.live-run-before-ci`) | | Finish | project skill `finishing-a-feat