brainstorming
Structured design dialogue that validates ideas before implementation begins.
d-verify
Verify hypotheses with debug logging. Updates ./.gtd/debug/current/ROOT_CAUSE.md
Full skill instructions
Core responsibilities:
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 testOutput:
./.gtd/debug/current/ROOT_CAUSE.md — When foundTest systematically. Don't add logs for all hypotheses at once.
Add logs that can definitively confirm or reject the hypothesis.
Root cause must be backed by debug output, not assumption.
If all hypotheses are rejected, stop and ask user to inspect again.
</philosophy>
<process>Read both files:
./.gtd/debug/current/SYMPTOM.md — For reproduction steps./.gtd/debug/current/HYPOTHESES.md — For hypotheses listif ! test -f "./.gtd/debug/current/SYMPTOM.md" || ! test -f "./.gtd/debug/current/HYPOTHESES.md"; then
echo "Error: Missing required files"
exit 1
fi
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}"
)
Review reports from all subagents.
If a subagent found definitive proof (e.g., obvious logic bug):
Select the most promising hypothesis based on subagent findings.
Action:
If all subagents report "Rejected" with strong evidence:
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}
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>
Structured design dialogue that validates ideas before implementation begins.
Comprehensive design intelligence for web and mobile UI/UX across 10 technology stacks.
Comprehensive implementation plans for multi-step tasks, breaking down specs into bite-sized, testable steps.
Introduction to the obra skills system with mandatory skill invocation rules and best practices.
Execute a written implementation plan with critical review and task checkpoints.
Delegate independent tasks to specialized agents working concurrently with isolated context.
Isolated git worktrees with smart directory selection and safety verification.
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.
Plan searchable and shareable content that drives traffic, builds authority, and generates leads.
README-first repository scanner that extracts commands and classifies reproduction candidates without executing them.
Brainstorm and prioritize marketing strategies tailored to your SaaS stage, budget, and goals.
Plan and optimize your website's page hierarchy, navigation, URL structure, and internal linking.
The world's fastest calendar for remote work
Capture, organize, and utilize your knowledge effortlessly.
Instant Summaries of Audio & Video Interviews with AnySummary
Transform PDFs into engaging mind maps.
Chat with any PDF instantly
Create an optimal daily plan using your voice
A productivity platform to centralize organizational knowledge and workflows with contextual AI assistance.
AskYourPDF Pricing Plans: Tailored to Your Needs