npx claudepluginhub mission42-ai/m42-claude-plugins --plugin m42-sprint/helpDisplays Hookify plugin help: hook events, markdown config files with regex patterns, creation via /hookify or manual files, subcommands, and examples for safe behaviors.
/helpExplains Ralph Loop plugin for iterative AI development via repeated Claude prompts with file self-reference, and lists commands /ralph-loop to start loops and /cancel-ralph to cancel.
/helpDisplays a complete table of all available SuperClaude (/sc) commands with their descriptions and functionality.
/helpDisplays full reference guide for Ouroboros commands and agents by rendering the dedicated SKILL.md file.
/helpDisplays the complete GSD command reference, listing all available commands with descriptions, usage examples, quick start guide, and core workflow.
/helpDisplays categorized tsumiki command list, details for named command, or recommends best match for trouble description. Accepts optional command name or query text.
Please explain the following to the user:
The M42 Sprint plugin provides autonomous workflow-based execution for development sprints. It uses a compilation model where SPRINT.yaml defines collections, which are compiled into a hierarchical phase structure in PROGRESS.yaml for execution.
Core concept:
| Command | Description |
|---|---|
/init-sprint <name> | Initialize new sprint directory structure |
/run-sprint <dir> [--max-iterations N] | Compile and start sprint execution loop |
/pause-sprint | Pause gracefully after current phase |
/resume-sprint | Resume a paused sprint |
/stop-sprint | Forcefully stop active loop |
/sprint-status | Show hierarchical progress dashboard |
| Command | Description |
|---|---|
/add-step <prompt> | Add step to SPRINT.yaml collections |
/import-steps issues --label <label> | Bulk import GitHub issues as steps |
/import-steps file <path.yaml> | Import steps from YAML file |
# 1. Create a sprint
/init-sprint auth-feature
# 2. Add steps to SPRINT.yaml
/add-step "Implement user login API endpoint"
/add-step "Add authentication middleware"
# Or import from GitHub issues
/import-steps issues --label sprint-ready
# 3. Run the sprint (compiles and executes)
/run-sprint .claude/sprints/2026-01-15_auth-feature --max-iterations 20
# 4. Check progress
/sprint-status
.claude/sprints/YYYY-MM-DD_sprint-name/
SPRINT.yaml # Configuration with collections
PROGRESS.yaml # Compiled phases hierarchy (generated)
context/ # Cached context files
artifacts/ # Generated outputs
The sprint uses a compilation model:
SPRINT.yaml - Source definition with collections:
collections:
steps:
- prompt: "Implement feature X"
- prompt: "Add tests for feature X"
Compilation - Collections expand into phases:
Execution - Phases run sequentially:
The sprint uses a fresh-context execution model:
/run-sprint compiles SPRINT.yaml to PROGRESS.yamlclaude -p for ONE phase (fresh context)Status Values:
completed - All phases doneblocked - Current phase cannot proceedpaused - Pause was requestedneeds-human - Human decision requiredKey Benefits:
Good for:
Not good for:
--max-iterations as a safety limit/pause-sprint for graceful stops/stop-sprint for immediate stops/sprint-status to monitor hierarchical progress/run-sprint