bmad-method 6.0.0-alpha.9 → 6.0.2

package/src/modules/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/instructions.md

@@ -1,292 +0,0 @@
-# Epic and Story Decomposition - Intent-Based Implementation Planning
-
-<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
-<critical>This workflow transforms requirements into BITE-SIZED STORIES for development agents</critical>
-<critical>EVERY story must be completable by a single dev agent in one focused session</critical>
-<critical>BMAD METHOD WORKFLOW POSITION: This is the FIRST PASS at epic breakdown</critical>
-<critical>After this workflow: UX Design will add interaction details → UPDATE epics.md</critical>
-<critical>After UX: Architecture will add technical decisions → UPDATE epics.md AGAIN</critical>
-<critical>Phase 4 Implementation pulls context from: PRD + epics.md + UX + Architecture</critical>
-<critical>This is a LIVING DOCUMENT that evolves through the BMad Method workflow chain</critical>
-<critical>Communicate all responses in {communication_language} and adapt to {user_skill_level}</critical>
-<critical>Generate all documents in {document_output_language}</critical>
-<critical>LIVING DOCUMENT: Write to epics.md continuously as you work - never wait until the end</critical>
-<critical>Input documents specified in workflow.yaml input_file_patterns - workflow engine handles fuzzy matching, whole vs sharded document discovery automatically</critical>
-
-<workflow>
-
-<step n="1" goal="Load PRD and extract requirements">
-<action>Welcome {user_name} to epic and story planning
-
-Load required documents (fuzzy match, handle both whole and sharded):
-
-- PRD.md (required)
-- domain-brief.md (if exists)
-- product-brief.md (if exists)
-
-**CRITICAL - PRD FRs Are Now Flat and Strategic:**
-
-The PRD contains FLAT, capability-level functional requirements (FR1, FR2, FR3...).
-These are STRATEGIC (WHAT capabilities exist), NOT tactical (HOW they're implemented).
-
-Example PRD FRs:
-
-- FR1: Users can create accounts with email or social authentication
-- FR2: Users can log in securely and maintain sessions
-- FR6: Users can create, edit, and delete content items
-
-**Your job in THIS workflow:**
-
-1. Map each FR to one or more epics
-2. Break each FR into stories with DETAILED acceptance criteria
-3. Add ALL the implementation details that were intentionally left out of PRD
-
-Extract from PRD:
-
-- ALL functional requirements (flat numbered list)
-- Non-functional requirements
-- Domain considerations and compliance needs
-- Project type and complexity
-- MVP vs growth vs vision scope boundaries
-- Product differentiator (what makes it special)
-- Technical constraints
-- User types and their goals
-- Success criteria
-
-**Create FR Inventory:**
-
-List all FRs to ensure coverage:
-
-- FR1: [description]
-- FR2: [description]
-- ...
-- FRN: [description]
-
-This inventory will be used to validate complete coverage in Step 4.
-</action>
-
-<template-output>fr_inventory</template-output>
-</step>
-
-<step n="2" goal="Propose epic structure from natural groupings">
-<action>Analyze requirements and identify natural epic boundaries
-
-INTENT: Find organic groupings that make sense for THIS product
-
-Look for natural patterns:
-
-- Features that work together cohesively
-- User journeys that connect
-- Business capabilities that cluster
-- Domain requirements that relate (compliance, validation, security)
-- Technical systems that should be built together
-
-Name epics based on VALUE, not technical layers:
-
-- Good: "User Onboarding", "Content Discovery", "Compliance Framework"
-- Avoid: "Database Layer", "API Endpoints", "Frontend"
-
-Each epic should:
-
-- Have clear business goal and user value
-- Be independently valuable
-- Contain 3-8 related capabilities
-- Be deliverable in cohesive phase
-
-For greenfield projects:
-
-- First epic MUST establish foundation (project setup, core infrastructure, deployment pipeline)
-- Foundation enables all subsequent work
-
-For complex domains:
-
-- Consider dedicated compliance/regulatory epics
-- Group validation and safety requirements logically
-- Note expertise requirements
-
-Present proposed epic structure showing:
-
-- Epic titles with clear value statements
-- High-level scope of each epic
-- **FR COVERAGE MAP: Which FRs does each epic address?**
-  - Example: "Epic 1 (Foundation): Covers infrastructure needs for all FRs"
-  - Example: "Epic 2 (User Management): FR1, FR2, FR3, FR4, FR5"
-  - Example: "Epic 3 (Content System): FR6, FR7, FR8, FR9"
-- Suggested sequencing
-- Why this grouping makes sense
-
-**Validate FR Coverage:**
-
-Check that EVERY FR from Step 1 inventory is mapped to at least one epic.
-If any FRs are unmapped, add them now or explain why they're deferred.
-</action>
-
-<template-output>epics_summary</template-output>
-<template-output>fr_coverage_map</template-output>
-</step>
-
-<step n="3" goal="Decompose each epic into bite-sized stories with DETAILED AC" repeat="for-each-epic">
-<action>Break down Epic {{N}} into small, implementable stories
-
-INTENT: Create stories sized for single dev agent completion
-
-**CRITICAL - ALTITUDE SHIFT FROM PRD:**
-
-PRD FRs are STRATEGIC (WHAT capabilities):
-
-- ✅ "Users can create accounts"
-
-Epic Stories are TACTICAL (HOW it's implemented):
-
-- Email field with RFC 5322 validation
-- Password requirements: 8+ chars, 1 uppercase, 1 number, 1 special
-- Password strength meter with visual feedback
-- Email verification within 15 minutes
-- reCAPTCHA v3 integration
-- Account creation completes in < 2 seconds
-- Mobile responsive with 44x44px touch targets
-- WCAG 2.1 AA compliant
-
-**THIS IS WHERE YOU ADD ALL THE DETAILS LEFT OUT OF PRD:**
-
-- UI specifics (exact field counts, validation rules, layout details)
-- Performance targets (< 2s, 60fps, etc.)
-- Technical implementation hints (libraries, patterns, APIs)
-- Edge cases (what happens when...)
-- Validation rules (regex patterns, constraints)
-- Error handling (specific error messages, retry logic)
-- Accessibility requirements (ARIA labels, keyboard nav, screen readers)
-- Platform specifics (mobile responsive, browser support)
-
-For each epic, generate:
-
-- Epic title as `epic_title_{{N}}`
-- Epic goal/value as `epic_goal_{{N}}`
-- All stories as repeated pattern `story_title_{{N}}_{{M}}` for each story M
-
-CRITICAL for Epic 1 (Foundation):
-
-- Story 1.1 MUST be project setup/infrastructure initialization
-- Sets up: repo structure, build system, deployment pipeline basics, core dependencies
-- Creates foundation for all subsequent stories
-- Note: Architecture workflow will flesh out technical details
-
-Each story should follow BDD-style acceptance criteria:
-
-**Story Pattern:**
-As a [user type],
-I want [specific capability],
-So that [clear value/benefit].
-
-**Acceptance Criteria using BDD:**
-Given [precondition or initial state]
-When [action or trigger]
-Then [expected outcome]
-
-And [additional criteria as needed]
-
-**Prerequisites:** Only previous stories (never forward dependencies)
-
-**Technical Notes:** Implementation guidance, affected components, compliance requirements
-
-Ensure stories are:
-
-- Vertically sliced (deliver complete functionality, not just one layer)
-- Sequentially ordered (logical progression, no forward dependencies)
-- Independently valuable when possible
-- Small enough for single-session completion
-- Clear enough for autonomous implementation
-
-For each story in epic {{N}}, output variables following this pattern:
-
-- story*title*{{N}}_1, story_title_{{N}}\*2, etc.
-- Each containing: user story, BDD acceptance criteria, prerequisites, technical notes</action>
-
-<template-output>epic*title*{{N}}</template-output>
-<template-output>epic*goal*{{N}}</template-output>
-
-<action>For each story M in epic {{N}}, generate story content</action>
-<template-output>story-title-{{N}}-{{M}}</template-output>
-
-</step>
-
-<step n="4" goal="Review initial epic breakdown and prepare for updates">
-<action>Review the complete epic breakdown for quality and completeness
-
-**Validate FR Coverage:**
-
-Create FR Coverage Matrix showing each FR mapped to epic(s) and story(ies):
-
-- FR1: [description] → Epic X, Story X.Y
-- FR2: [description] → Epic X, Story X.Z
-- FR3: [description] → Epic Y, Story Y.A
-- ...
-- FRN: [description] → Epic Z, Story Z.B
-
-Confirm: EVERY FR from Step 1 inventory is covered by at least one story.
-If any FRs are missing, add stories now.
-
-**Validate Story Quality:**
-
-- All functional requirements from PRD are covered by stories
-- Epic 1 establishes proper foundation (if greenfield)
-- All stories are vertically sliced (deliver complete functionality, not just one layer)
-- No forward dependencies exist (only backward references)
-- Story sizing is appropriate for single-session completion
-- BDD acceptance criteria are clear and testable
-- Details added (what was missing from PRD FRs: UI specifics, performance targets, etc.)
-- Domain/compliance requirements are properly distributed
-- Sequencing enables incremental value delivery
-
-**BMad Method Next Steps:**
-
-This epic breakdown is the INITIAL VERSION. It will be updated as you progress:
-
-1. **After UX Design Workflow:**
-   - UX Designer will design interactions for capabilities
-   - UPDATE story acceptance criteria with UX specs (mockup references, flow details)
-   - Add interaction patterns, visual design decisions, responsive breakpoints
-
-2. **After Architecture Workflow:**
-   - Architect will define technical implementation approach
-   - UPDATE story technical notes with architecture decisions
-   - Add references to data models, API contracts, tech stack choices, deployment patterns
-
-3. **During Phase 4 Implementation:**
-   - Each story pulls context from: PRD (why) + epics.md (what/how) + UX (interactions) + Architecture (technical)
-   - Stories may be further refined as implementation uncovers edge cases
-   - This document remains the single source of truth for story details
-
-Confirm with {user_name}:
-
-- Epic structure makes sense
-- All FRs covered by stories (validated via coverage matrix)
-- Story breakdown is actionable with detailed acceptance criteria
-- Ready for UX Design workflow (next BMad Method step)
-  </action>
-
-<template-output>epic_breakdown_summary</template-output>
-<template-output>fr_coverage_matrix</template-output>
-
-<output>**✅ Epic Breakdown Complete (Initial Version)**
-
-**Created:** epics.md with epic and story breakdown
-
-**FR Coverage:** All functional requirements from PRD mapped to stories (see coverage matrix in document)
-
-**Next Steps in BMad Method:**
-
-1. **UX Design** (if UI exists) - Run: `workflow ux-design`
-   → Will add interaction details to stories in epics.md
-
-2. **Architecture** - Run: `workflow create-architecture`
-   → Will add technical details to stories in epics.md
-
-3. **Phase 4 Implementation** - Stories ready for context assembly
-
-**Important:** This is a living document that will be updated as you progress through the workflow chain. The epics.md file will evolve with UX and Architecture inputs before implementation begins.
-</output>
-</step>
-
-</workflow>

package/src/modules/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/workflow.yaml

@@ -1,53 +0,0 @@
-# Epic and Story Decomposition Workflow
-name: create-epics-and-stories
-description: "Transform PRD requirements into bite-sized stories organized into deliverable functional epics. This workflow takes a Product Requirements Document (PRD) and breaks it down into epics and user stories that can be easily assigned to development teams. It ensures that all functional requirements are captured in a structured format, making it easier for teams to understand and implement the necessary features."
-author: "BMad"
-
-# Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
-project_name: "{config_source}:project_name"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-document_output_language: "{config_source}:document_output_language"
-user_skill_level: "{config_source}:user_skill_level"
-date: system-generated
-
-# Input requirements
-recommended_inputs:
-  - prd: "Product Requirements Document with FRs and NFRs"
-  - product_brief: "Product Brief with vision and goals (optional)"
-  - domain_brief: "Domain-specific requirements and context (optional)"
-
-# Smart input file references - handles both whole docs and sharded docs
-# Priority: Whole document first, then sharded version
-input_file_patterns:
-  prd:
-    whole: "{output_folder}/*prd*.md"
-    sharded: "{output_folder}/*prd*/index.md"
-  product_brief:
-    whole: "{output_folder}/*product*brief*.md"
-    sharded: "{output_folder}/*product*brief*/index.md"
-  domain_brief:
-    whole: "{output_folder}/*domain*brief*.md"
-    sharded: "{output_folder}/*domain*brief*/index.md"
-
-# Module path and component files
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories"
-instructions: "{installed_path}/instructions.md"
-template: "{installed_path}/epics-template.md"
-
-# Output configuration
-default_output_file: "{output_folder}/epics.md"
-
-standalone: true
-
-web_bundle:
-  name: "create-epics-and-stories"
-  description: "Transform PRD requirements into bite-sized stories organized in epics for 200k context dev agents"
-  author: "BMad"
-  instructions: "{bmad_folder}/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/instructions.md"
-  template: "{bmad_folder}/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/epics-template.md"
-  web_bundle_files:
-    - "{bmad_folder}/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/instructions.md"
-    - "{bmad_folder}/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/epics-template.md"

package/src/modules/bmm/workflows/2-plan-workflows/prd/domain-complexity.csv

@@ -1,13 +0,0 @@
-domain,signals,complexity,key_concerns,required_knowledge,suggested_workflow,web_searches,special_sections
-healthcare,"medical,diagnostic,clinical,FDA,patient,treatment,HIPAA,therapy,pharma,drug",high,"FDA approval;Clinical validation;HIPAA compliance;Patient safety;Medical device classification;Liability","Regulatory pathways;Clinical trial design;Medical standards;Data privacy;Integration requirements","domain-research","FDA software medical device guidance {date};HIPAA compliance software requirements;Medical software standards {date};Clinical validation software","clinical_requirements;regulatory_pathway;validation_methodology;safety_measures"
-fintech,"payment,banking,trading,investment,crypto,wallet,transaction,KYC,AML,funds,fintech",high,"Regional compliance;Security standards;Audit requirements;Fraud prevention;Data protection","KYC/AML requirements;PCI DSS;Open banking;Regional laws (US/EU/APAC);Crypto regulations","domain-research","fintech regulations {date};payment processing compliance {date};open banking API standards;cryptocurrency regulations {date}","compliance_matrix;security_architecture;audit_requirements;fraud_prevention"
-govtech,"government,federal,civic,public sector,citizen,municipal,voting",high,"Procurement rules;Security clearance;Accessibility (508);FedRAMP;Privacy;Transparency","Government procurement;Security frameworks;Accessibility standards;Privacy laws;Open data requirements","domain-research","government software procurement {date};FedRAMP compliance requirements;section 508 accessibility;government security standards","procurement_compliance;security_clearance;accessibility_standards;transparency_requirements"
-edtech,"education,learning,student,teacher,curriculum,assessment,K-12,university,LMS",medium,"Student privacy (COPPA/FERPA);Accessibility;Content moderation;Age verification;Curriculum standards","Educational privacy laws;Learning standards;Accessibility requirements;Content guidelines;Assessment validity","domain-research","educational software privacy {date};COPPA FERPA compliance;WCAG education requirements;learning management standards","privacy_compliance;content_guidelines;accessibility_features;curriculum_alignment"
-aerospace,"aircraft,spacecraft,aviation,drone,satellite,propulsion,flight,radar,navigation",high,"Safety certification;DO-178C compliance;Performance validation;Simulation accuracy;Export controls","Aviation standards;Safety analysis;Simulation validation;ITAR/export controls;Performance requirements","domain-research + technical-model","DO-178C software certification;aerospace simulation standards {date};ITAR export controls software;aviation safety requirements","safety_certification;simulation_validation;performance_requirements;export_compliance"
-automotive,"vehicle,car,autonomous,ADAS,automotive,driving,EV,charging",high,"Safety standards;ISO 26262;V2X communication;Real-time requirements;Certification","Automotive standards;Functional safety;V2X protocols;Real-time systems;Testing requirements","domain-research","ISO 26262 automotive software;automotive safety standards {date};V2X communication protocols;EV charging standards","safety_standards;functional_safety;communication_protocols;certification_requirements"
-scientific,"research,algorithm,simulation,modeling,computational,analysis,data science,ML,AI",medium,"Reproducibility;Validation methodology;Peer review;Performance;Accuracy;Computational resources","Scientific method;Statistical validity;Computational requirements;Domain expertise;Publication standards","technical-model","scientific computing best practices {date};research reproducibility standards;computational modeling validation;peer review software","validation_methodology;accuracy_metrics;reproducibility_plan;computational_requirements"
-legaltech,"legal,law,contract,compliance,litigation,patent,attorney,court",high,"Legal ethics;Bar regulations;Data retention;Attorney-client privilege;Court system integration","Legal practice rules;Ethics requirements;Court filing systems;Document standards;Confidentiality","domain-research","legal technology ethics {date};law practice management software requirements;court filing system standards;attorney client privilege technology","ethics_compliance;data_retention;confidentiality_measures;court_integration"
-insuretech,"insurance,claims,underwriting,actuarial,policy,risk,premium",high,"Insurance regulations;Actuarial standards;Data privacy;Fraud detection;State compliance","Insurance regulations by state;Actuarial methods;Risk modeling;Claims processing;Regulatory reporting","domain-research","insurance software regulations {date};actuarial standards software;insurance fraud detection;state insurance compliance","regulatory_requirements;risk_modeling;fraud_detection;reporting_compliance"
-energy,"energy,utility,grid,solar,wind,power,electricity,oil,gas",high,"Grid compliance;NERC standards;Environmental regulations;Safety requirements;Real-time operations","Energy regulations;Grid standards;Environmental compliance;Safety protocols;SCADA systems","domain-research","energy sector software compliance {date};NERC CIP standards;smart grid requirements;renewable energy software standards","grid_compliance;safety_protocols;environmental_compliance;operational_requirements"
-gaming,"game,player,gameplay,level,character,multiplayer,quest",redirect,"REDIRECT TO GAME WORKFLOWS","Game design","game-brief","NA","NA"
-general,"",low,"Standard requirements;Basic security;User experience;Performance","General software practices","continue","software development best practices {date}","standard_requirements"