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
Securityby
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/iteration-plan/SKILL.md- Read the latest file in
iterations/to understand the vision and any existing Q&A. - Identify open questions that block planning (deployment target, auth method, data model, scope cuts). Ask them one at a time and document each answer in the "Q and A" section of the iteration file before asking the next.
- Once all blockers are answered, break the vision into 2–4 independent steps. Each step must:
- Be deployable on its own (no step depends on a later one to work)
- Add exactly one user-visible capability
- Be expressible as a Gherkin scenario
- For each step, create
iterations/Iteration-{N}-plan-{step}.mdwith this structure:
# Iteration N — Step {step}: <title>
## Goal
One sentence.
## Acceptance Criteria
- [ ] ...
## Gherkin Outline
Feature: <name>
Scenario: <happy path>
Given ...
When ...
Then ...
## Out of Scope
What is explicitly NOT included in this step.
## Definition of Done
- npm run check passes
- npm test passes (all new scenarios implemented)
- Deployed and manually verified on Cloud Run- Think MVP at every step: ask "what is the simplest thing that works?" before adding anything.
- Present a one-line summary of each step to the user and ask for approval before writing the plan files.
- Repository
- koenighotze/wheel-of-meeting
- Commit
18189d1
- Last updated
- First committed
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.