bmad-elsabro 1.0.0

package/src/bmm/workflows/parallel-work/parallel-analysis/steps/step-02-launch-streams.md

@@ -0,0 +1,135 @@
+---
+name: step-02-launch-streams
+description: Launch parallel analysis streams with different expert perspectives
+---
+
+# Step 2: Launch Parallel Streams
+
+## OBJECTIVE
+
+Invoke 4 expert perspectives SIMULTANEOUSLY to analyze the target.
+
+## EXECUTION
+
+### Launch All Streams Concurrently
+
+**IMPORTANT:** These streams run IN PARALLEL, not sequentially.
+
+---
+
+### Stream 1: Technical Architect Analysis
+
+**Focus:**
+- System design patterns applicable
+- API design considerations
+- Scalability implications
+- Integration points
+- Technical debt risks
+
+**Output Format:**
+```markdown
+## Technical Analysis
+
+### Architecture Considerations
+- {findings}
+
+### API Design
+- {findings}
+
+### Scalability
+- {findings}
+
+### Recommendations
+- {list}
+```
+
+---
+
+### Stream 2: UX Designer Analysis
+
+**Focus:**
+- User flow implications
+- Accessibility requirements (WCAG)
+- Usability considerations
+- Edge cases in UI
+- Error states and feedback
+
+**Output Format:**
+```markdown
+## UX Analysis
+
+### User Flow Impact
+- {findings}
+
+### Accessibility
+- {findings}
+
+### Usability Concerns
+- {findings}
+
+### Recommendations
+- {list}
+```
+
+---
+
+### Stream 3: Test Architect (TEA) Analysis
+
+**Focus:**
+- Test strategy for this feature
+- Edge cases to cover
+- Risk areas needing extra coverage
+- Test priority matrix (P0-P3)
+- Integration test needs
+
+**Output Format:**
+```markdown
+## Test Analysis
+
+### Test Strategy
+- {findings}
+
+### Edge Cases
+- {list}
+
+### Risk Areas
+- {findings}
+
+### Priority Matrix
+| Priority | Test Area | Rationale |
+|----------|-----------|-----------|
+| P0 | {area} | {why} |
+```
+
+---
+
+### Stream 4: Developer Analysis
+
+**Focus:**
+- Implementation complexity
+- Effort estimation
+- Technical approach options
+- Dependencies needed
+- Potential blockers
+
+**Output Format:**
+```markdown
+## Implementation Analysis
+
+### Complexity Assessment
+- {findings}
+
+### Effort Estimate
+- {estimate with breakdown}
+
+### Approach Options
+1. {option 1}
+2. {option 2}
+
+### Dependencies
+- {list}
+```
+
+## NEXT STEP
+
+Proceed to: `step-03-sync-point.md`

package/src/bmm/workflows/parallel-work/parallel-analysis/steps/step-03-sync-point.md

@@ -0,0 +1,74 @@
+---
+name: step-03-sync-point
+description: Synchronization point for all parallel streams to share findings
+---
+
+# Step 3: Sync Point
+
+## OBJECTIVE
+
+Collect findings from all 4 streams, detect conflicts, and identify gaps.
+
+## EXECUTION
+
+### 1. Collect Stream Outputs
+
+Gather completed analysis from each stream:
+
+| Stream | Status | Key Findings Count | Conflicts Detected |
+|--------|--------|-------------------|-------------------|
+| 1 - Architect | {complete/pending} | {n} | {y/n} |
+| 2 - UX Designer | {complete/pending} | {n} | {y/n} |
+| 3 - TEA | {complete/pending} | {n} | {y/n} |
+| 4 - Developer | {complete/pending} | {n} | {y/n} |
+
+### 2. Conflict Detection
+
+Identify conflicting recommendations between streams:
+
+**Common Conflict Types:**
+- Architect vs Developer: Ideal architecture vs implementation pragmatism
+- UX vs Developer: User experience ideals vs technical constraints
+- TEA vs All: Test coverage requirements vs timeline pressures
+
+**Conflict Resolution Strategy:**
+1. Identify the conflict clearly
+2. Understand each perspective's rationale
+3. Propose compromise or prioritized approach
+4. Document trade-off decision
+
+### 3. Gap Analysis
+
+Check for uncovered areas:
+
+- [ ] Security implications analyzed?
+- [ ] Performance considerations addressed?
+- [ ] Error handling covered?
+- [ ] Data migration needs identified?
+- [ ] Backwards compatibility checked?
+
+### 4. Cross-Stream Insights
+
+Identify synergies between perspectives:
+
+| Insight | Contributing Streams | Action |
+|---------|---------------------|--------|
+| {insight} | Architect + Developer | {action} |
+| {insight} | UX + TEA | {action} |
+
+### 5. Sync Point Report
+
+```markdown
+## Sync Point Summary
+
+### Streams Completed: {n}/4
+### Total Findings: {count}
+### Conflicts Detected: {count}
+### Gaps Identified: {count}
+
+### Ready for Merge: {yes/no}
+```
+
+## NEXT STEP
+
+Proceed to: `step-04-merge-insights.md`

