cn-project-report

name: cn-project-report description: Draft and format Chinese horizontal-project technical reports in 中文项目报告 style. Use when users ask for 项目报告/技术报告 style imitation, structured Chinese engineering writing, report templates, Word typography rules, formula numbering with right-aligned equation numbers, figure/table caption规范, references with cross-references, TOC generation, or stable Word-native PDF export. Also use for large/complex reports that need a butler-style multi-session production line with staged decomposition from research to writing to typesetting and final merge/review.

中文项目报告

Always load references/style-spec.md first. For format/template tasks, also load references/layout-spec.md and references/word-pdf-pipeline.md. Use assets/中文项目报告模板_子课题风格_交叉引用版_v6.docx as the baseline template when users ask for direct Word deliverables. For style-learning from sample reports, also load references/workflow.md. For large or complex report delivery, also load references/production-line.md.

Execution Rules

0. For large tasks, run production-line orchestration.

• Use the butler workflow from references/production-line.md.
• Split work into independent sub-sessions: research -> writing -> typesetting -> merge/review.
• Keep each sub-session prompt precise, with explicit deliverables and acceptance checks.

1. Define scope first.

• Separate style transfer from fact transfer.
• Reuse writing style and formatting rules, never copy project-specific conclusions.

2. Build report structure before drafting.

• Use heading hierarchy by default: 1 -> 1.1 -> 1.1.1.
• Keep progression stable: background -> mechanism -> comparison/constraint -> implementation -> summary.

3. Write paragraphs with engineering logic.

• Start with a claim sentence.
• Add mechanism/process explanation.
• Add boundary, trade-off, or risk constraint.
• End key paragraphs/sections with a convergence sentence.
• In multi-session runs, cite using stable placeholder ids first (for example BIBREF12), then resolve to final cross-references during typesetting.

4. Apply layout standards when delivering Word/PDF.

• Follow references/layout-spec.md for body, heading, formula, table, figure, references, and TOC rules.
• Keep formulas editable (OMML), not image-based fallback.
• Keep table captions above tables and figure captions below figures.
• Trim large blank margins of sourced web images before insertion so figures fit the text area.
• Keep bibliography paragraphs with no first-line indent (正文缩进, 参考文献不缩进).

5. Export and verify.

• Use Word-native PDF export path from references/word-pdf-pipeline.md.
• Handle Word field-update popup by choosing 是(Y) before export when it appears.
• Verify Word/PDF version consistency before delivery.
• Avoid LibreOffice PDF export for this skill when strict layout is required.

6. Run final check.

• Check structure completeness and language consistency.
• Check formula numbering alignment, table overflow, caption placement, reference cross-links, TOC updates.
• For long formulas, verify equation number parentheses are not split across lines; if split appears, apply the layout-spec width fix and re-export.
• Check cleanup rules: keep final deliverables only when requested.

Output Modes

• mode=direct-write: write report text in this style.
• mode=style-brief: output concise style/format checklist.
• mode=template-build: produce report template with required elements.
• mode=normalize: rewrite user text into this style while preserving meaning.
• mode=production-line: run butler-style multi-session pipeline for large report delivery.