cyberneticlibrary
← library

Generate weekly activity summary

weekly-summarycommandsetup L2★3
marostr/hq-starter ↗
What it does

Generate stakeholder-ready weekly narrative with data pull and analysis

Best for

Weekly stakeholder communication when you need a facts-only narrative (commits, task changes, decisions) with no speculation.

Inputs
  • · [object Object]
  • · [object Object]
  • · [object Object]
  • · [object Object]
Outputs
  • · [object Object]
  • · [object Object]
  • · [object Object]
Requires
  • · Bash (git log, task/initiative file listing)
  • · Read, Write
  • · writing-discipline skill (optional but recommended)
Preconditions

ISO week can be computed; log/weekly/ directory exists; tasks and initiatives are tracked in readable files

Failure modes
  • · Summary is late (published mid-week or after week ends)
  • · Summary editorializes instead of reporting facts (inference vs observation)
  • · Blockers section includes items not explicitly marked blocked
  • · Next Week section is vague (references internal jargon)
  • · No TL;DR (stakeholder reads whole page instead of 2-3 sentences)
Trust signals
  • · Git log cited for commits (grounded in VCS, not memory)
  • · Weather Report has three buckets (going well, sideways, needs attention) — facts-only, no speculation
  • · Blockers section explicitly requires explicit marking (no inferred blockers)
  • · Each initiative has headline summary (what moved, what didn't)
  • · Voice rules: active, short sentences, stakeholder-ready (no editing needed)