---
name: weekly-manager-update
description: "Get a draft update that preserves the current plan, shows proposals and reflects authorized changes."
---

# Write a weekly update from tracker and notes

Use the tracker, meeting notes and brief I provide to prepare a weekly update for the intended reader and reporting period. Use only these supplied files. If the period or reader is missing, ask before choosing them.

Create an editable document with Summary, Progress this period, Coming up next and Needs attention. Finish with open questions. Use the requested format if supported; otherwise save weekly-update.md. Save source-list.md linking every factual statement to its file and row, task ID, note date or section.

Distinguish the current plan or approval from proposals and history. An unconfirmed proposed change does not replace the existing plan: state the current plan, the proposal and the confirmation still needed. When the sources establish a named person's authority and explicitly record that person's correction, supersession or withdrawal, use the changed decision as current and retain the earlier decision and its source as history. A newer timestamp alone does not establish authority. For genuinely unresolved contradictions, show both versions with their sources and name what remains unknown. When approval is withdrawn, say there is no current authority to proceed and show dependent work on hold, including in Coming up next; an unchanged tracker or an old due date is not permission. Preserve the source tracker, and do not claim it was updated or the external action stopped.

Keep blockers visible. For a missing owner say “No owner listed.” Include material issues found in one source but absent from the other. Treat a notes-only issue as an issue, not a new tracker row or assigned task. Do not invent approval, completion, deadlines or optimism. Do not infer a completion date or an achievement within the reporting period from a due date. If a completion date is missing, label the current completed status with “Completion date unknown.” Distinguish the reporting period from the source snapshot; do not imply the rest of the period has already occurred. Mark only the unsettled part unknown, not an existing plan that an unconfirmed proposal has not changed.

Save new output files and preserve the inputs. Do not send or share the update. Return links or paths to the created files and state anything incomplete.

## Required inputs

- Project tracker and meeting notes, attached or in an authorized folder
- Reporting period, intended reader and any required format

## Expected outputs

- Editable weekly update
- Source list and open questions

## Checks

- Every factual sentence has a source locator.
- The current plan remains visible beside an unconfirmed proposal; unknown confirmation does not make the existing plan unknown.
- An explicit authorized correction or withdrawal replaces earlier current authority in the whole update, while the earlier source remains visible as history.
- Unresolved contradictions, missing owners and real blockers remain visible; a later timestamp alone does not choose a winner.
- Completed status is supported; missing completion dates are labeled unknown, and due dates do not establish in-period achievement.
- Material notes-only issues appear without invented owners or decisions.
- A preview is not described as deployed, and a mid-period snapshot is not a full-period record.

## Limits

- Only the supplied snapshot is available; later events remain unknown.
- File access and editable output formats depend on the connected environment.
- Copying this instruction does not send the update or start an agent.

Revision: 2.1.1. [Read the complete kit](files/README.md) before use. This optional format is not a claim of support by every tool.