Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tobihagemann/implement-plan
Execute an implementation plan file produced by /draft-plan, /turboplan, or /expand-shell. Runs pre-implementation prep, then runs /implement to execute the steps and finalize once they are all done.
Passed 5 of 12 test cases with the skill, and 2 of 12 without it.
and 8 more in the full report
7 fixed3 passed either way13 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
When create_goal succeeds in Step 1 for .turbo/plans/api-v2.md, what file is initialized and what initial status is written to it?
| Checked | Without skill | With skill |
|---|---|---|
| Writes workflow state to .turbo/workflows/api-v2.md. | Missed | Passed |
| Sets Status: active in the workflow file. | Missed | Passed |
The instructions your model reads when the skill loads.
Execute an implementation plan file.
At the start, use update_plan to track each step, restating any remaining steps of a parent workflow alongside them:
$implement skillDetermine which plan file to implement using these rules in order:
add-image-cache), resolve to .turbo/plans/<slug>.md if that file exists.turbo/plans/*.md. If exactly one plan exists, use it.turbo/plans/ does not exist but .turbo/plan.md exists, use it$turboplan and stop. When a slug or path was passed but no file matched it, say which one was triedIf multiple plans exist and the most-recent choice is non-obvious (e.g., several plans were modified within the same minute), use request_user_input to let the user pick from the candidates.
State the resolved plan path before continuing, then read the file.
Unless an explicit path or slug was passed, confirm the resolved plan still describes work that remains to be done:
status: is doneWhen the signal fires, output it as text. Then use request_user_input to offer:
.turbo/plans/, then confirm that plan against this same signalOn Leave it unimplemented, tell the user to bring the plan current with $refine-plan and run this skill again. Call update_plan to drop the remaining implement steps, restating any remaining steps of a parent workflow, then continue with the next step of the active workflow.
test cases passed, vs 2 / 12 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.