Paper Lifecycle Orchestrator

Drive a paper from idea to released artifact. The job is to know what stage the project is in, what the next decision is, and which singleton to hand to — and to gate transitions so the paper doesn't march forward on a weak foundation (no writing before the contribution is stable; no scaling before the claim is isolated). This file owns sequencing and gates only; it never does the ideation, experiments, or prose itself.

For one isolated stage, skip the orchestrator and invoke that skill directly. Use this when the user wants the whole path managed.

Before You Start: Locate the Project

Ask only what you can't infer. You need:

• Current stage — idea, lit review, experiments running, results in hand, drafting, under review, accepted. This sets the entry point; most projects don't start at stage 1.
• The intended contribution — even one rough sentence. The whole pipeline is in service of making one claim defensible.
• Target venue / deadline — shapes scope, baseline bar, and how much to invest at each stage.

If the contribution can't be stated at all yet, start at stage 1. If it's stated but shaky, start at stage 2.

The Pipeline

Run in order; enter at the project's actual stage and resume from the last unmet gate.