article-workflow-clean-sources

Article Workflow Clean Sources

这是流程类 Skill，默认仅在用户显式调用 $article-workflow-clean-sources 时运行。

This is Phase 0.5 of the article-workflow-* skill series, corresponding to "oral draft cleaning" in the article optimization workflow overview.

Goal: first correct obvious errors introduced by oral transcription, preventing downstream structural reviews from being disrupted by transcription mistakes. AI only performs cleaning — no polishing, rewriting, structural changes, or opinion processing. The author makes the final call on terminology, style, and uncertain items.

Trigger Scenarios

Use this skill when the user requests:

• Referencing Phase 0.5 to clean oral drafts
• Organizing, cleaning, or correcting .article-workflow/sources/oral-draft/
• Generating .article-workflow/00-cleaned-sources/
• Standardizing proper nouns, capitalization, and obvious transcription errors in oral drafts
• Recording terminology questions or uncertain items from oral draft cleaning

Input and Output

Default input:

• .article-workflow/sources/oral-draft/
• .article-workflow/brief.md

Default output:

• .article-workflow/00-cleaned-sources/*.md: cleaned oral draft text, saved under the original filenames
• .article-workflow/00-cleaned-sources/terminology-notes.md: proper noun corrections, uncertain items, and cleaning boundary records

If the user provides an article directory, first look for .article-workflow/ within that directory. If brief.md is missing, ask whether to proceed; without a brief, only basic transcription cleaning can be done — do not infer the article's terminology system on your own.

Core Principles

• Clean, not polish.
• Preserve the author's speaking style, sentence patterns, tone, and order of ideas.
• Only correct obvious typos, speech recognition errors, proper noun capitalization and spelling, clearly redundant filler words, and basic spacing between Chinese and English text.
• Do not restructure sentences, replace the author's word choices, optimize expressions, delete ideas, or add content.
• Terminology notes are intermediate artifacts, always using terminology-notes.md, to avoid being mistaken for article body text in later phases.
• When uncertain about proper nouns, facts, colloquial style boundaries, or cleaning strategies that affect whole-document consistency, do not guess — proactively ask the author to confirm via dialog before writing into the cleaned draft.
• Terminology notes record confirmed treatments and a small number of low-risk doubtful points; they do not replace proactive confirmation.
• Blockquotes, code blocks, and original excerpts are kept as-is by default, unless the user explicitly requests synchronized corrections.
• By default, standardize issue/issues in body text to Issue/Issues, but do not change blockquotes, code blocks, or original excerpts by default.
• After each round of output, a sub-agent must be launched for goal-alignment review; the sub-agent only provides review opinions, and the main agent decides whether to adopt them.