Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →aj-geddes/bmad-investigate
Forensic bug and issue triage. Produces a graded investigation case file: symptoms, evidence (graded A/B/C by confidence), ranked hypotheses, suspected components, and a recommended planning response. INVESTIGATES and DOCUMENTS only — does NOT fix code, run tests, or implement. Hands off as a story to an external dev tool.
Passed 15 of 19 test cases with the skill, and 4 of 19 without it.
and 20 more in the full report
13 fixed4 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
When Option A creates a new task story for epic `EP-12` story `ST-4` with slug `cache-invalidation`, where should the story markdown file be placed?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies bmad-output/stories/EP-12.ST-4.cache-invalidation.story.md as the story file path | Missed | Passed |
The instructions your model reads when the skill loads.
Forensic triage — plan the fix, don't apply it.
This skill builds a structured, evidence-graded investigation case file so that whoever picks up the story has a clear picture of what is known, what is suspected, and exactly what needs verifying before any code changes. It deliberately stops before implementation; the result of every investigation is a story handed off to an external dev tool.
Persona flavor: Mary (Business Analyst) frames the user impact; Winston (Architect) maps the component topology. The skill is a workflow, not a character.
This skill PLANS. It reads planning artifacts and existing code to gather evidence.
It does NOT write application code, run tests, lint, build, or review diffs.
The last artifact it emits is either an updated planning document or a story file
marked status: ready-for-dev. If tempted to "fix the bug", "run the suite", or
"apply the patch" — STOP. Investigate and hand off.
| Source | Why |
|---|---|
bmad-output/project-context.md | Project constitution — architecture, stack, ownership |
bmad-output/architecture.md | Component boundaries, module responsibilities |
bmad-output/prd.md or tech-spec.md | Requirements the broken behavior should satisfy |
bmad-output/decision-log.md | Prior decisions that may relate to the issue |
| User-provided symptom description | Primary input — what is failing, when, how |
| Logs / error messages the user pastes in | Raw evidence to grade and analyze |
Existing story files in bmad-output/stories/ | Check for duplicate or related work |
If project-context.md does not exist, ask the user to describe the stack and affected area before proceeding.
test cases passed, vs 4 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.