wise-implement-plan-autolisted

# /wise-implement-plan-auto — execute a plan, autonomously ## Why this skill exists `ticket-plan` and `ticket-auto` produce a `PLAN-*.md` but no skill *executes* one. `/wise-implement-plan-auto` is that executor — a phase-gated model: parse the plan's task waves, dispatch one fresh-context executor agent per task in parallel, commit each task atomically, verify as it goes. It is the reusable building block the `ticket-auto` workflow's implement phase follows. ## Arguments Read `$ARGUMENTS`. The first whitespace-separated token, if present, is the path to the `PLAN-*.md` to implement. When absent, look for a single `PLAN-*.md` at the git toplevel and use it; if there are zero or several, stop and ask the user to name one. ## Procedure ### 1. Resolve the worktree + plan ```bash git rev-parse --show-toplevel ``` Use the toplevel as `worktree`. Resolve `plan_path` from `$ARGUMENTS` (or the discovery rule above). ### 2. Follow the shared fragment Read `${CLAUDE_PLUGIN_ROOT}/workflows/ticket-auto/prompts/implement-plan.md` and follow it end to end with `plan_path`, `worktree`, and `project.kind` (infer from the worktree's manifest if unknown). The fragment processes waves in order, dispatches a parallel executor `Task` per task (persona: this skill's `agents/executor.md`), then simplifies (per-task, scoped to the task's files via `references/simplify-pass.md`) and commits each task sequentially, and verifies per task. ### 3. Relay the result The fragment's final line is