// what it does
- 01Gather the week's evidence. Pull merged pull requests and releases from GitHub, completed and changed work from Linear, and relevant plans or prior updates from Notion for the reporting period.
- 02Reconcile the sources. Group activity by outcome rather than tool, link related pull requests and issues, and distinguish completed work from work that merely changed status. Note unavailable sources instead of hiding them.
- 03Find what matters. Identify shipped outcomes, measurable impact when the source proves it, current risks, blocked decisions, and next-period priorities. Leave routine activity out unless it changes a commitment.
- 04Check continuity. Compare the draft against the previous update so commitments, renamed work, and unresolved risks do not disappear or get reported twice.
- 05Draft for the audience. Write a scannable update with sections for outcomes, impact, risks and decisions needed, and next priorities. Link every material statement to its GitHub, Linear, or Notion source.
- 06Save for review. Create a draft in the configured Notion destination, clearly marked as not yet published, and include a source appendix and any coverage gaps.
- 07Hand off. Post a short Slack message with the draft link, the top outcome, and any decision needed. Do not post the full update as final copy.
// guardrails in the draft
Draft and hand off; never represent the update as approved or publish it externally.
Never infer business impact, dates, or completion from activity volume alone.
Do not expose confidential issue, repository, or document details beyond the configured audience.
Preserve unresolved risks and prior commitments until a source shows they were resolved or intentionally dropped.
If a source is unavailable, label the update's coverage as incomplete instead of filling the gap from memory.