name: status
version: 1.0.0
description: "[Project Management] Generate status reports for sprints or projects. Use when creating status reports, checking progress, or summarizing sprint metrics. Triggers on keywords like "status report", "sprint status", "progress", "how are we doing", "what's done", "project status"."
allowed-tools: Read, Write, Grep, Glob, Bash, TaskCreate
[IMPORTANT] Use TaskCreate to break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI MUST ask user whether to skip.
Quick Summary
Goal: Generate a project status report covering progress, blockers, and next steps.
Workflow:
- Gather -- Collect data from git, tasks, plans, and recent activity
- Analyze -- Assess progress against goals, identify blockers
- Report -- Write structured status report with metrics
Key Rules:
- Include: completed items, in-progress work, blockers, next steps
- Quantify where possible (files changed, tests passing, coverage)
- Save report to plans/reports/ with standard naming
Be skeptical. Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence percentages (Idea should be more than 80%).
Status Report
Generate project/sprint status reports with metrics.
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
| Metric | Planned | Actual | Status |
| ------ | ------- | ------ | ------ |
#### Completed
| Item | Owner |
#### In Progress
| Item | Status | Blocker |
#### Blockers
| Blocker | Impact | Action |
#### Risks
| Risk | Probability | Impact |
Output
- Path:
plans/reports/{YYMMDD}-status-{scope}.md
Related
- Role Skill:
project-manager
- Command:
/status
IMPORTANT Task Planning Notes (MUST FOLLOW)
- Always plan and break work into many small todo tasks
- Always add a final review todo task to verify work quality and identify fixes/enhancements
Workflow Recommendation
IMPORTANT MUST: If you are NOT already in a workflow, use AskUserQuestion to ask the user:
- Activate
pm-reporting workflow (Recommended) — status → dependency
- Execute
/status directly — run this skill standalone
1---2name: status-153description: > [IMPORTANT] Use TaskCreate to break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI MUST ask user whether to skip.4---5
6---
7name: status
8version: 1.0.0
9description: "[Project Management] Generate status reports for sprints or projects. Use when creating status reports, checking progress, or summarizing sprint metrics. Triggers on keywords like "status report", "sprint status", "progress", "how are we doing", "what's done", "project status"."
10allowed-tools: Read, Write, Grep, Glob, Bash, TaskCreate
11---
12
13> **[IMPORTANT]** Use `TaskCreate` to break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI MUST ask user whether to skip.
14
15## Quick Summary
16
17**Goal:** Generate a project status report covering progress, blockers, and next steps.
18
19**Workflow:**
20
211. **Gather** -- Collect data from git, tasks, plans, and recent activity
222. **Analyze** -- Assess progress against goals, identify blockers
233. **Report** -- Write structured status report with metrics
24
25**Key Rules:**
26
27- Include: completed items, in-progress work, blockers, next steps
28- Quantify where possible (files changed, tests passing, coverage)
29- Save report to plans/reports/ with standard naming
30
31**Be skeptical. Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence percentages (Idea should be more than 80%).**
32
33# Status Report
34
35Generate project/sprint status reports with metrics.
36
37## When to Use
38
39- Sprint status needed
40- Project progress report
41- Stakeholder update
42
43## Quick Reference
44
45### Workflow
46
471. Read PBIs in scope
482. Check git log for recent commits
493. Find open issues/PRs
504. Calculate metrics
515. Generate report
526. Save to `plans/reports/`
53
54### Metrics
55
56- Completed vs Planned
57- Velocity (if sprint)
58- Bug count
59- Blocker count
60
61### Report Structure
62
63```markdown
64## Status Report - {Date}
65
66### Sprint: {Name} | Day {N}/{Total}
67
68#### Progress
69
70| Metric | Planned | Actual | Status |
71| ------ | ------- | ------ | ------ |
72
73#### Completed
74
75| Item | Owner |
76
77#### In Progress
78
79| Item | Status | Blocker |
80
81#### Blockers
82
83| Blocker | Impact | Action |
84
85#### Risks
86
87| Risk | Probability | Impact |
88```
89
90### Output
91
92- **Path:** `plans/reports/{YYMMDD}-status-{scope}.md`
93
94### Related
95
96- **Role Skill:** `project-manager`
97- **Command:** `/status`
98
99---
100
101**IMPORTANT Task Planning Notes (MUST FOLLOW)**
102
103- Always plan and break work into many small todo tasks
104- Always add a final review todo task to verify work quality and identify fixes/enhancements
105
106---
107
108## Workflow Recommendation
109
110> **IMPORTANT MUST:** If you are NOT already in a workflow, use `AskUserQuestion` to ask the user:
111>
112> 1. **Activate `pm-reporting` workflow** (Recommended) — status → dependency
113> 2. **Execute `/status` directly** — run this skill standalone
majiayu000