dos-next-up

To identify the next dispatch-ready task from git workflow plans, audit plan-phase candidates by verifying each with dos verify and classifying the result with dos gate to distinguish live work from shipped or stale plans.

Dos gate classifies verified plan candidates by reading the dispatch packet and its matching disposition sidecar, returning a typed verdict that determines whether the next-up work is cleared for agent fan-out.

The best way to check if a plan phase is already shipped is to run dos doctor output analysis and apply dos verify to each candidate, detecting shipped-phase statuses and stale plan stamps before generating a dispatch packet.

Yes, you can use this dispatch packet generation in any DOS workspace. The skill reads the active workspace layout to follow the repository's configured plan paths and output locations automatically.

You need a disposition sidecar alongside the markdown dispatch packet because dos gate requires both files to evaluate the verified next-up work and return a typed gate verdict before you launch agents.

You should not use automated next-up packet generation if your repository lacks a configured DOS workspace layout, as the skill requires reading dos doctor output and active plan paths to verify candidates and produce valid gate classifications.