sprint-execution

Automate CFN Loop sprint planning, execution, and checkpointing with Redis persistence.

14|2|Updated Sep 23, 2025
One-click install
npx skills add https://github.com/masharratt/claude-flow-novice --skill sprint-execution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-execution
Source: https://github.com/masharratt/claude-flow-novice/tree/main/.claude/skills/cfn-sprint-execution/lib/execution
Command: npx skills add https://github.com/masharratt/claude-flow-novice --skill sprint-execution

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, redis-cli, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Provides a focused wrapper for executing individual sprints within a multi-sprint epic, injecting context and validating deliverables.

Core Features & Use Cases

  • Inject sprint context
  • Validate sprint deliverables
  • Signal outcomes (PROCEED/ITERATE/ABORT)

Quick Start

execute-sprint-task.sh <SPRINT_CONFIG> <TASK_ID> <AGENT_ID> <SPRINT_ID>

Frequently Asked Questions about sprint-execution

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

FAQPage Schema
How do I automate sprint planning and execution with checkpointing?

Sprint execution automates sprint planning, execution, and checkpointing for orchestration workflows. It injects context, validates deliverables, and persists checkpoint state to Redis with TTL, enabling recovery from orchestrator crashes and network faults without losing sprint progress.

Can I resume sprints after an orchestrator crash?

Yes. The Skill tracks wave-level state and container IDs in Redis, allowing you to resume interrupted sprints from the last checkpoint. Resume and cleanup workflows handle orphan containers automatically.

What dependencies do I need to run sprint execution?

You need jq for JSON processing and redis-cli to interact with Redis for checkpoint storage and retrieval. Both are required to persist and recover sprint state across execution cycles.

How do I signal sprint outcomes during execution?

The Skill lets you signal PROCEED, ITERATE, or ABORT outcomes after each sprint. These signals control the flow through multi-sprint epics and determine whether to continue, repeat, or halt the sequence.

What happens to containers when execution fails mid-sprint?

Wave-based state tracking captures container IDs at checkpoint boundaries. Orphan cleanup workflows identify and remove containers from failed waves, preventing resource leaks across resume cycles.

Can sprint execution handle network faults during long workflows?

Yes. Redis-based checkpointing with TTL persists sprint progress incrementally. On network recovery, you resume from the last saved checkpoint rather than restarting the entire epic.