Skip to content
Skip to contents
Skip to reading controls

Search skills⌘K

Setting the file. One moment.

This file

Type

Size

Lines

Position

obra
/
obra/superpowers

Test Academic · Systematic Debugging · obra/superpowers · Skills Docs

Repo No. 71 · Systematic Debugging

↖Back to the cover

Brainstorming
Diagnosing Superpowers
Dispatching Parallel Agents
Executing Plans
Finishing A Development Branch
Receiving Code Review
Requesting Code Review
Subagent Driven Development
Systematic Debugging
Appendix · 10 subchapters
Test Driven Development
Using Git Worktrees
Using Superpowers
Verification Before Completion
Writing Plans
Writing Skills

15 skills · 82 min

Skill 09 · Systematic Debugging

Subchapter 9.7

Test Academic

test-academic.mdMarkdown653 BView on GitHub

Academic Test: Systematic Debugging Skill

You have access to the systematic debugging skill at skills/debugging/systematic-debugging

Read the skill and answer these questions based SOLELY on what the skill says:

What are the four phases of systematic debugging?
What must you do BEFORE attempting any fix?

9Up to skill 9Systematic Debugging

This file

Number: 9.7
Position: 7 of 10
Type: Markdown
Size: 653 B

Nearby

Previous Root Cause Tracing
Next Test Pressure 1

Source

In Phase 3, what should you do if your first hypothesis doesn’t work?

What does the skill say about fixing multiple things at once?

What should you do if you don’t fully understand the issue?

Is it ever acceptable to skip the process for simple bugs?

Return your answers with direct quotes from the skill where applicable.

Bundled fileRoot Cause Tracing Bundled fileTest Pressure 1

test-academic.md

(opens in a new tab)

Raw file(opens in a new tab)

obra/superpowers(opens in a new tab)