Menu
Migrate legacy lifecycle state into darkrun's .darkrun/ StateStore — always dry-run first, get explicit approval, then apply one Run at a time
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Start a new darkrun Run — describe what you want to accomplish and the factory manager scaffolds a right-sized lifecycle for it
Create a composite Run combining stations from multiple factories with sync points
Configure darkrun for this project — auto-detect VCS, hosting, CI/CD, and default branch, confirm with the user, and write .darkrun/settings.yml
Parking lot for ideas not yet ready to become a Run — add, list, review, or promote a backlog item into a Run
Review and decide a Station's Checkpoint — approve to advance the Run, or request changes to route rework as drift
Run a Run lights-out in dark mode — pre-elaborate the work up front, then advance Station to Station without stopping for review, pausing only on external/await gates and ambiguity
| name | darkrun-migrate |
| description | Migrate legacy lifecycle state into darkrun's .darkrun/ StateStore — always dry-run first, get explicit approval, then apply one Run at a time |
Convert legacy state with darkrun migrate <slug> — dry-run is the default. Show the dry-run output and get the user's explicit OK before darkrun migrate <slug> --apply. One slug at a time unless the user approves --all; never pass --allow-dirty without approval. Then suggest /darkrun:darkrun-resume <slug> to resume. See darkrun migrate --help for flags.
