scrum-event-sprint-execution

Name: scrum-event-sprint-execution
Availability: InStock
Author: atusy

Orchestrate AI sprint execution with TDD and inspect-and-adapt cycles.

8|Updated Dec 29, 2025

Search Tags:#planning #tdd #ai-agent #scrum #subtasks #sprint #inspect-adapt

Ready to run

npx skills add https://github.com/atusy/agentic-scrum --skill scrum-event-sprint-execution

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scrum-event-sprint-execution
Source: https://github.com/atusy/agentic-scrum/tree/main/claude-plugins/agentic-scrum/skills/scrum-event-sprint-execution
Command: npx skills add https://github.com/atusy/agentic-scrum --skill scrum-event-sprint-execution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Sprint Execution facilitator orchestrates the inspect-and-adapt cycle during active sprints, coordinating subtasks, progress checks, and plan updates to keep the sprint on track.

Core Features & Use Cases

Orchestrates the pending-subtask execution loop using the AI agent team with tdd-based progress and status tracking.
Performs daily-style inspection after each subtask to assess learnings, risks, and alignment with the Sprint Goal.
Supports impediment reporting and plan adaptation, culminating in a holistic review and sprint state transition.

Quick Start

Start the sprint execution cycle to run the next pending subtask and automatically perform inspect-and-adapt after completion.

Frequently Asked Questions about scrum-event-sprint-execution

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I manage AI sprint execution and track subtask progress automatically?▼

AI sprint execution is managed by orchestrating a pending-to-red-to-green-to-refactoring workflow, tracking TDD-based progress, and updating sprint.ts automatically after each subtask completion.

What is the inspect-and-adapt cycle in AI-driven sprint development?▼

The inspect-and-adapt cycle is a daily-style assessment performed after each subtask to evaluate learnings, identify risks, check Sprint Goal alignment, and adapt the sprint plan based on current findings.

How do I report impediments and keep subtasks aligned with the Sprint Goal?▼

Impediments are reported by communicating blockers to team roles during the inspection phase, allowing plan adaptation to ensure subtasks remain aligned with the Sprint Goal.

Can I use TDD workflow status tracking for active sprint subtasks?▼

TDD workflow status tracking is supported through a pending to red to green to refactoring cycle, allowing the AI agent team to continuously execute and monitor active sprint subtasks.

Do I need a scrum-dashboard to maintain sprint state transitions?▼

A scrum-dashboard is required for maintenance, as sprint execution relies on it to manage state transitions and support the holistic review before updating sprint.ts.

Why does sprint execution require continuous plan adaptation during active sprints?▼

Continuous plan adaptation is required because iterative AI-driven development generates new learnings and risks after each subtask, necessitating inspection to keep the sprint on track.