agile-ceremonies
Agile ceremonies and sprint management specialist. Use when running standups, retrospectives, sprint planning, or tracking sprint progress.
Best use case
agile-ceremonies is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Agile ceremonies and sprint management specialist. Use when running standups, retrospectives, sprint planning, or tracking sprint progress.
Teams using agile-ceremonies should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/agile-ceremonies/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How agile-ceremonies Compares
| Feature / Agent | agile-ceremonies | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Agile ceremonies and sprint management specialist. Use when running standups, retrospectives, sprint planning, or tracking sprint progress.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 format - `references/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
Related Skills
agile-product-owner
Agile product ownership toolkit for Senior Product Owner including INVEST-compliant user story generation, sprint planning, backlog management, and velocity tracking. Use for story writing, sprint planning, stakeholder communication, and agile ceremonies.
agile-planning
Generate agile release plans with sprints and roadmaps using unique sprint codes. Use when creating sprint schedules, product roadmaps, release planning, or when user mentions agile planning, sprints, roadmap, or release plans.
agile-retrospective
When facilitating sprint retrospectives or team improvement sessions.
agile-metrics
Master agile metrics with velocity, burn-down charts, cycle time, and team health indicators for data-driven improvement.
agile-workflow
Orchestrate agile development workflows by invoking commands in sequence with checkpoint-based flow control. This skill should be used when the user asks to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wants guided step-by-step development assistance. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, PR, standup, retrospective.
Agile Scrum
Comprehensive guide to Agile Scrum methodology including roles, ceremonies, artifacts, sprint planning, and best practices for iterative software development
agile-methodology
Apply agile development practices. Use when planning sprints, running ceremonies, or improving team processes. Covers Scrum, Kanban, and agile principles.
agile-coordinator
Orchestrate multiple worker agents to implement groomed tasks. Use when multiple ready tasks need implementation, when you want autonomous multi-task execution, or when coordinating batch development work. Keywords: coordinator, orchestrator, multi-task, parallel, workers, batch, autonomous.
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
technical-architecture
Autonomous Staff Engineer agent that analyzes a product requirement brief, extracts non-functional requirements, and generates a comprehensive technical architecture document. Accepts an optional tech-stack-preferences.md file path. Runs end-to-end without asking questions. Use when turning product requirements into technical architecture decisions.
tdd
Use when implementing features or fixing bugs — write the test first, watch it fail, write minimal code to pass. Ensures tests verify behavior by requiring failure first.
tag-based-search
Code tagging system using @FEAT, @COMP, @TYPE tags for easy discovery and navigation. Use when adding documentation tags or searching for related code across the codebase.