executing-plans

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

0.75x

Quality

73%

Does it follow best practices?

Impact

21%

0.75x

Average score across 10 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

The canonical home for this skill is executing-plans in obra/superpowers

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.

The content is a well-structured, actionable process skill with explicit validation checkpoints, feedback loops, and stop conditions that satisfy the batch-operation requirements. It is lean overall with only minor recap redundancy in the closing sections.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean bullet points with no over-explanation of known concepts; only minor redundancy (the 'Remember' and 'Integration' sections recapitulate Step 5 and the process rules) keeps it at anchor 4 rather than 5.	4 / 5
Actionability	Concrete defaults and literal phrases are given ('Default: First 3 tasks', TodoWrite usage, 'Say: "Ready for feedback."'), providing mostly executable guidance with minor gaps since actual steps defer to the plan.	4 / 5
Workflow Clarity	Steps 1-5 are clearly sequenced with explicit validation ('Run verifications as specified'), feedback loops ('Apply changes if needed', wait for feedback), and a 'When to Stop and Ask for Help' checklist, matching the anchor 5 example for batch operations.	5 / 5
Progressive Disclosure	Well-organized sections (Overview, Process, When to Stop, When to Revisit, Integration) with clearly signaled one-level cross-skill references; no nested file references, but minor organization gaps from the recap-style sections keep it at anchor 4.	4 / 5
	Total	17 / 20 Passed

Description

65%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 answers both what and when with reasonably natural trigger terms and a distinct niche. Its main weakness is the second-person voice, which lowers specificity per the rubric, and slightly thin action enumeration.

Suggestions

Rewrite in third person (e.g. 'Executes a written implementation plan in a separate session with review checkpoints') to avoid the specificity penalty.

Add a couple more concrete actions (e.g. 'review plans critically, execute tasks in batches, report for review between batches') to lift specificity toward a 4-5.

Broaden trigger terms with synonyms like 'follow a plan' or 'run an implementation plan' to push trigger_term_quality to 5.

Dimension	Reasoning	Score
Specificity	Quotes 'execute a written implementation plan... in a separate session with review checkpoints' name the domain plus 1-2 concrete actions (anchor 3), but the second-person 'Use when you have' triggers the voice penalty, reducing specificity by one to 2.	2 / 5
Completeness	It states both what ('execute a written implementation plan in a separate session with review checkpoints') and when ('Use when you have a written implementation plan to execute'), matching anchor 4 where both are present but the 'when' could be more specific.	4 / 5
Trigger Term Quality	'written implementation plan', 'execute', and 'review checkpoints' are natural phrases a user would say; a few common synonyms (e.g. 'follow'/'run a plan') are missing, matching the good-coverage anchor 4.	4 / 5
Distinctiveness Conflict Risk	'separate session with review checkpoints' carves a clear niche for plan execution with only minor overlap risk against the closely related writing-plans skill, fitting anchor 4 rather than the fully distinct anchor 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: roman01la/skills-agents
Path: skills/executing-plans/SKILL.md
Commit: aa6f9d3

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.