| name | publication-pipeline |
| description | Three-round editorial review before publication. |
| metadata | {"owner":"dazza","version":"1.0","weight":"heavy"} |
Publication Pipeline
Purpose
Rigorous three-round review process for high-stakes content.
Default roster: use Claude Code and Codex peers. Do not assign Gemini CLI,
Antigravity CLI, or Antigravity Desktop unless the human prompt explicitly
selects that peer.
Roles
DRAFTER - Creates and revises the document
REVIEWER - Reviews for technical accuracy
REDTEAM - Attacks for weaknesses and gaps
ANALYST - Strategic/political analysis of implications
EDITOR - Copy-edit against style guide
PUBLISHER - Final approval authority
Protocol
ROUND 1: Review + Red Team
- DRAFTER creates initial draft
- REVIEWER checks technical accuracy, suggests improvements
- REDTEAM attacks: What's wrong? What's missing? What could backfire?
- DRAFTER revises based on both feedbacks
ROUND 2: Political/Strategic Analysis
- ANALYST reviews: Who are the audiences? What are the implications?
- DRAFTER addresses strategic concerns
ROUND 3: Copy-Edit
- EDITOR checks style, grammar, tone, formatting
- DRAFTER makes final fixes
- PUBLISHER reviews and signals [APPROVE] or [REJECT]
Termination
PUBLISHER signals [APPROVE] to complete. [REJECT] sends back to DRAFTER.
Optional Inputs
output - Path for final deliverable
work - Path to work.md with project context
max_turns - Override default (50 for heavy skills)
Example Prompt
Use publication-pipeline to publish the quarterly report.
Read work.md first: projects/q4-report/work.md
DRAFTER=CC, REVIEWER=CX, REDTEAM=CC-peer-02, ANALYST=CX, EDITOR=CC-peer-02, PUBLISHER=CC.
Output: projects/q4-report/final.md