gsd:sprint

Execute autonomous multi-phase sprints with Claude and Codex validation.

1|1|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/LucaDeLeo/ASTN --skill gsd-sprint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd:sprint
Source: https://github.com/LucaDeLeo/ASTN/tree/main/.claude/skills/gsd-sprint
Command: npx skills add https://github.com/LucaDeLeo/ASTN --skill gsd-sprint

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

GSD Sprint automates autonomous, multi-phase sprint execution for AI safety work, coordinating planning, execution, and verification with a self-healing fix loop to reduce manual intervention.

Core Features & Use Cases

  • Orchestrates planning, execution, and verification across multiple phases in a single bash-driven sprint.
  • Integrates Claude and Codex to validate plans and review code, automatically applying fixes up to three iterations when issues are found.
  • Supports interactive and AFK modes, explicit checkpoints for human gating, and resume-from-state capabilities.

Quick Start

Run /gsd:sprint 3 6 to execute phases 3 through 6.

Frequently Asked Questions about gsd:sprint

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

FAQPage Schema
How do I automate sprint planning and code review with Claude and Codex?

Autonomous sprint management automates planning, execution, and verification by coordinating Claude and Codex validation. It applies a self-healing fix loop to review code and automatically apply fixes up to three iterations when issues are found.

What is an autonomous sprint cycle and how does it reduce manual intervention?

An autonomous sprint cycle is a bash-driven process that orchestrates multi-phase execution for AI safety work. It reduces manual intervention by simulating iterative planning and code review, automatically applying fixes up to three iterations during the verification phase.

Do I need a specific directory structure to run autonomous sprint execution?

Yes, autonomous sprint execution requires a properly structured .planning directory containing a ROADMAP.md file and phase directories. You also need active Claude and Codex access to run the validation and self-healing fix loops.

How do I run a specific range of sprint phases in an autonomous workflow?

You can execute specific sprint phases by running the sprint command followed by the phase numbers, such as /gsd:sprint 3 6 to execute phases 3 through 6. The workflow supports interactive and AFK modes with resume-from-state capabilities.

Can I pause autonomous sprint execution for human approval at checkpoints?

Yes, autonomous sprint execution supports explicit checkpoints for human gating during the workflow. You can use interactive mode to pause for human approval, or switch to AFK mode for fully autonomous execution.

What happens when Codex validation fails during the automated sprint?

When Codex validation fails during the sprint, the self-healing fix loop automatically applies fixes to the code. This validation and fix process repeats up to three iterations until the issues are resolved or the maximum retry limit is reached.