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>
2.5 KiB
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:
- Verify Sprint Approval & Lifecycle State (required) - Check milestone for approval record. STOP if missing unless
--forceflag provided. Also verify lifecycle state isSprint/Planningperskills/sprint-lifecycle.md. SetSprint/Executingafter verification passes. - Detect Checkpoints - Check for resume points from interrupted sessions
- Fetch Sprint Issues - Get open issues from milestone
- Analyze Dependencies - Use
get_execution_orderfor parallel batches - Search Relevant Lessons - Find applicable past experiences
- 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] ║
╚══════════════════════════════════════════════════════════════════╝