Introduce Tracy (🔎), a forensic code investigator who treats every
issue like a crime scene. Findings are graded as Confirmed, Deduced,
or Hypothesized, hypotheses are never deleted (only updated), and the
deliverable is a structured investigation file another engineer can
pick up cold.
Skills under src/bmm-skills/4-implementation/:
- bmad-agent-investigator: Tracy persona, registered in the module.yaml
agent roster (which surfaces her in Party Mode automatically) and in
module-help.csv. Menu codes IN (investigate) and CX (code archaeology).
- bmad-investigate: full case workflow with intake, scene survey,
evidence analysis, source-code trace, and finalization phases. Phase 4
folds archaeology techniques inline when a bug requires broader area
understanding. Resume mode is intrinsic auto-detection.
- bmad-code-archaeology: standalone code-area exploration when there is
no bug to chase.
Workflow integration:
- bmad-create-prd step-01-init now scans
{implementation_artifacts}/investigations/*.md and reports
investigationCount alongside briefs, research, brainstorming, and
project docs. The PM agent treats the case file as input context.
Greenfield/brownfield branching, the PRD template, and downstream
Phase 3/4 skills stay untouched. Restructuring step-02+ for fix-driven
mode is left for a maintainer-aligned PR.
- bmad-create-prd step-02-discovery echoes the new count.
Public docs:
- New explainer at docs/explanation/forensic-investigation.md covering
evidence grading, hypothesis discipline, the two downstream paths, and
the Tracy/Amelia separation.
- docs/explanation/named-agents.md adds Tracy and drops the hardcoded
count so the table is self-counting.
- docs/reference/agents.md adds Tracy with IN/CX triggers.
- docs/reference/workflow-map.md gains an Entry Points section
(greenfield vs working-backwards) and places bmad-investigate on the
Quick Flow track feeding bmad-quick-dev.
- The Quick Flow box in workflow-map-diagram.html now shows Tracy and
Amelia in series with an arrow between them.
31034cc8da