refine-plan

# Refine Plan Loop the plan review pipeline over a plan file 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 file 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 File Determine which plan file to refine using these rules in order: 1. **Explicit path** — If an absolute or relative path was passed, use it 2. **Explicit slug** — If a slug was passed (e.g., `add-image-cache`), resolve to `.turbo/plans/<slug>.md` 3. **Single file** — Glob `.turbo/plans/*.md`, excluding shell files (see shell detection below). If exactly one non-shell file exists, use it 4. **Most recent** — If multiple non-shell files exist, use the most recently modified 5. **Legacy fallback** — If `.turbo/plans/` does not exist but `.turbo/plan.md` exists, use it 6. **Nothing found** — If no plan file exists, tell the user to run `/turboplan` (for a new task) or `/pick-next-prompt` (for an existing prompt plan) and stop If multiple files exist and the most-recent choice is non-obvious (e.g., several plans were modified within the same minute), use `AskUserQuestion` to let the user pick from the candidates. ### Shell Detection A file is a **shell** when it contains `## Produces`, `## Consumes`, and `## Covers Spec ...