Writing solid plans
Use when designing or planning a multi-step feature, refactor, or spec before implementation beginsFrom its SKILL.md
npx -y skills add yuchi-chang/no-cape --skill writing-solid-plansAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.8 KB, 382 tokens by cl100k_base, as published. Nobody here has run it
Writing Solid Plans
Write the plan for an engineer (or a fresh agent) with zero context for this codebase. Everything they need must be in the plan itself.
Before designing
- Confirm purpose, constraints, and success criteria. Ask only the questions whose answers would change the design.
- If the request bundles several independent subsystems, decompose into sub-projects first — one spec/plan each.
- Propose 2-3 approaches with trade-offs and a recommendation before committing to one. YAGNI: cut anything the goal doesn't need.
Plan content
- Exact file paths for every create / modify / test.
- Real code in code steps; exact commands with expected output.
- Each task leaves the codebase working and testable; commit per task.
Forbidden placeholders — each one is a plan failure:
- "TBD", "TODO", "fill in later"
- "Add appropriate error handling / validation / edge cases"
- "Write tests for the above" (without the actual test code)
- "Similar to Task N" (repeat the content — tasks may be read out of order)
- References to functions or types that no task defines
If the plan outlives this session
A plan executed across sessions, reviewed by others, or run alongside other in-flight changes must live on disk — [[durable-plans]] holds the file convention and lifecycle (persist, sync, retire).
Self-review before handoff
- Coverage: every spec requirement maps to a task — list any gaps.
- Placeholders: scan for the forbidden patterns above.
- Consistency: names, signatures, and types match across tasks (
clearLayers()in Task 3 butclearFullLayers()in Task 7 is a bug).
Fix findings inline and move on — no re-review loop needed.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.