executing-plans

当你有一份书面实现计划需要在单独的会话中执行，并设有审查检查点时使用

Quality

75%

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

88%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 body is a tightly structured, highly actionable execution playbook with concrete commands, templates, explicit validation checkpoints, and feedback loops for batch task execution. Progressive disclosure is well-handled through clear sectioning given there are no bundle files.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and assumes Claude's competence; the review-findings, task-rhythm, and completion-report blocks are illustrative templates rather than padding, with only minor instances that could be trimmed.	4 / 5
Actionability	Provides fully executable guidance — concrete commands (`git add`, `git commit -m "feat: ...（任务 2/5）"`, `npm test -- --grep "validation"`) and copy-paste-ready templates (review findings, per-task rhythm, completion report) covering the common cases.	5 / 5
Workflow Clarity	Clear three-step sequence (load/review → execute tasks → finish) with explicit validation checkpoints per task, feedback loops for error recovery (exception-handling section, stop-on-repeated-failure rule), and a checklist; the 'common exception handling' section supplies validate→fix→retry loops for a batch/multi-task operation.	5 / 5
Progressive Disclosure	Well-organized into clearly signaled sections with no nested or buried references; since there are no bundle files to navigate, structure is section-based and appropriately placed, with only minor organization gaps keeping it from a perfect 5.	4 / 5
	Total	18 / 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 states both what the skill does and when to use it with an explicit trigger clause, but it describes a single scenario rather than listing multiple concrete capabilities and lacks keyword synonyms. It is mostly distinct from sibling skills.

Suggestions

Add concrete capabilities the skill performs (e.g., 'loads, critically reviews, executes, and reports on a written plan') to raise specificity from 3 toward 4-5.

Broaden trigger terms with natural synonyms users might say (e.g., 'follow a plan', 'run a plan', 'execute a todo list', 'implementation plan') to improve trigger-term coverage.

Keep the explicit 'Use when...' clause but pair it with a sharper, more specific trigger phrase to push completeness from 4 to 5.

Dimension	Reasoning	Score
Specificity	Names the domain (executing a written implementation plan) with one concrete action ('执行' / execute) plus review checkpoints, but does not enumerate multiple specific concrete actions; matches 'Names domain and 1-2 concrete actions, but not comprehensive'.	3 / 5
Completeness	Explicitly answers both what (execute a written implementation plan in a separate session with review checkpoints) and when ('当你...时使用' is an explicit Use-when clause); the when is fairly specific but trigger phrasing could be more concrete, so it sits at 4 rather than 5.	4 / 5
Trigger Term Quality	Includes relevant trigger phrases like '书面实现计划' (written implementation plan) and '审查检查点' (review checkpoints), but lacks common synonyms or variations users might naturally say; matches 'Some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	The trigger (execute a written plan with review checkpoints in a separate session) carves a distinct niche from generic coding/planning skills, with only minor overlap risk against closely related planning skills.	4 / 5
	Total	14 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: jnMetaCode/superpowers-zh
Path: skills/executing-plans/SKILL.md
Commit: c68725b

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.