审稿校对word报告

概述

plan-proofread: formal Chinese document proofreading

Use this skill as a professional proofreading workflow for formal Chinese reports. Focus on concrete problems, direct replacement suggestions, and delivery-risk items that would prevent the document from being submitted.

Safety boundary: this skill only analyzes user-provided documents and supporting materials. Bundled scripts are local read-only helpers; they do not send network requests, modify the source file, or access protected system locations.

Scope

• Enterprise development plans and strategic plans
• Feasibility study reports and bidding documents
• Board-ready or committee-ready formal reports
• Chinese long-form deliverables that need wording, formatting, punctuation, data, and table-of-contents review

Do not use this skill for fiction, poetry, scripts, or purely creative writing unless the user explicitly asks for formal proofreading only.

Bundled Resources

Scripts live in scripts/:

• check_punctuation.py: scans common Chinese punctuation issues in .docx files.
• check_text_table_consistency.py: compares nearby text and tables for numeric consistency in .docx files.
• check_toc_and_pagination.py: checks table-of-contents entries, headings, chapter numbering, and page-number format in .docx files.
• check_data_sources.py: scans .docx files for data points without source attribution, vague attribution, and bare data; outputs "vague attribution (must fix)" and "suspected missing source (to confirm)" lists.

The scripts require python-docx. Run them only on user-provided .docx files, and treat their output as an initial screening that still needs human judgment.

References live in references/:

• public-sector-compliance-review.md: public-sector and enterprise formal wording compliance review.
• punctuation-rules.md: Chinese punctuation rules and common AI-draft punctuation issues.
• toc-and-pagination-rules.md: table-of-contents and page-number failure patterns.
• text-table-consistency.md: text-table consistency patterns and a five-step checking method.
• error-categories-27.md: error taxonomy for tagging findings (30 categories including data-source types).
• publication-standards.md: quantitative error-rate and quality-rating reference.
• data-source-verification.md: data source provenance verification guide, including the "five-type source qualification" standard, vague attribution blacklist, and optional online verification rules.

Format Standards

Before proofreading, identify the applicable format standard:

If standards conflict, follow the user-specified priority order. If no standard is specified, use Bowei V2.6 as the default.

Review Modes

Workflow

Step 1: Read the document

1. Identify the input type: .docx, .md, .txt, .pdf, or folder.
2. Read the content using an appropriate tool.
3. If no file is available, ask the user to provide one.

For long documents, build a chapter index first. Review by chapter and maintain a short cross-chapter memo containing full-name/abbreviation pairs, data definitions, recurring indicators, and strategic-framework terms.

Step 2: Build a framework summary

For full review, output a short review frame:

1. Document type
2. Planning or reporting period
3. Applicable format standard
4. Core strategic framework and abbreviations
5. Chapter index and table/figure count
6. Approximate length and segmentation plan
7. Main risk directions to inspect

Step 3: Review by priority

Review high-risk issues first, then language and formatting.

If a statement cannot be verified from the document or user-provided materials, mark it as 待确认 instead of inventing a correction.

Step 4: Text-table consistency check

For documents with tables or figures, check every table and nearby paragraph:

1. Build a table/figure list with number, title, indicator, unit, period, totals, and percentage columns.
2. Extract the nearby text window: five paragraphs before and two paragraphs after the table.
3. Map numbers both ways: table to text and text to table.
4. Check internal table consistency: totals, percentage sums, and obvious unit conflicts.
5. Compare repeated indicators across chapters.

Use check_text_table_consistency.py as an initial screening for .docx files, then manually confirm each finding.

Step 4.5: Data source provenance check

For documents containing statistics, rankings, benchmarks, predictions, or "research shows…" claims, run a data source verification scan. Read references/data-source-verification.md for full rules.

The Iron Rule: Every data point (statistic, ratio, ranking, benchmark, prediction, "research shows…") must be traceable. Five qualification types — any one suffices: (1) named source, (2) footnote, (3) parenthetical citation, (4) scope/caliber declaration, (5) calculation reference. Bare data and vague attribution ("据相关数据显示""业内通行""网传") are always flagged.

Run the script:

