status-report

Use when the user asks for a weekly / monthly status report, project update, individual or team progress summary. Produces a tight, scannable update with what shipped, what's in flight, what's blocked, and metrics.

Jump to install

Repository: shiwenwen/hope-agent
Last source activity: April 25, 2026 at 14:44
Detected SKILL.md language: English
Stars: 1,448
Forks: 134

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/shiwenwen/hope-agent --skill status-report

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

# <Your Name / Team Name> — Week of <YYYY-MM-DD>

## TL;DR
<2 sentences. What's the state of the world? Use plain English.>

## ✅ Shipped This Week
- <bullet — outcome, not activity. Link if relevant.>
- <bullet — outcome.>

## 🔄 In Flight
- <project> — <what stage, expected ship date>
- <project> — <what stage, expected ship date>

## ⚠️ Risks / Blockers
- <risk> — <impact + what's needed to unblock>

## 📊 Metrics (optional)
| Metric | This Week | Last Week | Δ |
|--------|-----------|-----------|---|
| <name> | <value> | <value> | <±> |

## 📅 Next Week
- <top 3 priorities, in order>

Gather inputs via recall_memory (if scope=session/project) and ask_user_question:
- Date range covered (default: last 7 days)
- Audience (manager? cross-functional? company all-hands?) — affects depth and jargon
- Key projects to cover
- Whether metrics are required and what the baseline is
Categorize ruthlessly — every bullet must fit exactly one bucket:
- Shipped = merged / launched / delivered / decided. Past tense.
- In Flight = work in progress, not yet shipped. Has an ETA.
- Risks/Blockers = something that will hurt the plan if not addressed. Has a specific owner ask.
Write outcomes, not activity:
- Bad: "Worked on auth migration. Had 3 design meetings."
- Good: "Auth migration: design approved, infra ready. Cutover scheduled for May 5 (low risk)."
Quantify when possible:
- "Shipped feature X" → "Shipped feature X (5% adoption in week 1, target was 3%)"
- "Faster builds" → "CI builds dropped from 12m → 7m (median)"
Sequence priorities by impact — the first item in "Next Week" should be the highest-leverage thing. Don't bury it.
Save state — offer to save the report to memory or to compose an email via email-draft:
```
Save this status to memory for next week's diff?
Send to <manager> as an email?
```

- Yesterday: <one outcome>
- Today: <one focus>
- Blockers: <none / specific ask>

## 🎯 Themes
- <pattern across the 4 weeks: what got better, what's recurring>

## 📈 Trends
| Metric | Month-over-Month | Notes |
|--------|------------------|-------|
| ... | ... | ... |

## 🔭 Looking Ahead (next month)
- <strategic priorities, not tactical tasks>

# Q<N> Review — <Team>

## Goals Status
| OKR | Target | Actual | Status | Confidence |
|-----|--------|--------|--------|------------|
| <name> | <metric> | <metric> | <On Track / At Risk / Off Track> | <0.0–1.0> |

## What Went Well
- <pattern, not single incident>

## What Didn't
- <honest pattern, with the lesson>

## Q<N+1> Bets
- <top 3 priorities for next quarter, with rationale>

Audience	Adjust
Direct manager	Include risks honestly; manager wants to help unblock
Cross-functional team	More context; less internal jargon
Company all-hands	Outcomes only; cut planning details
Skip-level / exec	TL;DR + 3 bullets total; skip metrics unless they're 1-2 headline numbers
External (board, investors)	Headline outcomes + roadmap; never blockers without solutions

Mistake	Fix
Listing every Jira ticket	Group into ≤5 outcomes, name them
"Working on …" everywhere	Pick a stage: design / implementation / review / shipped
Burying bad news	Lead with "TL;DR: slipping by 1 week, here's why"
Vague metrics ("better", "faster")	Specific numbers or skip the metric
Same priorities every week	Either reframe progress or admit it's stuck
No "next week" section	Always have one — shows you're proactive, not just reactive
Word-soup TL;DR	Two sentences max. If you can't compress, you don't understand the state.

# Alice — Week of 2026-04-25

## TL;DR
Shipped auth refactor; dashboard search done by Friday. Embedding migration blocked on infra capacity (need decision by Tuesday).

## ✅ Shipped This Week
- Auth refactor PR merged (#1234) — removes legacy session middleware, paves way for OAuth migration.

## 🔄 In Flight
- Dashboard search — backend + UI complete, integration tests pending. Ship target: Friday.

## ⚠️ Risks / Blockers
- Embedding migration — blocked waiting on infra team's capacity decision. **Need by Tuesday** or May ship date slips.

## 📅 Next Week
1. Land dashboard search to prod.
2. Kick off i18n rewrite (12 locales, scoping doc first).
3. Unblock embedding migration once infra responds.

name	status-report
description	Use when the user asks for a weekly / monthly status report, project update, individual or team progress summary. Produces a tight, scannable update with what shipped, what's in flight, what's blocked, and metrics.
version	1.0.0
author	Hope Agent
license	MIT
metadata	{"hermes":{"tags":["office","status","reporting","productivity","communication"],"related_skills":["meeting-notes","email-draft"]}}

name	status-report
description	Use when the user asks for a weekly / monthly status report, project update, individual or team progress summary. Produces a tight, scannable update with what shipped, what's in flight, what's blocked, and metrics.
version	1.0.0
author	Hope Agent
license	MIT
metadata	{"hermes":{"tags":["office","status","reporting","productivity","communication"],"related_skills":["meeting-notes","email-draft"]}}

status-report

Install options

Review the source files

Status Report

When to Use

Status Report

When to Use

The Weekly Template

Workflow

Style Rules

Cadence-Specific Adjustments

Daily / Standup (≤3 bullets)

Monthly (add to weekly template)

Quarterly / OKR (replace template)

Audience-Specific Adjustments

Common Pitfalls

Example

status-report

Source facts

Install options

Review the source files

More from this repository

More from this repository

Status Report

When to Use

Status Report

When to Use

The Weekly Template

Workflow

Style Rules

Cadence-Specific Adjustments

Daily / Standup (≤3 bullets)

Monthly (add to weekly template)

Quarterly / OKR (replace template)

Audience-Specific Adjustments

Common Pitfalls

Example