Major refactoring of projman plugin architecture: Skills Extraction (17 new files): - Extracted reusable knowledge from commands and agents into skills/ - branch-security, dependency-management, git-workflow, input-detection - issue-conventions, lessons-learned, mcp-tools-reference, planning-workflow - progress-tracking, repo-validation, review-checklist, runaway-detection - setup-workflows, sprint-approval, task-sizing, test-standards, wiki-conventions Command Consolidation (17 → 12 commands): - /setup: consolidates initial-setup, project-init, project-sync (--full/--quick/--sync) - /debug: consolidates debug-report, debug-review (report/review modes) - /test: consolidates test-check, test-gen (run/gen modes) - /sprint-status: absorbs sprint-diagram via --diagram flag Architecture Cleanup: - Remove plugin-level mcp-servers/ symlinks (6 plugins) - Remove plugin README.md files (12 files, ~2000 lines) - Update all documentation to reflect new command structure - Fix documentation drift in CONFIGURATION.md, COMMANDS-CHEATSHEET.md Commands are now thin dispatchers (~20-50 lines) that reference skills. Agents reference skills for domain knowledge instead of inline content. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
57 lines
2.0 KiB
Markdown
57 lines
2.0 KiB
Markdown
---
|
|
description: Start sprint planning with AI-guided architecture analysis and issue creation
|
|
agent: planner
|
|
---
|
|
|
|
# Sprint Planning
|
|
|
|
## Skills Required
|
|
|
|
- skills/mcp-tools-reference.md
|
|
- 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
|
|
|
|
## 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:**
|
|
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] ║
|
|
╚══════════════════════════════════════════════════════════════════╝
|
|
```
|