33-Strategies

Methodical Debug — Development skill for Claude Code

Development community

Please take a methodical, hypothesis-driven approach to debugging this issue.

How to install Methodical Debug

Installs to ~/.claude/commands/33-strategies-33-strategies-claude-code-starter-kit-methodical-debug.md

Terminal

mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/33-Strategies/33-strategies-claude-code-starter-kit/HEAD/.claude/commands/methodical-debug.md -o ~/.claude/commands/33-strategies-33-strategies-claude-code-starter-kit-methodical-debug.md

Restart Claude Code, or start a new session, for it to be picked up.

What Methodical Debug does

Please take a methodical, hypothesis-driven approach to debugging this issue:

**Review & Understand**: Use @task-context to guide a deep read all relevant docs, developer guides, READMEs, config files, and reference materials to build a complete mental model of the intended behavior. Pay attention to expected data shapes, dependencies, environment requirements, and any known edge cases.
**Map the Expected Flow**: Create a detailed, step-by-step articulation of what SHOULD happen—trace th

Alternatives in Development

Quick Plan — Create a detailed implementation plan based on the user's requirements provided through the USER_PROMPT variab 3.4k ★
Octo Debug — Systematic debugging with methodical problem investigation 2.8k ★
Rev Requirements — 既存のコードベースから要件定義書を逆生成します 974 ★