writing-plans
Extends superpowers:writing-plans with devflow's phase-handoff at the end.
48
50%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/writing-plans/SKILL.mdQuality
Discovery
0%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 extremely weak across all dimensions. It relies entirely on references to other internal tools/skills ('superpowers:writing-plans', 'devflow') without explaining what the skill actually does, when it should be used, or what user requests should trigger it. A user or Claude selecting from a list of skills would have no basis for choosing this one.
Suggestions
Replace internal jargon with a plain-language explanation of what the skill does, e.g., 'Creates structured writing plans with phase transitions and handoff documentation'
Add an explicit 'Use when...' clause with natural trigger terms that describe the scenarios where this skill should be selected, e.g., 'Use when the user asks for a writing plan, project phases, or workflow handoffs'
Describe the concrete actions the skill performs (e.g., 'generates writing outlines, defines project phases, produces handoff summaries') so it can be distinguished from other planning or writing skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language ('extends superpowers', 'phase-handoff') without describing any concrete actions. It doesn't explain what the skill actually does in practical terms. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is clearly answered. There is no 'Use when...' clause, and the description only references other skills/tools without explaining the actual functionality. | 1 / 3 |
Trigger Term Quality | Contains no natural keywords a user would say. Terms like 'superpowers:writing-plans', 'devflow', and 'phase-handoff' are internal jargon that users would never naturally use in a request. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it's unclear what domain or niche it occupies. Without understanding what 'writing-plans' or 'phase-handoff' entail, it's impossible to distinguish this from other skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
100%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 extension skill that is concise, actionable, and clearly structured. It efficiently layers additional behavior onto an existing skill with precise trigger points (before/after), concrete commands, and an important safety constraint preventing premature phase advancement. The only minor weakness is the trailing `$ARGUMENTS` placeholder which appears to be a template artifact rather than meaningful content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. It assumes Claude knows the base skill, avoids explaining what writing plans or phase handoffs are, and every line serves a purpose. The only minor note is the explanatory sentence about phase-handoff behavior, but it's necessary to prevent auto-invocation. | 3 / 3 |
Actionability | Provides concrete, executable guidance: specific regex for ticket detection, exact function call with arguments, a copy-paste-ready bash command for terminal title, and precise invocation arguments for phase-handoff. The constraint about NOT auto-invoking the next phase is explicit and clear. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced with a 'Before' and 'After' structure tied to specific events. Steps within each phase are numbered and unambiguous. The explicit prohibition on auto-invoking the next phase serves as a validation checkpoint preventing premature progression. | 3 / 3 |
Progressive Disclosure | For a short extension skill, the structure is appropriate. It references the base skill (`superpowers:writing-plans`) and the handoff skill (`devflow:phase-handoff`) without inlining their content. The two-section structure (Before/After) is clean and navigable. No bundle files are needed for this lightweight overlay. | 3 / 3 |
Total | 12 / 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
- AndreJorgeLopes/devflow
- Commit
b0b1bb6
- 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.