skills.rest
diegosanchespereira1
diegosanchespereira1COMMUNITY
Explore all skills by this author →
WebsiteGitHub

bmad-investigate

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

Updated May 23, 2026
Search Tags:#code analysis#debugging#investigation#incident response#evidence grading#case file
One-click install
npx skills add https://github.com/diegosanchespereira1/lavarapido --skill bmad-investigate-diegosanchespereira1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-investigate
Source: https://github.com/diegosanchespereira1/lavarapido/tree/main/lava-rapido/.agents/skills/bmad-investigate
Command: npx skills add https://github.com/diegosanchespereira1/lavarapido --skill bmad-investigate-diegosanchespereira1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you investigate bugs, incidents, and unfamiliar code areas by turning scattered evidence into a structured case file another engineer can pick up quickly.

Core Features & Use Cases

  • Evidence-graded findings: Separates confirmed observations from deductions and hypotheses so conclusions stay traceable.
  • Structured investigation workflow: Guides you through scoping, evidence collection, source tracing, and final reporting.
  • Cold-start handoff: Produces a concise investigation record with timeline, backlog, missing evidence, and next steps for a teammate.
  • Use case: Use it when a production bug appears, an error trace is unclear, or you need to understand a code path before making changes.

Quick Start

Ask the skill to investigate the specific bug, incident, or code area and provide any logs, error messages, or file paths you already have.

Frequently Asked Questions about bmad-investigate

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

FAQPage Schema
How do I investigate a production incident with unclear error logs?▼

To investigate a production incident with unclear error logs, you reconstruct the cause and sequence by grading evidence into confirmed observations, deductions, and hypotheses. This builds a structured case file for cold-start handoff.

What is evidence grading in code investigation?▼

Evidence grading in code investigation separates confirmed observations from deductions and hypotheses. This ensures your findings stay traceable and distinct when reconstructing bugs or unfamiliar code areas.

How do I create a handoff document for an unresolved bug?▼

You create a handoff document for an unresolved bug by compiling a structured case file that includes the timeline, backlog, missing evidence, and next steps. This provides a concise investigation record for a teammate.

Can I trace an unfamiliar code path before making changes?▼

Yes, you can trace an unfamiliar code path before making changes by applying source tracing and path-line citations. This exploratory walkthrough helps you understand the logic and build a structured investigation record.

What is the best way to track missing evidence during incident response?▼

The best way to track missing evidence during incident response is to use a structured investigation workflow that maintains a dedicated backlog. This clearly distinguishes confirmed findings from unresolved hypotheses.

Related Skills

Explore More Software Engineering Skills→
acartineacartine
1

investigate

Trace runtime failures with file:line citations before proposing fixes.

Community
Advanced
menoncellomenoncello
3

orchestrator-agent

Orchestrate subagents, commands, MCP servers, and skills with parallel execution.

Community
Intermediate
salazarsebassalazarsebas
9

investigate

Collect evidence into structured case files for incident investigations.

Community
Advanced
kynoptickynoptic
1

Debugging Runtime Errors

Analyze stack traces and error logs to identify root causes and propose fixes.

Community
Advanced