agile
Sprint-based agile development with parallel agent execution. Use when the user wants to run an agile sprint, plan sprint work, conduct standups, run retrospectives, manage a backlog, estimate story points, track velocity, or coordinate parallel development across multiple agents acting as Scrum team roles (Scrum Master, Product Owner, Tech Lead, Frontend Dev, Backend Dev, QA Engineer). Also use when the user mentions sprints, user stories, acceptance criteria, definition of done, kanban, or SAFe. Triggers on: 'run a sprint', 'sprint planning', 'standup', 'retrospective', 'backlog grooming', 'agile workflow', 'scrum team'.
Works with
This skill's source license couldn't be confirmed as safe to mirror here, so it isn't inlined. View the full skill directly on its source repository.
View on GitHubMore 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.
