Menu
Task graph management for a session. Use to create tasks, track progress, execute the next unblocked task, or manage dependencies between work items.
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
Write an implementation plan as a markdown file, then immediately serialize it to a timestamped YAML task file in .ctx/tasks/. Use before touching any code when given a spec or approved design.
Design-first workflow for new features, components, or architecture decisions. Use before writing any code — get explicit approval on a design first.
Commit-and-push workflow with validation. Use when asked to "cap", "commit and push", or "ship it".
Systematic debugging for Rust. Use before proposing any fix — establish root cause first, then write a failing test, then fix.
Dispatch parallel subagents for independent tasks. Use when 2+ tasks have no shared state or sequential dependencies.
Test-driven development workflow for Rust. Use before writing any implementation code — write a failing test first, then implement, then refactor.
| name | godmode-tasks |
| description | Task graph management for a session. Use to create tasks, track progress, execute the next unblocked task, or manage dependencies between work items. |
Godmode maintains a task graph at .ctx/GODMODE.tasks.yaml via the godmode CLI. Tasks
persist across sessions, encode causal dependencies, and drive sequential or parallel
execution. Never edit the YAML directly — always use the CLI.
godmode handon # running, next runnable, blocked, next doob todo
godmode task next # next runnable task(s)
godmode task next --json # machine-readable — exit 1 if empty
godmode handoff # warns on running tasks, calls hj handoff
# Ingest from a plan doc
godmode plan ingest docs/plans/YYYY-MM-DD-<feature>.md
# Add manually
godmode task add <id> "<title>" [--depends-on t1,t2] [--crate-name <crate>]
# Lifecycle
godmode task start <id>
godmode task done <id> [--commit <sha>] [--notes "<text>"]
godmode task block <id> "<reason>"
godmode task unblock <id>
# List
godmode task list # human table
godmode task list --json # full JSON — exit 1 if empty
depends_on entries have status: done.godmode-parallel.godmode dispatch [--max 5] --json
Emits independent chains shaped for parallel agents. Each chain targets one crate.
godmode plan ingest docs/plans/2026-05-01-my-feature.md
godmode handon
godmode task start t1
# implement...
godmode task done t1 --commit abc1234
godmode task next # → t2 is now runnable
godmode task start t2
# ...
godmode handoff