document

Solution content generation

Scope

This skill controls document content and figure planning: topic understanding, section writing, detail depth, final narrative quality, and where diagrams should appear in the document.

Use this skill when users ask to write, rewrite, expand, or polish document text. When diagrams would improve comprehension, include clear figure placeholders and diagram specifications in the document content. This skill does not directly edit binary Word/PDF/PPT files; use file-format skills for final document packaging.

Workflow

Request → Plan → Draft → Audit → Refine → Deliver

Language-process constraints (no script orchestration required):

• Request: Restate objective, audience, output type, and constraints before drafting.
• Plan: Build a clear section-level outline with intended depth for each section.
• Draft: Produce a complete first draft (not skeleton bullets) following the plan.
• Audit: Check structure, factual consistency, clarity, actionability, and audience fit.
• Refine: Revise weak sections with concrete detail; remove repetition and vague claims.
• Deliver: Return a polished final version with clear conclusions and next actions when applicable.

Complexity gate (must decide before writing):

• Treat as complex when any of the following is true: multi-section deliverable, high-stakes audience, requested depth is standard/thorough, non-trivial constraints (policy/compliance/format/terminology), or requested length exceeds short memo scope.
• Treat as simple when the request is short, low-risk, single-purpose, and can be completed with one concise pass.

Execution rules:

• For complex tasks, follow all six stages in order and do not skip stages.
• For simple tasks, stage merging is allowed (for example, Request+Plan or Audit+Refine), but the output must still meet quality requirements.
• If information is missing, state assumptions explicitly and continue.
• Keep outputs substantive by default unless the user explicitly requests brevity.
• If the user asks for only one stage (for example, outline only), comply while preserving quality standards for that stage.
• Match the user's language by default unless they request another language.
• Do not fabricate specific facts, metrics, citations, or policy details; mark uncertain items clearly.
• When the document would benefit from a visual, plan the figure location during Plan, draft the surrounding explanation during Draft, and verify every figure has a purpose, title, and source/specification during Audit. See diagram-inserts.md for diagram placement rules and data-chart-inserts.md for data chart planning rules.
• For formal方案/设计文档, require Draw.io diagram sources and exported PNG/SVG assets for all required design figures. Do not use Mermaid. The final document package is incomplete until exported images are embedded in the Word/PDF/PPTX body near their relevant sections.