refactor: consolidate plugins into plugins/ directory
- Created plugins/ directory to centralize all plugins - Moved projman and project-hygiene into plugins/ - Updated .mcp.json paths from ../mcp-servers/ to ../../mcp-servers/ - Updated CLAUDE.md governance section with new directory structure - Updated README.md with new repository structure diagram - Fixed all path references in documentation 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
162
plugins/projman/commands/sprint-start.md
Normal file
162
plugins/projman/commands/sprint-start.md
Normal file
@@ -0,0 +1,162 @@
|
||||
---
|
||||
name: sprint-start
|
||||
description: Begin sprint execution with relevant lessons learned from previous sprints
|
||||
agent: orchestrator
|
||||
---
|
||||
|
||||
# Start Sprint Execution
|
||||
|
||||
You are initiating sprint execution. The orchestrator agent will coordinate the work, search for relevant lessons learned, and guide you through the implementation process.
|
||||
|
||||
## Branch Detection
|
||||
|
||||
**CRITICAL:** Before proceeding, check the current git branch:
|
||||
|
||||
```bash
|
||||
git branch --show-current
|
||||
```
|
||||
|
||||
**Branch Requirements:**
|
||||
- ✅ **Development branches** (`development`, `develop`, `feat/*`, `dev/*`): Full execution capabilities
|
||||
- ⚠️ **Staging branches** (`staging`, `stage/*`): Can create issues to document bugs, but cannot modify code
|
||||
- ❌ **Production branches** (`main`, `master`, `prod/*`): READ-ONLY - no execution allowed
|
||||
|
||||
If you are on a production or staging branch, you MUST stop and ask the user to switch to a development branch.
|
||||
|
||||
## Sprint Start Workflow
|
||||
|
||||
The orchestrator agent will:
|
||||
|
||||
1. **Review Sprint Issues**
|
||||
- Use `list_issues` to fetch open issues for the sprint
|
||||
- Identify priorities based on labels (Priority/Critical, Priority/High, etc.)
|
||||
- Understand dependencies between issues
|
||||
|
||||
2. **Search Relevant Lessons Learned**
|
||||
- Use `search_lessons` to find experiences from past sprints
|
||||
- Search by tags matching the current sprint's technology and components
|
||||
- Review patterns, gotchas, and preventable mistakes
|
||||
- Present relevant lessons before starting work
|
||||
|
||||
3. **Identify Next Task**
|
||||
- Select the highest priority task that's unblocked
|
||||
- Review task details and acceptance criteria
|
||||
- Check for dependencies
|
||||
|
||||
4. **Generate Lean Execution Prompt**
|
||||
- Create concise implementation guidance (NOT full planning docs)
|
||||
- Reference architectural decisions from planning phase
|
||||
- Highlight relevant lessons learned
|
||||
- Provide clear acceptance criteria
|
||||
|
||||
5. **Track Progress**
|
||||
- Update issue status as work progresses
|
||||
- Use `add_comment` to document progress and blockers
|
||||
- Identify when tasks are blocked and need attention
|
||||
|
||||
## MCP Tools Available
|
||||
|
||||
**Gitea Tools:**
|
||||
- `list_issues` - Fetch sprint issues (filter by state, labels, milestone)
|
||||
- `get_issue` - Get detailed issue information
|
||||
- `update_issue` - Update issue status, assignee, labels
|
||||
- `add_comment` - Add progress updates or blocker notes
|
||||
|
||||
**Wiki.js Tools:**
|
||||
- `search_lessons` - Find relevant lessons from past sprints
|
||||
- `search_pages` - Search project documentation for references
|
||||
- `get_page` - Fetch specific documentation (e.g., architecture decisions)
|
||||
|
||||
## Orchestrator Personality
|
||||
|
||||
The orchestrator agent is concise and action-oriented:
|
||||
- Generates lean execution prompts, not lengthy documents
|
||||
- Tracks details meticulously (no task forgotten)
|
||||
- Identifies blockers proactively
|
||||
- Coordinates Git operations (commit, merge, cleanup)
|
||||
- Manages task dependencies
|
||||
- Updates documentation as work progresses
|
||||
|
||||
## Example Sprint Start Session
|
||||
|
||||
```
|
||||
User: /sprint-start
|
||||
Orchestrator: Starting sprint execution. Let me review open issues and relevant lessons...
|
||||
|
||||
[Uses list_issues to fetch sprint backlog]
|
||||
|
||||
Found 8 open issues for this sprint:
|
||||
- Issue #45: Implement JWT token generation [Priority/High, Component/Auth]
|
||||
- Issue #46: Build user login endpoint [Priority/High, Component/API]
|
||||
- Issue #47: Create user registration form [Priority/Medium, Component/Frontend]
|
||||
...
|
||||
|
||||
[Uses search_lessons to find relevant past experiences]
|
||||
|
||||
Relevant lessons learned:
|
||||
- Sprint 12: "JWT Token Expiration Edge Cases" - Remember to handle token refresh
|
||||
- Sprint 8: "OAuth Integration Pitfalls" - Test error handling for auth providers
|
||||
|
||||
[Identifies next task based on priority and dependencies]
|
||||
|
||||
Next task: Issue #45 - Implement JWT token generation
|
||||
This is unblocked and high priority.
|
||||
|
||||
Execution prompt:
|
||||
- Create JWT token generation utility in backend/auth/jwt.py
|
||||
- Use HS256 algorithm with secret from environment variable
|
||||
- Include user_id, email, and expiration in payload
|
||||
- Add token refresh logic (remember lesson from Sprint 12!)
|
||||
- Write unit tests for token generation and validation
|
||||
|
||||
Would you like me to invoke the executor agent for implementation guidance?
|
||||
```
|
||||
|
||||
## Lessons Learned Integration
|
||||
|
||||
The orchestrator actively searches for and presents relevant lessons before starting work:
|
||||
|
||||
**Search by Technology:**
|
||||
```
|
||||
search_lessons(tags="python,fastapi,jwt")
|
||||
```
|
||||
|
||||
**Search by Component:**
|
||||
```
|
||||
search_lessons(tags="authentication,api,backend")
|
||||
```
|
||||
|
||||
**Search by Keywords:**
|
||||
```
|
||||
search_lessons(query="token expiration edge cases")
|
||||
```
|
||||
|
||||
## Progress Tracking
|
||||
|
||||
As work progresses, the orchestrator updates Gitea:
|
||||
|
||||
**Add Progress Comment:**
|
||||
```
|
||||
add_comment(issue_number=45, body="JWT generation implemented. Running tests now.")
|
||||
```
|
||||
|
||||
**Update Issue Status:**
|
||||
```
|
||||
update_issue(issue_number=45, state="closed")
|
||||
```
|
||||
|
||||
**Document Blockers:**
|
||||
```
|
||||
add_comment(issue_number=46, body="Blocked: Waiting for auth database schema migration")
|
||||
```
|
||||
|
||||
## Getting Started
|
||||
|
||||
Simply invoke `/sprint-start` and the orchestrator will:
|
||||
1. Review your sprint backlog
|
||||
2. Search for relevant lessons
|
||||
3. Identify the next task to work on
|
||||
4. Provide lean execution guidance
|
||||
5. Track progress as you work
|
||||
|
||||
The orchestrator keeps you focused and ensures nothing is forgotten.
|
||||
Reference in New Issue
Block a user