Editorial Pipeline

Apply a sequence of focused editorial refinements to a draft, passing output from each stage as input to the next. The pipeline reads 7 agent prompts from ./agents/ and applies cross-cutting constraints from ./rules/ to preserve author voice, maintain detail level, and track changes.

When to use

• User asks to "polish this draft" or run iterative multi-pass editing
• Draft needs systematic refinement (typos → UK English → flow → headings → fact-checking → sources → SEO)
• User wants to inspect intermediate outputs and decide which stages to run or reorder
• Prose requires cross-cutting consistency (voice, detail, structure)

Inputs to gather

• Draft text — the source document to refine (paste, file, or workspace reference)
• Workspace path — which content-writing workspace to write intermediates to (user must have provisioned via /content-writing:new-workspace)
• Draft name — short slug for the working subdirectory (e.g., blog-post-v1, opinion-piece-draft)
• Stages to run (optional) — default is all 7 in order; user may skip, reorder, or stop early
• Author voice / style notes (optional) — guidance from rules/author-voice.md to preserve tone and register