plan-implement

Automating backlog plan execution requires orchestrating plan files like PLAN_NEXT.md into a reproducible run that validates each story against acceptance criteria and the DoD. This skill enforces Git bootstrap, per-story test wiring, and CodeQL prepush checks to ensure deterministic, auditable delivery across sprints.

Validating acceptance criteria across plan stories is best handled by an end-to-end workflow that parses plan files, wires per-story tests, and runs CodeQL prepush checks. This approach enforces quality gates and performs a final DoD revalidation before marking any epic or story complete.

Setting up reproducible Git bootstrap and per-story test wiring involves providing a structured plan file such as PLAN_NEXT.md. The workflow parses the plan, orchestrates dependencies across stories, and applies strict bootstrap steps to ensure every execution is auditable and deterministic.

Yes, this skill operates within the Gait workflow to orchestrate plan stories, dependencies, and CodeQL validation. It parses your existing product plans, applies Git bootstrap, and enforces CodeQL prepush checks to satisfy functional requirements and final DoD revalidation.

Automating plan execution without final DoD revalidation risks delivering incomplete stories that pass initial tests but fail acceptance criteria. Without strict quality gates like CodeQL prepush checks and Git bootstrap, the delivery lacks the deterministic and auditable guarantees required for multi-story sprints.