package/src/bmm/workflows/parallel-work/parallel-analysis/steps/step-04-merge-insights.md

@@ -0,0 +1,179 @@
+---
+name: step-04-merge-insights
+description: Merge all stream insights into unified analysis report
+---
+
+# Step 4: Merge Insights
+
+## OBJECTIVE
+
+Combine all parallel stream findings into a single, actionable analysis report.
+
+## EXECUTION
+
+### 1. Consolidate Findings
+
+Merge insights from all 4 streams into unified sections:
+
+```markdown
+# Unified Analysis Report
+
+## Executive Summary
+
+**Target Analyzed:** {feature/story/requirement}
+**Analysis Duration:** {time}
+**Expert Perspectives:** 4 (Architect, UX, TEA, Developer)
+
+### Key Insights
+1. {top insight 1}
+2. {top insight 2}
+3. {top insight 3}
+
+### Critical Recommendations
+1. {must-do recommendation}
+2. {should-do recommendation}
+3. {could-do recommendation}
+
+---
+
+## Technical Perspective (Architect)
+
+{consolidated architect findings}
+
+### Architecture Decisions
+- {decision 1}
+- {decision 2}
+
+### Technical Risks
+| Risk | Severity | Mitigation |
+|------|----------|------------|
+| {risk} | High/Med/Low | {mitigation} |
+
+---
+
+## User Experience Perspective (UX Designer)
+
+{consolidated UX findings}
+
+### User Flow Changes
+- {change 1}
+- {change 2}
+
+### Accessibility Requirements
+- {requirement 1}
+- {requirement 2}
+
+---
+
+## Testing Perspective (TEA)
+
+{consolidated test findings}
+
+### Test Strategy
+- {strategy point 1}
+- {strategy point 2}
+
+### Priority Test Matrix
+| Priority | Area | Test Type | Effort |
+|----------|------|-----------|--------|
+| P0 | {area} | {type} | {effort} |
+| P1 | {area} | {type} | {effort} |
+| P2 | {area} | {type} | {effort} |
+
+---
+
+## Implementation Perspective (Developer)
+
+{consolidated dev findings}
+
+### Complexity Assessment
+- Overall: {Low/Medium/High/Very High}
+- Breakdown by component: {details}
+
+### Effort Estimate
+| Component | Estimate | Confidence |
+|-----------|----------|------------|
+| {component} | {hours/days} | {high/med/low} |
+
+### Implementation Approach
+1. {step 1}
+2. {step 2}
+3. {step 3}
+
+---
+
+## Conflicts & Resolutions
+
+| Conflict | Perspectives | Resolution | Rationale |
+|----------|--------------|------------|-----------|
+| {conflict} | {streams} | {resolution} | {why} |
+
+---
+
+## Consolidated Recommendations
+
+### Must Do (P0)
+1. {recommendation}
+
+### Should Do (P1)
+1. {recommendation}
+
+### Could Do (P2)
+1. {recommendation}
+
+---
+
+## Dev Notes
+
+Ready-to-use implementation notes:
+
+### Prerequisites
+- {prereq 1}
+- {prereq 2}
+
+### Implementation Order
+1. {first task}
+2. {second task}
+3. {third task}
+
+### Watch Out For
+- {gotcha 1}
+- {gotcha 2}
+```
+
+### 2. Quality Check
+
+Before finalizing, verify:
+
+- [ ] All 4 perspectives represented
+- [ ] Conflicts explicitly addressed
+- [ ] Recommendations are actionable
+- [ ] Effort estimates included
+- [ ] Risks identified with mitigations
+- [ ] Test strategy defined
+- [ ] Dev notes are implementation-ready
+
+### 3. Generate Final Report
+
+Save the unified report to:
+`{output_folder}/analysis-reports/{feature-name}-analysis.md`
+
+### 4. Completion Summary
+
+```
+PARALLEL ANALYSIS COMPLETE
+
+Time: {elapsed} (vs ~{4x elapsed} sequential)
+Streams: 4 experts
+Insights: {count} findings
+Conflicts: {count} resolved
+Recommendations: {count} actionable items
+
+Report saved to: {path}
+```
+
+---
+
+## WORKFLOW COMPLETE
+
+Parallel Analysis finished. 4 perspectives merged into 1 unified report.

