bmad-investigate

Automate forensic case investigation by grading evidence and managing case files.

1|Updated May 31, 2026
One-click install
npx skills add https://github.com/sfines/slf-llm-wiki-py --skill bmad-investigate-sfines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-investigate
Source: https://github.com/sfines/slf-llm-wiki-py/tree/main/.agents/skills/bmad-investigate
Command: npx skills add https://github.com/sfines/slf-llm-wiki-py --skill bmad-investigate-sfines

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines forensic case investigations by offering evidence-graded findings, tailored to the input context. It's useful for debugging, incident analysis, code understanding, and building mental models before working on code.

Core Features & Use Cases

  • Evidence-Graded Findings: Provides findings that are graded based on the evidence, ensuring a thorough and structured investigation.
  • Case Management: Manages case files with evidence inventory, investigation backlog, and timeline.
  • Automated Analysis: Automates the analysis of diagnostic archives, issue trackers, version control, test results, and source code.
  • Use Case: When you need to investigate a bug, trace the cause of an incident, or understand an unfamiliar code area, this Skill can help you build a case file that an engineer can pick up and continue from.

Quick Start

Use the bmad-investigate skill to start a new investigation for a bug with the ticket ID 'BUG-1234'.

Frequently Asked Questions about bmad-investigate

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

FAQPage Schema
How do I debug unfamiliar code by building a structured investigation case file?

To debug unfamiliar code, you can build a structured investigation case file by automating the analysis of source code, test results, and version control. This process grades evidence and creates a continuous timeline for engineers to pick up and continue.

What is the best way to trace the root cause of an incident using evidence grading?

The best way to trace an incident's root cause is using evidence grading to evaluate diagnostic archives and issue trackers. This grades findings based on collected evidence, ensuring a thorough and structured forensic investigation.

Can I use Python scripts to automate forensic case management and evidence inventory?

Yes, you can use Python scripts to automate forensic case management and evidence inventory. The workflow requires Python scripts for processing evidence, managing case files, and maintaining an investigation backlog and timeline.

Does this approach work for analyzing diagnostic archives and version control history together?

Yes, this approach works for analyzing diagnostic archives and version control history together. It automates the analysis of various data sources, including version control, issue trackers, and test results, to build a comprehensive mental model.

When should I use an automated forensic investigation workflow for bug debugging?

You should use an automated forensic investigation workflow for bug debugging when you need to trace the cause of an incident, understand an unfamiliar code area, or build a case file that another engineer can easily pick up and continue from.