SpecGraph

Operate the SpecGraph supervisor for bounded refinement, explicit targeted runs, loop mode, gate resolution, split proposal flows, child materialization, and supervisor runtime diagnosis. Use when working in the SpecGraph repository and you need to choose the correct supervisor command, run it safely, interpret outcome or gate state, or continue a spec branch without losing supervisor context.

Apply one approved SpecGraph split proposal into canonical parent and child specs. Use when an explicit split proposal already exists, is ready for application, and the next step is deterministic canonical materialization plus parent-child reconciliation rather than emitting a new proposal.

Reconstruct the current state of one SpecGraph supervisor branch and choose the next bounded step. Use when work resumes after several runs or merges and you need to recover the active parent, child nodes, gates, latest run outcomes, and the most likely next deterministic supervisor action without rereading the whole graph.

Run one explicit SpecGraph supervisor child-materialization pass for a targeted spec when ordinary refinement has reached a clean structural plateau and the next bounded step is to create exactly one new child spec. Use when a node repeatedly returns clean split_required, the remaining concern is nameable, and the run should use operator_note plus run_authority materialize_one_child instead of another ordinary pass.

Inspect and resolve SpecGraph supervisor gate states for one bounded spec. Use when a target is in review_pending, blocked, retry_pending, split_required, or another gate state and you need to decide the next bounded action, prepare a human review decision, or run the correct resolve-gate command.

Detect when a SpecGraph node has reached structural refinement plateau under ordinary supervisor runs. Use when repeated targeted runs keep returning clean split_required or only tiny policy-text changes, and you need to decide whether to switch to child materialization, split proposal flow, or stop further ordinary refinement.

Diagnose whether a SpecGraph supervisor result is a runtime failure or a real spec-structure blocker. Use when a run shows broken YAML, transport or startup issues, timeout residue, noisy stderr, unexpected lifecycle drift, or any case where it is unclear whether the supervisor runtime or the target spec is at fault.

Emit one bounded split proposal for a targeted SpecGraph node when the next correct step is proposal-first decomposition rather than another ordinary refinement or direct child-materialization pass. Use when a node is still structurally oversized, the change exceeds one immediate bounded child step, and canonical spec files should not be mutated directly yet.