hoklims

Orchestrated coding workflow — the unified entry point for all OCO capabilities. Use when the user types /oco followed by any request, or when a task would benefit from structured orchestration combining code intelligence, impact analysis, verification, and…

Systematic evidence-first bug investigation without a full stacktrace. Auto-activates when the user reports a bug, broken behavior, unexpected results, a regression, something not working, or a problem without a clear error message. Enforces strict workflow:…

Structured refactoring with impact analysis, staged changes, and verification. Auto-activates when the user asks to refactor, rename, restructure, extract, move, reorganize, decouple, or split code. Enforces a strict workflow: impact analysis before any…

Stack trace and runtime error analysis to identify root cause. Auto-activates when the user pastes a stacktrace, traceback, panic, exception, crash, or error with line number. Also detects runtime errors in command output (build, test, run). Enforces…

Mandatory verification suite after any code change. Auto-activates after every source file modification, even trivial ones (one-liner). Detects project type (Cargo.toml, package.json, pyproject.toml, go.mod, .csproj) and runs in order: build → types → lint →…

Systematic evidence-first bug investigation without a full stacktrace. Auto-activates when the user reports a bug, broken behavior, unexpected results, a regression, something not working, or a problem without a clear error message. Enforces strict workflow:…

Structured refactoring with impact analysis, staged changes, and verification. Auto-activates when the user asks to refactor, rename, restructure, extract, move, reorganize, decouple, or split code. Enforces a strict workflow: impact analysis before any…

Orchestrated coding workflow — the unified entry point for all OCO capabilities. Use when the user types /oco followed by any request, or when a task would benefit from structured orchestration combining code intelligence, impact analysis, verification, and…

Use semctx through its MCP tools for top-down root-cause diagnosis, repository impact analysis, authored goals and invariants, proof-carrying change contracts, handoffs, bounded target proposals, and fail-closed migration planning. Use for non-trivial code…

Use semctx through its MCP tools for top-down root-cause diagnosis, repository impact analysis, authored goals and invariants, proof-carrying change contracts, handoffs, bounded target proposals, and fail-closed migration planning. Use for non-trivial code…

Use semctx through its MCP tools for top-down root-cause diagnosis, repository impact analysis, authored goals and invariants, proof-carrying change contracts, handoffs, bounded target proposals, and fail-closed migration planning. Use for non-trivial code…

Carry intent, invariants, decisions, evidence and unknowns through a non-trivial change using the semctx semantic layer. Use when starting substantial work: open or select a change contract, pull a bounded semantic slice, then keep the contract honest as you…

Verify the semantic blast radius of a code change before finishing. Use after any non-trivial edit and before a commit or push: check impacted invariants/contracts and run the recommended tests. Invoke when the user asks to commit, open a PR, or "make sure…

Govern long, uncertain engineering efforts with Codex as the sole lead and Claude Code as a manually isolated executor. Use only when the user explicitly invokes $wayfinder to chart decisions, fog, and frontier; select the next decision; generate a copy-paste…