Positioning
- Input: the current period's departmental summary folder + planning file (Markdown / DOCX / TXT) + previous period's summary file (Markdown / DOCX / TXT, may be multiple)
- Output: two files: one overall reporting report for the boss and the management team; one separate manual supplement checklist
- Style principles: objective, concise, honest. Let the data speak; if there is no data, do not infer, and put the gap into the manual supplement checklist; vague words are prohibited
- Core principles: the planning file and the previous period's summary file together form a complete tracking ledger. The main report only contains facts and conclusions that can be reported directly, does not mark sources, and does not mix manual supplement details into the body text; content that requires manual supplementation or confirmation must be generated as a separate supplement checklist, clearly stating what needs to be supplemented, whom to confirm with, and why it needs to be supplemented.
Step 1: Understand the input
1.1 Obtain input files
First identify whether the user has given a reporting period, for example:
2026052026-052026年5月5月周报、5月月报
If the user does not provide the path to the folder containing the departmental documents but does provide a reporting period, first automatically scan the current run directory for a matching directory; do not ask the user directly. The scanning priority is as follows:
- Exact period directory match: for example, if the user wants to generate
202605, first look in the current run directory for202605/。 - Normalized match: try uniformly matching
2026-05、2026年5月、2026年05月against202605/、2026-05/、2026年05月/、2026年5月/。 - Contains match: if there is no exact directory, look in the first level under the current run directory for a directory whose name contains that period, for example
202605月报材料/、2026-05部门总结/。
Recommended scanning command:
find . -maxdepth 2 -type d | sort
Directory selection rules:
- When there is only one obvious matching directory, use it directly as the folder containing the departmental documents.
- When there are multiple matching directories, list the candidate directories and let the user choose.
- When there is no matching directory, then ask the user to provide the path to the folder containing the departmental documents.
- If the planning file and the previous period's summary file are also not provided, within the matching directory first look for files whose names contain
规划、计划、上期、总结、复盘; if it still cannot be determined, ask follow-up questions.
Ask the user (only when automatic scanning cannot confirm):
- Path to the folder containing the departmental documents
- Path to the planning file
- Path to the previous period's summary file (used to extract leftover items from the previous period, previous-period risks, and the previous period's next-period plan; multiple files may be provided)
- Reporting period (this week / this month / custom date range)
If the planning file or the previous period's summary file still cannot be confirmed after automatic scanning, ask follow-up questions first; do not generate the report directly.
1.2 Traverse the folder
find <folder_path> -type f | sort
Process files according to the following priority:
| Priority | File type | Processing method |
|---|---|---|
| High | .md .txt |
Read directly |
| High | .docx |
Read with the docx skill |
| Medium | .pdf |
Read using pdf-reading skill |
| Low | .xlsx .csv |
Extract key numbers/tables |
| Skip | Images, compressed files, etc. | Record in the manual supplement list under "file or material anomalies" |
After reading each file, record:
- File name (for internal verification only, not to be written into the main report body)
- Department (inferred from file name or path)
- File modification time (used to determine whether it is within the reporting period)
⚠️ If the file modification time is significantly earlier than the reporting period, record it in the manual supplement list under "file or material anomalies".
1.3 Read planning documents
Parse the planning documents and extract:
- Each milestone, metric, key project, department plan, and risk item
- For each goal,quantifiable metrics(if any)
- Responsible department/person for the goal
- Expected completion time node
Planning documents can be quarterly/monthly plans, or annual plans, phase plans, or the next-period plan in the previous period summary. When reading, establish a "goal tracking list" according to the following levels:
- Planning milestones: for example, product launch, pilot implementation, platform delivery, acceptance milestones.
- Metrics: for example, external acceptance amount, internal acceptance amount, revenue target, completion rate.
- Topics/solutions: for example, campus solutions, exhibition materials, key solution updates.
- Core delivery plans of each department: broken down by department, not merged into general statements.
- Identified risks/obstacles: retained as risk tracking items for the next period.
Reference output format:
- First write "planning milestone completion status and deviations", comparing goals with actual results item by item.
- Then write "metrics" and "core delivery results of each department".
- Finally write "existing obstacles and risks" and "next-period plan".
- Do not only analyze matters mentioned in the current period's files; matters not mentioned in the goal list must also be included in internal verification, and those that cannot form a main report conclusion should go into the manual supplement list.
1.4 Read the previous period summary file
Parse the previous period summary file and extract:
- Unfinished matters, deviation matters, and unrecorded matters from the previous period
- Risks and obstacles from the previous period
- "Next-period plan" or follow-up to-dos in the previous period report
- Time nodes, metric targets, and responsible departments committed in the previous period
Merge these contents into the goal tracking list, marking the category as "previous period carryover" or "previous period plan". If a matter exists in both the planning document and the previous period summary file, the planning document takes precedence, supplemented by the progress background, risk reasons, or historical status in the previous period summary.
Step 2: Information extraction and classification
For each department document, extract the following information (write as much as can be extracted; do not infer what cannot be extracted):
Matters completed in the current period
- What was specifically done and what the result was (retain numbers if any)
Goal association status
- Which goal/plan/carryover matter in the planning document or previous period summary file it corresponds to
- Completion level: completed / partially completed / not completed / not mentioned
Unplanned matters
- Matters not in the planning document or previous period summary document but actually done
Next period plan
- Next period plans or to-dos explicitly mentioned in the document
Risks and obstacles
- Issues, reasons for delays, dependencies not in place, etc. mentioned in the document
Step 3: Variance analysis
Against the objective tracking list, analyze item by item:
目标 → 实际 → 偏差类型 → 原因(如有记录)
Variance types are divided into four categories:
- ✅ Achieved: completed on schedule or exceeded
- ⚠️ Variance: partially completed, with clear progress
- ❌ Not completed: explicitly stated as not done, paused, or delayed
- 📝 Information gap: no record or cannot be determined; do not include in the main report body, write into the manual supplementation list
Important rules:
- Variance analysis must cover all items in the objective tracking list; internal verification must not be omitted just because the current period summary has no progress explanation.
- If an objective or carryover item from the previous period has no related record in any department document, do not write "no record, pending manual supplementation" into the main report body; write that item into a separate manual supplementation list.
- If the planning document or previous period summary document lists a department plan but the department summary does not cover it, do not force the gap details into the department subsection of the main report; write that gap into the manual supplementation list, and specify the progress, indicators, reasons, time nodes, or owners that need to be supplemented.
- Do not fill blanks based on "common sense" or "inference"
- In the reason column, only write content explicitly mentioned in the document; otherwise leave it blank
Step 4: Generate output files
Output two files according to the following structure, see references/report-template.md。
Key formatting requirements:
- The summary must not exceed 5 sentences
- The main report body does not indicate source files, does not write "Source:", does not write file paths, and does not add parenthetical sources at the end of sentences
- The beginning of the main report does not list source information such as "current period source files", "planning document", "previous period summary document", etc.
- The main report does not set up a "items pending manual supplementation" section; supplementary matters only appear in the manual supplementation list file
- Variance analysis is the core; the main report and manual supplementation list together must completely cover the objective tracking list
- For the report body, refer to
references/report-template.md, adopt a vertical listing structure, and do not use tables - Matters that are required in the planning document or previous period summary document but have no progress explanation in the current period input shall be uniformly written into the manual supplementation list and detailed according to the section they belong to
- Prohibited words: basically completed, on the whole, generally good, steadily advancing, carried out in an orderly manner
4.1 Main report file
Suggested file name:{报告周期}-整体汇报报告.md。
The main report is for direct reporting, requirements:
- Do not indicate sources, and do not include file-name-style citations
- Do not expose the internal verification process
- Do not write gap details into the body
- For gaps, retain only an aggregate-level indication in the summary or notes, for example "there are additionally X information gaps listed in the manual supplementation list"
- Only write progress, variances, risks, and next period plans that existing materials can support
4.2 Manual supplementation list file
Suggested file name:{报告周期}-人工补充清单.md。
The manual supplementation list is used to let relevant personnel complete the materials; each gap must at least clearly state:
- Category: Milestone / Metric / Topic / Department delivery / Risk / Next-period plan / File or data anomaly
- Item name
- Involved department or responsible person (write "To be confirmed" if it cannot be determined from the materials)
- Current gaps: missing progress, result figures, completion status, reason for deviation, time nodes, responsible person, risk handling status, etc.
- Specific content to be supplemented: break it down into answerable questions; do not just write "please supplement"
- Purpose after supplementation: which judgment in the main report it will be used for, e.g., completion status, reason for deviation, next-period risk, metric completion rate
- Suggested priority: High / Medium / Low; mark issues that affect the main report conclusions or the boss's decisions as High
The manual supplementation checklist also does not need source citations; keep only business items, departments, gaps, and questions to be confirmed.
Notes
Handling multiple files for the same department: when the same department has multiple files, merge the content; source information is only for internal verification and is not written into the main report.
Handling file read failures: list the files that cannot be read and the reasons for skipping in "File or data anomaly" in the manual supplementation checklist; do not write them into the main report body.
Handling non-standard formats of planning documents or prior-period summary documents: if the structure is unclear, first list the goal-tracking checklist you parsed, and continue only after the user confirms it.
Report tone: state facts; do not make evaluations. Do not write qualitative descriptions such as "outstanding performance" or "worthy of praise" unless the user explicitly requests it.