article-writer

Article content generation

Scope

This skill controls text content only: topic understanding, section writing, detail depth, and final narrative quality.

Use this skill when users ask to write, rewrite, expand, or polish document text.

Do not use this skill for OOXML structure editing, Word styling, table rendering, PDF conversion, or page layout operations.

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. Include subheadings when they improve structure and readability. Example (structure only):
  1. Background 1.1 Current state 1.2 Key pain points
  2. Objectives
  3. Proposed solution 3.1 Core approach 3.2 Implementation steps
  4. Risks and mitigations
  5. Expected outcomes and next steps
• 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.
• Output policy: Only the Deliver stage content should be output to the user or written to files. All other stage notes are internal only and must not appear in the final output.
• Structure fidelity: The Deliver content must follow the section structure finalized in Plan (same order, headings, and subheadings). If the plan is adjusted during drafting, update it internally and keep the deliver structure aligned.