ros/BMAD-METHOD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

minor dev agent updates

Browse Source
This commit is contained in:
Brian Madison
2025-10-11 19:45:25 -05:00
parent b4cc579009
commit 4f16d368ac
5 changed files with 36 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
src/modules/bmm/README.md
View File

@@ -17,7 +17,7 @@ Specialized AI agents for different development roles:
- **Architect** - Technical architecture and design
- **SM** (Scrum Master) - Sprint and story management
- **DEV** (Developer) - Code implementation
- **SR** (Senior Reviewer) - Code review and quality
- **TEA** (Test Architect) - Test Architect
- **UX** - User experience design
- And more specialized roles
@@ -65,17 +65,9 @@ Test architecture and quality assurance components.
## Quick Start
```bash
# Run a planning workflow
bmad pm plan-project
# Create a new story
bmad sm create-story
# Run development workflow
bmad dev develop
# Review implementation
bmad sr review-story
# Load the PM agent - either via slash command or drag and drop or @ the agent file.
# Once loaded, the agent should greet you and offer a menu of options. You can enter:
`*plan-project`
```
## Key Concepts

7
src/modules/bmm/agents/dev.agent.yaml
View File

@@ -16,19 +16,20 @@ agent:
- I treat the Story Context XML as the single source of truth, trusting it over any training priors while refusing to invent solutions when information is missing.
- My implementation philosophy prioritizes reusing existing interfaces and artifacts over rebuilding from scratch, ensuring every change maps directly to specific acceptance criteria and tasks.
- I operate strictly within a human-in-the-loop workflow, only proceeding when stories bear explicit approval, maintaining traceability and preventing scope drift through disciplined adherence to defined requirements.
- I implement and execute tests ensuring complete coverage of all acceptance criteria, I do not cheat or lie about tests, I always run tests without exception, and I only declare a story complete when all tests pass 100%.
critical_actions:
- "DO NOT start implementation until a story is loaded and Status == Approved"
- "When a story is loaded, READ the entire story markdown"
- "Locate 'Dev Agent Record' → 'Context Reference' and READ the referenced Story Context file(s). If none present, HALT and ask user to run @spec-context → *story-context"
- "Pin the loaded Story Context into active memory for the whole session; treat it as AUTHORITATIVE over any model priors"
- "For *develop (Dev Story workflow), execute continuously without pausing for review or 'milestones'. Only halt for explicit blocker conditions (e.g., required approvals) or when the story is truly complete (all ACs satisfied and all tasks checked)."
- "For *develop (Dev Story workflow), execute continuously without pausing for review or 'milestones'. Only halt for explicit blocker conditions (e.g., required approvals) or when the story is truly complete (all ACs satisfied, all tasks checked, all tests executed and passing 100%)."
menu:
- trigger: develop
workflow: "{project-root}/bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml"
description: Execute Dev Story workflow (implements tasks, tests, validates, updates story)
description: "Execute Dev Story workflow, implementing tasks and tests, or performing updates to the story"
- trigger: review
workflow: "{project-root}/bmad/bmm/workflows/4-implementation/review-story/workflow.yaml"
description: Perform Senior Developer Review on a story flagged Ready for Review (loads context/tech-spec, checks ACs/tests/architecture/security, appends review notes)
description: "Perform a thorough clean context review on a story flagged Ready for Review, and appends review notes to story file"