Skip to content
d-verify logo

Root Cause

d-verify

Verify hypotheses with debug logging. Updates ./.gtd/debug/current/ROOT_CAUSE.md

SKILL.md

Full skill instructions

<role> You are a hypothesis tester. You systematically verify hypotheses until the root cause is found.

Core responsibilities:

  • Load hypotheses in confidence order
  • Add strategic debug logs to test each hypothesis
  • Run reproduction steps
  • Analyze debug output
  • Move to next hypothesis if rejected
  • Document root cause when found </​role>
<objective> Find the actual root cause through systematic verification.

Flow: Load Hypotheses → Test Highest Confidence → Analyze → Found or Next </​objective>

<context> **Required files:**
  • ./​.gtd/​debug/​current/​SYMPTOM.md — Reproduction steps
  • ./​.gtd/​debug/​current/​HYPOTHESES.md — Hypotheses to test

Output:

  • ./​.gtd/​debug/​current/​ROOT_CAUSE.md — When found
  • Debug logs in code (temporary) </​context>
<philosophy>

One Hypothesis at a Time

Test systematically. Don't add logs for all hypotheses at once.

Strategic Logging

Add logs that can definitively confirm or reject the hypothesis.

Evidence-Based Conclusion

Root cause must be backed by debug output, not assumption.

Know When to Stop

If all hypotheses are rejected, stop and ask user to inspect again.

</​philosophy>

<process>

1. Load Context

Read both files:

  • ./​.gtd/​debug/​current/​SYMPTOM.md — For reproduction steps
  • ./​.gtd/​debug/​current/​HYPOTHESES.md — For hypotheses list
if ! test -f "./​.gtd/​debug/​current/​SYMPTOM.md" || ! test -f "./​.gtd/​debug/​current/​HYPOTHESES.md"; then
    echo "Error: Missing required files"
    exit 1
fi

2. Spawn Verification Agents

For each hypothesis, spawn a researcher to inspect code for confirmation/​rejection (READ-ONLY).

Concurrency: As many as needed (Parallel). Trigger: After loading hypotheses.

Fill prompt for each hypothesis:

<objective>
Verify Hypothesis: {hypothesis_description}
</​objective>

<context>
- Symptom: {symptom_description}
- Evidence: {existing_evidence}
</​context>

<related>

| Workflow      | Relationship                    |
| ------------- | ------------------------------- |
| `/​d-inspect`  | Provides hypotheses to test     |
| `/​d-plan-fix` | Creates fix plan for root cause |

</​related>

<investigation_checklist>

1. Locate relevant code
2. Check for logic errors matching hypothesis
3. Verify if preconditions/​assumptions hold true
4. Identify where to add debug logs if needed
   </​investigation_checklist>

<output_format>
Verification Report:

- Status: Confirmed / Rejected / Inconclusive
- Evidence Found: (Code snippets, logic analysis)
- Recommended Debug Log Location: (File:Line)
  </​output_format>
Task(
  prompt=filled_prompt,
  subagent_type="researcher",
  description="Verifying hypothesis: {short_desc}"
)

3. Review & Decide Actions

Review reports from all subagents.

3a. If Root Cause Confirmed by Inspection

If a subagent found definitive proof (e.g., obvious logic bug):

  • Skip logging.
  • Proceed to Document Root Cause.

3b. If Inconclusive / Needs Logs

Select the most promising hypothesis based on subagent findings.

Action:

  1. Add debug logs to locations recommended by subagent.
  2. Run reproduction steps.
  3. Analyze output.

3c. If All Rejected

If all subagents report "Rejected" with strong evidence:

  • STOP.
  • Ask user to re-inspect or provide new ideas.

4. Document Root Cause

When confirmed (by inspection or logs), write to ./​.gtd/​debug/​current/​ROOT_CAUSE.md:

# Root Cause

**Found:** {date}
**Status:** CONFIRMED

## Root Cause

{Clear description of the actual root cause}

## Verified Hypothesis

