Article Pipeline Master
Overview
Run a full, ordered article workflow and return stage-by-stage results with a final publish recommendation.
Trigger Examples
- •"Прогони полный цикл для этого черновика."
- •"Сделай pipeline: структура, стиль, фактчек, финальная проверка, репак."
- •"Нужен один проход от идеи до постов по каналам."
Required Skills
Use these skills in this exact order:
- •
article-outline - •
style-editor-ru - •
fact-check-citations - •
publication-checklist - •
repurpose-content
If any required skill is missing, continue with available stages and report what was skipped.
Pipeline Modes
Choose mode based on user intent:
- •
full: run all 5 stages. - •
draft-only: run stages 1-2. - •
verification: run stages 3-4. - •
distribution: run stage 5 (requires near-final source text).
Use full when mode is unspecified.
Stage Execution Rules
- •Outline
- •Build or refactor structure.
- •Output working title, thesis, and section flow.
- •Style edit (RU)
- •Improve clarity and rhythm.
- •Preserve meaning and factual content.
- •Fact-check + citations
- •Verify factual claims.
- •Mark status/confidence per claim.
- •Prepublish QA
- •Return go/no-go with blockers first.
- •Repurpose
- •Generate channel outputs with consistent message and CTA.
Handoff Contract Between Stages
- •Stage 2 must preserve structure intent from Stage 1.
- •Stage 3 checks Stage 2 text only.
- •Stage 4 checks Stage 3-corrected version.
- •Stage 5 uses Stage 4-approved text (or clearly marks unresolved risks).
Output Format
Return sections in order:
- •
Pipeline mode - •
Stage results - •
Blocking issues - •
Final verdict - •
Distribution assets(only if stage 5 executed)
In Stage results, include one concise subsection per stage with:
- •
Input - •
Key output - •
Risks - •
Next action
Read references/pipeline-profiles.md to apply the correct mode profile and minimum outputs.