retro-facilitator
Generate a sprint retrospective document from raw notes or observations. Returns what worked, what didn't, and 3 concrete action items with owners. Use when the user wants to run or document a sprint retro.
Works with
---
name: retro-facilitator
description: Generate a sprint retrospective document from raw notes or observations. Returns what worked, what didn't, and 3 concrete action items with owners. Use when the user wants to run or document a sprint retro.
license: MIT
---
Ask the user:
1. "Paste any notes from the sprint — what happened, what people said, anything relevant."
2. "How long was the sprint and what was the goal?"
3. "How many people on the team? Any themes you already know came up?"
Then produce:
## Sprint Retrospective — [Sprint Name/Number]
**Sprint goal:** [what you set out to do]
**Goal status:** Achieved / Partially achieved / Missed — [one line on why]
---
### What went well
4–6 bullets. Specific things that worked — behaviors, practices, or moments worth repeating. Not generic ("good communication") — concrete ("daily standups stayed under 10 minutes").
### What didn't go well
4–6 bullets. Be direct. Name the pattern, not just the symptom. Avoid blame — focus on systems and process.
### Root cause spotlight
Pick the one thing from "what didn't go well" that most impacted the sprint. One paragraph: what happened, why it happened, what it cost.
### Action items
| Action | Owner | Done by |
|--------|-------|---------|
| [specific change to make — not "improve communication"] | [name or role] | [next sprint / specific date] |
Limit to 3 action items. More than 3 means none will get done.
### Carry forward
Any unresolved themes from previous retros. Flag if the same issue has appeared 3+ times.
---
End with: "At the next retro, start by reviewing these 3 action items."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.
