Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ibrahim-3d/writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
Passed 11 of 19 test cases with the skill, and 3 of 19 without it.
and 14 more in the full report
12 fixed2 passed either way8 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
We just finished drafting the task plan for track tr-88. What checkpoint update needs to be written to the track's metadata file before stopping?
| Checked | Without skill | With skill |
|---|---|---|
| The response specifies updating metadata.json checkpoint status to "PLAN: PASSED". | Missed | Passed |
The instructions your model reads when the skill loads.
Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.
Assume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well.
Announce at start: "I'm using the writing-plans skill to create the implementation plan."
Save plans to: The active conductor track directory: conductor/tracks/{track_id}/plan.md
If no conductor track exists, create one first using the /orchestrator-supaconductor:new-track flow.
Each step is one action (2-5 minutes):
Every plan MUST start with this header:
# [Feature Name] Implementation Plan
> **For Claude:** REQUIRED SUB-SKILL: Use orchestrator-supaconductor:executing-plans to implement this plan task-by-task.
**Goal:** [One sentence describing what this builds]
**Architecture:** [2-3 sentences about approach]
**Tech Stack:** [Key technologies/libraries]
---
test cases passed, vs 3 / 19 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.