Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mhattingpete/feature-planning
Break down feature requests into detailed, implementable plans with clear tasks.
Passed 11 of 18 test cases with the skill, and 10 of 18 without it.
and 5 more in the full report
6 fixed8 passed either way4 still failing4 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are planning gRPC service additions in `proto/service.proto`. What project context document should be checked for architectural patterns?
| Checked | Without skill | With skill |
|---|---|---|
| References checking architectural patterns in CLAUDE.md. | Missed | Passed |
The instructions your model reads when the skill loads.
Systematically analyze feature requests and create detailed, actionable implementation plans.
Ask clarifying questions:
Explore the codebase:
Use Task tool with subagent_type='Explore' and thoroughness='medium' to understand:
Identify components:
Consider architecture:
test cases passed, vs 10 / 18 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.