package/src/bmm/workflows/parallel-work/parallel-analysis/workflow.md

@@ -0,0 +1,55 @@
+---
+name: parallel-analysis
+description: 'Multiple experts analyze simultaneously - 4x speedup on analysis phase'
+---
+
+# Parallel Analysis Workflow
+
+**Goal:** Get insights from multiple expert perspectives SIMULTANEOUSLY instead of sequentially.
+
+**Speedup:** 4x faster than sequential analysis
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** with parallel streams:
+
+- Step 1: Parse target and prepare context
+- Step 2: Launch parallel analysis streams
+- Step 3: Sync point and conflict detection
+- Step 4: Merge insights and generate report
+
+---
+
+## INITIALIZATION
+
+### Configuration Loading
+
+Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+
+- `user_name`, `communication_language`, `user_skill_level`
+- `output_folder`, `planning_artifacts`
+
+### Parallel Settings
+
+Load from `{project-root}/_bmad/bmm/data/parallelization-config.yaml`:
+
+```yaml
+parallel_config:
+  mode: "analysis"
+  max_concurrent: 4
+  sync_interval: "5min"
+  conflict_strategy: "merge-insights"
+```
+
+### Paths
+
+- `installed_path` = `{project-root}/_bmad/bmm/workflows/parallel-work/parallel-analysis`
+- `project_context` = `**/project-context.md` (load if exists)
+
+---
+
+## EXECUTION
+
+Read fully and follow: `steps/step-01-parse-target.md` to begin the workflow.

package/src/bmm/workflows/parallel-work/parallel-generation/workflow.md

@@ -0,0 +1,109 @@
+---
+name: parallel-generation
+description: 'Generate code, tests, and docs simultaneously - 4x speedup'
+---
+
+# Parallel Generation Workflow
+
+**Goal:** Generate code, tests, AND documentation AT THE SAME TIME.
+
+**Speedup:** 4x faster than sequential generation
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+Launch 4 generation streams in parallel:
+- Stream 1: Developer (implementation code)
+- Stream 2: Test Architect (test code)
+- Stream 3: Tech Writer (documentation)
+- Stream 4: Architect (validation + security review)
+
+---
+
+## INITIALIZATION
+
+### Parallel Settings
+
+```yaml
+parallel_config:
+  mode: "generation"
+  max_concurrent: 4
+  sync_interval: "10min"
+  conflict_strategy: "code-first"
+```
+
+---
+
+## EXECUTION
+
+### Step 1: Prepare Generation Context
+
+Gather:
+- Story/spec to implement
+- Existing code patterns
+- Test patterns
+- Doc templates
+
+### Step 2: Launch Parallel Streams
+
+**SIMULTANEOUSLY:**
+
+#### Stream 1: Developer
+- Write implementation code
+- Follow existing patterns
+- Output: Source files
+
+#### Stream 2: Test Architect
+- Write unit tests
+- Write integration tests
+- Output: Test files
+
+#### Stream 3: Tech Writer
+- Write/update README
+- Write API docs
+- Write usage examples
+- Output: Doc files
+
+#### Stream 4: Architect
+- Validate against architecture
+- Security review
+- Performance considerations
+- Output: Validation report
+
+### Step 3: Sync Point (10 min)
+
+Detect:
+- Interface mismatches between code and tests
+- Doc references to non-existent code
+- Security concerns in implementation
+
+### Step 4: Integration
+
+1. Developer adjusts code if architect flagged issues
+2. Tests verify code works
+3. Docs reflect actual implementation
+
+### Step 5: Final Validation
+
+Run:
+- All tests pass
+- Docs build successfully
+- No security warnings
+
+### Step 6: Report
+
+```
+✅ PARALLEL GENERATION COMPLETE
+📁 Code: {files created/modified}
+🧪 Tests: {test files} ({coverage}%)
+📚 Docs: {doc files}
+🔒 Security: {status}
+⏱️ Time: {elapsed} (vs ~{4x elapsed} sequential)
+```
+
+---
+
+## WORKFLOW COMPLETE
+
+Parallel Generation done. Code + Tests + Docs, all at once. 🚀

