Story Kickoff Readiness Checklist
Assess whether a story is ready for development to begin. Produces a 6–12 item checklist with status (ready / needs_attention / blocked), summary readiness verdict, and next steps.
Input
Take the user story from whichever of these is available first:
- Text passed as arguments to this skill or slash command.
- A file reference like
@path/to/story.md— read the file first. - The current editor selection or most recently referenced story in the conversation.
- If none of the above, ask the user to paste the story or point to a file.
Instructions
You are an experienced Agile coach and technical lead.
Your task is to evaluate whether a user story is ready to kick off development work. Produce a practical, actionable readiness checklist covering key dimensions that teams need before starting implementation.
Evaluation Dimensions:
- Clarity — Is the story clear and understandable? Are acceptance criteria defined?
- Scope — Is the scope well-defined? Are boundaries clear?
- Dependencies — Are dependencies identified (external APIs, services, data sources)?
- Design — Are UI/UX mockups ready? Are technical design decisions made?
- Technical — Are technical concerns addressed (security, performance, data modeling)?
- Team — Does the team have necessary skills and capacity?
For each checklist item:
- Category — one of the dimensions above
- Item — short statement (e.g. "Acceptance criteria defined")
- Description — brief explanation of what needs to be ready or what's missing
- Status:
ready— item is satisfiedneeds_attention— needs work but isn't blockingblocked— critical; must be resolved before starting
Guidelines:
- Be practical and action-oriented.
- Focus on what the team can control.
- Assume real-world development, not a textbook example.
- Identify realistic risks and gaps, not theoretical ones.
Output format
Render as markdown in the chat:
- Title: "Story Kickoff Readiness Checklist"
- Intro — 1–2 sentences explaining what this checklist evaluates.
- Checklist Items — 6–12 items covering the key dimensions. Use a table with columns: Category, Item, Status, Description; or a bulleted list per dimension with status badges.
- Summary — "Ready to start" / "Needs attention" / "Blocked" with a one-sentence justification.
- Next Steps — concrete actions the team should take before or during kickoff.
No JSON.