Skip to content

chore(bmm): retire bmad-investigate skill and its documentation#2509

Merged
alexeyv merged 2 commits into
mainfrom
chore/retire-bmad-investigate
Jun 25, 2026
Merged

chore(bmm): retire bmad-investigate skill and its documentation#2509
alexeyv merged 2 commits into
mainfrom
chore/retire-bmad-investigate

Conversation

@alexeyv

@alexeyv alexeyv commented Jun 25, 2026

Copy link
Copy Markdown
Collaborator

What

Retires the bmad-investigate skill in full. Removes the skill (SKILL.md, customize.toml, case-file-template.md), both EN/FR forensic-investigation explainer docs, and every integration point:

  • Amelia's IN menu entry (bmad-agent-dev/customize.toml)
  • the plugin marketplace manifest (.claude-plugin/marketplace.json)
  • module-help.csv
  • the workflow-map reference tables and HTML diagrams (EN + FR)
  • the agent-trigger tables (agents.md, named-agents.md, EN + FR)

EN/FR explanation sidebar order values are renumbered to close the gap left by the removed doc. npm run quality → 0 errors.

Why

I tested it. Four real "why" questions about a C++ codebase, each answered twice by identical agents — one using bmad-investigate, one just investigating normally.

Every pair landed on the same answer. The skill never got it more right. On one question the plain agent actually found more. The skill cost about 1.5× as much and took twice as long every time. One time out of a hundred where I need an investigation file, I can just ask the LLM to create it.

In my experience, this gets invoked unexpectedly in response to random questions, burns some tokens and produces output that speaks in birds language. In the few acts that I knew of its existence, I never actually asked for it or needed it per se.

Github issues pointing the same way:

Supersedes / resolves

Testing

  • npm ci && npm run qualityErrors: 0 (17 pre-existing cs/vi-vn/zh-cn sidebar-order warnings, unrelated).

🤖 Generated with Claude Code

Removes the bmad-investigate skill, its case-file template, the EN/FR
forensic-investigation explainer docs, and every integration point:
Amelia's `IN` menu entry, the plugin marketplace manifest, module-help,
the workflow-map tables and HTML diagrams, and the agent-trigger tables.
EN/FR explanation sidebar orders are renumbered to close the gap left by
the removed doc.

Rationale: the skill's only non-redundant value was a durable, hand-off
case-file artifact — a workflow that is unproven in practice. Everything
else (evidence grading, hypothesis discipline, causal tracing) is
behavior a capable model already performs without a dedicated skill. The
skill also carried method-internal metaphor ("stronghold", "evidence
perimeter") that leaked into user-facing chat. Upstream signals agreed:
issue #2452 flagged the vocabulary leak and a maintainer noted the skill
should not auto-fire. Added in #2364.

Supersedes the in-flight cleanup in #2478 and resolves #2452 by removal.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@augmentcode

augmentcode Bot commented Jun 25, 2026

Copy link
Copy Markdown
🤖 Augment PR Summary

Summary: This PR fully retires the bmad-investigate skill and removes its documentation and all known integration points.

Changes:

  • Removed the bmad-investigate skill directory (SKILL.md, customization surface, and case-file template)
  • Dropped the skill from the Claude plugin marketplace manifest so it is no longer distributed/advertised
  • Removed Amelia’s IN menu entry and deleted skill references from agent trigger tables (EN/FR)
  • Deleted the EN/FR forensic-investigation explainer pages and removed links to them from docs
  • Updated workflow-map reference tables (EN/FR) to remove the investigate row
  • Renumbered docs sidebar order values to close the gap left by the removed explanation page

Technical Notes: The PR is largely subtractive; it aims to prevent the skill’s internal “forensics” metaphor from leaking into user-facing chat by removing the skill entirely.

🤖 Was this summary useful? React with 👍 or 👎

@augmentcode augmentcode Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review completed. No suggestions at this time.

Comment augment review to trigger a new review at any time.

@coderabbitai

coderabbitai Bot commented Jun 25, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

The PR removes the bmad-investigate skill from plugin and agent wiring, deletes related skill artifacts and forensic-investigation docs, removes corresponding English/French references, and renumbers sidebar orders on affected explanation pages.

Changes

bmad-investigate removal and doc cleanup

Layer / File(s) Summary
Skill package removal
src/bmm-skills/4-implementation/bmad-agent-dev/customize.toml, src/bmm-skills/4-implementation/bmad-investigate/SKILL.md, src/bmm-skills/4-implementation/bmad-investigate/customize.toml, src/bmm-skills/4-implementation/bmad-investigate/references/case-file-template.md
The bmad-investigate skill prompt, workflow config, case-file template, and IN agent menu entry are removed.
Marketplace and reference cleanup
.claude-plugin/marketplace.json, docs/reference/agents.md, docs/fr/reference/agents.md, docs/explanation/named-agents.md, docs/fr/explanation/named-agents.md, docs/reference/workflow-map.md, docs/fr/reference/workflow-map.md, docs/explanation/forensic-investigation.md, docs/fr/explanation/forensic-investigation.md
The marketplace skills list and the English/French agent and workflow pages remove bmad-investigate, IN, and forensic-investigation references, and the English/French forensic-investigation pages are deleted.
Sidebar order renumbering
docs/explanation/established-projects-faq.md, docs/explanation/forge-idea.md, docs/explanation/party-mode.md, docs/explanation/project-context.md, docs/fr/explanation/established-projects-faq.md, docs/fr/explanation/party-mode.md, docs/fr/explanation/project-context.md
The English and French explanation pages update sidebar.order values to keep their sidebar positions aligned.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

Suggested reviewers

  • bmadcode
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: retiring the bmad-investigate skill and its docs.
Linked Issues check ✅ Passed Removing the skill and its integrations addresses #2452 by eliminating the jargon-leaking workflow.
Out of Scope Changes check ✅ Passed The visible changes all align with retiring bmad-investigate; no unrelated additions are evident.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description check ✅ Passed The description accurately matches the PR’s removal of bmad-investigate and its related docs, menu entries, workflow references, and sidebar renumbering.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/retire-bmad-investigate

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

The retirement commit removed the skill source and docs but did not add
the removals.txt entry that triggers cleanup of the skill directory on
existing installs during update. Add it, plus an Unreleased CHANGELOG note.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@alexeyv alexeyv merged commit 7b2d90a into main Jun 25, 2026
5 checks passed
@alexeyv alexeyv deleted the chore/retire-bmad-investigate branch June 25, 2026 02:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bmad-investigate: method-internal jargon ("stronghold") leaks into user-facing communication

1 participant