agile-ceremonies_skill

This skill helps agile teams run standups, retrospectives, and sprint planning smoothly by organizing formats, tracking progress, and documenting actions.
  • Python

2

GitHub Stars

1

Bundled Files

3 weeks ago

Catalog Refreshed

2 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstart where the catalogue uses aiagentskills.

npx veilstart add skill 89jobrien/steve --skill agile-ceremonies

  • SKILL.md1.4 KB

Overview

This skill helps teams run efficient agile ceremonies and manage sprint progress. It provides structured templates for daily standups, retrospectives, and sprint tracking so meetings stay focused and outcomes are recorded. Use it to capture action items, measure team health, and generate concise weekly summaries. The goal is to reduce meeting overhead and increase follow-through on improvements.

How this skill works

The skill supplies clear formats for standups (yesterday, today, blockers) and retrospectives (what went well, what didn’t, lessons, action items). It tracks sprint progress and team health metrics, collects and documents decisions and assigned follow-ups, and can produce weekly summaries for stakeholders. Facilitators use the templates to run short, actionable ceremonies and to ensure retro actions are tracked across sprints.

When to use it

  • Daily standups, synchronous or asynchronous
  • Sprint retrospectives to surface continuous improvement
  • Sprint planning to align scope and commitments
  • Tracking sprint progress and team health during the sprint
  • Generating weekly summaries for stakeholders and managers

Best practices

  • Keep standups under 15 minutes and focused on outcomes
  • Make blockers specific, owned, and actionable
  • Always record retro action items with owners and deadlines
  • Follow up on previous retrospective actions each sprint
  • Quantify progress where possible and celebrate completed work

Example use cases

  • Run a 10-minute daily standup using the yesterday/today/blockers structure
  • Facilitate a sprint retrospective using the four-part retro format and assign improvement actions
  • Track sprint burndown and health indicators to identify risks early
  • Document action items and owners so retro improvements are visible next sprint
  • Prepare a one-page weekly summary of progress, risks, and completed actions for stakeholders

FAQ

Yes. Standup and retro templates work for both synchronous meetings and asynchronous updates; use the async format to collect inputs ahead of time.

How do I ensure retro action items are completed?

Assign owners and deadlines to each action, review previous retro items at the start of every retro, and include progress in weekly summaries to maintain accountability.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational