buildsystemlisted

# Buildsystem — Orchestrated Development Wave This skill automates one complete development wave: backlog prioritization, parallel Haiku agent dispatch, code review, merge train, and state checkpoint. It reads your `CLAUDE.md` rules and project backlog, then orchestrates a fleet of small, focused agents to deliver working features or fixes. **Core principle**: A wave is a bounded unit of work (2–4 hours) that delivers measurable progress. The orchestrator dispatches independent Haiku agents to parallel worktrees, each agent works in isolation, all agents converge on a merge train, and the wave closes with a checkpoint and audit. --- ## Quick Start ### Prerequisites Before running `/buildsystem`, ensure: 1. **Repository is primed** — Run `/power` first to load your CLAUDE.md layer and confirm orchestrator brain health 2. **Backlog exists** — Create a ranked backlog in `state/BACKLOG.md` or document your work items in the active `STATE.md` 3. **Aesop is initialized** — Config file (`aesop.config.json`), watchdog running, state directory populated ### One Command ```bash /buildsystem ``` The orchestrator reads your backlog, dispatches agents, monitors progress, and delivers a closed wave with merged PRs. --- ## Wave Phases ### Phase 0: Preflight (1–2 min) The orchestrator validates setup: - Confirms CLAUDE.md is loaded and rules are understood - Checks watchdog heartbeat (healthy daemon) - Validates backlog format and work-item sizing - Confirms all repos in config