CtrlK
BlogDocsLog inGet started
Tessl Logo

executing-plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

51

Quality

55%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/executing-plans/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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 well-structured workflow skill with clear sequencing, good stop conditions, and appropriate references to related skills. Its main weakness is the lack of concrete, executable examples (e.g., what a plan file looks like, how to use TodoWrite) and some redundancy between the 'Remember' summary and the body content. The workflow clarity is strong with explicit validation checkpoints and error recovery paths.

Suggestions

Add a brief concrete example showing what a plan file looks like and how to interact with it (e.g., a sample TodoWrite call or plan snippet)

Remove or significantly trim the 'Remember' section since it mostly restates guidance already covered in the process steps and stop conditions

DimensionReasoningScore

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 context but slightly verbose.

2 / 3

Actionability

Provides a clear process with concrete steps (mark as in_progress, run verifications, use TodoWrite), but lacks executable examples — no sample plan format, no concrete commands, no example of what a TodoWrite call looks like or how to mark tasks. It's instructional but not copy-paste ready.

2 / 3

Workflow Clarity

The multi-step process is clearly sequenced (Load → Execute → Complete) with explicit validation checkpoints (run verifications, raise concerns before starting), clear stop conditions, and feedback loops (stop when blocked, return to Step 1 when plan updates). The 'When to Stop' and 'When to Revisit' sections provide excellent error recovery guidance.

3 / 3

Progressive Disclosure

For a skill of this size and scope, the content is well-organized with clear sections. References to sub-skills (finishing-a-development-branch, using-git-worktrees, writing-plans) are clearly signaled in the Integration section and inline where needed, all one level deep.

3 / 3

Total

10

/

12

Passed

Description

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.

This description only addresses when to use the skill but completely fails to explain what the skill actually does. It lacks concrete actions, specific domain context, and natural trigger terms. The vagueness of 'execute' an 'implementation plan' with 'review checkpoints' provides minimal information for Claude to distinguish this skill from others.

Suggestions

Add a clear 'what' clause listing specific concrete actions the skill performs (e.g., 'Executes multi-step coding plans by implementing changes file-by-file, running tests, and pausing for review at defined checkpoints').

Include natural trigger terms users would say, such as 'execute plan', 'implement step by step', 'phased implementation', 'checkpoint review', or 'follow the plan'.

Specify the domain or type of work this skill handles (e.g., code implementation, document generation, infrastructure setup) to reduce conflict risk with other skills.

DimensionReasoningScore

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

It provides a 'Use when...' clause addressing when to use the skill, but the 'what does this do' part is essentially absent—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 not natural phrases users would typically say. Missing common variations like 'execute plan', 'run plan', 'step-by-step implementation', or 'phased execution'.

2 / 3

Distinctiveness Conflict Risk

The mention of 'implementation plan', 'separate session', and 'review checkpoints' provides some distinctiveness, but the lack of specificity about what domain or actions are involved means it could overlap with many planning or execution-related skills.

2 / 3

Total

7

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
obra/superpowers
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.