C:UsersLenovo.workbuddybinariespythonenvsdefaultScriptspython.exe 
    ~/.workbuddy/skills/plan-proofread/scripts/check_data_sources.py 
    report.docx --out data_source_report.md

The script outputs two actionable lists:

• Vague attribution (必改): data points using blacklisted phrases — must add explicit source or downgrade to 【估算】
• Suspected missing source (待确认): bare data with no attribution — confirm each, then add source, mark 【估算】, or rewrite

Optional online verification: For a small number of key data points that (a) support core conclusions and (b) are publicly verifiable, use WebSearch to cross-check against National Bureau of Statistics, yearbooks, or listed-company announcements. Never search for client real operating data or unpublished data — confidentiality red line.

Step 5: Output the issue list

Output findings chapter by chapter. Sort by severity first.

Use this format:

【#序号】位置：章节/段落首句
原文："……"
类型：XX | 程度：必改/建议优化/待确认
问题：……
改为："……"

For simple issues, a compressed line is acceptable:

【#序号】位置 | 类型 | "原文" -> "修改后" | 必改

Allowed issue types:

错别字 · 漏字别字 · 标点错误 · 数字格式错误 · 语病 · 术语不规范 · 名称简称不统一 · 政策引用不准确 · 法律条文存疑 · 规划周期混淆 · 上下文逻辑不一致 · 表述过满 · 语言口语化 · AI写作痕迹 · 图表编号错误 · 图表标题位置不规范 · 页码目录不一致 · 排版格式问题 · 内容缺失 · 风险考虑不足 · 目标不量化 · 战略逻辑脱节 · 文表数据不一致 · 表内合计加和错 · 占比合计不等于100% · 单位量纲错配 · 口径同名不同义 · 改稿残留 · 合规用语待确认 · 数据缺来源 · 来源模糊 · 来源过时

Step 6: Output three summaries

After the detailed list, provide:

• 必改问题清单
• 建议优化清单
• 待确认清单

Step 7: Optional scoring and quality rating

For full review, use publication-standards.md as a reference to calculate:

• approximate checked characters
• number of mandatory corrections
• de-duplicated error count
• error rate per 10,000 characters
• quality rating and delivery suggestion

Quality ratings are advisory. Do not present them as a legal or regulatory judgment.

Step 8: Final self-check

Before delivering:

1. Recheck cross-chapter consistency.
2. Confirm high-risk dimensions were not skipped.
3. Remove overconfident findings that should be 待确认.
4. Run text-table, punctuation, table-of-contents, and data-source scripts when the input is .docx and the user asked for a full check.
5. Data source self-check: confirm no vague-attribution items remain unfixed; confirm all bare data points have been addressed (source added, marked 【估算】, or rewritten); confirm no client confidential data was searched online.
6. Remind the user to refresh the table of contents and fields in Word before final submission.

Quick Rules

• Chapter numbering: 一、 -> （一） -> 1. -> （1）.
• Use full-width punctuation in Chinese paragraphs.
• Use an em dash for year ranges, for example 2026—2030年.
• Repeat the percent sign in ranges: 15%～30%, not 15～30%.
• Quote planning-period names consistently.
• Use six-corner brackets for official document numbers, for example 国发〔2025〕1号.
• Figure titles go below figures; table titles go above tables.
• Do not add punctuation after attachment names.
• Prefer 其他; use 截至 as a preposition.
• Every number cited in text should be checked against its source table or figure.
• Data source iron rule: Every data point must be traceable — named source, footnote, parenthetical citation, scope declaration, or calculation reference (any one suffices). Bare data and vague attribution ("据相关数据显示""业内通行""网传") must be flagged and either given a source or downgraded to 【估算】.
• Before submission, refresh the full table of contents and all fields in Word, then export PDF and inspect the table-of-contents pages.

Style Review Standards

Preferred style: formal, accurate, concise, conclusion-led, and stable.

Flag these patterns:

Execution Preferences

1. Prioritize concrete delivery-risk issues.
2. Use stable formal wording; do not over-polish into marketing language.
3. Align the whole document with its stated strategic framework.
4. Give replacement text whenever possible.
5. Mark unverifiable items as 待确认.

Reference Index

Source Inspirations

Use these inspirations as general product-pattern references only. Do not cite them as evidence unless the current task requires verified sourcing.