Files
leo-claude-mktplace/plugins/projman/commands/sprint-start.md
lmiranda bea46d7689 feat(projman): add sprint lifecycle state machine via milestone metadata
- New skill: sprint-lifecycle.md defines states, transitions, and check protocol
- All sprint commands now check and set lifecycle state
- States tracked in milestone description metadata (Sprint/Planning, Sprint/Executing, Sprint/Reviewing)
- Out-of-order calls produce warnings with guidance
- --force override available for all lifecycle checks
- Added Sprint/* labels to label taxonomy documentation

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-02-02 13:48:13 -05:00

2.4 KiB

description, agent
description agent
Begin sprint execution with relevant lessons learned from previous sprints orchestrator

Start Sprint Execution

Skills Required

  • skills/mcp-tools-reference.md
  • skills/branch-security.md
  • skills/sprint-approval.md
  • skills/dependency-management.md
  • skills/lessons-learned.md
  • skills/git-workflow.md
  • skills/progress-tracking.md
  • skills/runaway-detection.md
  • skills/sprint-lifecycle.md

Purpose

Initiate sprint execution. The orchestrator agent verifies approval, analyzes dependencies for parallel execution, searches relevant lessons, and coordinates task dispatch.

Invocation

Run /sprint-start when ready to begin executing a planned sprint.

Flags:

  • --force — Bypass approval gate (emergency only, logged to milestone)

Workflow

Execute the sprint start workflow:

  1. Verify Sprint Approval & Lifecycle State (required) - Check milestone for approval record. STOP if missing unless --force flag provided. Also verify lifecycle state is Sprint/Planning per skills/sprint-lifecycle.md. Set Sprint/Executing after verification passes.
  2. Detect Checkpoints - Check for resume points from interrupted sessions
  3. Fetch Sprint Issues - Get open issues from milestone
  4. Analyze Dependencies - Use get_execution_order for parallel batches
  5. Search Relevant Lessons - Find applicable past experiences
  6. Dispatch Tasks - Parallel when safe, sequential when file conflicts exist

File Conflict Prevention: Before parallel dispatch, check target files for overlap. Sequentialize tasks that modify the same files.

Branch Isolation: Each task runs on its own branch (feat/<issue>-<desc>).

Sequential Merge: After completion, merge branches sequentially to detect conflicts.

Visual Output

╔══════════════════════════════════════════════════════════════════╗
║  📋 PROJMAN                                                      ║
║  ⚡ EXECUTION                                                    ║
║  [Sprint Name]                                                   ║
╚══════════════════════════════════════════════════════════════════╝