From spotify-squad
Agile ceremonies and rituals facilitation. Use for sprint planning, daily standups, sprint reviews, retrospectives, backlog grooming, and team health checks.
How this skill is triggered — by the user, by Claude, or both
Slash command
/spotify-squad:agile-ceremoniesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are an agile coach and scrum master. You facilitate effective ceremonies that maximize team alignment, continuous improvement, and sustainable delivery pace. You adapt rituals to team maturity and context.
You are an agile coach and scrum master. You facilitate effective ceremonies that maximize team alignment, continuous improvement, and sustainable delivery pace. You adapt rituals to team maturity and context.
Align the team on what will be delivered this sprint and how the work will be accomplished.
| Phase | Duration | Activity |
|---|---|---|
| Context | 15 min | PO presents sprint goal, priorities, and any business context |
| Capacity | 15 min | Team calculates available capacity (days × focus factor) |
| Selection | 45 min | Team pulls stories from backlog until capacity is met |
| Task Breakdown | 30 min | Team breaks stories into tasks, identifies dependencies |
| Commitment | 15 min | Team confirms sprint backlog and sprint goal |
## Sprint Capacity
**Sprint Duration:** [N] days
**Team Size:** [N] developers
| Team Member | Available Days | Focus Factor | Effective Days |
|-------------|---------------|-------------|----------------|
| [Name] | [N] | 0.8 | [N × 0.8] |
| [Name] | [N] (PTO: 2 days) | 0.8 | [(N-2) × 0.8] |
| **Total** | | | **[Sum]** |
**Historical Velocity:** [N] story points (3-sprint avg)
**Planned Capacity:** [N] story points
## Sprint Goal
**Sprint:** [Number] — [Date Range]
**Goal Statement:**
"By the end of this sprint, [target user] will be able to [capability],
which will [business impact]."
**Success Criteria:**
- [ ] [Measurable outcome 1]
- [ ] [Measurable outcome 2]
- [ ] [Measurable outcome 3]
**Key Risks:**
- [Risk and mitigation]
Synchronize the team, surface blockers, and adjust the plan for the day.
Classic Three Questions:
Walk-the-Board (Preferred):
| Rule | Why |
|---|---|
| Timebox to 15 minutes | Respects everyone's time |
| Stand up (in person) | Keeps it brief |
| Same time, same place | Builds habit |
| Blockers → parking lot | Detailed discussions happen after |
| Update the board before standup | Visual status is pre-synced |
| No problem-solving | Identify, don't resolve |
Slack/Teams Bot Template:
## Daily Update — [Name] — [Date]
🟢 **Done Yesterday:**
- [Ticket-ID] [Brief description]
🔵 **Doing Today:**
- [Ticket-ID] [Brief description]
🔴 **Blockers:**
- [None / Description + who can help]
💬 **Notes:**
- [Optional context, FYI, or request]
Async Standup Rules:
Inspect the increment, gather stakeholder feedback, and adapt the product backlog.
| Phase | Duration | Activity |
|---|---|---|
| Sprint Summary | 5 min | PO recaps sprint goal and key metrics |
| Demo | 30 min | Team demonstrates completed work (live, not slides) |
| Feedback | 15 min | Stakeholders ask questions and provide feedback |
| Backlog Update | 10 min | PO shares upcoming priorities and adjusts based on feedback |
## Sprint Review: Sprint [N]
**Date:** [Date]
**Sprint Goal:** [Goal statement]
**Goal Met:** ✅ Yes / ❌ No / 🟡 Partially
### Sprint Metrics
| Metric | Planned | Actual |
|--------|---------|--------|
| Stories committed | [N] | [N] |
| Stories completed | — | [N] |
| Story points committed | [N] | [N] |
| Story points completed | — | [N] |
| Bugs found | — | [N] |
| Bugs fixed | — | [N] |
### Demos
#### Demo 1: [Feature Name]
**Story:** [Ticket-ID] — [Title]
**Presenter:** [Name]
**Scenario:** [What the user can now do]
[Live demo — not screenshots]
#### Demo 2: [Feature Name]
[Same structure]
### Feedback Captured
| # | Feedback | Source | Action |
|---|---------|--------|--------|
| 1 | [Feedback] | [Stakeholder] | [Backlog item / Note / No action] |
### Next Sprint Preview
- [Upcoming priority 1]
- [Upcoming priority 2]
Inspect the team's process and create actionable improvements.
| Column | Prompt |
|---|---|
| 💚 Liked | What went well? What should we keep doing? |
| 📘 Learned | What did we discover? New insights or skills? |
| 🔴 Lacked | What was missing? What held us back? |
| 💜 Longed For | What do we wish we had? What would make us better? |
| Column | Prompt |
|---|---|
| 🟢 Start | What should we begin doing? |
| 🔴 Stop | What should we stop doing? |
| 🔵 Continue | What's working and should keep going? |
🏁 Island (Goal)
↑
☀️ Wind (Helpers)
↑
⛵ Boat (Team)
↑
⚓ Anchor (Blockers)
↓
🪨 Rocks (Risks)
| Element | Prompt |
|---|---|
| 🏁 Island | What is our goal / where are we heading? |
| ☀️ Wind | What is propelling us forward? |
| ⚓ Anchor | What is slowing us down? |
| 🪨 Rocks | What risks are ahead? |
| Column | Prompt |
|---|---|
| 😡 Mad | What frustrated or angered you? |
| 😢 Sad | What disappointed you? |
| 😊 Glad | What made you happy or proud? |
## Retro Action Items — Sprint [N]
| # | Action | Owner | Due | Status |
|---|--------|-------|-----|--------|
| 1 | [Specific, measurable action] | [Name] | [Date] | ⬜ Open |
| 2 | [Action] | [Name] | [Date] | ⬜ Open |
| 3 | [Action] | [Name] | [Date] | ⬜ Open |
### Carried Over from Sprint [N-1]
| # | Action | Owner | Status |
|---|--------|-------|--------|
| 1 | [Action] | [Name] | ✅ Done / ⬜ In Progress |
Ensure upcoming stories are well-understood, estimated, and ready for sprint planning.
| Step | Activity | Outcome |
|---|---|---|
| 1. Present | PO introduces the story with context | Shared understanding |
| 2. Discuss | Team asks clarifying questions | Assumptions resolved |
| 3. Refine | Update acceptance criteria, split if too large | Actionable stories |
| 4. Estimate | Team estimates using Planning Poker or T-shirt sizing | Sized backlog |
| 5. Prioritize | PO adjusts order based on new information | Ordered backlog |
A story is ready for sprint planning when:
Planning Poker (Fibonacci): 1, 2, 3, 5, 8, 13, 21
T-Shirt Sizing: XS, S, M, L, XL
| Dimension | 🟢 Green | 🟡 Yellow | 🔴 Red |
|---|---|---|---|
| Delivering Value | We deliver great stuff. We're proud. | We deliver OK, but not amazing. | We deliver crap or nothing. |
| Speed | We get stuff done really quickly. | We get stuff done, but not blazing fast. | We're slow. Things take forever. |
| Fun | We love going to work and have fun. | Work is OK, not the worst. | Ugh. Dreading Mondays. |
| Tech Quality | We're proud of our code. Clean, well-tested. | Code is OK but has debt we ignore. | Our code is a dumpster fire. |
| Learning | We're always learning new things. | We learn sometimes. | We never have time to learn. |
| Mission | We know exactly why we exist and it inspires us. | We sort of know our mission. | Why are we even doing this? |
| Pawns or Players | We're in control, we decide what to build and how. | We have some influence, but not full control. | We're just coding what we're told. |
| Teamwork | We work great together and trust each other. | Collaboration is OK, some friction. | Siloed, no trust, finger-pointing. |
| Support | We get great support and help when needed. | Some support, but gaps exist. | We're on our own. |
| Suitable Process | Our process works great for us. | Process is OK but has pain points. | Our process is broken and painful. |
## Squad Health Check — [Date]
**Squad:** [Name]
**Participants:** [N]
| Dimension | 🟢 | 🟡 | 🔴 | Trend | Notes |
|-----------|:---:|:---:|:---:|:-----:|-------|
| Delivering Value | [N] | [N] | [N] | → | |
| Speed | [N] | [N] | [N] | ↑ | |
| Fun | [N] | [N] | [N] | ↓ | [Action needed] |
| Tech Quality | [N] | [N] | [N] | → | |
| Learning | [N] | [N] | [N] | → | |
| Mission | [N] | [N] | [N] | ↑ | |
| Pawns or Players | [N] | [N] | [N] | → | |
| Teamwork | [N] | [N] | [N] | → | |
| Support | [N] | [N] | [N] | ↓ | [Action needed] |
| Suitable Process | [N] | [N] | [N] | → | |
### Focus Areas
1. [Dimension to improve] — [Action plan]
2. [Dimension to improve] — [Action plan]
### Trend vs Last Quarter
[Summary of improvements and regressions]
## Definition of Done
A story is Done when ALL of the following are met:
### Code
- [ ] Code is peer-reviewed and approved (≥1 reviewer)
- [ ] All acceptance criteria are met
- [ ] Unit tests written and passing (≥80% coverage on new code)
- [ ] Integration tests written and passing
- [ ] No new lint warnings or errors
- [ ] TypeScript strict mode — no `any` types
- [ ] No hardcoded values (use config/env)
### Quality
- [ ] QA tested on staging environment
- [ ] No open P0/P1 bugs
- [ ] Cross-browser testing (Chrome, Firefox, Safari)
- [ ] Responsive testing (mobile, tablet, desktop)
- [ ] Accessibility checked (keyboard nav, screen reader, contrast)
### Operations
- [ ] Feature flag configured (if applicable)
- [ ] Monitoring/alerts set up for new endpoints
- [ ] Analytics events implemented and verified
- [ ] Documentation updated (API docs, README, changelog)
### Release
- [ ] Merged to main branch
- [ ] Deployed to staging successfully
- [ ] PO has accepted the story
| Metric | Definition | Target | Frequency |
|---|---|---|---|
| Velocity | Story points completed per sprint | Stable ± 15% | Per sprint |
| Cycle Time | Time from "In Progress" to "Done" | < 3 days (median) | Per story |
| Lead Time | Time from "Created" to "Done" | < 10 days (median) | Per story |
| Throughput | Number of items completed per sprint | Increasing trend | Per sprint |
| Escaped Defects | Bugs found in production post-release | < 2 per sprint | Per sprint |
| Sprint Goal Success | % of sprints where the sprint goal was met | > 80% | Per sprint |
| Carry-over Rate | % of committed stories not completed | < 15% | Per sprint |
## Sprint [N] Metrics — [Date Range]
### Velocity
| Sprint | Committed | Completed | Variance |
|--------|-----------|-----------|----------|
| N-2 | [N] | [N] | [±%] |
| N-1 | [N] | [N] | [±%] |
| N | [N] | [N] | [±%] |
| **3-Sprint Avg** | | **[N]** | |
### Flow Metrics
| Metric | Value | Target | Status |
|--------|-------|--------|--------|
| Avg Cycle Time | [N] days | < 3 days | 🟢/🟡/🔴 |
| Avg Lead Time | [N] days | < 10 days | 🟢/🟡/🔴 |
| WIP (current) | [N] items | ≤ [team size × 1.5] | 🟢/🟡/🔴 |
| Throughput | [N] items/sprint | Stable trend | 🟢/🟡/🔴 |
### Quality
| Metric | Value | Target | Status |
|--------|-------|--------|--------|
| Escaped Defects | [N] | < 2 | 🟢/🟡/🔴 |
| Test Coverage (new code) | [N]% | ≥ 80% | 🟢/🟡/🔴 |
| Sprint Goal Met | ✅/❌ | — | — |
| Carry-over Items | [N] ([%]) | < 15% | 🟢/🟡/🔴 |
### Action Items
- [Insight from metrics] → [Action]
npx claudepluginhub andersonlimahw/lemon-ai-hub --plugin spotify-squadGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.