plan
Restate requirements, assess risks, and create step-by-step implementation plan. WAIT for user CONFIRM before touching any code.
56
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
17%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 focuses heavily on internal process behavior (waiting for confirmation) rather than helping Claude select the skill appropriately. It lacks explicit trigger terms and a 'Use when...' clause, making it difficult for Claude to know when to choose this skill from a large skill library. The actions described are somewhat generic planning activities without clear domain specificity.
Suggestions
Add a 'Use when...' clause with natural trigger terms like 'plan a feature', 'think through implementation', 'before making changes', 'design approach', or 'break down this task'
Include specific domains or contexts where this planning skill applies (e.g., 'code refactoring', 'new feature development', 'complex changes')
Replace process instructions ('WAIT for user CONFIRM') with user-facing capability descriptions - behavioral rules belong in the skill body, not the description
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names some actions ('Restate requirements', 'assess risks', 'create step-by-step implementation plan') but they are somewhat generic planning activities rather than concrete, specific capabilities. | 2 / 3 |
Completeness | Describes what it does (planning steps) but has no 'Use when...' clause or equivalent trigger guidance. The 'WAIT for user CONFIRM' is a behavioral instruction, not a usage trigger. | 1 / 3 |
Trigger Term Quality | No natural keywords users would say when needing this skill. Terms like 'requirements', 'risks', 'implementation plan' are internal process terms, not user-facing triggers like 'plan my feature' or 'help me think through this change'. | 1 / 3 |
Distinctiveness Conflict Risk | The planning/requirements focus provides some distinction, but 'assess risks' and 'implementation plan' could overlap with many development, architecture, or project management skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill effectively communicates the planning workflow with a clear confirmation checkpoint, which is its strongest aspect. However, it's somewhat verbose with redundant sections and lacks concrete invocation syntax or executable examples. The example output, while illustrative, is lengthy and could be externalized.
Suggestions
Remove redundant sections - merge 'What This Skill Does' into 'How It Works' or eliminate it entirely
Add concrete invocation syntax showing exactly how to trigger the planner (e.g., command format, required parameters)
Move the lengthy example output to a separate EXAMPLES.md file and reference it
Remove 'When to Use' section - Claude can infer appropriate usage contexts from the skill description
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary sections like 'What This Skill Does' which largely duplicates 'How It Works', and the 'When to Use' section explains scenarios Claude could infer. | 2 / 3 |
Actionability | Provides a good example output and explains the workflow conceptually, but lacks executable code or commands. The skill describes what the planner does rather than providing concrete implementation details or invocation syntax. | 2 / 3 |
Workflow Clarity | Clear sequence with explicit validation checkpoint (WAITING FOR CONFIRMATION). The workflow is well-defined: analyze → break down → identify → assess → present → wait. The modification options provide good feedback loop guidance. | 3 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the example output is quite long and could be in a separate file. References to other commands at the end are helpful but the main content could be more concise with details linked out. | 2 / 3 |
Total | 9 / 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.