Weekly Report

Collect the inputs for this report before drafting.

Record:

• The reporting period and the audience for the report
• What got done this week — completed work, shipped items, results
• In-progress work and where it stands
• Blockers and risks
• Any metrics or numbers to include
• What is planned for next week

Pull from notes, task updates, or the operator's recollection. If a key
area is empty, ask before assuming nothing happened.

Save the gathered inputs as a task note with task_notes_add. The next
step — Draft — reads this note.

Read the task notes with task_notes_list — the note from the Gather
step contains the week's inputs. Work from it.

Write the report. What good looks like:

• A one- or two-line headline summary of the week
• Wins and completed work
• In-progress work with status
• Blockers and risks, with what is needed to clear them
• Metrics, if any, with plain context
• Next week's plan

Keep it scannable — a stakeholder should grasp the state in under a
minute. State numbers plainly; do not inflate.

Save the full report draft as a task note with task_notes_add. The
Review step reads this note.

Read the task notes with task_notes_list — the Draft note holds the
report and the Gather note holds the source inputs. Work from them.

Review the report:

• Every claim and number traces back to a gathered input
• Blockers are stated honestly, not buried
• The summary matches the body
• Nothing important from the inputs was dropped

Ask the operator to approve the report for publishing. This is a
checkpoint — once published it informs decisions, so the AI cannot
advance until you approve. If you reject, the workflow returns to Draft.

Read the task notes with task_notes_list — the Review note holds the
approved report. Work from it.

Publish the report to its audience — the channel, doc, or email the
team uses. Save the published report as a task note with task_notes_add
so the record of what was sent stays on file, then close out the task.