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. Use `/ce-plan` when the scope or architecture is still unsettled. Use `/ce-spec` or `/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, retry 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. - Product, security-acceptance, destructive, architectural, and scope decisions are parked for the human. They are never guessed to keep the batch moving. - The run never creates branches or commits, pushes, opens or merges pull requests, deploys, or writes to external systems. - The final result is not "done" until a human reviews the report and working-tree diff. ## Fixed workflow ```te