bmad-investigate

Grade evidence and reconstruct scenarios into structured case files.

1|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/peshay/portfolixir --skill bmad-investigate-peshay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-investigate
Source: https://github.com/peshay/portfolixir/tree/main/.claude/skills/bmad-investigate
Command: npx skills add https://github.com/peshay/portfolixir --skill bmad-investigate-peshay

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill aids in forensic case investigation by providing evidence-graded findings, tailored to the input. It is used for bug investigation, incident tracing, code exploration, and mental model building.

Core Features & Use Cases

  • Evidence-Graded Findings: Provides findings based on confirmed, deduced, and hypothesized evidence.
  • Investigation Workflow: Offers a structured process for tracing the root cause of issues.
  • Use Case: When a user needs to investigate a bug or understand an unfamiliar code area, this Skill can help reconstruct the situation and document findings.

Quick Start

Run the bmad-investigate skill with the ticket ID '12345' to start an investigation.

Frequently Asked Questions about bmad-investigate

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

FAQPage Schema
How do I trace the root cause of a bug using forensic code analysis?▼

Forensic code analysis traces the root cause of a bug by collecting evidence, grading it as confirmed or hypothesized, and reconstructing scenarios to provide structured case files.

What is evidence grading in incident response and code exploration?▼

Evidence grading in incident response categorizes findings into confirmed, deduced, and hypothesized evidence, helping you build a mental model and understand unfamiliar code areas.

How do I start an investigation for bug tracking and incident tracing?▼

You start an investigation for bug tracking by providing a ticket ID, which initiates a structured workflow to reconstruct the situation and document the findings.

Can I use this approach for understanding unfamiliar code areas?▼

Yes, you can use forensic case investigation for code exploration to reconstruct scenarios, test hypotheses, and build a mental model of unfamiliar code areas.

What is the best way to document findings during incident response?▼

The best way to document incident response findings is using structured case files that separate confirmed evidence from deduced or hypothesized conclusions.