retrospective
Sprint retrospective facilitation — what went well, what didn't, action items for next sprint.
Works with
--- name: retrospective description: Sprint retrospective facilitation — what went well, what didn't, action items for next sprint. license: MIT --- # /retrospective — Sprint Retrospective ## Delegate to: producer ## Steps ### 1. Identify Sprint Ask: "Which sprint are we retrospecting?" - Default: most recent sprint in `production/sprints/` ### 2. Load Sprint Data Read: - Sprint plan (original commitments) - Milestone reviews (if this sprint spanned a milestone) - Decision log entries from this sprint's timeframe - Any bug reports filed - Metrics if available (agent log, time tracking) ### 3. Facilitate Reflection Ask the user to reflect on: **What went well?** - Features shipped as planned - Good process moments - Effective collaboration - Technical wins **What didn't go well?** - Tasks that slipped - Unexpected blockers - Process friction - Bugs that escaped to production **What should we try?** - New practices to experiment with - Changes to existing process - Tool improvements - Agent delegation patterns that might help **What should we stop?** - Practices that aren't paying off - Meetings or overhead that's not useful - Tool usage that's hurting flow ### 4. Extract Action Items For each "try" or "stop": - Make it concrete and assignable - Give it a target sprint - Define success criteria ### 5. Generate Retro Document ```markdown # Retrospective: Sprint [N] **Date**: YYYY-MM-DD **Duration**: [start date] to [end date] **Participants**: [user] ## Sprint Summary - Committed: X tasks - Completed: Y tasks - Added mid-sprint: Z tasks - Carried over: W tasks ## What Went Well 🟢 1. [Specific win] 2. [Specific win] ## What Didn't Go Well 🔴 1. [Specific issue] 2. [Specific issue] ## What to Try 🆕 1. [Concrete experiment] 2. [Concrete experiment] ## What to Stop 🛑 1. [Practice to drop] ## Action Items - [ ] [Action item with owner and target sprint] - [ ] [Action item with owner and target sprint] ## Key Learnings - [Insight worth remembering] - [Insight worth remembering] ``` ## Output Present the retro draft. On approval, save to `production/sprints/sprint-<N>-retro.md`. Update `production/decision-log.md` with key learnings.
More Project Management skills
firecrawl-build-onboarding
firecrawl/skills
Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.
email-sequence
coreyhaines31/marketingskills
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.
onboard
pbakaus/impeccable
Designs and improves onboarding flows, empty states, and first-run experiences to help users reach value quickly. Use when the user mentions onboarding, first-time users, empty states, activation, getting started, or new user flows.

