systematic-debugging

systematic-debugging: What this skill does

systematic-debugging is a reusable agent skill listed on skills.sh under obra/superpowers. skills.sh rank #113, installs 93.2K, GitHub stars 204.9K, first seen Jan 19, 2026.

Structured debugging methodology that mandates root cause investigation before attempting any fixes. Four-phase process: root cause investigation, pattern analysis, hypothesis testing, and implementation with mandatory test cases Requires completing Phase 1 (evidence gathering, error analysis, data flow tracing) before proposing any fixes; blocks symptom-based patching Includes diagnostic instrumentation guidance for multi-component systems and backward call-stack tracing techniques to isolate failure points Enforces stopping and questioning architecture after three failed fix attempts, treating repeated failures as a sign of fundamental design problems rather than implementation issues

When to use it

• Use this skill when the task matches the package name, repository context, or skills.sh topic: Agent workflows.
• Prefer it when a repeatable workflow is better than a one-off prompt: setup, review, design, deployment, automation, research, media generation, or operational checks.
• For production work, read the linked repository and install command before allowing the agent to run scripts or modify files.

How an agent should use it

1. Confirm the user intent and whether this skill is the right fit.
2. Install or inspect the skill with the official command from skills.sh.
3. Read the local SKILL.md and only load extra files referenced by that skill.
4. Follow the skill's workflow, then verify the result with tests, screenshots, audits, or source-backed checks as appropriate.
5. Record any constraints, missing credentials, tool permissions, or security warnings before handoff.

Quality and safety checks

• Check repository ownership and source reputation: obra/superpowers.
• Review security audit signals before installing; skills.sh reports: Gen Agent Trust Hub Pass Socket Pass Snyk Pass.
• Never grant broad shell, browser, cloud, or deployment permissions without user approval.
• Treat generated output as draft until validated by the skill's own acceptance criteria.
• If the skill touches cloud resources, costs, credentials, customer data, or production deploys, require a human review step.

Sources and install

• skills.sh page: https://www.skills.sh/obra/superpowers/systematic-debugging
• Repository: https://github.com/obra/superpowers
• Install command: npx skills add https://github.com/obra/superpowers --skill systematic-debugging

FAQ

Is systematic-debugging an agent, a prompt, or a skill?
It is a skill: a reusable package of task-specific instructions and supporting files that an agent can load when the user's request matches the workflow.

Should I install it automatically?
Only after checking the repository, install command, audit status, and whether the user wants this capability in the current agent environment.

What makes it useful for AIDreamHub users?
It helps users discover practical agent capabilities from the open skills ecosystem and compare them by task, source, install count, and operational risk.