paper-orchestration

What problem does it solve?

paper-orchestration prevents low-quality “one prompt writes the paper” failures by forcing the controller to detect the current stage, require evidence-driven inputs, and gate drafting through plans, task packets, and reviews.

Core Features & Use Cases

• Stage-detected writing workflow: Automatically classifies work into scope, evidence, method, experiments, drafting, and review stages, then routes to the appropriate next skills.
• Plan-first hard gates: Blocks manuscript text until required planning artifacts exist (project overview, outline, progress, task packet, and—when applicable—chapter architecture).
• Full-paper redraft safety: Locks chapter architecture before drafting and forbids inheriting an outdated chapter split when venue or paper type changes.
• Multi-agent chapter ownership: Enforces one fresh agent per major chapter with disjoint edit ownership, records provenance in plan/chapter-agent-provenance.md, and requires a controller review gate.
• Auditability and quality checks: Requires persistent task packets, two review gates (spec compliance + quality), and a capability-use audit written to plan/progress.md.

Quick Start

Use paper-orchestration when your research-writing task needs a structured, multi-stage controller workflow for a medium or full-paper revision with repeated quality failures.