iteration-plan

Create a structured iteration plan for wheel-of-meeting. Reads the latest iteration file, asks clarifying questions, then produces deployable step plans with Gherkin outlines and acceptance criteria.

Quality

82%

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

Quality

Content

93%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.

An exemplary lean, highly actionable instruction skill: concrete file paths, a complete output template with executable verification commands, and a clear sequenced workflow gated by user approval. The only minor gap is the absence of a post-write verification/feedback step, which keeps workflow clarity at 4.

Dimension	Reasoning	Score
Conciseness	The body is ~40 lean lines of pure instruction with zero padding and no explanation of concepts Claude already knows; every token earns its place, matching the lean-and-efficient anchor.	5 / 5
Actionability	Guidance is fully concrete: exact file paths (iterations/Iteration-{N}-plan-{step}.md), a complete plan-file template with all sections, specific commands (npm run check, npm test, Cloud Run deploy verification), and numeric constraints (2–4 steps, one question at a time). For an instruction-only skill this is copy-paste-ready guidance, matching the top anchor.	5 / 5
Workflow Clarity	A clear numbered 1–6 sequence with an explicit user-approval checkpoint ("ask for approval before writing the plan files") and a Definition of Done checklist. It falls short of 5 because there is no verification or feedback step after the plan files are written (e.g., re-checking each file against the step criteria).	4 / 5
Progressive Disclosure	The skill is under 50 lines with no need for external references, and the numbered workflow with an embedded template is well organized; per the simple-skill guideline this scores 5 with well-organized sections alone.	5 / 5
	Total	19 / 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.

A concise, specific description that clearly states what the skill does with concrete actions and a distinct niche, but it omits any 'Use when...' trigger guidance, which both caps completeness and limits its natural trigger-term coverage. Adding an explicit activation clause would lift the two weakest dimensions.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to plan the next iteration or break a vision into deployable steps for wheel-of-meeting."

Include natural phrases users would actually say when invoking this skill, such as "iteration plan", "plan the next iteration", or "break this into steps".

State the target output context more fully (e.g. mention that plans are markdown files in iterations/) to round out action coverage toward the top anchor.

Dimension	Reasoning	Score
Specificity	The description lists several specific actions — "Reads the latest iteration file, asks clarifying questions, then produces deployable step plans with Gherkin outlines and acceptance criteria" — matching the several-specific-actions-with-minor-gaps anchor. It falls short of the score-5 anchor's comprehensive multi-action coverage.	4 / 5
Completeness	The "what" is clear and concrete, but there is no "Use when..." clause or any equivalent trigger guidance; the judging guidelines explicitly cap this at 3 in that case. It does not reach 4 because no 'when' context is present even implicitly.	3 / 5
Trigger Term Quality	Relevant keywords exist ("iteration plan", "Gherkin", "acceptance criteria", "step plans"), but common natural variations a user might say ("planning", "roadmap", "break the vision into steps") are missing, matching the some-keywords-but-missing-variations anchor rather than the good-coverage anchor.	3 / 5
Distinctiveness Conflict Risk	The description is tied to a named project ("for wheel-of-meeting") with distinctive artifacts (Gherkin outlines, iteration files), giving it a clear niche with minimal overlap risk against generic planning skills.	5 / 5
	Total	15 / 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: koenighotze/wheel-of-meeting
Path: .claude/skills/iteration-plan/SKILL.md
Commit: 4aca8e3

Reviewed: 16 hours 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.