skills.rest
mol4
mol4COMMUNITY
Explore all skills by this author →
GitHub

bmad-investigate

Reconstruct bug causes from logs, traces, and code into evidence-graded case files.

1|Updated Mar 31, 2026
Search Tags:#debugging#investigation#code-analysis#incident-response#evidence-grading#case-file
One-click install
npx skills add https://github.com/mol4/BMAD-Board --skill bmad-investigate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-investigate
Source: https://github.com/mol4/BMAD-Board/tree/main/BMAD%20board/.agents/skills/bmad-investigate
Command: npx skills add https://github.com/mol4/BMAD-Board --skill bmad-investigate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you investigate bugs, incidents, and unfamiliar code paths by turning scattered evidence into a clear, evidence-graded case file another engineer can continue from.

Core Features & Use Cases

  • Evidence-driven debugging: Distinguish confirmed facts from hypotheses and avoid guesswork while tracing failures.
  • Structured case files: Capture findings, timelines, backlog items, source traces, and next steps in a consistent format.
  • Codebase exploration: Build a mental model of an unknown area before changing it, especially when the root cause is not yet obvious.

Quick Start

Use the bmad-investigate skill to analyze the reported issue in this code area and produce an evidence-graded investigation case file.

Frequently Asked Questions about bmad-investigate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a production incident using logs and stack traces?▼

Debug unfamiliar code paths by building a mental model from available evidence, grading each finding as confirmed fact or hypothesis, and capturing source traces with path-and-line citations in a structured case file.

Can I investigate an issue ticket before starting implementation work?▼

Yes, you can investigate issue tickets before implementation by analyzing diagnostic archives and exploratory code walkthroughs to produce an evidence-graded case file capturing findings, timeline, and follow-up steps.

What is the best way to trace a bug without guessing the root cause?▼

The best way to trace a bug without guessing is to apply evidence-driven investigation, requiring evidence grading, hypothesis tracking, and path-and-line citations to reconstruct the actual cause from available diagnostics.

Does evidence-driven debugging work for exploratory code walkthroughs?▼

Evidence-driven debugging works for exploratory code walkthroughs by building a mental model of unknown code areas, grading observations, and outputting a structured case file another engineer can continue from.

How do I create an investigation case file another engineer can continue from?▼

Create an investigation case file by grading evidence, tracking hypotheses, citing path-and-line sources, and structuring the output to capture findings, backlog items, timeline, and follow-up steps for seamless handoff.

Related Skills

Explore More Software Engineering Skills→
ChegginCheggin
1

debug

Diagnose OMC/Claude-Code session failures by aggregating logs, traces, and state.

Community
Advanced
leonardoteodorooleonardoteodoroo

postmortem-writing

Generate blameless postmortems with root cause analysis, timelines, and action items.

Community
Advanced
vladpolewoivladpolewoi

debrief

Automate post-incident analysis and generate debrief documents from codebase evidence.

Community
Advanced
diegosanchespereira1diegosanchespereira1

bmad-investigate

Reconstruct bug causes, sequences, and evidence into structured case files.

Community
Advanced