package/src/bmm/workflows/parallel-work/parallel-reviews/workflow.md

@@ -0,0 +1,111 @@
+---
+name: parallel-reviews
+description: 'Multiple reviewers check different aspects simultaneously - 3.75x speedup'
+---
+
+# Parallel Reviews Workflow
+
+**Goal:** Get comprehensive code review from multiple perspectives AT ONCE.
+
+**Speedup:** 3.75x faster than sequential reviews
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+Launch 4 review streams:
+- Stream 1: Code Quality (SOLID, DRY, patterns)
+- Stream 2: Performance (N+1, memoization, optimization)
+- Stream 3: Security (XSS, CSRF, injection, auth)
+- Stream 4: Test Coverage (edge cases, coverage %)
+
+---
+
+## EXECUTION
+
+### Step 1: Identify Review Target
+
+From user input:
+- PR number or branch
+- Specific files to review
+- Full codebase review
+
+### Step 2: Launch Parallel Reviews
+
+**SIMULTANEOUSLY:**
+
+#### Stream 1: Code Quality Reviewer
+Focus:
+- SOLID principles
+- DRY violations
+- Design patterns
+- Code readability
+- Naming conventions
+
+#### Stream 2: Performance Reviewer
+Focus:
+- N+1 queries
+- Missing memoization
+- Unnecessary re-renders
+- Bundle size impact
+- Algorithm complexity
+
+#### Stream 3: Security Reviewer
+Focus:
+- XSS vulnerabilities
+- CSRF protection
+- SQL injection
+- Authentication issues
+- Authorization checks
+- Secrets exposure
+
+#### Stream 4: Test Coverage Reviewer
+Focus:
+- Test coverage %
+- Missing edge cases
+- Flaky test patterns
+- Test quality
+
+### Step 3: Merge Findings
+
+Combine all reviews into priority matrix:
+
+| Finding | Severity | Category | File:Line | Auto-Fix? |
+|---------|----------|----------|-----------|-----------|
+| XSS risk | 🔴 HIGH | Security | api.ts:45 | No |
+| N+1 query | 🟡 MED | Perf | db.ts:12 | Yes |
+| Missing test | 🟢 LOW | Tests | - | Yes |
+
+### Step 4: Auto-Fix (Optional)
+
+For auto-fixable issues:
+- Apply fixes
+- Re-run tests
+- Verify fix worked
+
+### Step 5: Report
+
+```
+✅ PARALLEL REVIEW COMPLETE
+
+📊 Summary:
+- Files reviewed: {count}
+- Streams: 4
+- Findings: {total}
+
+🔴 Critical: {count}
+🟡 Medium: {count}
+🟢 Low: {count}
+
+⏱️ Time: {elapsed} (vs ~{4x elapsed} sequential)
+
+📋 Action Items:
+1. {critical items}
+2. {medium items}
+```
+
+---
+
+## WORKFLOW COMPLETE
+
+Comprehensive review done. 4 perspectives, one report.