full-sprint

Automate end-to-end sprint cycles with phase-isolated claude -p sessions.

5|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/rbah31/claude-code-workflow --skill full-sprint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: full-sprint
Source: https://github.com/rbah31/claude-code-workflow/tree/main/.claude/skills/full-sprint
Command: npx skills add https://github.com/rbah31/claude-code-workflow --skill full-sprint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to run an end-to-end sprint workflow with phase isolation, ensuring reviews and builds don't leak context between stages.

Core Features & Use Cases

  • Phase-isolated execution using claude -p for each sprint stage (plan, build, review, fix, retrospective).
  • Automatic phase sequencing, input/output artifact management, and per-phase validation.
  • Use Case: You want a reproducible sprint that can be paused, audited, and automatically documented.

Quick Start

Tell Claude to execute a full sprint with the directive file and sprint directive.

Frequently Asked Questions about full-sprint

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

FAQPage Schema
How do I automate an end-to-end agile sprint workflow with phase isolation?

Automate end-to-end agile sprint workflows by running isolated phases for planning, build, review, fix, and retrospective using claude -p sessions. This prevents context leakage between stages while automatically sequencing phases and managing input/output artifacts.

What is the best way to ensure sprint build and review phases don't leak context?

Isolating sprint build and review phases is achieved by executing each stage in a separate claude -p session with guardrails. This ensures reviews and builds do not leak context between stages, enabling a reproducible and auditable sprint process.

Can I automatically generate PR-ready summaries after a sprint retrospective?

Automated PR-ready summaries are generated after completing the sprint retrospective phase. The workflow automatically validates each phase, manages per-phase artifacts, and outputs summaries via claude -p sessions to streamline project management.

How do I set up automated validation for each phase of a sprint cycle?

Automated validation for sprint cycles is configured by applying guardrails to each isolated phase. The orchestration automatically validates inputs and outputs after planning, building, reviewing, fixing, and retrospective stages to ensure phase compliance.

Does sprint orchestration work for projects requiring reproducible and pausable phases?

Sprint orchestration supports projects requiring reproducible and pausable phases by isolating per-phase contexts and managing artifacts. It applies automated validation and guardrails to ensure each sprint stage can be paused, audited, and automatically documented.