CodexWorkWrite a weekly update from tracker and notes
Get a draft update that preserves the current plan, shows proposals and reflects authorized changes.
Only the supplied snapshot is available; later events remain unknown.
What you supply
- Project tracker and meeting notes, attached or in an authorized folder
- Reporting period, intended reader and any required format
What it saves
- Editable weekly update
- Source list and open questions
Designed example · synthetic data
See the finished example
Read the result before using it
Use the tracker, meeting notes and reporting brief together. The update should distinguish the current plan from a suggestion, and completed work from a date that merely says when it was due.
| Source | What it establishes | What the update can say |
|---|---|---|
| T07 | Review planned for 14 October | 14 October remains the current plan. |
| N02 | 16 October proposed; no confirmed change | The proposed move awaits confirmation. |
| T01 | Checklist complete and approved; no completion date | Completed status is known. In-period completion is not established. |
- A proposal does not change the plan. Retain the 14 October plan beside the unconfirmed 16 October proposal. The historical model output incorrectly called the review date unknown.
- Authority matters more than recency. An authorized owner's explicit withdrawal retires an earlier approval. A later timestamp alone does not resolve a contradiction, and an unconfirmed suggestion is not a withdrawal.
- Status does not supply a completion date. Keep completed status when supported, label an absent date unknown, and do not turn due dates into achievements during the reporting period.
The current instruction was editorially revised on 24 October 2026 and has not been rerun. The 13 October model output stays unchanged; the correction is teaching material, not a tested-success badge.
The instruction
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.
Show plain text
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.
Stops in this kit
Unresolved contradictions or unconfirmed proposed changes
Reporting period or reader, if missing
Tasks with no owner
Unknown completion dates
Sending the update (it never sends)
Checks to run
- 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.
What has been tested
Editorially revised · not rerun
Current instructions were editorially revised on 24 October 2026 to preserve a current plan beside an unconfirmed proposal and distinguish authorized changes from unresolved contradictions. They have not been rerun. The preserved 13 October 2026 Codex run used the older exact instruction and incorrectly called the review date unknown; the current planned date was 14 October, with 16 October only proposed. A separate editorial correction explains the difference without changing the model output. Source dates are unchanged; no real project or external sending was tested.
Checked 2026-10-13
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.
Optional tool setup
Using a kit
- Attach the tracker, notes and reporting brief. The sample pack contains all three.
- Give the instruction to an agent that can read those files and save outputs.
- Open the saved update and source list before using the update.
ChatGPT
- Paste the instruction, attach the sample files or your own, and read the stops first.
- Pick Work for a multi-step task and supply the context it needs.
- For reuse, follow the documented skill or plugin setup on your surface. Downloading a kit does not install it.
Check the permissions for the tools and actions you use. The kit's stops are instructions to the agent; they do not create an enforced approval setting.
ChatGPT · dated notes →Claude
- Paste the instruction, attach the sample files or your own, and read the stops first.
- In Cowork, choose the authorized folder containing your inputs where that feature is available. A generic kit-to-skill import was not established by the reviewed pages.
- In Claude Code, use CLAUDE.md for project guidance. AGENTS.md is read by default on supported versions (2.1.277+) only when project-path CLAUDE.md or CLAUDE.local.md does not take precedence; session and configuration exceptions apply.
Check the controls in your Claude surface. Anthropic describes approval handbacks, but the kit's stops do not enforce a product permission boundary.
Claude · dated notes →Codex
- Paste the instruction, attach the sample files or your own, and read the stops first.
- For project guidance, use AGENTS.md. For a reusable skill, follow the supported setup, such as .agents/skills/<name>/SKILL.md in a repository.
- Check the sandbox and approval settings before you start the job.
Codex has sandbox and approval settings. Check them before a job that touches real files.
Codex · dated notes →Copilot
- Paste the plain instruction into a Copilot chat you can access, and read the stops first.
- Check which file inputs and actions your tenant's actual surface supports before supplying files.
- Keep the kit as a manual prompt. The reviewed posts do not document importing it as a skill, plugin or agent.
Ask your administrator which actions, permissions and approval controls your organization has enabled. A kit's stops do not create those controls.
Copilot · dated notes →Gemini
- Paste the instruction, attach the sample files or your own, and read the stops first.
- Where Skills is available, copy or import the skill using that surface's documented setup.
- Gemini app and Workspace skills do not sync. Set up the skill separately on each available surface you use.
Some Gemini Tasks may require confirmation. Check current eligibility and permissions before real account work; the kit's stops are instructions, not enforced approval settings.
Gemini · dated notes →Grok
- Paste the plain instruction as a message and read the stops first.
- If Bot is available to you, show it the workflow; xAI describes routine learning by following along.
- Keep the instruction as plain text; we could not confirm SKILL.md support.
xAI describes approval handbacks for Grok Bot. Check what your account and connected apps allow before real actions.
Grok · dated notes →Other agents
- Paste the plain instruction into an agent that accepts text, then supply inputs through its supported route and read the stops first.
- If your agent reads AGENTS.md, save the instruction there.
- If the named client supports Agent Skills, use the documented skill folder location and setup for that client and version.
This varies by agent. Look up its approval settings; the kit's stops stay in the instruction wherever you paste it.
Other agents · dated notes →Markdown · README.md
# Write a weekly update from tracker and notes Get a draft update that preserves the current plan, shows proposals and reflects authorized changes. ## Start 1. Edit [brief.md](weekly-manager-update/files/brief.md) and [input-template.md](weekly-manager-update/files/input-template.md). 2. Supply authorized inputs to your own file-capable agent with [instruction.txt](weekly-manager-update/files/instruction.txt). 3. Inspect the saved outputs using [checks.md](weekly-manager-update/files/checks.md) before using them. Keep original inputs. ## Inputs - Project tracker and meeting notes, attached or in an authorized folder - Reporting period, intended reader and any required format ## Outputs - Editable weekly update - Source list and open questions ## Steps - Attach the tracker, notes and reporting brief. The sample pack contains all three. - Give the instruction to an agent that can read those files and save outputs. - Open the saved update and source list before using the update. ## Instruction 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. ## Decisions that need your context - Reporting period or reader, if missing - Unresolved contradictions or unconfirmed proposed changes - Tasks with no owner - Unknown completion dates - Sending the update (it never sends) ## Settled by the brief No separately annotated settled rules are supplied. Follow the instruction as written. ## Check the output - 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. ## Materials - [examples/weekly-manager-update/designed-example.html](weekly-manager-update/files/examples/weekly-manager-update/designed-example.html) - [examples/weekly-manager-update/designed-example.md](weekly-manager-update/files/examples/weekly-manager-update/designed-example.md) - [examples/weekly-manager-update/editorial-correction.html](weekly-manager-update/files/examples/weekly-manager-update/editorial-correction.html) - [examples/weekly-manager-update/editorial-correction.md](weekly-manager-update/files/examples/weekly-manager-update/editorial-correction.md) - [examples/weekly-manager-update/input.csv](weekly-manager-update/files/examples/weekly-manager-update/input.csv) - [examples/weekly-manager-update/input.md](weekly-manager-update/files/examples/weekly-manager-update/input.md) - [examples/weekly-manager-update/recorded-run/input.md](weekly-manager-update/files/examples/weekly-manager-update/recorded-run/input.md) (original recorded evidence; links retain their recorded form) - [examples/weekly-manager-update/recorded-run/instruction.txt](weekly-manager-update/files/examples/weekly-manager-update/recorded-run/instruction.txt) (original recorded evidence; links retain their recorded form) - [examples/weekly-manager-update/recorded-run/output/source-list.md](weekly-manager-update/files/examples/weekly-manager-update/recorded-run/output/source-list.md) (original recorded evidence; links retain their recorded form) - [examples/weekly-manager-update/recorded-run/output/weekly-update.md](weekly-manager-update/files/examples/weekly-manager-update/recorded-run/output/weekly-update.md) (original recorded evidence; links retain their recorded form) - [examples/weekly-manager-update/recorded-run/report.html](weekly-manager-update/files/examples/weekly-manager-update/recorded-run/report.html) (original recorded evidence; links retain their recorded form) - [examples/weekly-manager-update/recorded-run/report.md](weekly-manager-update/files/examples/weekly-manager-update/recorded-run/report.md) (original recorded evidence; links retain their recorded form) - [examples/weekly-manager-update/source-list.md](weekly-manager-update/files/examples/weekly-manager-update/source-list.md) ## Evidence [Recorded context and file identities](weekly-manager-update/files/evidence.json) Editorially revised · not rerun Current instructions were editorially revised on 24 October 2026 to preserve a current plan beside an unconfirmed proposal and distinguish authorized changes from unresolved contradictions. They have not been rerun. The preserved 13 October 2026 Codex run used the older exact instruction and incorrectly called the review date unknown; the current planned date was 14 October, with 16 October only proposed. A separate editorial correction explains the difference without changing the model output. Source dates are unchanged; no real project or external sending was tested. Observed or source-checked: 2026-10-13. ## Revision and corrections Revision: 2.1.1. Lifecycle: active. [Current kit](https://codexwork.com/kits/weekly-manager-update/) · [Changes and corrections](https://codexwork.com/changes/) [Rights and notices](weekly-manager-update/files/LICENSES.md) · [Sources](weekly-manager-update/files/sources.md) · [Manifest](weekly-manager-update/files/manifest.json) Downloading these files does not run an agent, install a skill, create a schedule, or grant file or account permissions.Open Markdown file ↗
SKILL.md
--- 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.Open SKILL.md ↗