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 update_plan to track each step, restating any remaining steps of a parent workflow alongside them:

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 request_user_input.

State the resolved path before continuing.

Unless an explicit path or slug was passed, or .turbo/loops/<slug>.md exists with Status: active, 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 request_user_input 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, call update_plan to drop the remaining refine steps, restating any remaining steps of a parent workflow, then continue with the next step of the active workflow.

Loop State

Loop state lives at .turbo/loops/<slug>.md — slug from the resolved plan; for a legacy single-file fallback, use the file's basename. At the start of every invocation, read the ledger if it exists.