think

Generate a validated .godmode/spec.md with up to three implementation approaches.

26|8|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/arbazkhan971/godmode --skill think-arbazkhan971
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: think
Source: https://github.com/arbazkhan971/godmode/tree/main/skills/think
Command: npx skills add https://github.com/arbazkhan971/godmode --skill think-arbazkhan971

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designs a clear, testable implementation plan when a feature or change is requested and no existing spec exists, reducing ambiguity and wasted engineering cycles.

Core Features & Use Cases

  • Codebase scan and discovery: Automatically inspect repository entry points, recent changes, types, and tests to ground design decisions.
  • Approach generation and selection: Produce 2–3 viable implementation approaches with pros, cons, file impact estimates, and a single recommended approach.
  • Spec authoring and validation: Write a concise .godmode/spec.md with a shell-command success criterion, verify referenced paths, and commit the spec under project rules.
  • Use Case: When asked to add a new API endpoint, produce a spec that lists files to modify/create, a concrete testable success command, and mitigation for top risks.

Quick Start

Ask the agent: /godmode:think with a one-sentence goal and receive a validated .godmode/spec.md ready for commit.

Frequently Asked Questions about think

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a validated implementation spec for a new feature?

To create a validated implementation spec, you can trigger an exploratory design session to scan your codebase, generate viable approaches, and commit a concise spec under 100 lines with a shell-command success criterion.

What is the best way to compare implementation approaches before modifying a codebase?

Comparing implementation approaches involves generating 2-3 viable options with pros, cons, and file impact estimates, followed by selecting a single recommended approach to guide your development.

Can I use a codebase scan to ground design decisions for a new API endpoint?

Yes, a codebase scan automatically inspects repository entry points, recent changes, types, and tests to ground design decisions when planning a new API endpoint or feature modification.

Do I need an existing spec.md file to start an exploratory design session?

No, you do not need an existing spec file; an exploratory design session applies when no existing spec.md exists or when a rethink gate is triggered for your project.

What limitations exist when authoring a spec under project rules?

Spec authoring is constrained to under 100 lines, requires verifying referenced file paths and parent directories, and must enforce a shell-command success criterion to ensure testability.

Why does my implementation plan lack a testable success criterion?

Your implementation plan lacks testability if the generated spec does not enforce a shell-command success criterion, which is required to validate the proposed feature change.