Agent skill
sprint-orchestrator
Manage multi-project sprints with daily planning, progress tracking, and context switching. Use when coordinating work across multiple repositories.
Install this agent skill to your Project
npx add-skill https://github.com/mjohnson518/claude_superpowers/tree/main/skills/sprint-orchestrator
SKILL.md
Sprint Orchestrator
Coordinate development across multiple projects with systematic tracking.
Critical Rule
Never execute git commands. Always output git commands for manual execution.
Daily Workflow
Morning: Generate Tasks
## Today's Focus: Day [X] of [Total]
### Primary Project: [Name]
**Tasks:**
1. [P0] [Task]
2. [P1] [Task]
### Secondary Project: [Name]
**Tasks:**
1. [P1] [Task]
During Work: Log Progress
## Progress: [Project] - [Date]
### Completed
- [x] Task description
### Next Steps
- [ ] Remaining task
### Git Commands to Run
```bash
git add .
git commit -m "feat: description"
### Project Switch: Context Handoff
```markdown
# Handoff: [From] → [To]
## Exiting [From]
- **Summary:** What was done
- **State:** Current status
- **Resume:** Instructions for continuing
## Git Commands Before Switch
```bash
git add .
git commit -m "wip: in progress"
Entering [To]
- Last session: Previous state
- Today's focus: Priority tasks
### End of Day: Summary
```markdown
# Daily Summary: Day [X]
| Project | Tasks Done | Time |
|---------|-----------|------|
| project | task list | Xh |
## Tomorrow
1. Primary: [Project] - [Focus]
2. Secondary: [Project] - [Focus]
Best Practices
- Never switch mid-task—complete or checkpoint first
- Log progress immediately after completing work
- Generate handoff document before every switch
- All git commands output only, never executed
See references/templates.md for full templates.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
production-readiness
Enterprise-grade production readiness assessment system for comprehensive codebase evaluation. Use when (1) Evaluating a GitHub repository for production deployment, (2) Conducting pre-launch security and architecture reviews, (3) Assessing technical debt and system reliability, (4) Identifying gaps, vulnerabilities, and incomplete features, (5) Generating actionable remediation plans for engineering teams, (6) Validating scalability, observability, and operational readiness, (7) Reviewing cost optimization and resource efficiency, (8) Auditing compliance with industry standards (SOC2, GDPR, HIPAA, PCI-DSS), (9) Evaluating API contracts and integration stability, (10) Assessing team knowledge transfer and documentation completeness. Performs CTO-level multi-dimensional analysis exceeding top-tier tech company standards.
api-design
REST, GraphQL, and API design best practices. Use when designing APIs, defining contracts, or reviewing API architecture.
performance-optimization
Performance profiling, optimization techniques, and bottleneck identification. Use when addressing performance issues or optimizing systems.
architecture-patterns
Architectural patterns and design principles for scalable, maintainable systems. Use when designing systems, refactoring architecture, or choosing patterns.
project-analysis
Analyze and understand codebase structure, dependencies, and patterns. Use when onboarding to a new project or auditing existing code.
claude-code-optimizer
Claude Code productivity patterns including EPCC workflow, context management, and extended thinking triggers. Use when starting sessions or managing context.
Didn't find tool you were looking for?