ce-auto-buildlisted

# Auto Build **Invocation input:** plan, optional feature range, and optional `--resume`: $ARGUMENTS Build the selected features of an existing plan in ship order. For each feature, create the specification, validate it, implement it, verify it, and run an independent review before moving on. The workflow is deliberately sequential and has one operating profile. Use this skill when a plan is already approved and the human wants a bounded batch run. Stage 0 enforces the plan's human-owned architecture disposition before any worker starts. Use `/core-engineering:ce-plan` when the scope or architecture convergence is still unsettled, `/core-engineering:ce-architecture` when a required governed baseline is missing or stale, and `/core-engineering:ce-spec` or `/core-engineering:ce-implement` when the human wants to drive one feature directly. ## Execution Contract Auto-build provides supervised autonomy, not release authority. - The human approves the exact scope, token/compute budget, failure-attempt cap, and park cap at kickoff. - Features run one at a time in `ship_order`. There is no parallel or worktree mode. - A fresh spec worker and implementation worker preserve the spec-to-code boundary. An independent review worker examines the result. - On-disk artifacts and deterministic scripts gate progress; worker claims do not. - A full plan must pass `plan-lint.py` and carry a valid `architecture_disposition`. Every present architecture package is consumer-linted.