agentleFS
Sign inStart free
ProjectWajaProjectWaja/claude-skillcraft/skills/sprint-flow/SKILL.md

sprint-flow

Skill0 starsChanged 6 months agoMITView on GitHub

Agile execution discipline. Use when breaking down stories, writing acceptance criteria, planning a sprint, or running a retro.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. boyingliu01/xp-gate★ 4same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository13 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    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:

    When the user describes a feature or body of work, break it into user stories:

    line 18
  2. Distinctive:

    No story should depend on another story being complete to be verified (split differently if so)

    line 38
  3. Distinctive:

    If a story is size L, ask: "Can this be split further?"

    line 40
  4. Distinctive:

    When starting a new sprint or work cycle:

    line 44
  5. Distinctive:

    Set capacity: Ask the user how much time they have (or default to 1 week)

    line 47
  6. Distinctive:

    Update this board as stories move through states.

    line 71
  7. Distinctive:

    Keep retros short. The goal is a 5-minute reflection, not a meeting.

    line 82
  8. Distinctive:

    Don't over-process. A solo developer's sprint planning is 10 minutes, not an hour.

    line 86
  9. Distinctive:

    If the user doesn't want sprints, respect that.

    line 89

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Sprint Flow

Agile isn't just for teams. Solo builders who run sprints ship faster than those who don't. This skill brings sprint discipline to AI-assisted development.

Story Breakdown

When the user describes a feature or body of work, break it into user stories:

Story Format

As a [persona],
I want [capability],
So that [benefit].

Acceptance Criteria:
- Given [context], when [action], then [outcome]
- Given [context], when [action], then [outcome]

Estimate: [S/M/L]

Breakdown Rules

  • Each story should be completable in one session (roughly 1-4 hours of work)
  • Stories must be independently testable
  • No story should depend on another story being complete to be verified (split differently if so)
  • Include at least 2 acceptance criteria per story
  • If a story is size L, ask: "Can this be split further?"

Sprint Planning

When starting a new sprint or work cycle:

  1. Review backlog: List all known stories, ordered by priority
  2. Set capacity: Ask the user how much time they have (or default to 1 week)
  3. Select stories: Pick stories that fit the capacity, starting from highest priority
  4. Identify risks: Flag any stories with dependencies, unknowns, or technical risk
  5. Define sprint goal: One sentence describing what "done" looks like for this sprint

Sprint Board

Maintain a simple board in .claude/sprint.md:

# Sprint: [Goal]
**Period:** [start] — [end]

## To Do
- [ ] Story 1: [title] (S)
- [ ] Story 2: [title] (M)

## In Progress
- [ ] Story 3: [title] (M)

## Done
- [x] Story 4: [title] (S)

Update this board as stories move through states.

Retrospective Prompts

At the end of a sprint (or when the user asks for a retro):

  1. What went well? List completed stories and wins.
  2. What didn't go well? Unfinished stories, blockers, surprises.
  3. What did we learn? New patterns, tools, or insights discovered.
  4. What will we change? One concrete adjustment for the next sprint.

Keep retros short. The goal is a 5-minute reflection, not a meeting.

Rules

  • Don't over-process. A solo developer's sprint planning is 10 minutes, not an hour.
  • Estimates are for capacity planning, not accountability. Don't track velocity unless the user asks.
  • The sprint board is a tool, not a deliverable. Update it naturally as part of the workflow.
  • If the user doesn't want sprints, respect that. Offer story breakdown as a standalone service.

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.

Check your setup, free