writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
62
53%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Critical
Do not install without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/writing-plans/SKILL.mdQuality
Discovery
14%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is critically incomplete - it only provides timing guidance ('when to use') without ever explaining what the skill actually does. The vague language ('multi-step task') provides no differentiation from other planning or pre-coding skills, making it nearly impossible for Claude to correctly select this skill from a pool of alternatives.
Suggestions
Add explicit capability statements describing what the skill does (e.g., 'Breaks down specifications into implementation steps, creates task lists, identifies dependencies').
Include a broader range of trigger terms users might say (e.g., 'planning', 'breakdown', 'implementation plan', 'task decomposition', 'project planning').
Restructure to follow the pattern: '[What it does]. Use when [triggers].' to ensure both components are clearly present.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - it only describes when to use the skill ('have a spec or requirements') but never states what the skill actually does. 'Multi-step task' is extremely vague. | 1 / 3 |
Completeness | The description only addresses 'when' (before touching code, when you have specs) but completely fails to explain 'what' the skill does. There is no indication of the skill's actual capabilities or outputs. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords like 'spec', 'requirements', and 'multi-step task' that users might naturally say, but lacks variations and specific terms (e.g., 'planning', 'breakdown', 'implementation plan', 'architecture'). | 2 / 3 |
Distinctiveness Conflict Risk | 'Multi-step task' and 'before touching code' are extremely generic and could apply to many skills including planning, architecture, design, testing strategy, or project management skills. | 1 / 3 |
Total | 5 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that provides clear, actionable guidance for writing implementation plans. It excels at workflow clarity with its explicit TDD cycle and validation steps, and maintains excellent conciseness by assuming Claude's developer competence. The only minor weakness is that the template sections could be organized into separate reference files for better progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, assuming Claude's competence as a developer. Every section serves a purpose with no unnecessary explanations of basic concepts like what TDD is or how git works. | 3 / 3 |
Actionability | Provides fully executable examples with exact file paths, complete code snippets, specific pytest commands with expected outputs, and copy-paste ready git commit commands. The task structure template is immediately usable. | 3 / 3 |
Workflow Clarity | Clear 5-step sequence for each task with explicit validation checkpoints (run test to verify fail, run test to verify pass). Includes feedback loop pattern and explicit commit steps. The TDD workflow is unambiguous. | 3 / 3 |
Progressive Disclosure | References external skills (superpowers:executing-plans, superpowers:subagent-driven-development, superpowers:dispatching-parallel-agents) appropriately, but the skill itself is somewhat monolithic. The plan document header and task structure could potentially be separate reference files for cleaner organization. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- roman01la/skills-agents
- Commit
45417f2
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.