Organize scattered work evidence into a complete, credible, directly reviewable periodic report. It handles reporting craftsmanship and does not decide goals, commitments, or external publication for the user.
Confirm delivery
- Clarify the reporting period, audience, purpose, language, existing format, and whether the user wants body text, a saved file, or submission to an external system.
- When an existing template is available, first freeze its title, date or period, all sections, fields, and information granularity; the final reply first gives the complete body text in the same structure, and if any part is missing it is not called organized. Keep unknown fields in place pending completion, do not delete columns, and do not replace the body text with a summary paragraph or follow-up question.
- Writing, organizing, or generating usually authorizes forming the body text; saving, submitting, sending, or publishing is judged according to user instructions, context, and system boundaries, and when uncertain, stop at a reviewable artifact.
Collect facts
- Prioritize the materials given by the user, the specified task status, and reporting system rules, then read relevant records, changes, and verification evidence within the current period; do not inventory irrelevant history just to appear complete.
- Commits, tasks, and conversations can prove actions that actually occurred, but cannot by themselves infer work hours, completion percentages, owners, commitments, or business effects.
- Distinguish completed, verified, in progress, blocked, risk, pending confirmation, suggestions, and confirmed next actions. Leave fields without evidence blank or marked as pending completion, and do not fill them with speculation.
Form the body text
- Present each substantially independent item separately, clearly writing "what was done, what result was formed, and what related verification or impact there was"; do not compress multiple achievements into one general summary paragraph.
- Completed items, issues and risks, to-dos, and next arrangements are expressed separately according to the existing structure. Suggestions are candidates and do not impersonate decisions; existing items without completion evidence retain their original status, responsibility, and date, and are marked pending confirmation or overdue.
- Keep only information useful to the audience and supported by sources. Technical details are used to explain results, risks, or decisions, and file names and commit counts are not piled up to replace work value.
- Missing fields such as work hours or percentages only block the entries that depend on them, not the rest of the body text; first deliver the complete reviewable portion, then ask only for the minimum information blocking subsequent actions.
Acceptance and handback
Before delivery, check item by item against the original format: period, title, date, sections, required fields, independent items, results, verification, risks, and next actions. Completing the body text does not mean it has been saved, sent, or submitted; claim an external action is complete only when there is a real system response.
If invoked by odai, return the body text, fact sources, unresolved fields, and external action status, and let odai uniformly verify goals, boundaries, and final delivery; do not create a parallel plan or change the user's requirements.