
Agile Ceremonies
- 28 installs
- 4 repo stars
- Updated April 11, 2026
- 89jobrien/steve
agile-ceremonies is a Claude Code skill that structures agile team ceremonies - standups, retrospectives, and sprint planning - and tracks sprint progress.
About
agile-ceremonies is a Claude Code skill that supports agile team ceremonies including standups, retrospectives, and sprint management. It structures daily standups around Yesterday/Today/Blockers, facilitates retrospectives, and tracks sprint progress. A developer uses it to run or document sprint ceremonies and capture action items and team-health notes. It bundles reference templates for retrospectives and standups.
- Structures agile ceremonies: standups, retrospectives, and sprint planning
- Ships retrospective and daily-standup markdown templates
- Tracks sprint progress and documents action items
Agile Ceremonies by the numbers
- 28 all-time installs (skills.sh)
- Ranked #1,889 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Jul 28, 2026 (Skillselion catalog sync)
agile-ceremonies capabilities & compatibility
- Capabilities
- standup facilitation · retrospective facilitation · sprint planning
- Use cases
- project management · planning
- Pricing
- Free
What agile-ceremonies says it does
Supports agile team ceremonies including standups, retrospectives, and sprint management.
npx skills add https://github.com/89jobrien/steve --skill agile-ceremoniesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 28 |
|---|---|
| repo stars | ★ 4 |
| Last updated | April 11, 2026 |
| Repository | 89jobrien/steve ↗ |
What it does
Run and document agile ceremonies (standups, retrospectives, sprint planning) and track sprint progress.
Who is it for?
Facilitating and documenting standups, retrospectives, and sprint planning
Skip if: Writing or reviewing code; it is a team-process facilitator
When should I use this skill?
You are running a standup, retrospective, sprint planning, or tracking sprint progress
What you get
Structured standup and retrospective notes plus tracked sprint progress and action items.
- structured standup notes
- retrospective summary
- sprint progress tracking
By the numbers
- 3-part standup format (Yesterday, Today, Blockers)
- 4-part retrospective format (went well, didn't go well, learned, action items)
Files
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 formatreferences/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
Daily Standup Template
Date: {{DATE}} Sprint: {{SPRINT_NUMBER}} Team: {{TEAM_NAME}}
---
Status Update Format
Individual Update
## {{NAME}}
### Yesterday
- {{COMPLETED_TASK_1}}
- {{COMPLETED_TASK_2}}
### Today
- {{PLANNED_TASK_1}}
- {{PLANNED_TASK_2}}
### Blockers
- {{BLOCKER_1}} (need: {{WHAT_NEEDED}})
- None---
Team Standup Template
# Standup - {{DATE}}
## Team Status
| Member | Yesterday | Today | Blockers |
|--------|-----------|-------|----------|
| {{NAME}} | {{COMPLETED}} | {{PLANNED}} | {{BLOCKER}} |
## Key Updates
### Completed
- [x] {{MAJOR_COMPLETION}}
### In Progress
- [ ] {{ACTIVE_WORK}} ({{PERCENT}}%)
### Blocked
- [ ] {{BLOCKED_ITEM}} - Waiting on: {{DEPENDENCY}}
## Action Items
| Item | Owner | Due |
|------|-------|-----|
| {{ACTION}} | {{OWNER}} | {{DATE}} |
## Notes
{{ADDITIONAL_CONTEXT}}---
Async Standup (Slack/Discord)
**Standup - {{DATE}}**
✅ **Done:**
• {{COMPLETED_1}}
• {{COMPLETED_2}}
🔄 **Today:**
• {{PLANNED_1}}
• {{PLANNED_2}}
🚧 **Blockers:**
• {{BLOCKER}} (need help from @{{PERSON}})---
Sprint Progress Template
# Sprint {{NUMBER}} Progress
**Period:** {{START_DATE}} - {{END_DATE}}
**Day:** {{DAY_NUMBER}} of {{TOTAL_DAYS}}
## Burndown
| Day | Planned | Actual | Remaining |
|-----|---------|--------|-----------|
| {{N}} | {{PTS}} | {{PTS}} | {{PTS}} |
## Story Status
| Story | Points | Status | Owner |
|-------|--------|--------|-------|
| {{STORY_ID}}: {{TITLE}} | {{PTS}} | {{STATUS}} | {{OWNER}} |
### Status Legend
- 🔴 Not Started
- 🟡 In Progress
- 🟢 Complete
- 🔵 In Review
- ⚫ Blocked
## Risks
| Risk | Impact | Mitigation |
|------|--------|------------|
| {{RISK}} | {{HIGH/MED/LOW}} | {{ACTION}} |
## Decisions Needed
- [ ] {{DECISION_1}}
- [ ] {{DECISION_2}}---
Weekly Summary Template
# Week {{NUMBER}} Summary
**Period:** {{START}} - {{END}}
## Accomplishments
### Shipped
- {{FEATURE_1}}
- {{FEATURE_2}}
### Progress
- {{WIP_1}} ({{PERCENT}}%)
## Metrics
| Metric | This Week | Last Week | Trend |
|--------|-----------|-----------|-------|
| Velocity | {{PTS}} | {{PTS}} | {{↑/↓}} |
| Bugs Fixed | {{N}} | {{N}} | {{↑/↓}} |
| PRs Merged | {{N}} | {{N}} | {{↑/↓}} |
## Learnings
- {{LEARNING_1}}
- {{LEARNING_2}}
## Next Week Focus
1. {{PRIORITY_1}}
2. {{PRIORITY_2}}---
Quality Checklist
- [ ] Updates are specific and measurable
- [ ] Blockers include what's needed to unblock
- [ ] Action items have owners and dates
- [ ] Progress is quantified where possible
- [ ] Risks are identified proactively
Sprint Retrospective
Sprint: {{SPRINT_NUMBER}} Date: {{YYYY-MM-DD}} Facilitator: {{NAME}} Attendees: {{NAMES}}
---
Sprint Summary
| Metric | Planned | Actual |
|---|---|---|
| Story Points | {{N}} | {{N}} |
| Stories Completed | {{N}} | {{N}} |
| Bugs Fixed | {{N}} | {{N}} |
| Velocity | {{N}} | {{N}} |
---
What Went Well
{{POSITIVE_1}}
{{DETAILS}}
Impact: {{IMPACT}}
{{POSITIVE_2}}
{{DETAILS}}
{{POSITIVE_3}}
{{DETAILS}}
---
What Didn't Go Well
{{NEGATIVE_1}}
{{DETAILS}}
Root Cause: {{CAUSE}}
{{NEGATIVE_2}}
{{DETAILS}}
Root Cause: {{CAUSE}}
{{NEGATIVE_3}}
{{DETAILS}}
---
What We Learned
1. {{LEARNING_1}} 2. {{LEARNING_2}} 3. {{LEARNING_3}}
---
Action Items
| Action | Owner | Due Date | Status |
|---|---|---|---|
| {{ACTION_1}} | {{OWNER}} | {{DATE}} | {{TODO}} |
| {{ACTION_2}} | {{OWNER}} | {{DATE}} | {{TODO}} |
| {{ACTION_3}} | {{OWNER}} | {{DATE}} | {{TODO}} |
Follow-up from Last Retro
| Action | Owner | Status | Outcome |
|---|---|---|---|
| {{PREV_ACTION}} | {{OWNER}} | {{DONE/IN_PROGRESS}} | {{RESULT}} |
---
Team Health
Mood Check
| Team Member | Energy | Satisfaction |
|---|---|---|
| {{NAME}} | {{1-5}} | {{1-5}} |
Team Average
- Energy: {{AVG}}/5
- Satisfaction: {{AVG}}/5
---
Process Improvements
Start Doing
- {{START_1}}
- {{START_2}}
Stop Doing
- {{STOP_1}}
- {{STOP_2}}
Continue Doing
- {{CONTINUE_1}}
- {{CONTINUE_2}}
---
Kudos & Recognition
- {{PERSON}}: {{RECOGNITION}}
- {{PERSON}}: {{RECOGNITION}}
---
Discussion Notes
{{FREE_FORM_NOTES}}
---
Next Sprint Focus
1. {{FOCUS_1}} 2. {{FOCUS_2}} 3. {{FOCUS_3}}
---
Quality Checklist
- [ ] All team members participated
- [ ] Previous action items reviewed
- [ ] New action items have owners
- [ ] Improvements are specific and actionable
- [ ] Positives celebrated
Related skills
FAQ
What ceremonies does it cover?
Daily standups (sync or async), sprint retrospectives, sprint planning, progress tracking, and team health checks.
What standup format does it use?
Yesterday (what was completed), Today (what's planned), and Blockers (what's blocking progress), with standups kept under 15 minutes.