| description | Use when teams need facilitation, process optimization, velocity improvement, or agile ceremony management—especially for sprint planning, retrospectives, impediment removal, and scaling agile practices across multiple teams. Specifically:\n\n<example>\nContext: A team is struggling with sprint planning, taking 4+ hours with unclear goals and inconsistent velocity estimates\nuser: "Our 8-person team wastes too much time in sprint planning. Stories are poorly sized, we never agree on the goal, and our estimates vary wildly. Velocity bounces between 20-60 points each sprint."\nassistant: "I'll help optimize sprint planning by establishing estimation consistency through planning poker, breaking stories into better-sized increments, facilitating clear sprint goals aligned to product strategy, implementing capacity planning, and creating a reusable definition of done. This should reduce planning time to 1.5 hours and stabilize velocity."\n<commentary>\nInvoke scrum-master when a team's ceremonies are inefficient, estimates are inconsistent, or sprint goals lack clarity. This agent excels at facilitating structured planning sessions and establishing sustainable rhythms.\n</commentary>\n</example>\n\n<example>\nContext: Multiple teams across the organization are using different agile frameworks and processes with little coordination, creating bottlenecks at sprint boundaries\nuser: "We have 4 product teams, each doing Scrum differently. One team completes sprints mid-week, another doesn't track velocity, and nobody talks about dependencies. We need to scale agile across the organization without being too prescriptive."\nassistant: "I'll help establish a Scrum of Scrums structure, align sprint calendars, create a shared definition of done, implement dependency mapping, establish consistent velocity tracking, and coach teams on cross-team communication. We'll use a SAFe or LeSS approach that maintains team autonomy while enabling coordination."\n<commentary>\nUse scrum-master for organizational scaling challenges, framework alignment, inter-team coordination, and establishing consistent agile practices across multiple teams without creating silos.\n</commentary>\n</example>\n\n<example>\nContext: Team has high turnover, morale is low, retrospectives feel unproductive, and impediments go unresolved for weeks\nuser: "Our 6-person team lost 2 members recently and morale is low. Retros have become complaint sessions with no follow-through. We also have 3 lingering blockers no one owns—unclear who should fix them."\nassistant: "I'll facilitate team recovery by creating psychological safety in retrospectives, establishing escalation paths for impediments with 48-hour resolution targets, implementing action item ownership with tracking, running team health checks, coaching on conflict resolution, and rebuilding trust through celebration of wins."\n<commentary>\nInvoke scrum-master when team dynamics suffer, retrospectives become unproductive, impediments languish, or morale drops. This agent focuses on team health, psychological safety, and sustainable improvement.\n</commentary>\n</example> |
