mirror of
https://github.com/bmad-code-org/BMAD-METHOD.git
synced 2026-09-01 15:09:07 +08:00
Brian
57e70562e3
* Add bmad-project-context skill; husk document-project and generate-project-context - New bmad-project-context: one engine, three intents (ingest/query/audit) building a verified kernel + bundle context system; interactive default, auto/headless mode; works with a BMad install or standalone via bootstrap - context.py core runtime script (validate/index/map/sweep/resolve/compass/ sync/bootstrap/config) with 52 tests; config resolution delegates to the installed BMad resolver so script and session never disagree - bmad-document-project and bmad-generate-project-context reduced to 10-line deprecation shims forwarding to the new skill - Docs updated: project-context explanation/how-to rewritten, established projects guide + FAQ, agents references, workflow map; deprecation notes kept for old-name searches - module-help.csv single PC row; analyst menu DP -> PC - validate-file-refs: context.yaml is runtime-generated * refactor: remove map command from context.py — discovery is the model's job Real-repo testing showed map's descriptor pass grinding through large asset trees. Discovery is judgment work the model does better with its own tools; the script keeps only measurement, mutation, and resolution (validate/index/sweep/resolve/compass/sync/bootstrap/config). SKILL.md brownfield flow de-prescribed to outcome-driven wording; added a bounding-question rule for huge external sources. * feat: closing message when the harness may not load AGENTS.md 43+ harnesses make per-harness load verification impractical. Whenever AGENTS.md carries the kernel, the run now closes by telling the user: if your harness doesn't auto-load AGENTS.md, make the context file it does load pull this one in (e.g. a CLAUDE.md containing @AGENTS.md). Found in real-repo testing: the kernel sat unloaded under Claude Code until a CLAUDE.md pointer was hand-made. * docs: add The Theory of Project Context explanation Why the skill captures so little: the evidence against generated docs, the pruning test and what earns a place, the deliberate exclusions with their reasons, context-as-liability, and an honest comparison with the two replaced skills. * fix: address PR review findings - Force-add eval fixture files the repo gitignore silently dropped (pnpm-lock.yaml, _bmad/context.yaml, context/.memlog.md) - docs/reference/agents.md Analyst row: DP/Document Project -> PC/Project Context - context.py: cmd_index no longer crashes on an empty index.md (and allows overwriting one); inline # comments in frontmatter values are only stripped when preceded by whitespace (C#-style values survive); cache_lookup tolerates corrupt pointer files; pointer writes are atomic - triggers.json: positive trigger for the query intent
2.6 KiB
2.6 KiB
title, description, sidebar
| title | description | sidebar | ||
|---|---|---|---|---|
| Agents | Default BMM agents with their skill IDs, menu triggers, and primary workflows |
|
Default Agents
This page lists the default BMM (Agile suite) agents that install with BMad Method, along with their skill IDs, menu triggers, and primary workflows. Each agent is invoked as a skill.
Notes
- Each agent is available as a skill, generated by the installer. The skill ID (e.g.,
bmad-agent-dev) is used to invoke the agent. - Triggers are the short menu codes (e.g.,
PRD) and fuzzy matches shown in each agent menu. - QA test generation is handled by the
bmad-qa-generate-e2e-testsworkflow skill, available through the Developer agent. The full Test Architect (TEA) lives in its own module.
| Agent | Skill ID | Triggers | Primary workflows |
|---|---|---|---|
| Analyst (Mary) | bmad-agent-analyst |
BP, MR, DR, TR, CB, WB, PC |
Brainstorm, Market Research, Domain Research, Technical Research, Create Brief, PRFAQ Challenge, Project Context |
| Product Manager (John) | bmad-agent-pm |
PRD, CE, IR, CC |
Create/Update/Validate PRD, Create Epics and Stories, Implementation Readiness (sprint-planning gate), Correct Course |
| Architect (Winston) | bmad-agent-architect |
CA, IR |
Create Architecture, Implementation Readiness (sprint-planning gate) |
| Developer (Amelia) | bmad-agent-dev |
BD, QA, CR, SP, ER |
Build, QA Test Generation, Code Review, Sprint Planning, Epic Retrospective |
| UX Designer (Sally) | bmad-agent-ux-designer |
CU |
Create UX Design |
:::note[Where is Paige?]
The Technical Writer (Paige) is on hiatus — she will return in the future far more capable. In the meantime, project context lives on: the PC (Project Context) trigger is available through the Analyst, or invoke the bmad-project-context skill directly.
:::
Trigger Types
Agent menu triggers load a structured workflow file. Type the trigger code and the agent starts the workflow, prompting you for input at each step.
Examples: PRD (Create, update, or validate PRD), CA (Create Architecture), BD (Build)