lmiranda
2d51df7a42
Phase 1b: Rename all ~94 commands across 12 plugins to /<noun> <action> sub-command pattern. Git-flow consolidated from 8→5 commands (commit variants absorbed into --push/--merge/--sync flags). Dispatch files, name: frontmatter, and cross-reference updates for all plugins. Phase 2: Design documents for 8 new plugins in docs/designs/. Phase 3: Scaffold 8 new plugins — saas-api-platform, saas-db-migrate, saas-react-platform, saas-test-pilot, data-seed, ops-release-manager, ops-deploy-pipeline, debug-mcp. Each with plugin.json, commands, agents, skills, README, and claude-md-integration. Marketplace grows from 12→20. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2.4 KiB
2.4 KiB
name, description, agent
| name | description | agent |
|---|---|---|
| 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/*.mdfile 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).
- Run pre-planning validations (branch, repo org, labels)
- Detect input source (file, wiki, or conversation)
- Search relevant lessons learned
- Create/update wiki proposal and implementation pages
- Perform architecture analysis
- Create Gitea issues with wiki references (respecting task sizing rules)
- Set up dependencies
- Create or select milestone
- Request explicit sprint approval
Visual Output
╔══════════════════════════════════════════════════════════════════╗
║ 📋 PROJMAN ║
║ 🎯 PLANNING ║
║ [Sprint Name] ║
╚══════════════════════════════════════════════════════════════════╝