**Original Hypothesis {N}:** {description}
**Confidence:** {original percentage} → **Confirmed**

## Evidence

{Debug output and observations that confirmed this}

**Debug logs showed:**

- {key finding 1}
- {key finding 2}

## Location

- **Files:** `{file1}`, `{file2}`
- **Lines:** {line ranges}
- **Function/​Method:** {specific location}

## Why It Causes The Symptom

{Explain the causal chain from root cause to observed symptom}

## Rejected Hypotheses

{List other hypotheses tested and why they were rejected}

4a. Clean Up Debug Logs

Remove or comment out temporary debug logs added during verification.


</​process>

<offer_next>

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 GTD:DEBUG ► ROOT CAUSE FOUND ✓
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Root cause documented: ./​.gtd/​debug/​current/​ROOT_CAUSE.md

Verified hypothesis: {N}
Location: {files}

─────────────────────────────────────────────────────

▶ Next Up

/​d-plan-fix — create fix plan

─────────────────────────────────────────────────────

</​offer_next>

<forced_stop> STOP. The workflow is complete. Do NOT automatically run the next command. Wait for the user. </​forced_stop>

More Productivity & Planning skills

brainstorming logo
Productivity & Planning

brainstorming

Structured design dialogue that validates ideas before implementation begins.

295.4K 385.7K
View
ui-ux-pro-max logo
Productivity & Planning

ui-ux-pro-max

Comprehensive design intelligence for web and mobile UI/UX across 10 technology stacks.

133.1K 383.9K
View
writing-plans logo
Productivity & Planning

writing-plans

Comprehensive implementation plans for multi-step tasks, breaking down specs into bite-sized, testable steps.

295.4K 268K
View
using-superpowers logo
Productivity & Planning

using-superpowers

Introduction to the obra skills system with mandatory skill invocation rules and best practices.

295.4K 259.8K
View
executing-plans logo
Productivity & Planning

executing-plans

Execute a written implementation plan with critical review and task checkpoints.

295.4K 229.1K
View
dispatching-parallel-agents logo
Productivity & Planning

dispatching-parallel-agents

Delegate independent tasks to specialized agents working concurrently with isolated context.

295.4K 206.3K
View
using-git-worktrees logo
Productivity & Planning

using-git-worktrees

Isolated git worktrees with smart directory selection and safety verification.

295.4K 205.2K
View
webapp-testing logo
Productivity & Planning

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

179.7K 170.6K
View
content-strategy logo
Productivity & Planning

content-strategy

Plan searchable and shareable content that drives traffic, builds authority, and generates leads.

53.3K 150.9K
View
repo-intake-and-plan logo
Productivity & Planning

repo-intake-and-plan

README-first repository scanner that extracts commands and classifies reproduction candidates without executing them.

497 139.6K
View
marketing-ideas logo
Productivity & Planning

marketing-ideas

Brainstorm and prioritize marketing strategies tailored to your SaaS stage, budget, and goals.

53.3K 137.2K
View
site-architecture logo
Productivity & Planning

site-architecture

Plan and optimize your website's page hierarchy, navigation, URL structure, and internal linking.

53.3K 112.8K
View

Productivity AI tools

Vimcal logo
Productivity

Vimcal

The world's fastest calendar for remote work

Free
View
SaveDay logo
Productivity

SaveDay

Capture, organize, and utilize your knowledge effortlessly.

Free
View
A
Productivity

Any Summary

Instant Summaries of Audio & Video Interviews with AnySummary

Freemium
View
M
Productivity

Map This

Transform PDFs into engaging mind maps.

Freemium
View
ChatPDF logo
Productivity

ChatPDF

Chat with any PDF instantly

Free
View
I
Productivity

intellisay

Create an optimal daily plan using your voice

Paid
View
A
Productivity

Aurora AI

A productivity platform to centralize organizational knowledge and workflows with contextual AI assistance.

Paid
View
AskYourPDF logo
Productivity

AskYourPDF

AskYourPDF Pricing Plans: Tailored to Your Needs

Free
View