agile-delivery
Skill0 starsChanged 6 days agoMITView on GitHub
Methodology-agnostic agile delivery support — iteration/sprint planning, backlog refinement, retrospectives, and increment/PI planning prep. Use when the task mentions sprint, iteration, backlog, refinement/grooming, retro/retrospective, standup, velocity, story points, definition of done/ready, increment or PI planning, Scrum, or Kanban. Complements the PMI pack; does not commit to any single framework (Scrum, Kanban, SAFe).
In this repository6 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- change-controlSkill
- pmi-project-managementSkill
- risk-managementSkill
- stakeholder-managementSkill
- status-reportingSkill
The file
Files
Agile Delivery
A light, framework-agnostic set of agile ceremonies. It works for Scrum, Kanban, or a
hybrid — read the Methodology: field in project-context.md and use the team's own
terms. Treat these as synonyms, not different concepts:
- Iteration = sprint = cycle — a fixed timebox of delivery.
- Backlog refinement = grooming = backlog review — making items ready.
- Retrospective = retro — inspect-and-adapt on how the team worked.
- Increment / PI / quarter planning — looking ahead across several iterations.
Discipline (same as the PMI pack)
- Never invent velocity, estimates, capacity, or dates. Mark gaps
[TBC]and ask. - Everything produced is a draft for human review; the team owns the commitment.
- Facts (from the data pasted in) stay separate from PM judgement (labelled).
The four ceremonies
- Iteration/sprint planning — a goal, capacity, and a proposed (not committed)
selection of backlog items against a definition of done. →
/sprint-planning - Backlog refinement — check items are ready: clear, estimated, small enough,
with acceptance criteria.
→
/backlog-refinement - Retrospective — a fast, action-oriented inspect-and-adapt for one iteration.
Lighter and more frequent than
/lessons-learned(which is project/phase-level, by knowledge area). →/retro - Increment / PI planning prep — objectives, cross-team dependencies, risks, and
capacity for the next several iterations. →
/pi-planning-prep
Reuse, don't duplicate
- Ceremony notes →
/minutes. - Risks surfaced in planning →
/risk-register. - Independent second review of a saved backlog or requirements file →
requirements-analystagent (pass it the file path). - Number files by listing
docs/sprints/and taking the next freeNN; read the previous plan and retro first so the definition of done and open actions carry forward.
For PMI mapping these mostly serve Scope and Schedule in Planning, and Integration in Monitoring & Controlling — but lead with the team's agile language.
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
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.

