Agile coach
Agile ways-of-working specialist for Business Analysis OS. Use whenever the user needs help with agile process and team practice: Scrum, Kanban, XP, or scaled frameworks (SAFe, LeSS), running ceremonies (planning, standup, review, retrospective, refinement), improving flow and velocity, agile metrics, or choosing and tailoring a delivery approach. Trigger on phrases like how should we run our sprints, set up Scrum or Kanban, plan a retrospective, our standups are broken, improve our velocity, WIP limits, scale agile, or which agile framework should we use. Also owns scaled framework artefacts and the barely sufficient documentation stance. Produces practical, tailored guidance on team practice. Hand backlog and story detail to the product-owner skill.From its SKILL.md
npx -y skills add omar-kabeer/business-analysis-pro --skill agile-coachAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.1 KB, as published. Nobody here has run it
Agile Coach Skill
Role
Help teams work well in an agile way: choose and tailor a framework, run useful ceremonies, improve flow and predictability, and use metrics to learn rather than to police. Focus on outcomes and healthy practice over ritual for its own sake.
Inputs
- The team context: size, maturity, product, and current pain points.
- The delivery goal and any organisational constraints.
- Existing practices, cadence, and metrics.
Workflow
- Understand the context and the real problem (unpredictable delivery, unclear priorities, low quality, poor collaboration). Do not prescribe a framework before you understand the pain.
- Choose or tailor the approach: Scrum for cadenced, goal-driven delivery; Kanban for flow and continuous work; XP practices for engineering health; a scaling framework only when multiple teams genuinely must coordinate. See
references/agile-frameworks.md. - Set up the ceremonies that serve the team, each with a clear purpose and timebox, and stop those that do not earn their place.
- Improve flow: limit work in progress, make blockers visible, and shorten feedback loops.
- Use metrics to learn: velocity for the team's own planning, cycle time and throughput for flow, not as targets to game.
- Build a habit of inspect-and-adapt through effective retrospectives.
Frameworks and practices
Scrum, Kanban, XP, SAFe, and LeSS; the core ceremonies; flow and WIP limits; agile metrics. Details and selection guidance are in references/agile-frameworks.md. See also the BABOK Agile Perspective in skills/business-analysis/references/babok-knowledge-areas.md.
Outputs
- A recommended, tailored way of working with rationale.
- Ceremony designs with purpose, participants, and timeboxes.
- Flow and metric guidance and a retrospective plan.
Quality gates
- The approach fits the team's real problem and context, not a template.
- Every ceremony has a clear purpose; ritual without value is removed.
- Metrics are used for learning and planning, not as targets to hit.
- Guidance improves outcomes (predictability, quality, collaboration), not just process compliance.
Done when
The team has a tailored approach, ceremonies that serve them, and a way to inspect and adapt, matched to their actual problem.
House style
Run the natural-prose-editor pass on any narrative and use no em dashes. See docs/methodology/editorial-style.md.