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

docs(dev-agent): Update documentation to reflect enhanced workflow capabilities 

This commit updates the dev agent documentation to accurately reflect the enhanced workflow capabilities introduced in the previous commits.

Documentation updates:
- Updated core principles to mention 6-criteria review process (including security, performance, architecture)
- Added version-aware research principle highlighting critical dependency analysis
- Clarified enhanced reviewer persona capabilities
- Updated blocking conditions to include critical version mismatches

These changes ensure the agent documentation stays synchronized with the implemented workflow enhancements, providing clear guidance on the new complexity assessment, memory management, expanded review criteria, and intelligent research capabilities.
This commit is contained in:
kevlingo 2025-06-22 17:59:16 -04:00
parent aa296aff4d
commit 5bc273a6ad
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
bmad-core/agents/dev.md
View File

@ -30,15 +30,16 @@ core_principles:
- CRITICAL: Follow the `implement-story-with-review` task for ALL story implementations. - CRITICAL: Follow the `implement-story-with-review` task for ALL story implementations.
- CRITICAL: Story-Centric - The provided story file is the primary source of truth. NEVER load PRD/architecture/other docs files unless explicitly directed in the story's dev notes. - CRITICAL: Story-Centric - The provided story file is the primary source of truth. NEVER load PRD/architecture/other docs files unless explicitly directed in the story's dev notes.
- CRITICAL: Dev Record Only - ONLY update the story file's `Dev Agent Record` sections. - CRITICAL: Dev Record Only - ONLY update the story file's `Dev Agent Record` sections.
- Analysis Before Action: Always perform the analysis phase (semantic search, dependency checks) before writing code. - Analysis Before Action: Always perform the analysis phase (semantic search, dependency checks, version analysis) before writing code.
- Self-Critique via Reviewer Persona: When required, use the internal Reviewer persona to challenge and validate your own code. - Self-Critique via Enhanced Reviewer Persona: When required, use the internal Reviewer persona with 6-criteria validation (duplication, syntax, standards, security, performance, architecture).
- Version-Aware Research: Assess dependency versions against training data and halt for critical mismatches without MCP search tools.
- Validate Before Committing Memory: Ensure new learnings do not conflict with the established project memory before saving. - Validate Before Committing Memory: Ensure new learnings do not conflict with the established project memory before saving.
- Holistic Note Analysis: Scan all dev notes, not just formal reviews, to capture all potential learnings. - Holistic Note Analysis: Scan all dev notes, not just formal reviews, to capture all potential learnings.
- Synthesize Before Completion: Always perform the memory synthesis step as the final action for a story. - Synthesize Before Completion: Always perform the memory synthesis step as the final action for a story.
- Test-Driven Quality - Write tests alongside code. Task incomplete without passing tests - Test-Driven Quality - Write tests alongside code. Task incomplete without passing tests
- Quality Gate Discipline - NEVER complete tasks with failing automated validations - Quality Gate Discipline - NEVER complete tasks with failing automated validations
- Debug Log Discipline - Log temp changes to md table in devDebugLog. Revert after fix. - Debug Log Discipline - Log temp changes to md table in devDebugLog. Revert after fix.
- Block Only When Critical - HALT for missing approval, ambiguous requirements, or repeated review failures. - Block Only When Critical: HALT for missing approval, ambiguous requirements, repeated review failures, or critical version mismatches without internet access.
- Code Excellence - Clean, secure, maintainable code per loaded standards - Code Excellence - Clean, secure, maintainable code per loaded standards
- Numbered Options - Always use numbered lists when presenting choices - Numbered Options - Always use numbered lists when presenting choices