refine-plan

Solid

Iteratively review and revise a planning artifact until no new findings survive evaluation. Supports plans, shells, and specs. Use when the user asks to "refine the plan", "refine the shells", "refine this spec", "iterate on the plan", "iterate on the shells", "tighten the plan", "tighten the shells", "tighten the spec", "improve the plan", "improve the shells", or "improve the spec".

Code & Development 377 stars 29 forks Updated today MIT

Install

View on GitHub

Quality Score: 89/100

Stars 20%
86
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Refine Plan Loop the review pipeline over a planning artifact until no new findings are accepted. Writes back to the artifact file(s) in place. Supports plans, shells, and specs. ## 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 artifact 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 Artifact ### Determine Artifact Type 1. **Explicit argument** — If the user specified a type (e.g., "refine plan", "refine shells", "refine spec"), use it 2. **Conversation context** — Infer from conversation (e.g., if `/draft-plan` just ran, type is plan) 3. **Auto-detect** — Check `.turbo/` for existing artifacts. If multiple types exist, use `AskUserQuestion` ### Resolve the Artifact File(s) #### 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` (for a new task) or `/pick-next-shell` (for existing shells) and stop #### Shells 1. **Explicit spec slug** — Glob `.turbo/shells/<slug>-*.md` 2. **Explicit spec path** — derive slug from filename, glob as above 3. **Single spec** —...

Details

Author
tobihagemann
Repository
tobihagemann/turbo
Created
4 months ago
Last Updated
today
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

iterative-plan-review

Sharpens and stress-tests an existing plan file through multiple codebase-grounded review passes, editing it in place and recording every finding and iteration in cross-referenced companion files. Use this skill whenever the user wants to iterate on, refine, tighten, or improve a plan. Also use it when the user asks to verify, validate, or confirm feasibility of an approach. Does not implement plan steps, write test plans, review code, or investigate bugs, and does not generate new plans from scratch — use plan-a-feature for a new plan.

128 Updated today
testdouble
AI & Automation Listed

taskforge-refine

The universal entry point of the taskforge workflow - assess whether a task is executable and produce its Specification, or route it. Use whenever the user says to refine, spec, scope, groom, or prepare a taskforge task, asks "what's next for TASK-x", or wants to move a new task forward - and whenever a task's readiness is "refine" (including after escalations or invalidation cascades). Four modes - adopt a well-written task nearly verbatim, elaborate an underspecified one, generate blocking clarification prerequisites, or escalate to taskforge-explore for an architectural decision.

0 Updated 3 days ago
hashirventhodi
AI & Automation Solid

ase-task-edit

Iteratively edit and refine a named plan for a task through a conversational loop. Each round, the current plan is shown and the user is asked whether to keep refining, mark the plan as done, or proceed to the implementation or preflight. Use when the user wants to plan a task purely through chat-driven refinement.

42 Updated yesterday
rse