Stats
Actions
Tags
How this command is triggered — by the user, by Claude, or both
Slash command
/m42-sprint:add-step <step-prompt>This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Add Step to Sprint SPRINT.yaml ## Preflight Checks 1. Find current sprint directory: !`ls -dt .claude/sprints/*/ 2>/dev/null | head -1 || echo "NO_SPRINT"` 2. From the output above, identify the sprint directory path (e.g., `.claude/sprints/YYYY-MM-DD_name/`) ## Context Using the sprint directory identified in preflight, use the Read tool to read: - `<sprint-dir>/SPRINT.yaml` - to get existing collections.step ## Task Instructions Parse the argument `$ARGUMENTS` as the step prompt text. 1. Find the latest sprint directory from preflight output 2. Read SPRINT.yaml to get current...
Find current sprint directory:
!ls -dt .claude/sprints/*/ 2>/dev/null | head -1 || echo "NO_SPRINT"
From the output above, identify the sprint directory path (e.g., .claude/sprints/YYYY-MM-DD_name/)
Using the sprint directory identified in preflight, use the Read tool to read:
<sprint-dir>/SPRINT.yaml - to get existing collections.stepParse the argument $ARGUMENTS as the step prompt text.
- prompt: |
<step-prompt from $ARGUMENTS>
collections.step: in SPRINT.yamlNote: Adding a step requires recompilation. This happens automatically when running /run-sprint.
Use the Edit tool to:
collections.step:/run-sprintnpx claudepluginhub mission42-ai/m42-claude-plugins --plugin m42-sprint/add-phaseAppends a new phase to the current milestone roadmap using the provided [description], executing the learnship add-phase workflow end-to-end with gates, validations, and checkpoints.