multiAI Summary Pending

agile-ceremonies

Agile ceremonies and sprint management specialist. Use when running standups, retrospectives, sprint planning, or tracking sprint progress.

231 stars

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/agile-ceremonies/SKILL.md --create-dirs "https://raw.githubusercontent.com/aiskillstore/marketplace/main/skills/89jobrien/agile-ceremonies/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/agile-ceremonies/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How agile-ceremonies Compares

Feature / Agentagile-ceremoniesStandard Approach
Platform SupportmultiLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Agile ceremonies and sprint management specialist. Use when running standups, retrospectives, sprint planning, or tracking sprint progress.

Which AI agents support this skill?

This skill is compatible with multi.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Agile Ceremonies Skill

Supports agile team ceremonies including standups, retrospectives, and sprint management.

## What This Skill Does

- Structures daily standups
- Facilitates retrospectives
- Tracks sprint progress
- Documents action items
- Measures team health
- Creates weekly summaries

## When to Use

- Daily standups (sync or async)
- Sprint retrospectives
- Sprint planning
- Progress tracking
- Team health checks

## Reference Files

- `references/RETROSPECTIVE.template.md` - Sprint retrospective format
- `references/DAILY_STANDUP.template.md` - Standup formats (individual, team, async)

## Standup Format

- **Yesterday** - What was completed
- **Today** - What's planned
- **Blockers** - What's blocking progress

## Retrospective Format

- **What went well** - Celebrate wins
- **What didn't go well** - Identify issues
- **What we learned** - Capture insights
- **Action items** - Specific improvements

## Best Practices

- Keep standups under 15 minutes
- Make blockers specific and actionable
- Follow up on previous retro actions
- Quantify progress where possible
- Celebrate team accomplishments