agentleFS
Sign inStart free
link7373link7373/agentic-pmo/.claude/skills/plan-sprint/SKILL.md

plan-sprint

Skill1 starsChanged 3 months agoMITView on GitHub

Plan the next sprint — set a single Sprint Goal, check capacity, and select ready backlog items that fit. Use at the start of a sprint cycle. Dispatches the scrum-master with the product-owner. Supports optional tool sync.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Start from templates/sprint-plan.md.

    line 28
  2. Very specific:

    If a tool is configured in knowledge/integrations.md, offer to create/update the sprint and its items in that tool after recording the plan.

    line 32

“Common” is measured: kept by at least 6 in 10 of the 4 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

/plan-sprint — Commit the next sprint

When to use

At the start of a sprint cycle, or to re-plan a sprint.

Dispatches

scrum-master (facilitation) + product-owner (backlog/priority).

Inputs

knowledge/backlog.md (ordered, ready items), knowledge/cadence.md (sprint length, team), velocity history.

Steps

  1. Set one clear Sprint Goal aligned to the roadmap/current objective.
  2. Estimate capacity for the sprint (team availability, sprint length).
  3. Select top-priority items that meet Definition of Ready and fit capacity (use velocity as a forecast range).
  4. Confirm each selected item has acceptance criteria and no blocking dependencies.
  5. Record the sprint plan: goal, selected items, capacity, commitments.

Methods

knowledge/methods/agile-scrum-mechanics.md, knowledge/methods/requirements-and-stories.md.

Output

Start from templates/sprint-plan.md. Save a sprint plan artifact (e.g., knowledge/sprints/<sprint-id>.md); update item status in knowledge/backlog.md. Follow standards/agile-standards.md and standards/document-standards.md.

Optional sync

If a tool is configured in knowledge/integrations.md, offer to create/update the sprint and its items in that tool after recording the plan. Files remain source of truth; skip if not configured.

Created by Colin Beck<br> LinkedIn: https://www.linkedin.com/in/beckcolin/<br> GitHub: https://github.com/link7373

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