weekly-summary

Prompt file imported from marostr/hq-starter (.claude/commands/weekly-summary.md). Copyright stays with the author.

Generate the weekly summary — a report covering everything that happened in HQ this week. Useful for self-review, sharing with stakeholders, or sending to partners/investors.

Prerequisites

If you have writing-discipline skills available (e.g. elements-of-style:writing-clearly-and-concisely), invoke them first. The skill enforces short sentences, active voice, no filler.

Steps

1. Determine the week. Find the current ISO week number and date range (Monday–Sunday). Check if log/weekly/YYYY-Wnn.md already exists — if so, update it rather than creating a duplicate.

2. Gather data. Run these in parallel:

   • git log --format="%h %ad %s" --date=short --since=MONDAY --until=NEXT_MONDAY for commit history
   • Read all task files; note status changes (new, completed, blocked, unblocked)
   • Read all initiative files for status changes
   • Read log/ for any new decision/meeting/review entries this week
   • Read knowledge/ and library/ indexes for new additions

3. Write the summary. Follow the template in _templates/weekly-summary.md. Voice rules:

   • Short sentences, active voice, no filler, no weasel words
   • Refer to the operator by name; describe what was done
   • Stakeholder-ready — no editing required before sending
   • No emojis. No jargon without context.
   • Facts only, no editorializing. Report what happened (commits, task changes, decisions logged, meetings held). Do not infer problems, blockers, or constraints from observations. The Blockers section lists only items the operator explicitly identified as blocked. The narrative sections describe events, not diagnoses.

4. Section guidance.

   • TL;DR: 2–3 sentences tying the week together. The headline. What a stakeholder needs to know if they read nothing else.
   • The Big Picture: Strategic narrative. The theme of the week, what it means for direction, any macro shifts. One or two short paragraphs.
   • Weather Report: Three short bulleted lists — going well, going sideways, needs attention. Facts-only: cite the thing (initiative, task, commit, decision) that grounds each item. No speculation.
   • By Initiative: Per-initiative breakdown — what moved, what didn't. Lead each with the headline. Be honest about stalls.
   • Decisions: New entries from log/ this week with type: decision.
   • Next Week: What's queued up. Draw from task due dates and initiative plans.
   • Blockers: Only items explicitly marked as blocked. If nothing is blocked, say so.

5. Update indexes. Add the new entry to log/weekly/index.md and log/index.md.

6. Commit. Stage and commit the new/updated weekly summary and index changes.