CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

58

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/iteration-plan/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%Scale 1-5

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, actionable skill that clearly guides Claude through creating iteration plans. Its strengths are the concrete output template with Gherkin scenarios and the sequential workflow with an approval checkpoint. Minor weaknesses include the lack of a completed example plan and the absence of error handling guidance (e.g., what to do if no iteration files exist or if the user rejects proposed steps).

Suggestions

Add a brief example of a completed step plan file to make the template fully concrete and copy-paste verifiable.

Add guidance for edge cases: what to do if no iteration files exist in iterations/, or if the user rejects the proposed steps at the approval checkpoint.

DimensionReasoningScore

Conciseness

The content is efficient and assumes Claude's competence. Minor verbosity in step 5 ('Think MVP at every step: ask "what is the simplest thing that works?" before adding anything') which is general advice Claude already knows, but overall well-trimmed.

4 / 5

Actionability

Provides a concrete file template with specific sections (Goal, Acceptance Criteria, Gherkin Outline, Out of Scope, Definition of Done), a clear naming convention for output files, and specific validation commands (npm run check, npm test). Minor gap: no example of a completed plan file showing what a filled-in template looks like.

4 / 5

Workflow Clarity

Clear 6-step sequence with a logical flow: read → ask questions → break into steps → create files → apply MVP thinking → get approval. Has a checkpoint at step 6 (ask for approval before writing). Minor gap: no explicit validation/feedback loop if the user rejects the proposed steps or if the iteration file is missing/malformed.

4 / 5

Progressive Disclosure

For a skill of this size (~30 lines), the structure is appropriate — it's a concise overview that doesn't need external references. The content is well-organized with numbered steps and a clear template block. No bundle files are provided, but none seem necessary for this skill. Minor gap: could benefit from a brief reference to where example iteration files live or what the expected format of the input iteration file is.

4 / 5

Total

16

/

20

Passed

Description

58%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 does a reasonable job of explaining what the skill does with concrete actions (reading iteration files, producing Gherkin outlines and acceptance criteria), and the project-specific naming helps with distinctiveness. However, it lacks an explicit 'Use when...' clause which limits Claude's ability to know when to select it, and the trigger terms could be broader to capture natural user language around planning and iteration work.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'Use when the user asks to plan the next iteration, create step plans, or work on wheel-of-meeting sprint planning.'

Include natural synonyms and related terms users might say, such as 'sprint planning', 'next iteration', 'feature breakdown', or 'story planning'.

DimensionReasoningScore

Specificity

Lists several concrete actions: reads the latest iteration file, asks clarifying questions, produces deployable step plans with Gherkin outlines and acceptance criteria. Minor gaps in coverage (e.g., doesn't mention what 'wheel-of-meeting' is or what formats are involved).

4 / 5

Completeness

Has a clear 'what' (create structured iteration plans with Gherkin outlines and acceptance criteria) but lacks an explicit 'when' clause. There is no 'Use when...' guidance telling Claude when to select this skill over others.

3 / 5

Trigger Term Quality

Includes some relevant keywords like 'iteration plan', 'Gherkin', 'acceptance criteria', and the project name 'wheel-of-meeting', but misses natural user phrases like 'plan next iteration', 'sprint planning', 'feature planning', or 'backlog'. The project name is specific but niche.

3 / 5

Distinctiveness Conflict Risk

The combination of 'wheel-of-meeting' project name, 'iteration plan', and 'Gherkin outlines' makes this fairly distinct. Minor overlap risk with generic planning or Gherkin-related skills, but the project-specific naming reduces conflict significantly.

4 / 5

Total

14

/

20

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
koenighotze/wheel-of-meeting
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.