31034cc8da
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.
|
||
|---|---|---|
| .. | ||
| public | ||
| src | ||
| README.md | ||
| astro.config.mjs | ||
README.md
BMAD Method Documentation Site
This directory contains the Astro + Starlight configuration for the BMAD Method documentation site.
Architecture
The documentation uses a symlink architecture to keep content in docs/ at the repo root while serving it through Astro:
bmad2/
├── docs/ # Content lives here (repo root)
│ ├── index.md
│ ├── tutorials/
│ ├── how-to/
│ ├── explanation/
│ └── reference/
└── website/
├── astro.config.mjs # Astro + Starlight config
├── src/
│ ├── content/
│ │ └── docs -> ../../docs # Symlink to content
│ └── styles/
│ └── custom.css # Custom styling
└── public/ # Static assets
Development
# From repo root
npm run docs:dev # Start dev server
npm run docs:build # Build for production
npm run docs:preview # Preview production build
Platform Notes
Windows Symlink Support
The website/src/content/docs symlink may not work correctly on Windows without Developer Mode enabled or administrator privileges.
To enable symlinks on Windows:
-
Enable Developer Mode (recommended):
- Settings → Update & Security → For developers → Developer Mode: On
- This allows creating symlinks without admin rights
-
Or use Git's symlink support:
git config core.symlinks trueThen re-clone the repository.
-
Or create a junction (alternative):
# Run as Administrator mklink /J website\src\content\docs ..\..\docs
If symlinks don't work, you can copy the docs folder instead:
# Remove the symlink
rm website/src/content/docs
# Copy the docs folder
cp -r docs website/src/content/docs
Note: If copying, remember to keep the copy in sync with changes to docs/.
Build Output
The build pipeline (npm run docs:build) produces:
- Static HTML site in
build/site/ - LLM-friendly files:
llms.txt,llms-full.txt