Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →zzafergok/writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
Passed 11 of 24 test cases with the skill, and 5 of 24 without it.
and 6 more in the full report
7 fixed4 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.
Design an implementation plan for building a password strength validation function. A junior dev wants to combine test writing, coding, and refactoring into single broad task steps. Ensure the steps enforce strict micro-granularity.
| Checked | Without skill | With skill |
|---|---|---|
| Each task breaks execution into a 5-step cycle comprising failing test, run test, implementation, pass test, and commit. | Missed | Passed |
| Step 2 explicitly requires running the test command to verify failure before writing implementation code. | 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."
Context: This should be run in a dedicated worktree (created by brainstorming skill).
Save plans to: docs/plans/YYYY-MM-DD-<feature-name>.md
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 superpowers: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 5 / 24 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.