1---2name: plan-progress-reporting3description: Create concise progress reports, metrics, and stakeholder communications.4---56# Progress Reporting Skill78## What it does9- Crafts status updates with outcomes, risks, and next steps.10- Summarizes metrics (velocity, burndown, defect rate) for stakeholders.11- Tailors message per audience (executive, product, engineering).1213## When to use (khi nào dùng)14- When stakeholders request status or risk assessment.15- Before major milestones/releases to align expectations.1617## Key operations18- Identify active project; gather metrics from `current-sprint.json`, velocity/burndown charts, task logs.19- Compile key metrics and narrative: what changed, impact, risks; include RAG with rationale and asks.20- Tailor content length and depth to audience; highlight decisions needed.21- Attach evidence (demo links, PRs, dashboards, burndown/velocity charts); log updates in `memory/YYYY-MM-DD.md`.2223## Output files24- `projects/<ACTIVE>/reports/status.md` — current status, accomplishments, next steps, risks/asks.25- `projects/<ACTIVE>/reports/metrics.csv` — velocity, burndown snapshots, defects, lead time (if available).26- `projects/<ACTIVE>/reports/risks.md` — risk register with owners and due dates.27- `projects/<ACTIVE>/reports/weekly-report.md` or `sprint-review.md` when applicable.28- `memory/YYYY-MM-DD.md` — log shared updates, risks, and decisions.2930## Example workflow311) Gather metrics (velocity, burndown, completion %) and qualitative updates from `task-log` and sprint files.322) Write `status.md` with RAG, highlights, risks, asks, and links to evidence (demo, PRs, dashboards).333) Update `metrics.csv` and `risks.md`; share with stakeholders; log summary in `memory/YYYY-MM-DD.md`.3435## Best practices (best practice)36- Lead with outcomes and impact; keep metrics brief and relevant.37- Be explicit about risks, mitigations, and help needed.38- Keep updates consistent cadence and format; avoid surprise escalations.39- Use visuals (burndown chart) when possible.40- Keep audience-specific brevity; executives want outcomes/risks/asks; engineering wants detail/links.41- Ensure data sources match AGENTS files (current-sprint.json, velocity/burndown charts) to avoid drift.4243## Related resources (tài liệu liên quan)44- `AGENTS.md` (reporting guidance and cadence)45- `SKILLS.md`, `MEMORY.md`, `memory/YYYY-MM-DD.md`46- `projects/<ACTIVE>/sprints/current-sprint.json`, `reports/velocity-chart.json`, `reports/burndown-chart.json`47- `projects/<ACTIVE>/tasks/task-log.md`48- `company/status-template.md` (if present)