skills.rest
JaronTam
JaronTamCOMMUNITY
Explore all skills by this author →
GitHub

bmad-investigate

Conduct forensic software investigations by processing evidence-graded findings and automated inventory.

Updated May 22, 2026
Search Tags:#incident response#bug investigation#code tracing#evidence grading#forensic analysis
One-click install
npx skills add https://github.com/JaronTam/SDONE --skill bmad-investigate-jarontam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-investigate
Source: https://github.com/JaronTam/SDONE/tree/main/.agents/skills/bmad-investigate
Command: npx skills add https://github.com/JaronTam/SDONE --skill bmad-investigate-jarontam

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill simplifies forensic case investigation, allowing users to trace the source of bugs, incidents, and code areas with evidence-graded findings.

Core Features & Use Cases

  • Evidence-Graded Analysis: Analyze cases based on confirmed, deduced, and hypothesized evidence.
  • Investigation Workflow: Follow a structured process to trace causality, reconstruct timelines, and form hypotheses.
  • Automated Evidence Inventory: Gather and classify evidence across multiple categories, such as diagnostic archives, issue trackers, and source code.
  • Case Documentation: Document findings, conclusions, and recommended next steps in a structured case file.

Quick Start

Investigate a bug with the bmad-investigate skill by providing a ticket ID or log file path.

Frequently Asked Questions about bmad-investigate

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

FAQPage Schema
How do I conduct a forensic investigation of a software incident?▼

Conduct forensic investigation of software incidents by processing evidence-graded findings, following a structured workflow, and utilizing automated evidence inventory to trace causality and reconstruct timelines.

What is evidence-graded analysis for bug investigation?▼

Evidence-graded analysis classifies bug investigation findings into confirmed, deduced, and hypothesized evidence to systematically trace the source of incidents and code areas.

How do I start tracing the source of a bug using diagnostic archives and issue trackers?▼

Start bug tracing by providing a ticket ID or log file path, which triggers automated gathering and classification of evidence across diagnostic archives, issue trackers, and source code.

Can I use this approach to analyze binary content during incident response?▼

Yes, incident response requires parsing and analyzing binary content to gather diagnostic archives and manage structured data outputs for reconstructing incident timelines.

What is the best way to document conclusions and recommended next steps after an incident analysis?▼

Document incident analysis findings, conclusions, and recommended next steps in a structured case file generated after tracing causality and forming hypotheses.

Does this incident response workflow handle unconfirmed hypotheses during code exploration?▼

Yes, code exploration and incident analysis workflows explicitly handle hypothesized evidence alongside confirmed and deduced findings to form structured conclusions.

Related Skills

Explore More Software Engineering Skills→
AtharvaN16AtharvaN16

wayfinder

Create shared investigation ticket maps on issue trackers for project management.

Community
Advanced
Threat-Vector-SecurityThreat-Vector-Security
11

security-triage

Triage security alerts into evidence, timelines, and recommended next steps.

Official
Intermediate
EntroVyxEntroVyx
3

oss-forensics

Investigate open-source repositories for supply chain attacks using git history and GitHub API events.

Community
Advanced
peshaypeshay
1

bmad-investigate

Grade evidence and reconstruct scenarios into structured case files.

Community
Advanced