mirror of
https://github.com/bmadcode/BMAD-METHOD.git
synced 2025-12-29 16:14:59 +00:00
refactor: Major v6 epic creation improvements and documentation overhaul
## Key Changes ### 1. Epic Creation Workflow Enhancements - Added user-value focused epic structure principles (NO technical layer breakdown) - Implemented multi-mode detection: CONTINUE, REPLACE, or UPDATE existing epics - Added comprehensive anti-pattern examples showing wrong vs right epic breakdown - Epics now created AFTER architecture for technically-informed story breakdown - Added checkpoint protocol for interactive workflow progression ### 2. Removed Deprecated Solutioning Gate Check - Deleted entire solutioning-gate-check workflow (682 lines) - Replaced by new implementation-readiness workflow - Cleaner separation of concerns in solutioning phase ### 3. PRD Template Simplification - Removed hardcoded "Implementation Planning", "References", and "Next Steps" sections - PRD now focuses purely on requirements, not workflow orchestration - Epics/stories created as separate step after architecture ### 4. Documentation Overhaul (15+ docs updated) - Updated quick-start guide with v6 workflow sequence - Clarified that epics are created AFTER architecture, not during PRD - Updated solutioning docs to reflect implementation-readiness pattern - Improved agents-guide, brownfield-guide, enterprise docs - Enhanced glossary, FAQ, and workflow reference documentation ### 5. Workflow Path Adjustments - All 4 paths updated (enterprise/method × brownfield/greenfield) - Version bumps across BMGD, BMM, and CIS workflow YAMLs - Minor instruction file updates for consistency ### Files Changed - 65 files total: 468 insertions, 978 deletions (net reduction of 510 lines) - 4 files deleted (entire solutioning-gate-check workflow) - 1 new directory added (implementation-readiness placeholder)
This commit is contained in:
Brian Madison
@@ -117,7 +117,8 @@ Comprehensive documentation for all BMM workflows organized by phase:
|
||||
- Which planning workflow to use
|
||||
|
||||
- **[Phase 3: Solutioning Workflows](./workflows-solutioning.md)** - Architecture and validation (638 lines)
|
||||
- architecture, solutioning-gate-check
|
||||
- architecture, create-epics-and-stories, implementation-readiness
|
||||
- V6: Epics created AFTER architecture for better quality
|
||||
- Required for BMad Method and Enterprise Method tracks
|
||||
- Preventing agent conflicts
|
||||
|
||||
|
||||
@@ -63,7 +63,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
|
||||
|
||||
- Creating Product Requirements Documents (PRD) for Level 2-4 projects
|
||||
- Creating technical specifications for small projects (Level 0-1)
|
||||
- Breaking down requirements into epics and stories
|
||||
- Breaking down requirements into epics and stories (after architecture)
|
||||
- Validating planning documents
|
||||
- Course correction during implementation
|
||||
|
||||
@@ -72,10 +72,10 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
|
||||
**Workflows:**
|
||||
|
||||
- `workflow-status` - Check what to do next
|
||||
- `create-prd` - Create PRD for Level 2-4 projects
|
||||
- `create-prd` - Create PRD for Level 2-4 projects (creates FRs/NFRs only)
|
||||
- `tech-spec` - Quick spec for Level 0-1 projects
|
||||
- `create-epics-and-stories` - Break PRD into implementable pieces
|
||||
- `validate-prd` - Validate PRD + Epics completeness
|
||||
- `create-epics-and-stories` - Break PRD into implementable pieces (runs AFTER architecture)
|
||||
- `validate-prd` - Validate PRD completeness
|
||||
- `validate-tech-spec` - Validate Technical Specification
|
||||
- `correct-course` - Handle mid-project changes
|
||||
- `workflow-init` - Initialize workflow tracking
|
||||
@@ -136,7 +136,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
|
||||
- Creating system architecture for Level 2-4 projects
|
||||
- Making technical design decisions
|
||||
- Validating architecture documents
|
||||
- Solutioning gate checks (Phase 3→4 transition)
|
||||
- Validating readiness for implementation phase (Phase 3→4 transition)
|
||||
- Course correction during implementation
|
||||
|
||||
**Primary Phase:** Phase 3 (Solutioning)
|
||||
@@ -146,7 +146,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
|
||||
- `workflow-status` - Check what to do next
|
||||
- `create-architecture` - Produce a Scale Adaptive Architecture
|
||||
- `validate-architecture` - Validate architecture document
|
||||
- `solutioning-gate-check` - Validate readiness for Phase 4
|
||||
- `implementation-readiness` - Validate readiness for Phase 4
|
||||
|
||||
**Communication Style:** Comprehensive yet pragmatic. Uses architectural metaphors. Balances technical depth with accessibility. Connects decisions to business value.
|
||||
|
||||
@@ -482,7 +482,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
|
||||
|
||||
- Game system architecture
|
||||
- Technical foundation design for games
|
||||
- Solutioning gate checks for game projects
|
||||
- Validating readiness for implementation phase (game projects)
|
||||
- Course correction during game development
|
||||
|
||||
**Primary Phase:** Phase 3 (Solutioning - Games)
|
||||
@@ -491,7 +491,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
|
||||
|
||||
- `workflow-status` - Check what to do next
|
||||
- `create-architecture` - Game systems architecture
|
||||
- `solutioning-gate-check` - Validate Phase 3→4 transition
|
||||
- `implementation-readiness` - Validate Phase 3→4 transition
|
||||
- `correct-course` - Handle technical changes
|
||||
|
||||
**Communication Style:** Calm and measured. Systematic thinking about complex systems. Uses chess metaphors and military strategy. Emphasizes balance and elegance.
|
||||
@@ -604,15 +604,15 @@ Some workflows are available to multiple agents:
|
||||
|
||||
Many workflows have optional validation workflows that perform independent review:
|
||||
|
||||
| Validation | Agent | Validates |
|
||||
| ---------------------------- | ----------- | ---------------------------------- |
|
||||
| `validate-prd` | PM | PRD + Epics + Stories completeness |
|
||||
| `validate-tech-spec` | PM | Technical specification quality |
|
||||
| `validate-architecture` | Architect | Architecture document |
|
||||
| `validate-design` | UX Designer | UX specification and artifacts |
|
||||
| `validate-epic-tech-context` | SM | Epic technical context |
|
||||
| `validate-create-story` | SM | Story draft |
|
||||
| `validate-story-context` | SM | Story context XML |
|
||||
| Validation | Agent | Validates |
|
||||
| ---------------------------- | ----------- | -------------------------------- |
|
||||
| `validate-prd` | PM | PRD completeness (FRs/NFRs only) |
|
||||
| `validate-tech-spec` | PM | Technical specification quality |
|
||||
| `validate-architecture` | Architect | Architecture document |
|
||||
| `validate-design` | UX Designer | UX specification and artifacts |
|
||||
| `validate-epic-tech-context` | SM | Epic technical context |
|
||||
| `validate-create-story` | SM | Story draft |
|
||||
| `validate-story-context` | SM | Story context XML |
|
||||
|
||||
**When to use validation:**
|
||||
|
||||
@@ -849,7 +849,8 @@ Load the customized agent and verify the changes are reflected in its behavior a
|
||||
2. Analyst: *brainstorm-project or *product-brief (optional)
|
||||
3. PM: *create-prd (Level 2-4) or *tech-spec (Level 0-1)
|
||||
4. Architect: *create-architecture (Level 3-4 only)
|
||||
5. SM: *sprint-planning
|
||||
5. PM: *create-epics-and-stories (after architecture)
|
||||
6. SM: *sprint-planning
|
||||
```
|
||||
|
||||
**Starting with Existing Code (Brownfield):**
|
||||
@@ -859,7 +860,8 @@ Load the customized agent and verify the changes are reflected in its behavior a
|
||||
2. PM or Analyst: *workflow-init
|
||||
3. PM: *create-prd or *tech-spec
|
||||
4. Architect: *create-architecture (if needed)
|
||||
5. SM: *sprint-planning
|
||||
5. PM: *create-epics-and-stories (after architecture)
|
||||
6. SM: *sprint-planning
|
||||
```
|
||||
|
||||
**Story Development Cycle:**
|
||||
@@ -911,7 +913,7 @@ Agent analyzes project state → recommends next workflow
|
||||
```
|
||||
Each phase has validation gates:
|
||||
- Phase 2→3: validate-prd, validate-tech-spec
|
||||
- Phase 3→4: solutioning-gate-check
|
||||
- Phase 3→4: implementation-readiness
|
||||
Run validation before advancing
|
||||
```
|
||||
|
||||
@@ -943,14 +945,14 @@ Quick reference for agent selection:
|
||||
| **Analyst** | 📊 | 1 (Analysis) | brainstorm, brief, research, document-project | Discovery, requirements, brownfield |
|
||||
| **PM** | 📋 | 2 (Planning) | prd, tech-spec, epics-stories | Planning, requirements docs |
|
||||
| **UX Designer** | 🎨 | 2 (Planning) | create-design, validate-design | UX-heavy projects, design |
|
||||
| **Architect** | 🏗️ | 3 (Solutioning) | architecture, gate-check | Technical design, architecture |
|
||||
| **Architect** | 🏗️ | 3 (Solutioning) | architecture, implementation-readiness | Technical design, architecture |
|
||||
| **SM** | 🏃 | 4 (Implementation) | sprint-planning, create-story, story-context | Story management, sprint coordination |
|
||||
| **DEV** | 💻 | 4 (Implementation) | develop-story, code-review, story-done | Implementation, coding |
|
||||
| **TEA** | 🧪 | All Phases | framework, atdd, automate, trace, ci | Testing, quality assurance |
|
||||
| **Paige (Tech Writer)** | 📚 | All Phases | document-project, diagrams, validation | Documentation, diagrams |
|
||||
| **Game Designer** | 🎲 | 1-2 (Games) | brainstorm-game, gdd, narrative | Game design, creative vision |
|
||||
| **Game Developer** | 🕹️ | 4 (Games) | develop-story, story-done, code-review | Game implementation |
|
||||
| **Game Architect** | 🏛️ | 3 (Games) | architecture, gate-check | Game systems architecture |
|
||||
| **Game Architect** | 🏛️ | 3 (Games) | architecture, implementation-readiness | Game systems architecture |
|
||||
| **BMad Master** | 🧙 | Meta | party-mode, list tasks/workflows | Orchestration, multi-agent |
|
||||
|
||||
### Agent Capabilities Summary
|
||||
|
||||
@@ -291,9 +291,10 @@ See the [Workflows section in BMM README](../README.md) for details.
|
||||
|
||||
**BMad Method/Enterprise:** Use `prd` workflow
|
||||
|
||||
- Creates PRD.md + epic breakdown
|
||||
- Creates PRD.md with FRs/NFRs only
|
||||
- References existing architecture
|
||||
- Plans integration points
|
||||
- Epics+Stories created AFTER architecture phase
|
||||
|
||||
**Brownfield-specific:** See [Scale Adaptive System](./scale-adaptive-system.md) for complete workflow paths by track.
|
||||
|
||||
@@ -309,7 +310,8 @@ See the [Workflows section in BMM README](../README.md) for details.
|
||||
**Workflows:**
|
||||
|
||||
- `create-architecture` - Extend architecture docs (BMad Method/Enterprise)
|
||||
- `solutioning-gate-check` - Validate before implementation (BMad Method/Enterprise)
|
||||
- `create-epics-and-stories` - Create epics and stories AFTER architecture
|
||||
- `implementation-readiness` - Validate before implementation (BMad Method/Enterprise)
|
||||
|
||||
### Phase 4: Implementation (All Tracks)
|
||||
|
||||
@@ -473,8 +475,8 @@ Document in tech-spec/architecture:
|
||||
|
||||
1. **Document:** Run `document-project` (Deep scan) - Critical for understanding existing UI patterns
|
||||
2. **Analyze:** Load Analyst → `research` (if evaluating analytics libraries)
|
||||
3. **Plan:** Load PM → `prd`
|
||||
4. **Solution:** Load Architect → `create-architecture` → `solutioning-gate-check`
|
||||
3. **Plan:** Load PM → `prd` (creates FRs/NFRs)
|
||||
4. **Solution:** Load Architect → `create-architecture` → `create-epics-and-stories` → `implementation-readiness`
|
||||
5. **Implement:** Sprint-based (10-15 stories)
|
||||
- Load SM → `sprint-planning`
|
||||
- Per epic: `epic-tech-context` → stories
|
||||
@@ -495,10 +497,11 @@ Document in tech-spec/architecture:
|
||||
|
||||
1. **Document:** Run `document-project` (Exhaustive if not documented) - **Mandatory**
|
||||
2. **Analyze:** Load Analyst → `research` (WebSocket vs WebRTC vs CRDT)
|
||||
3. **Plan:** Load PM → `prd`
|
||||
3. **Plan:** Load PM → `prd` (creates FRs/NFRs)
|
||||
4. **Solution:**
|
||||
- Load Architect → `create-architecture` (extend for real-time layer)
|
||||
- Load Architect → `solutioning-gate-check`
|
||||
- Load Architect → `create-epics-and-stories`
|
||||
- Load Architect → `implementation-readiness`
|
||||
5. **Implement:** Sprint-based (20-30 stories)
|
||||
|
||||
**Time:** 3-6 weeks
|
||||
@@ -518,13 +521,14 @@ Document in tech-spec/architecture:
|
||||
- `brainstorm-project` - Explore multi-tenancy approaches
|
||||
- `research` - Database sharding, tenant isolation, pricing
|
||||
- `product-brief` - Strategic document
|
||||
3. **Plan:** Load PM → `prd` (comprehensive)
|
||||
3. **Plan:** Load PM → `prd` (comprehensive FRs/NFRs)
|
||||
4. **Solution:**
|
||||
- `create-architecture` - Full system architecture
|
||||
- `integration-planning` - Phased migration strategy
|
||||
- `create-architecture` - Multi-tenancy architecture
|
||||
- `validate-architecture` - External review
|
||||
- `solutioning-gate-check` - Executive approval
|
||||
- `create-epics-and-stories` - Create epics and stories
|
||||
- `implementation-readiness` - Executive approval
|
||||
5. **Implement:** Phased sprint-based (50+ stories)
|
||||
|
||||
**Time:** 3-6 months
|
||||
@@ -634,7 +638,8 @@ prd # BMad Method/Enterprise tracks
|
||||
# Phase 3: Solutioning (BMad Method/Enterprise)
|
||||
# Architect agent:
|
||||
create-architecture # Extend architecture
|
||||
solutioning-gate-check # Final validation
|
||||
create-epics-and-stories # Create epics and stories (after architecture)
|
||||
implementation-readiness # Final validation
|
||||
|
||||
# Phase 4: Implementation (All Tracks)
|
||||
# SM agent:
|
||||
@@ -668,8 +673,11 @@ correct-course # If issues
|
||||
**Phase 2 Planning:**
|
||||
|
||||
- `docs/tech-spec.md` (Quick Flow track)
|
||||
- `docs/PRD.md` (BMad Method/Enterprise tracks)
|
||||
- Epic breakdown
|
||||
- `docs/PRD.md` (BMad Method/Enterprise tracks - FRs/NFRs only)
|
||||
|
||||
**Phase 3 Solutioning:**
|
||||
|
||||
- Epic breakdown (created after architecture)
|
||||
|
||||
**Phase 3 Architecture:**
|
||||
|
||||
|
||||
@@ -140,34 +140,15 @@ bmad pm *create-prd
|
||||
**BMad produces:**
|
||||
|
||||
- Structured, machine-readable requirements
|
||||
- Testable acceptance criteria per requirement
|
||||
- Clear epic/story decomposition
|
||||
- Functional Requirements (FRs) with testable acceptance criteria
|
||||
- Non-Functional Requirements (NFRs) with measurable targets
|
||||
- Technical context for AI agents
|
||||
|
||||
**Why it matters:** Traditional PRDs are human-readable prose. BMad PRDs are **AI-executable work packages**.
|
||||
**Why it matters:** Traditional PRDs are human-readable prose. BMad PRDs are **AI-executable requirement specifications**.
|
||||
|
||||
**PM Value:** Write once, automatically translated into agent-ready stories. No engineering bottleneck for translation.
|
||||
**PM Value:** Clear requirements that feed into architecture decisions, then into story breakdown. No ambiguity.
|
||||
|
||||
### 2. Automated Epic/Story Breakdown
|
||||
|
||||
**PM Workflow:**
|
||||
|
||||
```bash
|
||||
bmad pm *create-epics-and-stories
|
||||
```
|
||||
|
||||
**BMad produces:**
|
||||
|
||||
- Epic files with clear objectives
|
||||
- Story files with acceptance criteria, context, technical guidance
|
||||
- Priority assignments (P0-P3)
|
||||
- Dependency mapping
|
||||
|
||||
**Why it matters:** Stories become **work packages for cloud AI agents**. Each story is self-contained with full context.
|
||||
|
||||
**PM Value:** No more "story refinement sessions" with engineering. AI agents execute directly from BMad stories.
|
||||
|
||||
### 3. Human-in-the-Loop Architecture
|
||||
### 2. Human-in-the-Loop Architecture
|
||||
|
||||
**Architect/PM Workflow:**
|
||||
|
||||
@@ -177,23 +158,46 @@ bmad architect *create-architecture
|
||||
|
||||
**BMad produces:**
|
||||
|
||||
- System architecture aligned with PRD
|
||||
- System architecture aligned with PRD's FRs/NFRs
|
||||
- Architecture Decision Records (ADRs)
|
||||
- Epic-specific technical guidance
|
||||
- FR/NFR-specific technical guidance
|
||||
- Integration patterns and standards
|
||||
|
||||
**Why it matters:** PMs can **understand and validate** technical decisions. Architecture is conversational, not template-driven.
|
||||
|
||||
**PM Value:** Technical fluency built through guided architecture process. PMs learn while creating.
|
||||
|
||||
### 3. Automated Epic/Story Breakdown (AFTER Architecture)
|
||||
|
||||
**PM Workflow:**
|
||||
|
||||
```bash
|
||||
bmad pm *create-epics-and-stories
|
||||
```
|
||||
|
||||
**V6 Improvement:** Epics and stories are now created AFTER architecture for better quality. The workflow uses both PRD (FRs/NFRs) and Architecture to create technically-informed stories.
|
||||
|
||||
**BMad produces:**
|
||||
|
||||
- Epic files with clear objectives
|
||||
- Story files with acceptance criteria, context, technical guidance
|
||||
- Priority assignments (P0-P3)
|
||||
- Dependency mapping informed by architectural decisions
|
||||
|
||||
**Why it matters:** Stories become **work packages for cloud AI agents**. Each story is self-contained with full context AND aligned with architecture.
|
||||
|
||||
**PM Value:** No more "story refinement sessions" with engineering. Stories are technically grounded from the start.
|
||||
|
||||
### 4. Cloud Agentic Pipeline (Emerging Pattern)
|
||||
|
||||
**Current State (2025):**
|
||||
|
||||
```
|
||||
PM writes BMad PRD
|
||||
PM writes BMad PRD (FRs/NFRs)
|
||||
↓
|
||||
create-epics-and-stories generates story queue
|
||||
Architect creates architecture (technical decisions)
|
||||
↓
|
||||
create-epics-and-stories generates story queue (informed by architecture)
|
||||
↓
|
||||
Stories loaded by human developers + BMad agents
|
||||
↓
|
||||
@@ -207,9 +211,11 @@ Merge and deploy
|
||||
**Near Future (2026):**
|
||||
|
||||
```
|
||||
PM writes BMad PRD
|
||||
PM writes BMad PRD (FRs/NFRs)
|
||||
↓
|
||||
create-epics-and-stories generates story queue
|
||||
Architecture auto-generated with PM approval
|
||||
↓
|
||||
create-epics-and-stories generates story queue (informed by architecture)
|
||||
↓
|
||||
Stories automatically fed to cloud AI agent pool
|
||||
↓
|
||||
|
||||
@@ -147,7 +147,7 @@ If status file exists, use workflow-status. If not, use workflow-init.
|
||||
|
||||
### Q: How do I know when Phase 3 is complete and I can start Phase 4?
|
||||
|
||||
**A:** For Level 3-4, run the solutioning-gate-check workflow. It validates that PRD, architecture, and UX (if applicable) are cohesive before implementation. Pass the gate check = ready for Phase 4.
|
||||
**A:** For Level 3-4, run the implementation-readiness workflow. It validates that PRD (FRs/NFRs), architecture, epics+stories, and UX (if applicable) are cohesive before implementation. Pass the gate check = ready for Phase 4.
|
||||
|
||||
### Q: Can I run workflows in parallel or do they have to be sequential?
|
||||
|
||||
@@ -155,7 +155,7 @@ If status file exists, use workflow-status. If not, use workflow-init.
|
||||
|
||||
- Phase 1: brainstorm → research → product-brief (optional order)
|
||||
- Phase 2: PRD must complete before moving forward
|
||||
- Phase 3: architecture → validate → gate-check (sequential)
|
||||
- Phase 3: architecture → epics+stories → implementation-readiness (sequential)
|
||||
- Phase 4: Stories within an epic should generally be sequential, but stories in different epics can be parallel if you have capacity
|
||||
|
||||
---
|
||||
@@ -175,8 +175,9 @@ Think of it as: tech-spec is for small projects (replaces PRD and architecture),
|
||||
|
||||
**A:** Level 2+ projects need product-level planning (PRD) and system-level design (Architecture), which tech-spec doesn't provide. Tech-spec is too narrow for coordinating multiple features. Instead, Level 2-4 uses:
|
||||
|
||||
- PRD (product vision, requirements, epics)
|
||||
- PRD (product vision, functional requirements, non-functional requirements)
|
||||
- Architecture (system design)
|
||||
- Epics+Stories (created AFTER architecture is complete)
|
||||
- Epic-tech-context (detailed implementation per epic, created just-in-time)
|
||||
|
||||
### Q: When do I create epic-tech-context?
|
||||
|
||||
@@ -77,7 +77,7 @@ The methodology path (Quick Flow, BMad Method, or Enterprise Method) chosen for
|
||||
|
||||
### PRD (Product Requirements Document)
|
||||
|
||||
**BMad Method/Enterprise tracks.** Product-level planning document containing vision, goals, feature requirements, epic breakdown, success criteria, and UX considerations. Replaces tech-spec for larger projects that need product planning.
|
||||
**BMad Method/Enterprise tracks.** Product-level planning document containing vision, goals, Functional Requirements (FRs), Non-Functional Requirements (NFRs), success criteria, and UX considerations. Replaces tech-spec for larger projects that need product planning. **V6 Note:** PRD focuses on WHAT to build (requirements). Epic+Stories are created separately AFTER architecture via create-epics-and-stories workflow.
|
||||
|
||||
### Architecture Document
|
||||
|
||||
@@ -263,7 +263,7 @@ Workflow that initializes Phase 4 implementation by creating sprint-status.yaml,
|
||||
|
||||
### Gate Check
|
||||
|
||||
Validation workflow (solutioning-gate-check) run before Phase 4 to ensure PRD, architecture, and UX documents are cohesive with no gaps or contradictions. Required for BMad Method and Enterprise Method tracks.
|
||||
Validation workflow (implementation-readiness) run before Phase 4 to ensure PRD, architecture, and UX documents are cohesive with no gaps or contradictions. Required for BMad Method and Enterprise Method tracks.
|
||||
|
||||
### DoD (Definition of Done)
|
||||
|
||||
|
||||
@@ -122,7 +122,7 @@ For v4 users or those who prefer to skip workflow-status guidance:
|
||||
|
||||
- **Analyst** → Brainstorming, Product Brief
|
||||
- **PM** → PRD (BMad Method/Enterprise tracks) OR tech-spec (Quick Flow track)
|
||||
- **UX-Designer** → UX Design Document (if UI-heavy)
|
||||
- **UX-Designer** → UX Design Document (if UI part of the project)
|
||||
- **Architect** → Architecture (BMad Method/Enterprise tracks)
|
||||
|
||||
#### Phase 2: Planning - Creating the PRD
|
||||
@@ -133,7 +133,6 @@ For v4 users or those who prefer to skip workflow-status guidance:
|
||||
2. Tell it to run the PRD workflow
|
||||
3. Once complete, you'll have:
|
||||
- **PRD.md** - Your Product Requirements Document
|
||||
- Epic breakdown
|
||||
|
||||
**For Quick Flow track:**
|
||||
|
||||
@@ -145,7 +144,7 @@ If your project has a user interface:
|
||||
|
||||
1. Load the **UX-Designer agent** in a new chat
|
||||
2. Tell it to run the UX design workflow
|
||||
3. After completion, run validations to ensure the Epics file stays updated
|
||||
3. After completion, you'll have your UX specification document
|
||||
|
||||
#### Phase 3: Architecture
|
||||
|
||||
@@ -153,14 +152,25 @@ If your project has a user interface:
|
||||
|
||||
1. Load the **Architect agent** in a new chat
|
||||
2. Tell it to run the create-architecture workflow
|
||||
3. After completion, run validations to ensure the Epics file stays updated
|
||||
3. After completion, you'll have your architecture document with technical decisions
|
||||
|
||||
#### Phase 3: Solutioning Gate Check (Highly Recommended)
|
||||
#### Phase 3: Create Epics and Stories (REQUIRED after Architecture)
|
||||
|
||||
Once architecture is complete:
|
||||
**V6 Improvement:** Epics and stories are now created AFTER architecture for better quality!
|
||||
|
||||
1. Load the **PM agent** in a new chat
|
||||
2. Tell it to run "create-epics-and-stories"
|
||||
3. This breaks down your PRD's FRs/NFRs into implementable epics and stories
|
||||
4. The workflow uses both PRD and Architecture to create technically-informed stories
|
||||
|
||||
**Why after architecture?** Architecture decisions (database, API patterns, tech stack) directly affect how stories should be broken down and sequenced.
|
||||
|
||||
#### Phase 3: Implementation Readiness Check (Highly Recommended)
|
||||
|
||||
Once epics and stories are created:
|
||||
|
||||
1. Load the **Architect agent** in a new chat
|
||||
2. Tell it to run "solutioning-gate-check"
|
||||
2. Tell it to run "implementation-readiness"
|
||||
3. This validates cohesion across all your planning documents (PRD, UX, Architecture, Epics)
|
||||
4. This was called the "PO Master Checklist" in v4
|
||||
|
||||
|
||||
@@ -154,10 +154,10 @@ Tech-Spec → Implement
|
||||
|
||||
**Planning Docs**:
|
||||
|
||||
- PRD.md (product requirements)
|
||||
- PRD.md (functional and non-functional requirements)
|
||||
- Architecture.md (system design)
|
||||
- UX Design (if UI components)
|
||||
- Epic breakdown with stories
|
||||
- Epics and Stories (created after architecture)
|
||||
|
||||
**Workflow Path**:
|
||||
|
||||
@@ -166,7 +166,7 @@ Tech-Spec → Implement
|
||||
↓
|
||||
(Optional: Analysis phase - brainstorm, research, product brief)
|
||||
↓
|
||||
PRD → (Optional UX) → Architecture → Gate Check → Implement
|
||||
PRD → (Optional UX) → Architecture → Create Epics and Stories → Implementation Readiness Check → Implement
|
||||
```
|
||||
|
||||
**Use For**:
|
||||
@@ -228,9 +228,11 @@ Your brownfield documentation might be huge. Architecture workflow distills mass
|
||||
↓
|
||||
Analysis (recommended/required) → PRD → UX → Architecture
|
||||
↓
|
||||
Create Epics and Stories
|
||||
↓
|
||||
Security Architecture → DevOps Strategy → Test Strategy
|
||||
↓
|
||||
Gate Check → Implement
|
||||
Implementation Readiness Check → Implement
|
||||
```
|
||||
|
||||
**Use For**:
|
||||
@@ -287,12 +289,14 @@ Gate Check → Implement
|
||||
**PRD (Product Requirements Document)**:
|
||||
|
||||
- Product vision and goals
|
||||
- Feature requirements
|
||||
- Epic breakdown with stories
|
||||
- Functional requirements (FRs)
|
||||
- Non-functional requirements (NFRs)
|
||||
- Success criteria
|
||||
- User experience considerations
|
||||
- Business context
|
||||
|
||||
**Note**: Epics and stories are created AFTER architecture in the create-epics-and-stories workflow
|
||||
|
||||
**Architecture Document**:
|
||||
|
||||
- System components and responsibilities
|
||||
@@ -444,11 +448,12 @@ flowchart TD
|
||||
**Workflow**:
|
||||
|
||||
1. (Recommended) Product Brief
|
||||
2. PRD with epics
|
||||
2. PRD (FRs/NFRs)
|
||||
3. (If UI) UX Design
|
||||
4. Architecture (system design)
|
||||
5. Gate Check
|
||||
6. Implement with sprint planning
|
||||
5. Create Epics and Stories
|
||||
6. Implementation Readiness Check
|
||||
7. Implement with sprint planning
|
||||
|
||||
**Time**: 1-2 weeks
|
||||
|
||||
@@ -465,11 +470,12 @@ flowchart TD
|
||||
**Workflow**:
|
||||
|
||||
1. Research + Product Brief
|
||||
2. Comprehensive PRD
|
||||
2. Comprehensive PRD (FRs/NFRs)
|
||||
3. UX Design (recommended)
|
||||
4. System Architecture (required)
|
||||
5. Gate check
|
||||
6. Implement with phased approach
|
||||
5. Create Epics and Stories
|
||||
6. Implementation Readiness Check
|
||||
7. Implement with phased approach
|
||||
|
||||
**Time**: 3-6 weeks
|
||||
|
||||
@@ -487,7 +493,13 @@ flowchart TD
|
||||
|
||||
1. **Run document-project** to analyze existing codebase
|
||||
|
||||
**Then Workflow**: 2. PRD for search feature 3. Architecture (integration design - highly recommended) 4. Implement following existing patterns
|
||||
**Then Workflow**:
|
||||
|
||||
2. PRD for search feature (FRs/NFRs)
|
||||
3. Architecture (integration design - highly recommended)
|
||||
4. Create Epics and Stories
|
||||
5. Implementation Readiness Check
|
||||
6. Implement following existing patterns
|
||||
|
||||
**Time**: 1-2 weeks
|
||||
|
||||
@@ -507,13 +519,14 @@ flowchart TD
|
||||
|
||||
1. Document-project (mandatory)
|
||||
2. Research (compliance, security)
|
||||
3. PRD (multi-tenancy requirements)
|
||||
3. PRD (multi-tenancy requirements - FRs/NFRs)
|
||||
4. Architecture (tenant isolation design)
|
||||
5. Security Architecture (data isolation, auth)
|
||||
6. DevOps Strategy (tenant provisioning, monitoring)
|
||||
7. Test Strategy (tenant isolation testing)
|
||||
8. Gate check
|
||||
9. Phased implementation
|
||||
5. Create Epics and Stories
|
||||
6. Security Architecture (data isolation, auth)
|
||||
7. DevOps Strategy (tenant provisioning, monitoring)
|
||||
8. Test Strategy (tenant isolation testing)
|
||||
9. Implementation Readiness Check
|
||||
10. Phased implementation
|
||||
|
||||
**Time**: 3-6 months
|
||||
|
||||
@@ -533,9 +546,9 @@ If `workflow-init` suggests BMad Method, there's probably complexity you haven't
|
||||
|
||||
Uncertain between Quick Flow and Method? Start with Quick Flow. You can create PRD later if needed.
|
||||
|
||||
### 4. Don't Skip Gate Checks
|
||||
### 4. Don't Skip Implementation Readiness Check
|
||||
|
||||
For BMad Method and Enterprise, gate checks prevent costly mistakes. Invest the time.
|
||||
For BMad Method and Enterprise, implementation readiness checks prevent costly mistakes. Invest the time.
|
||||
|
||||
### 5. Architecture is Optional but Recommended for Brownfield
|
||||
|
||||
|
||||
@@ -18,21 +18,23 @@ TEA integrates into the BMad development lifecycle during Solutioning (Phase 3)
|
||||
%%{init: {'theme':'base', 'themeVariables': { 'primaryColor':'#fff','primaryTextColor':'#000','primaryBorderColor':'#000','lineColor':'#000','secondaryColor':'#fff','tertiaryColor':'#fff','fontSize':'16px','fontFamily':'arial'}}}%%
|
||||
graph TB
|
||||
subgraph Phase2["<b>Phase 2: PLANNING</b>"]
|
||||
PM["<b>PM: *prd (creates PRD + epics)</b>"]
|
||||
PM["<b>PM: *prd (creates PRD with FRs/NFRs)</b>"]
|
||||
PlanNote["<b>Business requirements phase</b>"]
|
||||
PM -.-> PlanNote
|
||||
end
|
||||
|
||||
subgraph Phase3["<b>Phase 3: SOLUTIONING</b>"]
|
||||
Architecture["<b>Architect: *architecture</b>"]
|
||||
EpicsStories["<b>PM/Architect: *create-epics-and-stories</b>"]
|
||||
Framework["<b>TEA: *framework</b>"]
|
||||
CI["<b>TEA: *ci</b>"]
|
||||
GateCheck["<b>Architect: *solutioning-gate-check</b>"]
|
||||
Architecture --> Framework
|
||||
GateCheck["<b>Architect: *implementation-readiness</b>"]
|
||||
Architecture --> EpicsStories
|
||||
EpicsStories --> Framework
|
||||
Framework --> CI
|
||||
CI --> GateCheck
|
||||
Phase3Note["<b>Test infrastructure AFTER architecture</b><br/>defines technology stack"]
|
||||
Framework -.-> Phase3Note
|
||||
Phase3Note["<b>Epics created AFTER architecture,</b><br/><b>then test infrastructure setup</b>"]
|
||||
EpicsStories -.-> Phase3Note
|
||||
end
|
||||
|
||||
subgraph Phase4["<b>Phase 4: IMPLEMENTATION - Per Epic Cycle</b>"]
|
||||
@@ -90,8 +92,8 @@ graph TB
|
||||
|
||||
- **Phase 0** (Optional): Documentation (brownfield prerequisite - `*document-project`)
|
||||
- **Phase 1** (Optional): Discovery/Analysis (`*brainstorm`, `*research`, `*product-brief`)
|
||||
- **Phase 2** (Required): Planning (`*prd` creates PRD + epics)
|
||||
- **Phase 3** (Track-dependent): Solutioning (`*architecture` → TEA: `*framework`, `*ci` → `*solutioning-gate-check`)
|
||||
- **Phase 2** (Required): Planning (`*prd` creates PRD with FRs/NFRs)
|
||||
- **Phase 3** (Track-dependent): Solutioning (`*architecture` → `*create-epics-and-stories` → TEA: `*framework`, `*ci` → `*implementation-readiness`)
|
||||
- **Phase 4** (Required): Implementation (`*sprint-planning` → per-epic: `*test-design` → per-story: dev workflows)
|
||||
|
||||
**TEA workflows:** `*framework` and `*ci` run once in Phase 3 after architecture. `*test-design` runs per-epic in Phase 4. Output: `test-design-epic-N.md`.
|
||||
@@ -191,16 +193,16 @@ These cheat sheets map TEA workflows to the **BMad Method and Enterprise tracks*
|
||||
**Planning Track:** BMad Method (PRD + Architecture)
|
||||
**Use Case:** New projects with standard complexity
|
||||
|
||||
| Workflow Stage | Test Architect | Dev / Team | Outputs |
|
||||
| -------------------------- | ----------------------------------------------------------------- | ---------------------------------------------------- | ---------------------------------------------------------- |
|
||||
| **Phase 1**: Discovery | - | Analyst `*product-brief` (optional) | `product-brief.md` |
|
||||
| **Phase 2**: Planning | - | PM `*prd` (creates PRD + epics) | PRD, epics |
|
||||
| **Phase 3**: Solutioning | Run `*framework`, `*ci` AFTER architecture | Architect `*architecture`, `*solutioning-gate-check` | Architecture, test scaffold, CI pipeline |
|
||||
| **Phase 4**: Sprint Start | - | SM `*sprint-planning` | Sprint status file with all epics and stories |
|
||||
| **Phase 4**: Epic Planning | Run `*test-design` for THIS epic (per-epic test plan) | Review epic scope | `test-design-epic-N.md` with risk assessment and test plan |
|
||||
| **Phase 4**: Story Dev | (Optional) `*atdd` before dev, then `*automate` after | SM `*create-story`, DEV implements | Tests, story implementation |
|
||||
| **Phase 4**: Story Review | Execute `*test-review` (optional), re-run `*trace` | Address recommendations, update code/tests | Quality report, refreshed coverage matrix |
|
||||
| **Phase 4**: Release Gate | (Optional) `*test-review` for final audit, Run `*trace` (Phase 2) | Confirm Definition of Done, share release notes | Quality audit, Gate YAML + release summary |
|
||||
| Workflow Stage | Test Architect | Dev / Team | Outputs |
|
||||
| -------------------------- | ----------------------------------------------------------------- | ----------------------------------------------------------------------------------- | ---------------------------------------------------------- |
|
||||
| **Phase 1**: Discovery | - | Analyst `*product-brief` (optional) | `product-brief.md` |
|
||||
| **Phase 2**: Planning | - | PM `*prd` (creates PRD with FRs/NFRs) | PRD with functional/non-functional requirements |
|
||||
| **Phase 3**: Solutioning | Run `*framework`, `*ci` AFTER architecture and epic creation | Architect `*architecture`, `*create-epics-and-stories`, `*implementation-readiness` | Architecture, epics/stories, test scaffold, CI pipeline |
|
||||
| **Phase 4**: Sprint Start | - | SM `*sprint-planning` | Sprint status file with all epics and stories |
|
||||
| **Phase 4**: Epic Planning | Run `*test-design` for THIS epic (per-epic test plan) | Review epic scope | `test-design-epic-N.md` with risk assessment and test plan |
|
||||
| **Phase 4**: Story Dev | (Optional) `*atdd` before dev, then `*automate` after | SM `*create-story`, DEV implements | Tests, story implementation |
|
||||
| **Phase 4**: Story Review | Execute `*test-review` (optional), re-run `*trace` | Address recommendations, update code/tests | Quality report, refreshed coverage matrix |
|
||||
| **Phase 4**: Release Gate | (Optional) `*test-review` for final audit, Run `*trace` (Phase 2) | Confirm Definition of Done, share release notes | Quality audit, Gate YAML + release summary |
|
||||
|
||||
<details>
|
||||
<summary>Execution Notes</summary>
|
||||
@@ -218,8 +220,8 @@ These cheat sheets map TEA workflows to the **BMad Method and Enterprise tracks*
|
||||
<details>
|
||||
<summary>Worked Example – “Nova CRM” Greenfield Feature</summary>
|
||||
|
||||
1. **Planning (Phase 2):** Analyst runs `*product-brief`; PM executes `*prd` to produce PRD and epics.
|
||||
2. **Solutioning (Phase 3):** Architect completes `*architecture` for the new module; TEA sets up test infrastructure via `*framework` and `*ci` based on architectural decisions; gate check validates planning completeness.
|
||||
1. **Planning (Phase 2):** Analyst runs `*product-brief`; PM executes `*prd` to produce PRD with FRs/NFRs.
|
||||
2. **Solutioning (Phase 3):** Architect completes `*architecture` for the new module; `*create-epics-and-stories` generates epics/stories based on architecture; TEA sets up test infrastructure via `*framework` and `*ci` based on architectural decisions; gate check validates planning completeness.
|
||||
3. **Sprint Start (Phase 4):** Scrum Master runs `*sprint-planning` to load all epics into sprint status.
|
||||
4. **Epic 1 Planning (Phase 4):** TEA runs `*test-design` to create test plan for Epic 1, producing `test-design-epic-1.md` with risk assessment.
|
||||
5. **Story Implementation (Phase 4):** For each story in Epic 1, SM generates story via `*create-story`; TEA optionally runs `*atdd`; Dev implements with guidance from failing tests.
|
||||
@@ -240,17 +242,17 @@ These cheat sheets map TEA workflows to the **BMad Method and Enterprise tracks*
|
||||
- 🔄 Phase 4: `*test-design` - Focus on regression hotspots and brownfield risks
|
||||
- 🔄 Phase 4: Story Review - May include `*nfr-assess` if not done earlier
|
||||
|
||||
| Workflow Stage | Test Architect | Dev / Team | Outputs |
|
||||
| ----------------------------- | ---------------------------------------------------------------------------- | ---------------------------------------------------- | ---------------------------------------------------------------------- |
|
||||
| **Phase 0**: Documentation ➕ | - | Analyst `*document-project` (if undocumented) | Comprehensive project documentation |
|
||||
| **Phase 1**: Discovery | - | Analyst/PM/Architect rerun planning workflows | Updated planning artifacts in `{output_folder}` |
|
||||
| **Phase 2**: Planning | Run ➕ `*trace` (baseline coverage) | PM `*prd` (creates PRD + epics) | PRD, epics, ➕ coverage baseline |
|
||||
| **Phase 3**: Solutioning | Run `*framework`, `*ci` AFTER architecture | Architect `*architecture`, `*solutioning-gate-check` | Architecture, test framework, CI pipeline |
|
||||
| **Phase 4**: Sprint Start | - | SM `*sprint-planning` | Sprint status file with all epics and stories |
|
||||
| **Phase 4**: Epic Planning | Run `*test-design` for THIS epic 🔄 (regression hotspots) | Review epic scope and brownfield risks | `test-design-epic-N.md` with brownfield risk assessment and mitigation |
|
||||
| **Phase 4**: Story Dev | (Optional) `*atdd` before dev, then `*automate` after | SM `*create-story`, DEV implements | Tests, story implementation |
|
||||
| **Phase 4**: Story Review | Apply `*test-review` (optional), re-run `*trace`, ➕ `*nfr-assess` if needed | Resolve gaps, update docs/tests | Quality report, refreshed coverage matrix, NFR report |
|
||||
| **Phase 4**: Release Gate | (Optional) `*test-review` for final audit, Run `*trace` (Phase 2) | Capture sign-offs, share release notes | Quality audit, Gate YAML + release summary |
|
||||
| Workflow Stage | Test Architect | Dev / Team | Outputs |
|
||||
| ----------------------------- | ---------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
|
||||
| **Phase 0**: Documentation ➕ | - | Analyst `*document-project` (if undocumented) | Comprehensive project documentation |
|
||||
| **Phase 1**: Discovery | - | Analyst/PM/Architect rerun planning workflows | Updated planning artifacts in `{output_folder}` |
|
||||
| **Phase 2**: Planning | Run ➕ `*trace` (baseline coverage) | PM `*prd` (creates PRD with FRs/NFRs) | PRD with FRs/NFRs, ➕ coverage baseline |
|
||||
| **Phase 3**: Solutioning | Run `*framework`, `*ci` AFTER architecture and epic creation | Architect `*architecture`, `*create-epics-and-stories`, `*implementation-readiness` | Architecture, epics/stories, test framework, CI pipeline |
|
||||
| **Phase 4**: Sprint Start | - | SM `*sprint-planning` | Sprint status file with all epics and stories |
|
||||
| **Phase 4**: Epic Planning | Run `*test-design` for THIS epic 🔄 (regression hotspots) | Review epic scope and brownfield risks | `test-design-epic-N.md` with brownfield risk assessment and mitigation |
|
||||
| **Phase 4**: Story Dev | (Optional) `*atdd` before dev, then `*automate` after | SM `*create-story`, DEV implements | Tests, story implementation |
|
||||
| **Phase 4**: Story Review | Apply `*test-review` (optional), re-run `*trace`, ➕ `*nfr-assess` if needed | Resolve gaps, update docs/tests | Quality report, refreshed coverage matrix, NFR report |
|
||||
| **Phase 4**: Release Gate | (Optional) `*test-review` for final audit, Run `*trace` (Phase 2) | Capture sign-offs, share release notes | Quality audit, Gate YAML + release summary |
|
||||
|
||||
<details>
|
||||
<summary>Execution Notes</summary>
|
||||
@@ -268,8 +270,8 @@ These cheat sheets map TEA workflows to the **BMad Method and Enterprise tracks*
|
||||
<details>
|
||||
<summary>Worked Example – “Atlas Payments” Brownfield Story</summary>
|
||||
|
||||
1. **Planning (Phase 2):** PM executes `*prd` to update PRD and `epics.md` (Epic 1: Payment Processing); TEA runs `*trace` to baseline existing coverage.
|
||||
2. **Solutioning (Phase 3):** Architect triggers `*architecture` capturing legacy payment flows and integration architecture; TEA sets up `*framework` and `*ci` based on architectural decisions; gate check validates planning.
|
||||
1. **Planning (Phase 2):** PM executes `*prd` to create PRD with FRs/NFRs; TEA runs `*trace` to baseline existing coverage.
|
||||
2. **Solutioning (Phase 3):** Architect triggers `*architecture` capturing legacy payment flows and integration architecture; `*create-epics-and-stories` generates Epic 1 (Payment Processing) based on architecture; TEA sets up `*framework` and `*ci` based on architectural decisions; gate check validates planning.
|
||||
3. **Sprint Start (Phase 4):** Scrum Master runs `*sprint-planning` to load Epic 1 into sprint status.
|
||||
4. **Epic 1 Planning (Phase 4):** TEA runs `*test-design` for Epic 1 (Payment Processing), producing `test-design-epic-1.md` that flags settlement edge cases, regression hotspots, and mitigation plans.
|
||||
5. **Story Implementation (Phase 4):** For each story in Epic 1, SM generates story via `*create-story`; TEA runs `*atdd` producing failing Playwright specs; Dev implements with guidance from tests and checklist.
|
||||
@@ -290,15 +292,15 @@ These cheat sheets map TEA workflows to the **BMad Method and Enterprise tracks*
|
||||
- 🔄 Phase 4: `*test-design` - Enterprise focus (compliance, security architecture alignment)
|
||||
- 📦 Release Gate - Archive artifacts and compliance evidence for audits
|
||||
|
||||
| Workflow Stage | Test Architect | Dev / Team | Outputs |
|
||||
| -------------------------- | ------------------------------------------------------------------------ | ---------------------------------------------------- | ------------------------------------------------------------------ |
|
||||
| **Phase 1**: Discovery | - | Analyst ➕ `*research`, `*product-brief` | Domain research, compliance analysis, product brief |
|
||||
| **Phase 2**: Planning | Run ➕ `*nfr-assess` | PM `*prd` (creates PRD + epics), UX `*create-design` | Enterprise PRD, epics, UX design, ➕ NFR documentation |
|
||||
| **Phase 3**: Solutioning | Run `*framework`, `*ci` AFTER architecture | Architect `*architecture`, `*solutioning-gate-check` | Architecture, test framework, CI pipeline |
|
||||
| **Phase 4**: Sprint Start | - | SM `*sprint-planning` | Sprint plan with all epics |
|
||||
| **Phase 4**: Epic Planning | Run `*test-design` for THIS epic 🔄 (compliance focus) | Review epic scope and compliance requirements | `test-design-epic-N.md` with security/performance/compliance focus |
|
||||
| **Phase 4**: Story Dev | (Optional) `*atdd`, `*automate`, `*test-review`, `*trace` per story | SM `*create-story`, DEV implements | Tests, fixtures, quality reports, coverage matrices |
|
||||
| **Phase 4**: Release Gate | Final `*test-review` audit, Run `*trace` (Phase 2), 📦 archive artifacts | Capture sign-offs, 📦 compliance evidence | Quality audit, updated assessments, gate YAML, 📦 audit trail |
|
||||
| Workflow Stage | Test Architect | Dev / Team | Outputs |
|
||||
| -------------------------- | ------------------------------------------------------------------------ | ----------------------------------------------------------------------------------- | ------------------------------------------------------------------ |
|
||||
| **Phase 1**: Discovery | - | Analyst ➕ `*research`, `*product-brief` | Domain research, compliance analysis, product brief |
|
||||
| **Phase 2**: Planning | Run ➕ `*nfr-assess` | PM `*prd` (creates PRD with FRs/NFRs), UX `*create-design` | Enterprise PRD with FRs/NFRs, UX design, ➕ NFR documentation |
|
||||
| **Phase 3**: Solutioning | Run `*framework`, `*ci` AFTER architecture and epic creation | Architect `*architecture`, `*create-epics-and-stories`, `*implementation-readiness` | Architecture, epics/stories, test framework, CI pipeline |
|
||||
| **Phase 4**: Sprint Start | - | SM `*sprint-planning` | Sprint plan with all epics |
|
||||
| **Phase 4**: Epic Planning | Run `*test-design` for THIS epic 🔄 (compliance focus) | Review epic scope and compliance requirements | `test-design-epic-N.md` with security/performance/compliance focus |
|
||||
| **Phase 4**: Story Dev | (Optional) `*atdd`, `*automate`, `*test-review`, `*trace` per story | SM `*create-story`, DEV implements | Tests, fixtures, quality reports, coverage matrices |
|
||||
| **Phase 4**: Release Gate | Final `*test-review` audit, Run `*trace` (Phase 2), 📦 archive artifacts | Capture sign-offs, 📦 compliance evidence | Quality audit, updated assessments, gate YAML, 📦 audit trail |
|
||||
|
||||
<details>
|
||||
<summary>Execution Notes</summary>
|
||||
@@ -316,8 +318,8 @@ These cheat sheets map TEA workflows to the **BMad Method and Enterprise tracks*
|
||||
<details>
|
||||
<summary>Worked Example – “Helios Ledger” Enterprise Release</summary>
|
||||
|
||||
1. **Planning (Phase 2):** Analyst runs `*research` and `*product-brief`; PM completes `*prd` creating PRD and epics; TEA runs `*nfr-assess` to establish NFR targets.
|
||||
2. **Solutioning (Phase 3):** Architect completes `*architecture` with enterprise considerations; TEA sets up `*framework` and `*ci` with enterprise-grade configurations based on architectural decisions; gate check validates planning completeness.
|
||||
1. **Planning (Phase 2):** Analyst runs `*research` and `*product-brief`; PM completes `*prd` creating PRD with FRs/NFRs; TEA runs `*nfr-assess` to establish NFR targets.
|
||||
2. **Solutioning (Phase 3):** Architect completes `*architecture` with enterprise considerations; `*create-epics-and-stories` generates epics/stories based on architecture; TEA sets up `*framework` and `*ci` with enterprise-grade configurations based on architectural decisions; gate check validates planning completeness.
|
||||
3. **Sprint Start (Phase 4):** Scrum Master runs `*sprint-planning` to load all epics into sprint status.
|
||||
4. **Per-Epic (Phase 4):** For each epic, TEA runs `*test-design` to create epic-specific test plan (e.g., `test-design-epic-1.md`, `test-design-epic-2.md`) with compliance-focused risk assessment.
|
||||
5. **Per-Story (Phase 4):** For each story, TEA uses `*atdd`, `*automate`, `*test-review`, and `*trace`; Dev teams iterate on the findings.
|
||||
|
||||
@@ -72,7 +72,7 @@ The Decision Architecture workflow is a complete reimagining of how architectura
|
||||
```
|
||||
Step 0: Validate workflow and extract project configuration
|
||||
Step 0.5: Validate workflow sequencing
|
||||
Step 1: Load PRD and understand project context
|
||||
Step 1: Load PRD (with FRs/NFRs) and understand project context
|
||||
Step 2: Discover and evaluate starter templates ⭐ NEW
|
||||
Step 3: Adapt facilitation style and identify remaining decisions
|
||||
Step 4: Facilitate collaborative decision making (with version verification)
|
||||
@@ -122,11 +122,6 @@ Step 12: Final review and update workflow status
|
||||
- Non-Functional Requirements
|
||||
- Performance and compliance needs
|
||||
|
||||
- **Epics** file with:
|
||||
- User stories
|
||||
- Acceptance criteria
|
||||
- Dependencies
|
||||
|
||||
- **UX Spec** (Optional but valuable) with:
|
||||
- Interface designs and interaction patterns
|
||||
- Accessibility requirements (WCAG levels)
|
||||
@@ -280,7 +275,7 @@ workflow architecture
|
||||
|
||||
The AI agent will:
|
||||
|
||||
1. Load your PRD and epics
|
||||
1. Load your PRD (with FRs/NFRs)
|
||||
2. Identify critical decisions needed
|
||||
3. Facilitate discussion on each decision
|
||||
4. Generate a comprehensive architecture document
|
||||
|
||||
@@ -202,7 +202,9 @@ PRD Workflow: Loads docs/index.md
|
||||
→ Understands existing architecture
|
||||
→ Identifies reusable components
|
||||
→ Plans integration with existing APIs
|
||||
→ Creates contextual PRD with epics and stories
|
||||
→ Creates contextual PRD with FRs and NFRs
|
||||
Architecture Workflow: Creates architecture design
|
||||
Create-Epics-and-Stories Workflow: Breaks down into epics and stories
|
||||
```
|
||||
|
||||
### Other Use Cases
|
||||
|
||||
@@ -162,7 +162,8 @@ Stories move through these states in the sprint status file:
|
||||
### Sprint 0 (Planning Phase)
|
||||
|
||||
- Complete Phases 1-3 (Analysis, Planning, Solutioning)
|
||||
- PRD/GDD + Architecture + Epics ready
|
||||
- PRD/GDD + Architecture complete
|
||||
- **V6: Epics+Stories created via create-epics-and-stories workflow (runs AFTER architecture)**
|
||||
|
||||
### Sprint 1+ (Implementation Phase)
|
||||
|
||||
@@ -235,8 +236,9 @@ tech-spec (PM)
|
||||
### Level 2-4 (BMad Method / Enterprise)
|
||||
|
||||
```
|
||||
PRD + Architecture (PM/Architect)
|
||||
→ solutioning-gate-check (Architect)
|
||||
PRD (PM) → Architecture (Architect)
|
||||
→ create-epics-and-stories (PM) ← V6: After architecture!
|
||||
→ implementation-readiness (Architect)
|
||||
→ sprint-planning (SM, once)
|
||||
→ [Per Epic]:
|
||||
epic-tech-context (SM)
|
||||
|
||||
@@ -26,13 +26,17 @@ graph TB
|
||||
|
||||
subgraph BMadMethod["<b>BMAD METHOD (Recommended)</b>"]
|
||||
direction TB
|
||||
PRD["<b>PM: prd</b><br/>Strategic PRD"]
|
||||
PRD["<b>PM: prd</b><br/>Strategic PRD with FRs/NFRs"]
|
||||
GDD["<b>Game Designer: gdd</b><br/>Game design doc"]
|
||||
Narrative["<b>Game Designer: narrative</b><br/>Story-driven design"]
|
||||
|
||||
Epics["<b>PM: create-epics-and-stories</b><br/>Epic+Stories breakdown<br/>10-50+ stories typically"]
|
||||
UXDesign["<b>UX Designer: create-ux-design</b><br/>Optional UX specification"]
|
||||
end
|
||||
|
||||
UXDesign["<b>UX Designer: ux</b><br/>Optional UX specification"]
|
||||
subgraph Solutioning["<b>PHASE 3: SOLUTIONING</b>"]
|
||||
direction TB
|
||||
Architecture["<b>Architect: architecture</b><br/>System design + decisions"]
|
||||
Epics["<b>PM: create-epics-and-stories</b><br/>Epic+Stories breakdown<br/>(10-50+ stories typically)"]
|
||||
end
|
||||
|
||||
subgraph Enterprise["<b>ENTERPRISE METHOD</b>"]
|
||||
@@ -51,17 +55,20 @@ graph TB
|
||||
Start -->|Story-driven| Narrative
|
||||
Start -->|Enterprise needs| Enterprise
|
||||
|
||||
PRD --> Epics
|
||||
GDD --> Epics
|
||||
Narrative --> Epics
|
||||
Epics -.->|Optional| UXDesign
|
||||
UXDesign -.->|May update| Epics
|
||||
PRD -.->|Optional| UXDesign
|
||||
GDD -.->|Optional| UXDesign
|
||||
Narrative -.->|Optional| UXDesign
|
||||
PRD --> Architecture
|
||||
GDD --> Architecture
|
||||
Narrative --> Architecture
|
||||
UXDesign --> Architecture
|
||||
Architecture --> Epics
|
||||
|
||||
QuickFlow --> Phase4["<b>Phase 4: Implementation</b>"]
|
||||
Epics --> Phase3["<b>Phase 3: Architecture</b>"]
|
||||
Enterprise -.->|Uses BMad planning| Epics
|
||||
Epics --> ReadinessCheck["<b>Architect: implementation-readiness</b><br/>Gate check"]
|
||||
Enterprise -.->|Uses BMad planning| Architecture
|
||||
Enterprise --> Phase3Ext["<b>Phase 3: Extended</b><br/>(Arch + Sec + DevOps)"]
|
||||
Phase3 --> Phase4
|
||||
ReadinessCheck --> Phase4
|
||||
Phase3Ext --> Phase4
|
||||
|
||||
Phase4 -.->|Significant changes| CorrectCourse
|
||||
@@ -90,18 +97,18 @@ graph TB
|
||||
|
||||
## Quick Reference
|
||||
|
||||
| Workflow | Agent | Track | Purpose | Typical Stories |
|
||||
| ---------------------------- | ------------- | ----------- | ------------------------------------------ | --------------- |
|
||||
| **workflow-init** | PM/Analyst | All | Entry point: discovery + routing | N/A |
|
||||
| **tech-spec** | PM | Quick Flow | Technical document → Story or Epic+Stories | 1-15 |
|
||||
| **prd** | PM | BMad Method | Strategic PRD | 10-50+ |
|
||||
| **gdd** | Game Designer | BMad Method | Game Design Document | 10-50+ |
|
||||
| **narrative** | Game Designer | BMad Method | Story-driven game/experience design | 10-50+ |
|
||||
| **create-epics-and-stories** | PM | BMad Method | Break PRD/GDD into Epic+Stories | N/A |
|
||||
| **ux** | UX Designer | BMad Method | Optional UX specification | N/A |
|
||||
| **correct-course** | PM/SM | All | Mid-stream requirement changes | N/A |
|
||||
| Workflow | Agent | Track | Purpose | Typical Stories |
|
||||
| ---------------------------- | ------------- | ----------- | --------------------------------------------------------- | --------------- |
|
||||
| **workflow-init** | PM/Analyst | All | Entry point: discovery + routing | N/A |
|
||||
| **tech-spec** | PM | Quick Flow | Technical document → Story or Epic+Stories | 1-15 |
|
||||
| **prd** | PM | BMad Method | Strategic PRD with FRs/NFRs (no epic breakdown) | 10-50+ |
|
||||
| **gdd** | Game Designer | BMad Method | Game Design Document with requirements | 10-50+ |
|
||||
| **narrative** | Game Designer | BMad Method | Story-driven game/experience design | 10-50+ |
|
||||
| **create-ux-design** | UX Designer | BMad Method | Optional UX specification (after PRD) | N/A |
|
||||
| **create-epics-and-stories** | PM | BMad Method | Break requirements into Epic+Stories (AFTER architecture) | N/A |
|
||||
| **correct-course** | PM/SM | All | Mid-stream requirement changes | N/A |
|
||||
|
||||
**Note:** Story counts are guidance based on typical usage, not strict definitions.
|
||||
**Note:** Story counts are guidance. V6 improvement: Epic+Stories are created AFTER architecture for better quality.
|
||||
|
||||
---
|
||||
|
||||
@@ -135,11 +142,11 @@ BMM uses three distinct planning tracks that adapt to project complexity:
|
||||
|
||||
**Story Count:** Typically 10-50+ (guidance)
|
||||
|
||||
**Documents:** PRD.md (or GDD.md) + architecture.md + epic files + story files
|
||||
**Documents:** PRD.md (FRs/NFRs) + architecture.md + epics.md + epic files
|
||||
|
||||
**Greenfield:** Product Brief (optional) → PRD → UX (optional) → Architecture → Implementation
|
||||
**Greenfield:** Product Brief (optional) → PRD (FRs/NFRs) → UX (optional) → Architecture → Epics+Stories → Implementation
|
||||
|
||||
**Brownfield:** document-project → PRD → Architecture (recommended) → Implementation
|
||||
**Brownfield:** document-project → PRD (FRs/NFRs) → Architecture (recommended) → Epics+Stories → Implementation
|
||||
|
||||
**Example:** "Customer dashboard", "E-commerce platform", "Add search to existing app"
|
||||
|
||||
@@ -151,17 +158,17 @@ BMM uses three distinct planning tracks that adapt to project complexity:
|
||||
|
||||
**Best For:** Enterprise requirements, multi-tenant, compliance, security-sensitive
|
||||
|
||||
**Planning (Phase 2):** Uses BMad Method planning (PRD + Epic+Stories)
|
||||
**Planning (Phase 2):** Uses BMad Method planning (PRD with FRs/NFRs)
|
||||
|
||||
**Solutioning (Phase 3):** Extended workflows (Architecture + Security + DevOps + SecOps as optional additions)
|
||||
**Solutioning (Phase 3):** Extended workflows (Architecture + Security + DevOps + SecOps as optional additions) → Epics+Stories
|
||||
|
||||
**Time:** 3-7 days total (1-3 days planning + 2-4 days extended solutioning)
|
||||
|
||||
**Story Count:** Typically 30+ (but defined by enterprise needs)
|
||||
|
||||
**Documents Phase 2:** PRD.md + epics + epic files + story files
|
||||
**Documents Phase 2:** PRD.md (FRs/NFRs)
|
||||
|
||||
**Documents Phase 3:** architecture.md + security-architecture.md (optional) + devops-strategy.md (optional) + secops-strategy.md (optional)
|
||||
**Documents Phase 3:** architecture.md + epics.md + epic files + security-architecture.md (optional) + devops-strategy.md (optional) + secops-strategy.md (optional)
|
||||
|
||||
**Example:** "Multi-tenant SaaS", "HIPAA-compliant portal", "Add SOC2 audit logging"
|
||||
|
||||
@@ -231,7 +238,7 @@ The system guides but never forces. You can override recommendations.
|
||||
|
||||
### prd (Product Requirements Document)
|
||||
|
||||
**Purpose:** Strategic PRD with epic breakdown for software products (BMad Method track).
|
||||
**Purpose:** Strategic PRD with Functional Requirements (FRs) and Non-Functional Requirements (NFRs) for software products (BMad Method track).
|
||||
|
||||
**Agent:** PM (with Architect and Analyst support)
|
||||
|
||||
@@ -245,19 +252,19 @@ The system guides but never forces. You can override recommendations.
|
||||
|
||||
**Scale-Adaptive Structure:**
|
||||
|
||||
- **Light:** Single epic, 5-10 stories, simplified analysis (10-15 pages)
|
||||
- **Standard:** 2-4 epics, 15-30 stories, comprehensive analysis (20-30 pages)
|
||||
- **Comprehensive:** 5+ epics, 30-50+ stories, multi-phase, extensive stakeholder analysis (30-50+ pages)
|
||||
- **Light:** Focused FRs/NFRs, simplified analysis (10-15 pages)
|
||||
- **Standard:** Comprehensive FRs/NFRs, thorough analysis (20-30 pages)
|
||||
- **Comprehensive:** Extensive FRs/NFRs, multi-phase, stakeholder analysis (30-50+ pages)
|
||||
|
||||
**Key Outputs:**
|
||||
|
||||
- PRD.md (complete requirements)
|
||||
- epics.md (epic breakdown)
|
||||
- Epic files (epic-1-_.md, epic-2-_.md, etc.)
|
||||
- PRD.md (complete requirements with FRs and NFRs)
|
||||
|
||||
**Note:** V6 improvement - PRD focuses on WHAT to build (requirements). Epic+Stories are created AFTER architecture via `create-epics-and-stories` workflow for better quality.
|
||||
|
||||
**Integration:** Feeds into Architecture (Phase 3)
|
||||
|
||||
**Example:** E-commerce checkout → 3 epics (Guest Checkout, Payment Processing, Order Management), 21 stories, 4-6 week delivery.
|
||||
**Example:** E-commerce checkout → PRD with 15 FRs (user account, cart management, payment flow) and 8 NFRs (performance, security, scalability).
|
||||
|
||||
---
|
||||
|
||||
@@ -362,22 +369,26 @@ The system guides but never forces. You can override recommendations.
|
||||
|
||||
### create-epics-and-stories
|
||||
|
||||
**Purpose:** Break PRD/GDD requirements into bite-sized stories organized in epics (BMad Method track).
|
||||
**Purpose:** Break requirements into bite-sized stories organized in epics (BMad Method track).
|
||||
|
||||
**Agent:** PM
|
||||
|
||||
**When to Use:**
|
||||
|
||||
- After PRD/GDD complete (often run automatically)
|
||||
- Can also run standalone later to re-generate epics/stories
|
||||
- When planning story breakdown outside main PRD workflow
|
||||
- **REQUIRED:** After Architecture workflow is complete (Phase 3)
|
||||
- After PRD defines FRs/NFRs and Architecture defines HOW to build
|
||||
- Optional: Can also run earlier (after PRD, after UX) for basic structure, then refined after Architecture
|
||||
|
||||
**Key Outputs:**
|
||||
|
||||
- epics.md (all epics with story breakdown)
|
||||
- Epic files (epic-1-\*.md, etc.)
|
||||
|
||||
**Note:** PRD workflow often creates epics automatically. This workflow can be run standalone if needed later.
|
||||
**V6 Improvement:** Epics+Stories are now created AFTER architecture for better quality:
|
||||
|
||||
- Architecture decisions inform story breakdown (tech choices affect implementation)
|
||||
- Stories have full context (PRD + UX + Architecture)
|
||||
- Better sequencing with technical dependencies considered
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -19,7 +19,7 @@ Phase 3 (Solutioning) workflows translate **what** to build (from Planning) into
|
||||
```mermaid
|
||||
%%{init: {'theme':'base', 'themeVariables': { 'primaryColor':'#fff','primaryTextColor':'#000','primaryBorderColor':'#000','lineColor':'#000','fontSize':'16px','fontFamily':'arial'}}}%%
|
||||
graph TB
|
||||
FromPlanning["<b>FROM Phase 2 Planning</b><br/>PRD/GDD/Tech-Spec complete"]
|
||||
FromPlanning["<b>FROM Phase 2 Planning</b><br/>PRD (FRs/NFRs) complete"]
|
||||
|
||||
subgraph QuickFlow["<b>QUICK FLOW PATH</b>"]
|
||||
direction TB
|
||||
@@ -28,6 +28,7 @@ graph TB
|
||||
|
||||
subgraph BMadEnterprise["<b>BMAD METHOD + ENTERPRISE (Same Start)</b>"]
|
||||
direction TB
|
||||
OptionalUX["<b>UX Designer: create-ux-design</b><br/>(Optional)"]
|
||||
Architecture["<b>Architect: architecture</b><br/>System design + ADRs"]
|
||||
|
||||
subgraph Optional["<b>ENTERPRISE ADDITIONS (Optional)</b>"]
|
||||
@@ -36,11 +37,14 @@ graph TB
|
||||
DevOps["<b>Architect: devops-strategy</b><br/>(Future)"]
|
||||
end
|
||||
|
||||
GateCheck["<b>Architect: solutioning-gate-check</b><br/>Validation before Phase 4"]
|
||||
EpicsStories["<b>PM: create-epics-and-stories</b><br/>Break down FRs/NFRs into epics"]
|
||||
GateCheck["<b>Architect: implementation-readiness</b><br/>Validation before Phase 4"]
|
||||
|
||||
OptionalUX -.-> Architecture
|
||||
Architecture -.->|Enterprise only| Optional
|
||||
Architecture --> GateCheck
|
||||
Optional -.-> GateCheck
|
||||
Architecture --> EpicsStories
|
||||
Optional -.-> EpicsStories
|
||||
EpicsStories --> GateCheck
|
||||
end
|
||||
|
||||
subgraph Result["<b>GATE CHECK RESULTS</b>"]
|
||||
@@ -51,7 +55,7 @@ graph TB
|
||||
end
|
||||
|
||||
FromPlanning -->|Quick Flow| QuickFlow
|
||||
FromPlanning -->|BMad Method<br/>or Enterprise| Architecture
|
||||
FromPlanning -->|BMad Method<br/>or Enterprise| OptionalUX
|
||||
|
||||
QuickFlow --> Phase4["<b>Phase 4: Implementation</b>"]
|
||||
GateCheck --> Result
|
||||
@@ -67,9 +71,11 @@ graph TB
|
||||
style Phase4 fill:#ffcc80,stroke:#e65100,stroke-width:2px,color:#000
|
||||
|
||||
style SkipArch fill:#aed581,stroke:#1b5e20,stroke-width:2px,color:#000
|
||||
style OptionalUX fill:#64b5f6,stroke:#0d47a1,stroke-width:2px,color:#000
|
||||
style Architecture fill:#42a5f5,stroke:#0d47a1,stroke-width:2px,color:#000
|
||||
style SecArch fill:#ef9a9a,stroke:#c62828,stroke-width:2px,color:#000
|
||||
style DevOps fill:#ef9a9a,stroke:#c62828,stroke-width:2px,color:#000
|
||||
style EpicsStories fill:#42a5f5,stroke:#0d47a1,stroke-width:2px,color:#000
|
||||
style GateCheck fill:#42a5f5,stroke:#0d47a1,stroke-width:2px,color:#000
|
||||
style Pass fill:#81c784,stroke:#388e3c,stroke-width:2px,color:#000
|
||||
style Concerns fill:#ffb74d,stroke:#f57f17,stroke-width:2px,color:#000
|
||||
@@ -80,10 +86,12 @@ graph TB
|
||||
|
||||
## Quick Reference
|
||||
|
||||
| Workflow | Agent | Track | Purpose |
|
||||
| -------------------------- | --------- | ------------------------ | ------------------------------------------- |
|
||||
| **architecture** | Architect | BMad Method, Enterprise | Technical architecture and design decisions |
|
||||
| **solutioning-gate-check** | Architect | BMad Complex, Enterprise | Validate planning/solutioning completeness |
|
||||
| Workflow | Agent | Track | Purpose |
|
||||
| ---------------------------- | ----------- | ------------------------ | -------------------------------------------- |
|
||||
| **create-ux-design** | UX Designer | BMad Method, Enterprise | Optional UX design (after PRD, before arch) |
|
||||
| **architecture** | Architect | BMad Method, Enterprise | Technical architecture and design decisions |
|
||||
| **create-epics-and-stories** | PM | BMad Method, Enterprise | Break FRs/NFRs into epics after architecture |
|
||||
| **implementation-readiness** | Architect | BMad Complex, Enterprise | Validate planning/solutioning completeness |
|
||||
|
||||
**When to Skip Solutioning:**
|
||||
|
||||
@@ -116,14 +124,14 @@ Result: Consistent implementation, no conflicts
|
||||
|
||||
### Solutioning vs Planning
|
||||
|
||||
| Aspect | Planning (Phase 2) | Solutioning (Phase 3) |
|
||||
| -------- | ------------------ | ------------------------ |
|
||||
| Question | What and Why? | How? |
|
||||
| Output | Requirements | Technical Design |
|
||||
| Agent | PM | Architect |
|
||||
| Audience | Stakeholders | Developers |
|
||||
| Document | PRD/GDD | Architecture + Tech Spec |
|
||||
| Level | Business logic | Implementation detail |
|
||||
| Aspect | Planning (Phase 2) | Solutioning (Phase 3) |
|
||||
| -------- | ----------------------- | --------------------------------- |
|
||||
| Question | What and Why? | How? Then What units of work? |
|
||||
| Output | FRs/NFRs (Requirements) | Architecture + Epics/Stories |
|
||||
| Agent | PM | Architect → PM |
|
||||
| Audience | Stakeholders | Developers |
|
||||
| Document | PRD (FRs/NFRs) | Architecture + Epic Files |
|
||||
| Level | Business logic | Technical design + Work breakdown |
|
||||
|
||||
---
|
||||
|
||||
@@ -171,7 +179,7 @@ This is NOT a template filler. The architecture workflow:
|
||||
7. **Security Architecture** - Auth/authorization, data protection, security boundaries
|
||||
8. **Deployment Architecture** - Deployment model, CI/CD, environment strategy, monitoring
|
||||
9. **Architecture Decision Records (ADRs)** - Key decisions with context, options, trade-offs, rationale
|
||||
10. **Epic-Specific Guidance** - Technical notes per epic, implementation priorities, dependencies
|
||||
10. **FR/NFR-Specific Guidance** - Technical approach per functional requirement, implementation priorities, dependencies
|
||||
11. **Standards and Conventions** - Directory structure, naming conventions, code organization, testing
|
||||
|
||||
**ADR Format (Brief):**
|
||||
@@ -203,28 +211,69 @@ This is NOT a template filler. The architecture workflow:
|
||||
- Negative: Caching complexity, N+1 query risk
|
||||
- Mitigation: Use DataLoader for batching
|
||||
|
||||
**Implications for Epics:**
|
||||
**Implications for FRs:**
|
||||
|
||||
- Epic 1: User Management → GraphQL mutations
|
||||
- Epic 2: Mobile App → Optimized queries
|
||||
- FR-001: User Management → GraphQL mutations
|
||||
- FR-002: Mobile App → Optimized queries
|
||||
```
|
||||
|
||||
**Example:** E-commerce platform → Monolith + PostgreSQL + Redis + Next.js + GraphQL, with ADRs explaining each choice and epic-specific guidance.
|
||||
**Example:** E-commerce platform → Monolith + PostgreSQL + Redis + Next.js + GraphQL, with ADRs explaining each choice and FR/NFR-specific guidance.
|
||||
|
||||
**Integration:** Feeds into Phase 4 (Implementation). All dev agents reference architecture during implementation.
|
||||
**Integration:** Feeds into create-epics-and-stories workflow. Architecture provides the technical context needed for breaking FRs/NFRs into implementable epics and stories. All dev agents reference architecture during Phase 4 implementation.
|
||||
|
||||
---
|
||||
|
||||
### solutioning-gate-check
|
||||
### create-epics-and-stories
|
||||
|
||||
**Purpose:** Systematically validate that planning and solutioning are complete and aligned before Phase 4 implementation. Ensures PRD, architecture, and stories are cohesive with no gaps.
|
||||
**Purpose:** Transform PRD's functional and non-functional requirements into bite-sized stories organized into deliverable functional epics. This workflow runs AFTER architecture so epics/stories are informed by technical decisions.
|
||||
|
||||
**Agent:** PM (Product Manager)
|
||||
|
||||
**When to Use:**
|
||||
|
||||
- After architecture workflow completes
|
||||
- When PRD contains FRs/NFRs ready for implementation breakdown
|
||||
- Before implementation-readiness gate check
|
||||
|
||||
**Key Inputs:**
|
||||
|
||||
- PRD (FRs/NFRs) from Phase 2 Planning
|
||||
- architecture.md with ADRs and technical decisions
|
||||
- Optional: UX design artifacts
|
||||
|
||||
**Why After Architecture:**
|
||||
|
||||
The create-epics-and-stories workflow runs AFTER architecture because:
|
||||
|
||||
1. **Informed Story Sizing:** Architecture decisions (database choice, API style, etc.) affect story complexity
|
||||
2. **Dependency Awareness:** Architecture reveals technical dependencies between stories
|
||||
3. **Technical Feasibility:** Stories can be properly scoped knowing the tech stack
|
||||
4. **Consistency:** All stories align with documented architectural patterns
|
||||
|
||||
**Key Outputs:**
|
||||
|
||||
Epic files (one per epic) containing:
|
||||
|
||||
1. Epic objective and scope
|
||||
2. User stories with acceptance criteria
|
||||
3. Story priorities (P0/P1/P2/P3)
|
||||
4. Dependencies between stories
|
||||
5. Technical notes referencing architecture decisions
|
||||
|
||||
**Example:** E-commerce PRD with FR-001 (User Registration), FR-002 (Product Catalog) → Epic 1: User Management (3 stories), Epic 2: Product Display (4 stories), each story referencing relevant ADRs.
|
||||
|
||||
---
|
||||
|
||||
### implementation-readiness
|
||||
|
||||
**Purpose:** Systematically validate that planning and solutioning are complete and aligned before Phase 4 implementation. Ensures PRD, architecture, and epics are cohesive with no gaps.
|
||||
|
||||
**Agent:** Architect
|
||||
|
||||
**When to Use:**
|
||||
|
||||
- **Always** before Phase 4 for BMad Complex and Enterprise projects
|
||||
- After architecture workflow completes
|
||||
- After create-epics-and-stories workflow completes
|
||||
- Before sprint-planning workflow
|
||||
- When stakeholders request readiness check
|
||||
|
||||
@@ -237,14 +286,14 @@ This is NOT a template filler. The architecture workflow:
|
||||
|
||||
**Prevents:**
|
||||
|
||||
- ❌ Architecture doesn't address all epics
|
||||
- ❌ Stories conflict with architecture decisions
|
||||
- ❌ Architecture doesn't address all FRs/NFRs
|
||||
- ❌ Epics conflict with architecture decisions
|
||||
- ❌ Requirements ambiguous or contradictory
|
||||
- ❌ Missing critical dependencies
|
||||
|
||||
**Ensures:**
|
||||
|
||||
- ✅ PRD → Architecture → Stories alignment
|
||||
- ✅ PRD → Architecture → Epics alignment
|
||||
- ✅ All epics have clear technical approach
|
||||
- ✅ No contradictions or gaps
|
||||
- ✅ Team ready to implement
|
||||
@@ -256,8 +305,7 @@ This is NOT a template filler. The architecture workflow:
|
||||
- Problem statement clear and evidence-based
|
||||
- Success metrics defined
|
||||
- User personas identified
|
||||
- Feature requirements complete
|
||||
- All epics defined with objectives
|
||||
- Functional requirements (FRs) complete
|
||||
- Non-functional requirements (NFRs) specified
|
||||
- Risks and assumptions documented
|
||||
|
||||
@@ -268,7 +316,7 @@ This is NOT a template filler. The architecture workflow:
|
||||
- API architecture decided
|
||||
- Key ADRs documented
|
||||
- Security architecture addressed
|
||||
- Epic-specific guidance provided
|
||||
- FR/NFR-specific guidance provided
|
||||
- Standards and conventions defined
|
||||
|
||||
**Epic/Story Completeness:**
|
||||
@@ -281,8 +329,8 @@ This is NOT a template filler. The architecture workflow:
|
||||
|
||||
**Alignment Checks:**
|
||||
|
||||
- Architecture addresses all PRD requirements
|
||||
- Stories align with architecture decisions
|
||||
- Architecture addresses all PRD FRs/NFRs
|
||||
- Epics align with architecture decisions
|
||||
- No contradictions between epics
|
||||
- NFRs have technical approach
|
||||
- Integration points clear
|
||||
@@ -305,16 +353,16 @@ This is NOT a template filler. The architecture workflow:
|
||||
|
||||
- Critical gaps or contradictions
|
||||
- Architecture missing key decisions
|
||||
- Stories conflict with PRD/architecture
|
||||
- Epics conflict with PRD/architecture
|
||||
- **Action:** BLOCK Phase 4, resolve issues first
|
||||
|
||||
**Key Outputs:**
|
||||
|
||||
**solutioning-gate-check.md** containing:
|
||||
**implementation-readiness.md** containing:
|
||||
|
||||
1. Executive Summary (PASS/CONCERNS/FAIL)
|
||||
2. Completeness Assessment (scores for PRD, Architecture, Epics)
|
||||
3. Alignment Assessment (PRD↔Architecture, Architecture↔Epics, cross-epic consistency)
|
||||
3. Alignment Assessment (PRD↔Architecture, Architecture↔Epics/Stories, cross-epic consistency)
|
||||
4. Quality Assessment (story quality, dependencies, risks)
|
||||
5. Gaps and Recommendations (critical/minor gaps, remediation)
|
||||
6. Gate Decision with rationale
|
||||
@@ -339,26 +387,30 @@ Planning (tech-spec by PM)
|
||||
**BMad Method:**
|
||||
|
||||
```
|
||||
Planning (prd by PM)
|
||||
Planning (prd by PM - FRs/NFRs only)
|
||||
→ Optional: create-ux-design (UX Designer)
|
||||
→ architecture (Architect)
|
||||
→ solutioning-gate-check (Architect)
|
||||
→ create-epics-and-stories (PM)
|
||||
→ implementation-readiness (Architect)
|
||||
→ Phase 4 (Implementation)
|
||||
```
|
||||
|
||||
**Enterprise:**
|
||||
|
||||
```
|
||||
Planning (prd by PM - same as BMad Method)
|
||||
Planning (prd by PM - FRs/NFRs only)
|
||||
→ Optional: create-ux-design (UX Designer)
|
||||
→ architecture (Architect)
|
||||
→ Optional: security-architecture (Architect, future)
|
||||
→ Optional: devops-strategy (Architect, future)
|
||||
→ solutioning-gate-check (Architect)
|
||||
→ create-epics-and-stories (PM)
|
||||
→ implementation-readiness (Architect)
|
||||
→ Phase 4 (Implementation)
|
||||
```
|
||||
|
||||
**Note on TEA (Test Architect):** TEA is fully operational with 8 workflows across all phases. TEA validates architecture testability during Phase 3 reviews but does not have a dedicated solutioning workflow. TEA's primary setup occurs in Phase 2 (`*framework`, `*ci`, `*test-design`) and testing execution in Phase 4 (`*atdd`, `*automate`, `*test-review`, `*trace`, `*nfr-assess`).
|
||||
|
||||
**Note:** Enterprise uses the same planning and architecture as BMad Method. The only difference is optional extended workflows added AFTER architecture but BEFORE gate check.
|
||||
**Note:** Enterprise uses the same planning and architecture as BMad Method. The only difference is optional extended workflows added AFTER architecture but BEFORE create-epics-and-stories.
|
||||
|
||||
### Solutioning → Implementation Handoff
|
||||
|
||||
@@ -366,11 +418,12 @@ Planning (prd by PM - same as BMad Method)
|
||||
|
||||
1. **architecture.md** → Guides all dev agents during implementation
|
||||
2. **ADRs** (in architecture) → Referenced by agents for technical decisions
|
||||
3. **solutioning-gate-check.md** → Confirms readiness for Phase 4
|
||||
3. **Epic files** (from create-epics-and-stories) → Work breakdown into implementable units
|
||||
4. **implementation-readiness.md** → Confirms readiness for Phase 4
|
||||
|
||||
**How Implementation Uses Solutioning:**
|
||||
|
||||
- **sprint-planning** - Loads architecture for epic sequencing
|
||||
- **sprint-planning** - Loads architecture and epic files for sprint organization
|
||||
- **dev-story** - References architecture decisions and ADRs
|
||||
- **code-review** - Validates code follows architectural standards
|
||||
|
||||
@@ -414,17 +467,17 @@ Architecture documents are living. Update them as you learn during implementatio
|
||||
|
||||
### BMad Method
|
||||
|
||||
- **Planning:** prd (PM)
|
||||
- **Solutioning:** architecture (Architect) → solutioning-gate-check (Architect)
|
||||
- **Planning:** prd (PM) - creates FRs/NFRs only, NOT epics
|
||||
- **Solutioning:** Optional UX → architecture (Architect) → create-epics-and-stories (PM) → implementation-readiness (Architect)
|
||||
- **Implementation:** sprint-planning → epic-tech-context → dev-story
|
||||
|
||||
### Enterprise
|
||||
|
||||
- **Planning:** prd (PM) - same as BMad Method
|
||||
- **Solutioning:** architecture (Architect) → Optional extended workflows (security-architecture, devops-strategy) → solutioning-gate-check (Architect)
|
||||
- **Planning:** prd (PM) - creates FRs/NFRs only (same as BMad Method)
|
||||
- **Solutioning:** Optional UX → architecture (Architect) → Optional extended workflows (security-architecture, devops-strategy) → create-epics-and-stories (PM) → implementation-readiness (Architect)
|
||||
- **Implementation:** sprint-planning → epic-tech-context → dev-story
|
||||
|
||||
**Key Difference:** Enterprise adds optional extended workflows AFTER architecture but BEFORE gate check. Everything else is identical to BMad Method.
|
||||
**Key Difference:** Enterprise adds optional extended workflows AFTER architecture but BEFORE create-epics-and-stories. Everything else is identical to BMad Method.
|
||||
|
||||
**Note:** TEA (Test Architect) operates across all phases and validates architecture testability but is not a Phase 3-specific workflow. See [Test Architecture Guide](./test-architecture.md) for TEA's full lifecycle integration.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user