writing-plans
tessl i github:obra/superpowers --skill writing-plansUse when you have a spec or requirements for a multi-step task, before touching code
Review Score
67%
Validation Score
13/16
Implementation Score
92%
Activation Score
15%
Generated
Validation
Total
13/16Score
Passed| Criteria | Score |
|---|---|
metadata_version | 'metadata' field is not a dictionary |
license_field | 'license' field is missing |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow |
Implementation
Suggestions 1
Score
92%Overall Assessment
This is a well-crafted skill that provides highly actionable, concrete guidance for writing implementation plans. The TDD workflow is clearly sequenced with explicit validation steps, and the task structure template is immediately usable. Minor weakness is the references to other skills without clear navigation paths.
Suggestions
- Add explicit file paths or @ syntax links for referenced skills (superpowers:executing-plans, superpowers:subagent-driven-development, brainstorming skill) to improve navigation
| Dimension | Score | Reasoning |
|---|---|---|
Conciseness | 3/3 | 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. |
Actionability | 3/3 | Provides fully executable examples including exact file paths, complete code snippets, specific pytest commands with expected outputs, and git commit commands. The task structure template is copy-paste ready. |
Workflow Clarity | 3/3 | Clear 5-step TDD workflow with explicit validation checkpoints (run test to verify fail, run test to verify pass). The bite-sized task granularity section explicitly defines what constitutes a step, and the execution handoff provides clear decision paths. |
Progressive Disclosure | 2/3 | Good structure 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 self-contained but could better signal where to find referenced skills. |
Activation
Suggestions 3
Score
15%Overall Assessment
This description is critically incomplete - it only specifies when to use the skill but never explains what the skill actually does. The vague language ('multi-step task') provides no concrete capabilities and would conflict with many other skills. Without knowing the skill's purpose, Claude cannot make informed decisions about when to select it.
Suggestions
- Add explicit capability statements describing what the skill does (e.g., 'Creates implementation plans', 'Breaks down requirements into actionable steps', 'Generates task checklists')
- Include more specific trigger terms that users would naturally say (e.g., 'project planning', 'task breakdown', 'implementation roadmap', 'feature planning')
- Clarify the distinct niche by specifying the type of output or methodology (e.g., 'Generates structured implementation plans with dependencies and milestones')
| Dimension | Score | Reasoning |
|---|---|---|
Specificity | 1/3 | 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. |
Completeness | 1/3 | The description only addresses 'when' (before touching code, with a spec) but completely fails to answer 'what does this do'. There's no explanation of the skill's actual functionality. |
Trigger Term Quality | 2/3 | Contains some relevant keywords like 'spec', 'requirements', and 'multi-step task' that users might naturally say, but lacks common variations and specific domain terms. |
Distinctiveness Conflict Risk | 1/3 | Extremely generic - 'multi-step task' and 'spec or requirements' could apply to countless skills. Would likely conflict with any planning, architecture, or code generation skills. |