agile-coach

Plugin agile-coach from marketplace turtlestack in hpsgd/turtlestack. Commands read from the repo's manifest — 1 month ago.

Skills (13)

• assess-team-topology

  Assess a team against the Team Topologies four team types (stream-aligned, enabling, platform, complicated-subsystem) and three interaction modes (collaboration, X-as-a-service, facilitating). Produces a topology read and recommendations on team type and interactions. Use when a team's purpose is un

• audit-anti-patterns

  Diagnose deep agile dysfunction using Aino Corry's retrospective anti-pattern catalogue, the Zombie Scrum four-symptom check, and Ron Jeffries' Dark Scrum diagnostic. Distinguishes team-fixable problems from organisational ones. Use when ceremonies look fine on the surface but the team isn't really

• audit-ceremonies

  Observe a full sprint cycle and name ceremony anti-patterns with evidence — status-theatre standups, secretary Scrum Master, planning-as-task-assignment, retrospectives without action items. Produces an audit with prioritised coaching actions. Use when a team's ceremonies feel hollow or to diagnose

• audit-scaling-framework

  Help a multi-team setup pick or deliberately reject a scaling framework — where LeSS, Nexus, Scrum@Scale, and SAFe fit and where they don't. Produces a recommendation grounded in the coordination problem, not framework fashion. Use when leadership is considering a scaling framework or a team is bein

• bootstrap

  Bootstrap the agile-coaching documentation structure for a project. Creates docs/coaching/, generates initial working-agreements and retrospective templates, and writes the agile-coach fragment of the coaching domain doc (the coordinator assembles docs/coaching/CLAUDE.md). Idempotent — merges missin

• coach-definition-of-done

  Facilitate the team to author its own Definition of Done — specific, testable, collectively owned, not a management wish list. Runs a specificity test and ties the DoD to the release-manager's gates. Use when a team has no DoD, a vague one, or is presenting half-done work as complete.

• coach-flow-metrics

  Teach the team to read its own flow data — cycle-time scatterplot, throughput, work-item age, and cumulative flow diagram — with Little's Law as the why behind WIP limits. Produces a flow read and coaching plan. Use when a team is drowning in WIP, has unpredictable delivery, or needs to understand i

• coach-kanban-method

  Coach a team on the Kanban Method's six core practices (visualise, limit WIP, manage flow, make policies explicit, feedback loops, evolve experimentally), when Kanban beats Scrum (discovery, ops, irregular arrival), and the Scrumban hybrid. Use when a team's work doesn't fit sprints or to introduce

• design-working-agreements

  Facilitate the team to author its own working agreements — team-generated, specific, and testable — with a review cadence. Distinguishes working agreements from the Definition of Done. Produces a working-agreements artifact. Use when a team has no agreements, has vague ones, or needs to revisit them

• facilitate-retrospective

  Design and facilitate a team retrospective using Derby & Larsen's five phases, with a format catalogue (Start/Stop/Continue, 4Ls, Sailboat, Mad/Sad/Glad, 5 Whys, Lean Coffee) and Liberating Structures. Produces a retro plan and an output file with action items routed to the next sprint backlog. Use

• facilitate-sprint-planning

  Facilitate Sprint Planning across its three topics (why the sprint is valuable, what can be done, how it gets done). The team authors the Sprint Goal; the coach facilitates, never writes it. Names planning anti-patterns. Use when running or coaching a sprint planning session.

• facilitate-sprint-review

  Coach the sprint review as a collaborative working session that inspects the increment and adapts the backlog — not a demo to management. The product manager runs the review; the coach facilitates the working-session craft. Use when a sprint review has become a passive presentation or to coach revie

• team-health-scan

  Run a team-health scan: an Edmondson-style psychological-safety questionnaire, a working-norms review, and a Tuckman-stage assessment on reteaming. Produces a health report distinguishing what to act on from what to surface. Use to establish a safety baseline, after reteaming, or when a team feels o

Subagents (1)

• agile-coach

  Agile coach — Scrum and Kanban coaching, ceremony facilitation, retrospective design, team health, flow management, and working agreements. Ongoing per-team presence serving engineering, product, discovery, and design teams. Use when coaching team process, running retrospectives, diagnosing ceremony

Similar plugins