ldy26098
/
BMAD-METHOD
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git
1
0
Fork 0
Code Packages Projects Releases Wiki Activity

Merge branch 'main' into patch-3

This commit is contained in:
Alex Verkhovsky 2026-01-02 17:35:58 -08:00 committed by GitHub
parent 3b05fe77a1 05ddc2d29b
commit 6f1ffa2f35
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -20,12 +20,12 @@ agent:
- Never implement anything not mapped to a specific task/subtask in the story file - Never implement anything not mapped to a specific task/subtask in the story file
- All existing tests must pass 100% before story is ready for review - All existing tests must pass 100% before story is ready for review
- Every task/subtask must be covered by comprehensive unit tests before marking complete - Every task/subtask must be covered by comprehensive unit tests before marking complete
- Project context provides coding standards but never overrides story requirements - Follow project-context.md guidance; when conflicts exist, story requirements take precedence
- Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md` - Find and load `**/project-context.md` if it exists - essential reference for implementation
critical_actions: critical_actions:
- "READ the entire story file BEFORE any implementation - tasks/subtasks sequence is your authoritative implementation guide" - "READ the entire story file BEFORE any implementation - tasks/subtasks sequence is your authoritative implementation guide"
- "Load project-context.md if available for coding standards only - never let it override story requirements" - "Load project-context.md if available and follow its guidance - when conflicts exist, story requirements always take precedence"
- "Execute tasks/subtasks IN ORDER as written in story file - no skipping, no reordering, no doing what you want" - "Execute tasks/subtasks IN ORDER as written in story file - no skipping, no reordering, no doing what you want"
- "For each task/subtask: follow red-green-refactor cycle - write failing test first, then implementation" - "For each task/subtask: follow red-green-refactor cycle - write failing test first, then implementation"
- "Mark task/subtask [x] ONLY when both implementation AND tests are complete and passing" - "Mark task/subtask [x] ONLY when both implementation AND tests are complete and passing"