agentsclimarketplace

Agile ceremonies

Skill sandev/engineering-os/skills/leading-people-and-teams/agile-ceremonies

An operating system for engineering: durable, opinionated playbooks (Agent Skills) for software architecture, AI/agentic systems, product engineering, and technical leadership. Read by humans, loaded by any LLM/agent.

Install
npx -y skills add sandev/engineering-os --skill agile-ceremonies

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Run the recurring team ceremonies (standup, sprint planning, review/demo, retrospective, and backlog refinement) so they create alignment and improvement instead of ritual overhead. Use when facilitating or fixing standups, planning, retros, or demos, or when ceremonies feel like a waste of time.

SKILL.md

3.7 KB, as published. Nobody here has run it

Agile Ceremonies

Ceremonies exist to serve outcomes (alignment, flow, and continuous improvement) not to perform "agile." Each has a specific job; when it stops doing that job it's cargo-cult ritual and should be fixed or cut. Judge every ceremony by one test: does the team leave better off than the time it cost? (General meeting hygiene applies too, see the running-effective-meetings skill.)

Daily standup, synchronize and unblock

  • Purpose: surface blockers and coordinate for the day, not status reporting to a manager.
  • Keep it short (~15 min) and focused on flow: what's blocked, what needs handoff, are we on track for the sprint goal.
  • Talk to the board, not around the room. Walk the work (right-to-left, closest-to-done first), not person-by-person "what I did."
  • Take detailed discussions offline: flag it, then the two people dig in after.

Anti-pattern: a daily ritual where everyone recites yesterday/today to the lead and no blocker ever gets solved.

Sprint planning, commit to a realistic goal

  • Agree a sprint goal (the outcome), then pull in work the team believes it can finish.
  • Stories should be refined, small, and clear before planning, planning is not the time to discover requirements.
  • The team decides how much to take on; capacity is honest (account for leave, on-call, meetings). Overcommitting every sprint destroys trust in the plan (see the estimation-and-planning skill).

Backlog refinement, keep the top ready

  • Ongoing, lightweight grooming so the top of the backlog is understood, sized, and ready before planning.
  • Clarify acceptance criteria; split large items; drop what no longer matters.
  • A refined backlog is what makes planning fast and delivery predictable.

Sprint review / demo, show real, working results

  • Demo working software to stakeholders and gather feedback, reality, not slides.
  • It's a feedback loop on what was built (is this what's needed?), distinct from the retro's focus on how the team works.

Retrospective, improve how the team works

The most valuable ceremony and the first one teams skip. Protect it.

  • Blameless: focus on the system and process, not individuals (same posture as the incident-postmortem skill).
  • Structure: what went well, what didn't, what we'll change.
  • Produce 1–2 concrete, owned improvements and actually do them next sprint. A retro whose actions never happen trains the team that nothing changes.
  • Rotate facilitation and vary the format so it doesn't go stale.

Making ceremonies earn their place

  • Right people, timeboxed, clear purpose, apply general meeting discipline.
  • If a ceremony consistently adds no value, change or drop it; the framework serves the team, not the reverse.
  • More process is not more agility. Prefer the lightest ceremony that delivers the outcome.

Anti-patterns

  • Standup as status theater for the manager instead of unblocking the team.
  • Planning without refined stories, discovering scope mid-sprint.
  • Chronic overcommitment; treating estimates as commitments and commitments as deadlines.
  • Skipping retros when busy, cutting the one ceremony that improves the rest.
  • Retros that surface the same issues every time because no action is taken.
  • Demos of slideware instead of working software.
  • Doing ceremonies because "that's Scrum," with no idea what outcome each serves.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.