exec_plan

# exec_plan — Execute an Implementation Plan > **CodeOps Skills Version**: 3.19.0 Execute the implementation plan at `plans/$ARGUMENTS/99-execution-plan.md`. The first argument is the feature name; an optional flag selects the commit mode. This skill covers **execution only**. To create a plan, use the make_plan skill. ## Resolve the plan path first (layout-aware) Determine the layout via **[../../_shared/layout-convention.md](../../_shared/layout-convention.md)**: - **Flat layout** (no marker): the plan is at `plans/$ARGUMENTS/99-execution-plan.md` — as flat layout always has. - **Nested layout** (marker present): the plan is under a feature — `codeops/features/<f>/plans/<plan>/99-execution-plan.md`. If the target feature/plan is ambiguous, **ask the user** (never guess). A non-trivial **task** mini-plan lives at the same nested path and executes identically (see "Lightweight tasks" above). Everywhere below that says `plans/$ARGUMENTS/` means this resolved plan path. ## Commit modes | Flag | Behavior | |------|----------| | *(none)* / `--ask-commit` | **Default.** After each verified task, ask the user whether to commit. | | `--no-commit` | Never commit, never ask. Pure implementation. | | `--auto-commit` | Automatically commit + push (via `/gitcmp`) after each verified task. | Full prompt wording, end-of-plan reminders, and commit-message format live in [commit-modes.md](commit-modes.md) — read it before the first commit decision. ## Lightweight tasks (bot...