# Status Report

> Produce clear, scannable status reports that communicate progress, risks, decisions needed, and outlook. Use for project updates, weekly/monthly reports, steering committee packs, or any recurring status communication.

- Skill: `itsual/status-report` (Agent Skill)
- Install (CLI): `npx skillmds@latest add itsual/status-report`
- Raw SKILL.md: https://api.skillmd.com/api/skills/itsual/status-report/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: itsual (https://skillmd.com/u/itsual)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/itsual/status-report

---


# Status Report

## Overview

Status reports should answer: Where are we? Are we on track? What needs attention? What decisions are required?

## When to Use

- Project or program status updates
- Weekly / bi-weekly / monthly reports
- Steering committee or leadership updates
- Cross-team progress communication

## Recommended Structure

1. Snapshot (overall status, RAG/health, date)
2. Highlights / progress this period
3. Key metrics or milestones
4. Risks, issues, and blockers
5. Decisions needed
6. Plan for next period
7. Appendix (detail) if required

## Principles

- Put the most important information first
- Use consistent status indicators (RAG, trends)
- Separate facts from asks
- Be honest about problems early
- Keep the main view to 1–2 pages when possible

## Verification

- [ ] Overall status is obvious in seconds
- [ ] Risks and decisions needed are impossible to miss
- [ ] Progress claims are specific and evidence-based