Menú
Verification gate before claiming any work is complete. Use before committing, creating a PR, or reporting "done".
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
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.
Task graph management for a session. Use to create tasks, track progress, execute the next unblocked task, or manage dependencies between work items.
| name | godmode-verify |
| description | Verification gate before claiming any work is complete. Use before committing, creating a PR, or reporting "done". |
Rule: Evidence before claims, always. No completion claim without fresh verification output.
"NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE."
Before saying any task is done:
cargo nextest run -p <crate> # all tests green
cargo clippy -p <crate> -- -D warnings # zero warnings
cargo fmt --check # no formatting diff
git log --oneline -3 # commits present
For workspace-level completion:
cargo nextest run --workspace
cargo clippy --workspace -- -D warnings
Never trust a subagent's self-report without independent verification. Run the verification commands yourself after a subagent claims completion.
git log --oneline -5 # empty list = subagent did not finish