Files
leo-claude-mktplace/plugins/projman/commands/sprint-start.md
lmiranda 035cd00f4b fix(projman): align command names with git-flow pattern
All projman command names now start with 'projman' prefix to match
git-flow behavior and avoid forced plugin namespace in autocomplete.

Before: /projman:sprint-plan, /projman:project-status
After: /projman sprint plan, /projman project status

This matches git-flow which shows /gitflow commit, /gitflow status.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-02-08 22:57:42 -05:00

2.5 KiB

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

Start Sprint Execution

Skills Required

  • skills/mcp-tools-reference.md (frontmatter — auto-injected)
  • skills/batch-execution.md (frontmatter — auto-injected)
  • 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]                                                   ║
╚══════════════════════════════════════════════════════════════════╝