executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
50
55%
Does it follow best practices?
Impact
44%
1.69xAverage score across 8 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/executing-plans/SKILL.mdQuality
Discovery
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description focuses entirely on when to use the skill but fails to explain what the skill actually does. It lacks concrete actions, specific outputs, and domain context, making it difficult for Claude to confidently select this skill over others. The trigger terms are moderately useful but too abstract to reliably distinguish this skill in a large skill library.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Executes a multi-step implementation plan by writing code, running tests, and committing changes at each checkpoint.'
Include natural trigger terms users would say, such as 'follow the plan', 'execute steps', 'implement from plan', 'step-by-step execution'.
Specify the domain or type of work this applies to (e.g., coding tasks, infrastructure setup, document generation) to reduce conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions—it doesn't say what the skill actually does (e.g., write code, generate files, refactor). 'Execute' and 'review checkpoints' are vague and abstract. | 1 / 3 |
Completeness | The description provides a 'Use when...' clause addressing when to use the skill, but the 'what does this do' part is essentially missing—there is no explanation of what concrete actions or outputs the skill produces. | 2 / 3 |
Trigger Term Quality | Terms like 'implementation plan', 'separate session', and 'review checkpoints' are somewhat relevant but niche. Users are more likely to say things like 'execute my plan', 'follow the plan', or 'implement step by step', which are partially covered but not explicitly listed. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'implementation plan', 'separate session', and 'review checkpoints' provides some distinctiveness, but without specifying the domain or concrete actions, it could overlap with any skill that involves executing plans or multi-step workflows. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid orchestration/workflow skill that clearly sequences plan execution with good stop conditions and error recovery guidance. Its main weakness is the lack of concrete examples showing what a plan file looks like, how TodoWrite is used, or what verification output looks like. Some content in the 'Remember' section is redundant with earlier sections.
Suggestions
Add a brief concrete example showing what a plan file looks like and how to interact with it (e.g., example TodoWrite call with task items from a plan)
Remove or significantly trim the 'Remember' section since it mostly restates guidance from the process steps and stop conditions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some redundancy - the 'Remember' section largely repeats guidance already stated in the process steps and 'When to Stop' sections. The note about subagents is useful but slightly verbose. | 2 / 3 |
Actionability | Provides a clear process with specific steps but lacks concrete examples - no example plan format, no example TodoWrite usage, no specific commands. It's instructional rather than executable, relying heavily on references to other skills without showing what actual execution looks like. | 2 / 3 |
Workflow Clarity | Clear three-step sequential process with explicit validation checkpoints (run verifications, mark as completed), well-defined stop conditions, and feedback loops (stop when blocked, return to review when plan updates). The 'When to Stop' and 'When to Revisit' sections provide excellent error recovery guidance. | 3 / 3 |
Progressive Disclosure | Well-structured overview with clear references to related skills (using-git-worktrees, writing-plans, finishing-a-development-branch). Content is appropriately scoped - this skill focuses on execution while delegating plan creation and branch finishing to other skills. References are one level deep and clearly signaled. | 3 / 3 |
Total | 10 / 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
- obra/superpowers
- Commit
6efe32c
- 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.