agentleFS
jdinklajdinkla/user-story-skills/skills/story-kickoff/SKILL.md

story-kickoff

Skill0 starsChanged 7 months agoMITView on GitHub

Produce a development-readiness checklist for a user story across Clarity, Scope, Dependencies, Design, Technical, and Team dimensions — marking each item ready/needs-attention/blocked. Use when the user asks "is this story ready to start?", wants a kickoff checklist, or is about to pull a story into a sprint.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If none of the above, ask the user to paste the story or point to a file.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. Text passed as arguments to this skill or slash command.
  2. A file reference like @path/to/story.md — read the file first.
  3. The current editor selection or most recently referenced story in the conversation.
  4. 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:

  1. Clarity — Is the story clear and understandable? Are acceptance criteria defined?
  2. Scope — Is the scope well-defined? Are boundaries clear?
  3. Dependencies — Are dependencies identified (external APIs, services, data sources)?
  4. Design — Are UI/UX mockups ready? Are technical design decisions made?
  5. Technical — Are technical concerns addressed (security, performance, data modeling)?
  6. 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 satisfied
    • needs_attention — needs work but isn't blocking
    • blocked — 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.