chore: add BMAD agent workflows and configuration system

- Add comprehensive agent workflow definitions for 8 specialized roles (analyst, architect, developer, product manager, scrum master, technical writer, UX designer, QA engineer)
- Add 35+ workflow definitions covering analysis, planning, solutioning, and implementation phases
- Add BMAD configuration system with agent, task, tool, workflow, and file manifests
- Add BMM (Business Model Methodology) documentation including quick-start guides, architecture references, and workflow analysis
- Add test architecture knowledge base with 20+ testing patterns and best practices
- Add team configuration templates and party mode setup for collaborative development
- Establish foundation for enterprise agentic development framework with adaptive scaling capabilities
This commit is contained in:
mahdiarghyani
2025-11-30 14:36:05 +03:30
parent af8b45aadb
commit 1586bb7f80
355 changed files with 73215 additions and 306 deletions
@@ -0,0 +1,47 @@
# BMad Quick Flow - Greenfield
# Fast implementation path with tech-spec planning (1-15 stories typically)
method_name: "BMad Quick Flow"
track: "quick-flow"
field_type: "greenfield"
description: "Fast tech-spec based implementation for greenfield projects"
phases:
- phase: 0
name: "Discovery (Optional)"
optional: true
note: "User-selected during workflow-init"
workflows:
- id: "brainstorm-project"
optional: true
agent: "analyst"
command: "brainstorm-project"
included_by: "user_choice"
- id: "research"
optional: true
agent: "analyst"
command: "research"
included_by: "user_choice"
note: "Can have multiple research workflows"
- phase: 1
name: "Planning"
required: true
workflows:
- id: "tech-spec"
required: true
agent: "pm"
command: "tech-spec"
output: "Technical Specification with stories (auto-detects epic if 2+ stories)"
note: "Quick Spec Flow - implementation-focused planning"
- phase: 2
name: "Implementation"
required: true
workflows:
- id: "sprint-planning"
required: true
agent: "sm"
command: "sprint-planning"
note: "Creates sprint plan with all stories - subsequent work tracked in sprint plan output, not workflow-status"