using-godmode
From the author
Selects and composes the Godmode skills for a coding task, explains the activation boundary, keeps workflow skills from being skipped when they materially reduce risk, and identifies the task's current engineering lifecycle state. Use when starting a task with Godmode installed, deciding which skill to invoke, recovering a task after context loss, or checking whether a workflow applies. Not a replacement for the selected skill's instructions or for repository-local rules.
Install
npx skills add thiientv/godmode --skill using-godmode -a claude-code
Installs to .claude/skills/using-godmode/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 81
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- plan-modeCodeAlive-AI/ai-driven-developmentUse this skill when the user asks to plan, design, scope, estimate, or implement a feature, bug fix, refactor, migration, integration, API change, UI change, or other project modification. Enforces a planning gate before editing code — investigate project context, analyze the task, surface ambiguities, contradictions, risks, dependencies, and blockers, ask focused questions, produce an evidence-based step-by-step plan, and implement only after explicit user approval. Not for trivial one-line edits, pure questions about the codebase, or changes the user has already reviewed and approved for direct implementation.Planning★ 167
- team-modeoil-oil/codex-team-modeUse when a task may benefit from a bounded subagent for implementation, large-codebase discovery at task start, independent review, requested or pre-commit code simplification, or expert work on complex decisions, modeling, automation, or repeated failures. The main agent chooses whether to delegate and accepts the result. Do not use for simple questions or short work with no meaningful review or delegation.Engineering★ 232
- workflow-routerKerberosClaw/kc_ai_skillsUse when the user is unsure which engineering workflow skill to use: discussion, dispatch or code review, a full spec lifecycle, PRD/ADO, ADR, debugging, documentation, QA or release readiness. Choose the smallest applicable route, explain it, then hand off. The router does not author artifacts or execute tasks itself.Productivity★ 79
- spec-workflowtzachbon/smart-ralphThis skill should be used when the user asks to "build a feature", "create a spec", "start spec-driven development", "run research phase", "generate requirements", "create design", "plan tasks", "implement spec", "check spec status", "triage a feature", "create an epic", "decompose a large feature", or needs guidance on spec-driven development workflow, phase ordering, or epic orchestration.Planning★ 567
- code-explanationNickCrew/Claude-CortexUse when explaining code, concepts, or system behavior to a specific audience level - provides a structured explanation workflow with depth control and validation steps.Engineering★ 66
- workflow-routingcoco-research/cocoUse when starting any task, before invoking any other skill or GSD command, to route between Superpowers skills and GSD commands from project state and task scope. Fires first when both systems are installed.Productivity★ 785
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in