graph

# Graph Skill Run a deterministic orchestration graph from a declarative JSON descriptor. The runtime consumes the sealed-descriptor and pure-scheduler contracts in `src/graph/*` and executes through an independent OS process (`omc graph run`), so crash recovery (kill mid-run, rerun, resume from journal) works for real. ## Usage ``` /oh-my-claudecode:graph <descriptor.json> /oh-my-claudecode:graph "build then test then ask me before deploy" (author the descriptor first) ``` The execution surface is always the CLI subcommand: omc graph run <descriptor.json> [--runs-root <dir>] Run it via the Bash tool for non-interactive graphs. Progress lines stream as `[run]`, `[node]`, `[ok]`, `[fail]`, `[join]`, `[done]`. ## When To Use - Repeatable multi-step pipelines with explicit dependencies (DAG) - Work that must survive interruption: kill/restart resumes from journal - Auditable runs: OCC journal + projection snapshots under `.omc/graph-runs/<run_id>/` When NOT to use: exploratory one-off work (use conversation or /team); anything needing adaptive re-planning mid-run (graphs are deterministic). ## Workflow 1. **Descriptor given** -> go to step 3. 2. **Pipeline described** -> author the descriptor JSON (schema below), write it next to the project (suggest `.omc/graphs/<name>.json`) and show it to the user before running. `run_id` must be unique per logical pipeline; rerunning with the same `run_id` RESUMES, not restarts. 3. **Approval nodes**: if the descrip...