run-ceremony
Skill1 starsChanged 3 months agoMITView on GitHub
Facilitate and produce artifacts for an agile ceremony — sprint planning, daily standup, sprint review, or retrospective. Use to run or prepare a ceremony and capture its outputs (decisions, actions, retro improvements). Dispatches the scrum-master.
In this repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- build-business-caseSkill
- build-roadmapSkill
- capture-feedbackSkill
- close-projectSkill
- coordinate-programSkill
- define-metricsSkill
- define-strategySkill
- design-dashboardSkill
- elicit-requirementsSkill
- groom-backlogSkill
- make-deliverableSkill
- manage-changeSkill
- manage-resourcesSkill
- plan-capacitySkill
- plan-launchSkill
- plan-portfolio-automationSkill
- plan-projectSkill
- plan-sprintSkill
- powerbiSkill
- prioritizeSkill
- review-okrsSkill
- review-portfolio-intakeSkill
- run-discoverySkill
- run-gate-reviewSkill
- setup-pmoSkill
- track-financialsSkill
- track-portfolioSkill
- track-statusSkill
- write-prdSkill
The file
Files
/run-ceremony — Facilitate the cadence
When to use
Running or preparing a standup, sprint planning, sprint review, or retrospective.
Dispatches
scrum-master (lead). For planning, also product-owner; for review, pull status from delivery-monitor.
Inputs
Current sprint plan, knowledge/backlog.md, knowledge/cadence.md, knowledge/raid-log.md.
Steps
- Identify the ceremony and its purpose, then facilitate to that purpose:
- Planning → set one Sprint Goal, select ready items to capacity (or invoke
/plan-sprint). - Standup → inspect progress to the Sprint Goal; capture impediments; re-plan the day.
- Review → inspect the increment vs. the goal; capture stakeholder feedback; adapt the backlog.
- Retrospective → inspect how the team worked; produce a few specific, owned improvement actions
(start from
templates/retro.md).
- Planning → set one Sprint Goal, select ready items to capacity (or invoke
- Keep notes to decisions, actions (owner + due), and open questions — not a transcript.
- Capture impediments and risks in
knowledge/raid-log.mdwith owners. - Make retro output durable. Append lessons with lasting value to
knowledge/lessons-learned.mdand turn improvement actions into backlog items or owned actions — retro output never lives only in the ceremony notes. - Save the ceremony-notes artifact and log consequential decisions.
Methods
knowledge/methods/agile-scrum-mechanics.md, standards/agile-standards.md,
standards/communication-standards.md (ceremony-notes guidance).
Output
A ceremony-notes artifact (e.g., knowledge/ceremonies/<date>-<type>.md); for retros, start from
templates/retro.md and append durable lessons to knowledge/lessons-learned.md; update
knowledge/raid-log.md with impediments; log consequential decisions/improvements to
knowledge/decision-log.md.
Created by Colin Beck<br>
LinkedIn: https://www.linkedin.com/in/beckcolin/<br>
GitHub: https://github.com/link7373
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.

