build-epiclisted

# Build Epic Scope: one story. Called by orchestrate-project Phase 4. Not a replacement for orchestrate-project. Orchestrates the **build** flow for a single epic: survey → plan tasks → kickoff → TDD → verify → audit → commit → release. > **HARD GATE** — Set `specs/state.yaml` `active_flow: build_epic` and `active_epic: eNN` before starting. > > **HARD GATE** — Not on `main`/`master` before step 3 (kickoff-branch). ## Eight steps (`epic_cycle` in state.yaml) | Step | Skill / action | |------|----------------| | 1 | `survey-context` — confirm epic + story | | 2 | `plan-work` — flesh out story `tasks[]` in `specs/epics/eNN-slug/epic.yaml` | | 3 | `kickoff-branch` — feature branch + clean baseline | | 4 | `develop-tdd` — red-green per task | | 5 | `verify-work` — UAT + mechanical gates | | 6 | `audit-code` — self-review checklist | | 7 | `commit-message` — Conventional Commits draft | | 8 | `release-branch` — PR or solo land | ## Process 1. Read `specs/state.yaml`, `specs/execution-status.yaml`, `specs/release-plan.yaml`, active `specs/epics/eNN-slug/epic.yaml`. 2. **BCP Tracking (Step 2):** After `plan-work` completes, read the `bcps:` count (Business Complexity Points story size) from the epic capsule and carry it into `state.yaml` as `epic_cycle.story_bcps = N`. 3. If `epic_cycle.step` missing, set to `1`. 4. Run **only the current step** (resume mode) unless user asked for full auto-run. 5. After step verify passes, increment `epic_cycle.step` in `state.yaml` (or `bas