Orchestrate Paper

The conductor. The author brings a technical idea, their experiments, and a target — a venue, or "help me pick one." This skill sets the goal ("submission-ready for venue X by deadline D") and runs a goal → plan → execute → verify → reflect loop across the whole lifecycle: it plans which sub-skills run and in what order, invokes them, checkpoints with the author at every stage gate, and uses external, measurable signals — not its own say-so — to confirm each stage actually moved the paper forward before going on.

It does not write the paper for the author and it never submits anything. It coordinates the specialists (each of which is its own skill) and keeps a durable, reviewable record in paper-workspace/ so the author can pause, inspect, reject, and resume at any point.

This skill follows a few non-negotiable working principles at every checkpoint: name assumptions, show competing readings, surface tradeoffs, stop when confused, verify live, and keep the author the author.