sprint-plan SKILL.md skillA
sprint-plan from phuryn/pm-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add phuryn/pm-skills/sprint-plan@git:20260303.a372beePins git:20260303.a372bee in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- phuryn/pm-skills
- Path
pm-execution/skills/sprint-plan/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260303.a372bee, committed Mar 3, 2026
- First version recorded
- Mar 1, 2026
- Size
- 2,365 bytes
- Repository stars
- 28,158
- License
- MIT
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
## 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**: …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_55ks2hizhccc4s5r/54ac27165fd7d57fe3f598f1ef66087d03fbf56d9f583adf7608ccaca9ce3382.json
Then /plugin install sprint-plan@markdownregistry-55ks2hizhccc4s5r in Claude Code. It installs git:20260303.a372bee, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add phuryn/pm-skills/sprint-plan@sha256:54ac27165fd7d57fThe line at the top of this page pins the label git:20260303.a372bee, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_55ks2hizhccc4s5r)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in phuryn/pm-skills/sprint-plan since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of sprint-plan from somewhere else? Ask it: where did my sprint-plan come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 2 versions of this file, between Mar 1, 2026 and Mar 3, 2026, about one every day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260303.a372bee latest | 2026-03-03 | a372bee | 2,365 B | A | view · diff |
| git:20260301.77dbdfa | 2026-03-01 | 77dbdfa | 2,473 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/sprint-plan/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2365 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
phuryn/pm-skills · 28,158 stars · license MIT · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_55ks2hizhccc4s5r GET https://markdownregistry.com/api/v1/resolve?ref=phuryn/pm-skills/sprint-plan GET https://markdownregistry.com/api/v1/blob/54ac27165fd7d57fe3f598f1ef66087d03fbf56d9f583adf7608ccaca9ce3382
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from phuryn/pm-skills
Every file in phuryn/pm-skills