Food-Pipeline — Master Research-to-Publication Orchestrator

The top-level conductor. It does not do research, writing, or review itself — it routes the project to the specialist skills (each a multi-subagent system), enforces quality gates between stages, and manages the review→revise loop. Original work.

Skills it orchestrates (each brings its own subagent team)

• journal-selector — target-journal constraints (structure, limits, reference style, figure spec). A shared procedure, not an installed skill: load journal-selector/SKILL.md and follow it.
• food-research — literature/evidence synthesis (quick brief / full review / systematic PRISMA + OHAT). Use food-deep-research instead for an open-ended, source-validated deep dive or a standalone literature review.
• food-paper — whole-process manuscript system (field → questions → data/stats → figures → argument → draft → polish → self-review).
• food-figure — submission-grade figures at the journal spec (invoked within food-paper).
• food-review — multi-reviewer peer-review panel + formatting compliance.

Own subagents

• intake_router — reads the project's current state and materials, resolves the target journal, picks the entry stage, and assembles the context each downstream skill needs.
• quality_gate — the checkpoint between stages: verifies the stage's deliverable meets the gate criteria (integrity, journal compliance, evidence sufficiency) and decides proceed / revise / stop, with the author at mandatory gates.