using-godmode

# Using Godmode Treat the catalog as a set of working agreements, not a command list. Choose the smallest set of skills that changes the outcome of the task, then load the selected skill before acting on its responsibility. ## Select by task state - Ambiguous or consequential new work: `solution-design`, then `implementation-planning`. - An approved plan: `plan-execution`; add `test-driven-development` when code behavior changes. - A bug, failure, regression, or unexplained result: `root-cause-debugging`. - A code or configuration change ready for another set of eyes: `requesting-code-review` or `receiving-code-review` as appropriate. - A completion claim: `completion-verification`. - A visual or interaction change: `frontend-design` or `ui-ux-review`. - An unfamiliar or cross-cutting repository: `codebase-orientation`. - A version-sensitive external decision: `technical-research`. - A compatibility or state transition: `safe-migrations`. - A production rollout: `release-engineering`; active user impact switches ownership to `incident-response`. - A runnable public acceptance contract: `behavior-validation`. - A prompt, skill, tool, or agent quality claim: `agent-evaluation`. - Structural friction: `architecture-review`; local behavior-preserving cleanup: `code-simplification`. Add domain skills only when their boundary is present: API contracts, database schema, security risk, performance measurement, browser behavior, testing strategy, documentation decisions, o...