agentleFS
Sign inStart free
yuusakuriyuusakuri/agent-skills/skills/sprint-plan/SKILL.md

sprint-plan

Skill2 starsChanged 22 days agoMITView on GitHub

Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.

35 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use balance-check, team-combat and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CoralGameSkill

    balance-check

    Analyzes game balance data files, formulas, and configuration to identify outliers, broken progressions, degenerate strategies, and economy imbalances. Use after modifying any balance-related data or design.

    Also in 5 projects that use this

  • CoralGameSkill

    team-combat

    Orchestrate the combat team: coordinates game-designer, gameplay-programmer, ai-programmer, technical-artist, sound-designer, and qa-tester to design, implement, and validate a combat feature end-to-end.

    Also in 5 projects that use this

  • +10 more from CoralGame

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 27 edited versions we read keep these.

  • 3

    Distinctive

    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 the user provides files (backlogs, velocity data, team rosters, or previous sprint reports), read them first.

    line 14
  2. Distinctive:

    Verify each story meets the Definition of Ready (clear AC, estimated, no blockers)

    line 26
  3. Distinctive:

    Stop adding stories when capacity is reached

    line 28

“Common” is measured: kept by at least 6 in 10 of the 27 edited versions of this file we could read. “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 Planning

Plan a sprint by estimating team capacity, selecting and sequencing stories, and identifying risks.

Context

You are helping plan a sprint for $ARGUMENTS.

If the user provides files (backlogs, velocity data, team rosters, or previous sprint reports), read them first.

Instructions

  1. Estimate team capacity:
    • Number of team members and their availability (PTO, meetings, on-call)
    • Historical velocity (average story points per sprint from last 3 sprints)
    • Capacity buffer: reserve 15-20% for unexpected work, bugs, and tech debt
    • Calculate available capacity in story points or ideal hours
  2. Review and select stories:
    • Pull from the prioritized backlog (highest priority first)
    • Verify each story meets the Definition of Ready (clear AC, estimated, no blockers)
    • Flag stories that need refinement before committing
    • Stop adding stories when capacity is reached
  3. Map dependencies:
    • Identify stories that depend on other stories or external teams
    • Sequence dependent stories appropriately
    • Flag external dependencies and owners
    • Identify the critical path
  4. Identify risks and mitigations:
    • Stories with high uncertainty or complexity
    • External dependencies that could slip
    • Knowledge concentration (only one person can do it)
    • Suggest mitigations for each risk

  5. Create the sprint plan summary:

    Sprint Goal: [One sentence describing what success looks like]
Duration: [2 weeks / 1 week / etc.]
Team Capacity: [X story points]
Committed Stories: [Y story points across Z stories]
Buffer: [remaining capacity]

Stories:
1. [Story title] — [points] — [owner] — [dependencies]
...

Risks:
- [Risk] → [Mitigation]
  6. Define the sprint goal: A single, clear sentence that captures the sprint's primary value delivery.

Think step by step. Save as markdown.

Further Reading

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