lmiranda
2e65b60725
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>
53 lines
2.1 KiB
Markdown
53 lines
2.1 KiB
Markdown
---
|
|
description: Begin sprint execution with relevant lessons learned from previous sprints
|
|
agent: orchestrator
|
|
---
|
|
|
|
# Start Sprint Execution
|
|
|
|
## Skills Required
|
|
|
|
- skills/mcp-tools-reference.md
|
|
- 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
|
|
|
|
## 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.
|
|
|
|
## Workflow
|
|
|
|
Execute the sprint start workflow:
|
|
|
|
1. **Verify Sprint Approval** (recommended) - Check milestone for approval record
|
|
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] ║
|
|
╚══════════════════════════════════════════════════════════════════╝
|
|
```
|