writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
73
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/skillValidation for skill structure
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 specifies when to use the skill but never explains what the skill actually does. The vague language ('multi-step task') provides no concrete actions and would likely conflict with many other planning or preparation-related 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 subtasks', 'Generates task checklists')
Replace vague 'multi-step task' with specific domains or task types this skill handles (e.g., 'feature implementation', 'refactoring projects', 'API integrations')
Restructure to follow the pattern: '[What it does]. Use when [specific triggers]' to ensure both components are clearly addressed
| 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 a spec) but completely fails to answer 'what does this do'. There's no explanation of the skill's actual functionality or output. | 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 | 'Multi-step task' and 'spec or requirements' are extremely generic and could apply to dozens of different skills - planning, architecture, testing, documentation, etc. High conflict risk. | 1 / 3 |
Total | 5 / 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 an excellent skill that demonstrates best practices for plan-writing guidance. It's concise yet comprehensive, with concrete templates, exact syntax requirements, and clear TDD workflow. The common mistakes section proactively addresses failure modes, and the execution handoff provides a clean transition to implementation.
| 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. The content is well-organized with clear headers and minimal padding. | 3 / 3 |
Actionability | Provides fully executable guidance with concrete code examples, exact file path conventions, specific command syntax with expected outputs, and complete task structure templates. The markdown examples are copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear multi-step TDD workflow with explicit validation checkpoints (run test to verify fail, run test to verify pass). The task structure template shows exact sequence with expected outcomes at each step. Common mistakes section adds error prevention. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from overview to specifics. References other skills appropriately (kit:team-dev, brainstorming skill) without deep nesting. Content is appropriately scoped for a single SKILL.md file. | 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.
- 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.