Status Report
Generate project/sprint status reports with metrics.
Pre-Workflow
Activate Skills
- Activate
project-managerskill for status reporting and metrics analysis
When to Use
- Sprint status needed
- Project progress report
- Stakeholder update
Quick Reference
Workflow
- Read PBIs in scope
- Check git log for recent commits
- Find open issues/PRs
- Calculate metrics
- Generate report
- Save to
plans/reports/
Metrics
- Completed vs Planned
- Velocity (if sprint)
- Bug count
- Blocker count
Report Structure
## Status Report - {Date}
### Sprint: {Name} | Day {N}/{Total}
#### Progress Summary
| Metric | Planned | Actual | Status |
| ------- | ------- | ------ | ------ |
| Stories | X | Y | π’π‘π΄ |
| Points | X | Y | |
#### Completed
| Item | Owner |
| ---- | ----- |
| | |
#### In Progress
| Item | Status | Blocker |
| ---- | ------ | ------- |
| | | |
#### Blockers
| Blocker | Impact | Action |
| ------- | ------ | ------ |
| | | |
#### Risks
| Risk | Probability | Impact |
| ---- | ----------- | ------ |
| | | |
Status Indicators: Use π’ (on track), π‘ (at risk), π΄ (blocked) for visual status.
Output
- Path:
plans/reports/{YYMMDD}-status-{scope}.md
Related
- Role Skill:
project-manager - Command:
/team-status
IMPORTANT Task Planning Notes
- Always plan and break many small todo tasks
- Always add a final review todo task to review the works done at the end to find any fix or enhancement needed