claude-dagq

Register and inspect dagq goals and tasks through the locally built dagq binary. Use when the user brings a development problem to queue for dagq (register it as a goal, decompose it into tasks with title, description, acceptance criteria, verification commands, dependencies and context), make tasks ready, list goals or tasks, check a goal's progress or a task's status or run result, close a goal after reviewing its tasks' receipts and follow_ups, adopt or reject a draft goal, record or read notes (observations), or find the dagq binary and queue database.

Read the supervisor's review verdict of a dagq run (it lands a pass, sends revise to the live session and turns a concern into an approve_landing ask whose answer it applies). Only for a run whose headless review failed ("review by hand") or that predates it ("review and integrate"), review it in a subagent from the review.md file that review ID writes and land it with integrate (which also pushes main) when it passes; on doubt register an approve_landing ask, which the supervisor then applies. Use when status or watch reports "review by hand" or "review and integrate", or when asked to review, integrate, land, or push a finished dagq task. "reviewing (runtime)" needs nothing. A needs_session run is resumed (and, once integrate was called, landed) by the runtime; only one it gave up on is the dagq-session skill's. Not for a stuck integrating lease (dagq-recover).

Diagnose and recover one dagq run that is stuck, that its supervisor gave up on, whose supervisor or integrate process died, or that stays claimed/starting/running/validating/integrating after its process ended, without disturbing the runs executing next to it. Use when status or watch shows an attention with next "recover run", when the user reports an orphaned run, a run with last_error and no lease, a stale supervisor in status or doctor, a run stuck in integrating, or asks to recover or retry a run.