Files
leo-claude-mktplace/plugins/projman/commands/sprint-plan.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.4 KiB

name, description, agent
name description agent
projman sprint plan Start sprint planning with AI-guided architecture analysis and issue creation planner

Sprint Planning

Skills Required

  • skills/mcp-tools-reference.md (frontmatter — auto-injected)
  • skills/batch-execution.md (frontmatter — auto-injected)
  • skills/branch-security.md
  • skills/repo-validation.md
  • skills/input-detection.md
  • skills/lessons-learned.md
  • skills/wiki-conventions.md
  • skills/task-sizing.md
  • skills/issue-conventions.md
  • skills/sprint-approval.md
  • skills/planning-workflow.md
  • skills/label-taxonomy/labels-reference.md
  • skills/sprint-lifecycle.md

Purpose

Initiate sprint planning session. The planner agent validates prerequisites, gathers requirements, searches lessons learned, creates wiki pages, and creates well-structured Gitea issues with proper dependencies and labels.

Invocation

Provide sprint goals as natural language input, or prepare input via:

  • docs/changes/*.md file with frontmatter
  • Existing wiki proposal page
  • Direct conversation

Workflow

Execute the planning workflow as defined in skills/planning-workflow.md.

Key steps: 0. Check Lifecycle State - Execute skills/sprint-lifecycle.md check protocol. Expect idle state. Set Sprint/Planning after planning completes. Warn and stop if sprint is in another active state (unless --force).

  1. Run pre-planning validations (branch, repo org, labels)
  2. Detect input source (file, wiki, or conversation)
  3. Search relevant lessons learned
  4. Create/update wiki proposal and implementation pages
  5. Perform architecture analysis
  6. Create Gitea issues with wiki references (respecting task sizing rules)
  7. Set up dependencies
  8. Create or select milestone
  9. Request explicit sprint approval

Visual Output

╔══════════════════════════════════════════════════════════════════╗
║  📋 PROJMAN                                                      ║
║  🎯 PLANNING                                                     ║
║  [Sprint Name]                                                   ║
╚══════════════════════════════════════════════════════════════════╝