writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
71
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillAgent success when using this skill
Validation for skill structure
Discovery
22%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 critically fails to explain what the skill actually does - it only describes when to use it. Without knowing the skill's capabilities (planning? breaking down tasks? generating implementation steps?), Claude cannot make an informed decision about whether to select it. The description needs a complete rewrite to include concrete actions.
Suggestions
Add explicit capability statements describing what the skill does (e.g., 'Breaks down specifications into implementation steps, creates task checklists, identifies dependencies')
Expand trigger terms with natural variations users might say (e.g., 'project planning', 'task breakdown', 'implementation plan', 'PRD', 'feature spec')
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 doesn't specify what the skill actually does. 'Multi-step task' is vague and 'before touching code' only indicates timing, not capabilities. | 1 / 3 |
Completeness | The description only addresses 'when' (before touching code, with specs/requirements) but completely fails to answer 'what does this do'. There's no explanation of the skill's actual functionality. | 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 domain terms that would help with matching. | 2 / 3 |
Distinctiveness Conflict Risk | While 'before touching code' and 'spec or requirements' provide some specificity, 'multi-step task' is generic enough to potentially conflict with many planning or workflow skills. | 2 / 3 |
Total | 6 / 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 strong, actionable skill that provides clear templates and workflows for writing implementation plans. The TDD-focused task structure with explicit validation steps is excellent. Minor improvement needed in providing clearer navigation to referenced sub-skills rather than just naming them.
Suggestions
Add explicit file paths or links for referenced skills (superpowers:executing-plans, superpowers:subagent-driven-development, brainstorming skill) to enable one-click navigation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, using bullet points and code blocks without explaining concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable examples with exact file paths, complete code snippets, specific commands with expected outputs, and copy-paste ready templates for both the plan header and task structure. | 3 / 3 |
Workflow Clarity | Clear 5-step TDD workflow with explicit validation checkpoints (run test to verify fail, run test to verify pass), commit steps, and a structured handoff process with two clear execution paths. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but references to other skills (superpowers:executing-plans, superpowers:subagent-driven-development, brainstorming skill) are mentioned without clear navigation links. The skill is appropriately sized but could better signal where referenced skills live. | 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.
- 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.