refine-plan

# Refine Plan Loop the review pipeline over a plan until no new findings are accepted. Writes back to the plan file in place. ## Task Tracking At the start of every invocation (including re-runs from Step 5), use `TaskCreate` to create a task for each step: 1. Resolve the plan 2. Run `/review-plan` skill 3. Run `/evaluate-findings` skill 4. Run `/apply-findings` skill 5. Re-run `/refine-plan` skill if changed ## Step 1: Resolve the Plan 1. **Explicit path** — use it 2. **Explicit slug** — resolve to `.turbo/plans/<slug>.md` 3. **Single file** — Glob `.turbo/plans/*.md`. If exactly one file exists, use it 4. **Most recent** — most recently modified file 5. **Legacy fallback** — `.turbo/plan.md` if `.turbo/plans/` does not exist 6. **Nothing found** — tell the user to run `/turboplan` and stop If multiple candidates exist and the choice is non-obvious, use `AskUserQuestion`. State the resolved path before continuing. Unless an explicit path or slug was passed, confirm the resolved plan still describes work that remains to be done. The signal is a frontmatter `status:` of `done`. When the signal fires, output it as text. Then use `AskUserQuestion` to offer: - **Refine anyway** — the marker is stale - **Pick another plan** — resolve to a different file under `.turbo/plans/`, then confirm that plan against this same signal - **Leave the plan alone** — skip refining On **Leave the plan alone**, mark the remaining refine steps deleted, then use the TaskList tool and proc...