executing-plans

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

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/executing-plans/SKILL.md

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A compact, well-structured instruction skill with a clear sequenced workflow, explicit validation/feedback checkpoints, and concrete cross-skill references. Its main weakness is mild redundancy in the closing 'Remember' section and reliance on the external plan file for the detailed step content.

Dimension	Reasoning	Score
Conciseness	The body is lean with terse step lists and a one-line overview; the only padding is the closing 'Remember' section, which restates earlier points (e.g., 'Review plan critically first', 'Follow plan steps exactly'), keeping it efficient with minor trimmable redundancy.	4 / 5
Actionability	Provides concrete, executable guidance for an instruction-only skill — named sub-skills ('superpowers:using-git-worktrees', 'superpowers:finishing-a-development-branch'), explicit todo states ('Mark as in_progress'), and verbatim announce strings — with only the minor gap that it depends on the plan file to supply the bite-sized steps.	4 / 5
Workflow Clarity	A clearly sequenced three-step process with explicit validation checkpoints ('Run verifications as specified', 'After all tasks complete and verified') and feedback loops for error recovery (the 'When to Stop and Ask for Help' and 'When to Revisit Earlier Steps' sections), plus a closing checklist.	5 / 5
Progressive Disclosure	Well-organized into clear sections with one-level-deep, clearly signaled cross-skill references (e.g., '../using-superpowers/references/', 'superpowers:finishing-a-development-branch'); no local bundle files exist to verify, so it lands just short of the cleanly-split score-5 model.	4 / 5
	Total	17 / 20 Passed

Description

62%Weight 40%Scale 1-5

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 cleanly pairs an explicit 'Use when' trigger with a clear 'what', giving it solid completeness and a reasonably distinct niche. It is held back by generic action verbs and process jargon that limit specificity and natural trigger-term coverage.

Suggestions

Expand the 'what' with a couple of concrete actions (e.g., 'load the plan, review it critically, execute each task, run verifications') to lift specificity toward 4-5.

Add natural user-facing trigger phrases (e.g., 'when asked to follow, run, or carry out an implementation plan') alongside the process jargon.

Reinforce distinctiveness by contrasting with adjacent skills (e.g., 'for executing an already-written plan with checkpoints, not for authoring plans').

Dimension	Reasoning	Score
Specificity	Names the domain (implementation plan execution) and two concrete actions ('execute in a separate session', 'review checkpoints'), but the actions are generic and not comprehensive, fitting the '1-2 concrete actions' anchor rather than the 'several specific actions' level.	3 / 5
Completeness	Explicitly answers both what ('execute...a written implementation plan') and when ('Use when you have a written implementation plan to execute in a separate session with review checkpoints'); the when is concrete but lacks the dual-phrase breadth of the score-5 example, so it sits above the midpoint.	4 / 5
Trigger Term Quality	Includes relevant terms ('implementation plan', 'execute', 'review checkpoints', 'separate session') but they lean toward process jargon and miss natural phrasings a user would say like 'follow a plan' or 'run this plan', matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Carves a specific niche (executing a written plan in a separate session with review checkpoints) that is mostly distinct, with only minor overlap risk against general planning/exec skills; not the minimal-conflict level of 5.	4 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: obra/superpowers
Path: skills/executing-plans/SKILL.md
Commit: b36e082

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.