Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sickn33/writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
Passed 11 of 21 test cases with the skill, and 8 of 21 without it.
and 6 more in the full report
5 fixed2 passed either way14 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
Create a step-by-step TDD plan for adding a Redis caching layer to our Python REST API endpoint for product search. I want to save this plan in our documentation directory under docs/plans/ and then proceed with execution. How should the document header be structured, and what execution handoff options should be presented after saving?
| Checked | Without skill | With skill |
|---|---|---|
| Includes goal, architecture, and tech stack in the plan header section. | Missed | Passed |
| Presents Subagent-Driven and Parallel Session as the two execution choices. | 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 8 / 21 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.