Claude Skills
SkillsResultsReplayCollectionsGuidesNominate
© 2026 Curated Agent SkillsBrowse skillsHistorical indexAbout this guide·Learn more about Agent Skills
← All curated skills

Debugging · Jesse Vincent

Systematic Debugging by Jesse Vincent

Runs a four-phase root-cause process and treats symptom fixes as failures.

View original skill instructionsJesse Vincent Superpowers

Setup and compatibility

Part of Jesse Vincent Superpowers. The methodology is deliberately heavy. Brainstorming, chunked design review, and a full written plan add real friction to small or already-clear changes, and the automatic skill-invocation rule can feel rigid. Its richest behavior assumes a harness with subagents, hooks, and a plugin marketplace, so the experience is uneven across agents even though the skills themselves travel well.

Editorial compatibility guidance: Claude Code · Codex · Cursor · Gemini CLI. This is not an executed compatibility test; see the review for source and run evidence.

Read Systematic Debugging instructions and prerequisites · Read Jesse Vincent Superpowers setup documentation

Independent review

A four-phase root-cause process that treats symptom fixes as failures. It forces the agent to reproduce, isolate, understand, and only then change code, which is exactly the discipline most agents skip when they start guessing at a fix.

Read the Systematic Debugging review and usage guide

Try this skill

InstallGet starter request

Install · Collection / plugin

Run in Claude Code chat. Installs the whole Superpowers plugin: the methodology, other skills and harness integration. Install separately for each agent. Scope is chosen by the agent plugin manager.

/plugin install superpowers@claude-plugins-official

Command / route checked 30 October 2026. Upstream installation

Setup requirements and caveats

Run in Claude Code chat. Installs the whole Superpowers plugin: the methodology, other skills and harness integration. Install separately for each agent. Scope is chosen by the agent plugin manager.

Node.js with node:test; standard patch utility

These are documented requirements; installation has not been tested here.

Your agent needs its own account, runtime and model access. Usage charges depend on your plan; unrecorded costs are unknown.

Recorded outside costs:
  • Existing Codex account; incremental charges were not measured

Run the example

Start a fresh session in the target project. Provide the relevant files or diff. This is the review’s example request, not a record of your execution.

Use the systematic-debugging skill. Find the root cause of intermittent webhook timeouts without editing production code until the failing path is isolated.

Check your result · Successful first run

A reproduction and evidence-backed root cause before a patch is proposed.

Confirm the agent loaded the named skill, inspect the output and run the relevant checks. Installation alone does not prove a successful run.

Something not working?

The skill is missing from my agent

Check that the skill is installed for the selected agent and project/global scope. Open a fresh session in that project and check the agent’s skill list. Plugin installs may also need to be enabled.

The wrong skill runs, or nothing happens

Start a fresh conversation, explicitly name the skill using the request above, and provide the requested inputs. Ask the agent to confirm which skill it loaded. Check for duplicate installed copies or overlapping instructions.

The skill runs but the result is poor

Compare the result with the successful-first-run check above. Supply the missing files, reproduction steps or constraints, then ask for one focused correction. If the skill addresses a different problem, return to the task guide and compare alternatives.

Installation troubleshooting · missing dependencies

If npx fails, check the Node/npm versions in setup requirements, Git and network access. For skills CLI installs, run npx skills list (add -g for global). If a route changed, follow upstream instructions.

Collection background and tradeoffs

The methodology is deliberately heavy. Brainstorming, chunked design review, and a full written plan add real friction to small or already-clear changes, and the automatic skill-invocation rule can feel rigid. Its richest behavior assumes a harness with subagents, hooks, and a plugin marketplace, so the experience is uneven across agents even though the skills themselves travel well.

Source maintained by Jesse Vincent. Read original skill. Compatibility guidance and published showcase runs remain separate from your first run.

Inspect the recorded Systematic Debugging example and its limitations

Related workflows

  • Systematic Debugging