Autonomous Development with ClaudeSprint
Quick start
claudesprint init --spec <spec_file> # Create sprint from spec
claudesprint run # Run the sprint workflow
claudesprint status # Show current status
Core workflow
ClaudeSprint uses a dual-loop architecture:
Sprint Loop (outer): Manages issues from the sprint backlog
- Selects next available issue
- Tracks completion and progress
- Handles sprint-level concerns (branching, PRs)
Issue Loop (inner): Executes 13 workflow steps per issue
- read-docs → explore → plan → implement → write-tests →
- run-tests → fix-tests → browser-qa → fix-browser →
- stage-changes → commit-changes → verify → complete
Commands - Sprint Lifecycle
claudesprint init --spec <file> # Initialize sprint from spec file
claudesprint init --spec SPEC_01 # Use spec from .claudesprint/specs/
claudesprint run # Run active sprint workflow
claudesprint run --spec SPEC_01 # Run specific sprint
claudesprint run -n 5 # Limit to 5 iterations
claudesprint run --debug-conversations # Log agent I/O for debugging
claudesprint run -v # Verbose output
claudesprint run -vv # Debug output
claudesprint status # Show sprint and issue status
claudesprint status --spec SPEC_01 # Status for specific sprint
claudesprint-tools sprints # List all available sprints
claudesprint validate # Validate sprint.json structure
claudesprint reset # Clear current issue state
Commands - Planning
claudesprint plan # Run planning agent
claudesprint plan --spec SPEC_01 # Plan for specific spec
Commands - Issue Management (agent tools)
These commands are used by agents during workflow execution:
# Get current issue state
claudesprint-tools issue get
# Initialize issue state
claudesprint-tools issue init <issue_id>
claudesprint-tools issue init ISSUE_01 --step implement
claudesprint-tools issue init ISSUE_01 --goal "Add login feature"
# Update issue fields
claudesprint-tools issue update --goal "New goal"
claudesprint-tools issue update --next-action "Write tests"
# Set next workflow step
claudesprint-tools issue step <step_name>
claudesprint-tools issue step implement --goal "Build feature"
claudesprint-tools issue step run-tests --clear-failures
# Record file changes
claudesprint-tools issue change <path> <summary>
claudesprint-tools issue change src/auth.py "Added login endpoint"
# Record failures
claudesprint-tools issue failure <message>
claudesprint-tools issue failure "Tests failed: 2 assertions"
claudesprint-tools issue failure "Timeout" --no-increment
# Clear failures and retry count
claudesprint-tools issue clear-failures
Commands - Sprint Queries (agent tools)
Token-optimized queries for agents:
# List available issues (compact view)
claudesprint-tools sprint available
claudesprint-tools sprint available --spec SPEC_01
# Start working on an issue
claudesprint-tools sprint start <issue_id>
claudesprint-tools sprint start ISSUE_03 --spec SPEC_01
# Get full issue details
claudesprint-tools sprint details <issue_id>
claudesprint-tools sprint details ISSUE_03 --spec SPEC_01
Commands - Configuration
# Global config file
claudesprint config path # Show config file location
claudesprint config init # Create default config
claudesprint config init --force # Overwrite existing
claudesprint config show # Display current settings
claudesprint config edit # Open in $EDITOR
# Model configuration
claudesprint models # Show model per step
Commands - Diagnostics
claudesprint doctor # Check environment and deps
claudesprint doctor -v # Verbose diagnostics
claudesprint doctor --fix # Auto-fix issues
Examples
Full sprint workflow
# 1. Initialize repo (first time only)
claudesprint initrepo
# 2. Create spec file
# Write your spec to .claudesprint/specs/my-feature.md
# 3. Initialize sprint from spec
claudesprint init --spec my-feature.md
# 4. Run the sprint
claudesprint run
# 5. Monitor progress
claudesprint status
Issue step progression
# Agent navigating through workflow steps
claudesprint-tools issue step read-docs --goal "Understand requirements"
claudesprint-tools issue step explore --goal "Map codebase structure"
claudesprint-tools issue step plan --goal "Design implementation"
claudesprint-tools issue step implement --goal "Write the feature"
claudesprint-tools issue step write-tests --goal "Add test coverage"
claudesprint-tools issue step run-tests
claudesprint-tools issue step stage-changes
claudesprint-tools issue step commit-changes
claudesprint-tools issue step complete
Failure recovery
# Record a test failure
claudesprint-tools issue failure "AssertionError in test_login"
# Check current state
claudesprint-tools issue get
# After fixing, clear failures and continue
claudesprint-tools issue clear-failures
claudesprint-tools issue step run-tests
Debugging
# Validate sprint structure
claudesprint validate
# Verbose logging
claudesprint run -v # Verbose
claudesprint run -vv # Debug level
# Log agent conversations
claudesprint run --debug-conversations
# Output written to agent_conversations.log
# Environment check
claudesprint doctor -v
Converted and distributed by TomeVault — claim your Tome and manage your conversions.