From f14014f0c78ca3998a11066efefb6ad5f6668b9c Mon Sep 17 00:00:00 2001 From: Brian Madison Date: Fri, 14 Nov 2025 23:54:29 -0600 Subject: [PATCH] refactor: Major workflow enhancements - time estimates prohibition, progressive epic creation, and workflow simplification MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ## Key Changes ### 1. Time Estimate Prohibition (All Modules) - Added critical warnings against providing ANY time estimates (hours/days/weeks/months) - Acknowledges AI has fundamentally changed development speed - Applied to 33 workflow instruction files across BMB, BMGD, BMM, and CIS modules - Updated workflow creation guide with prohibition guidelines ### 2. Enhanced Epic Creation Workflow - Added intelligent UPDATE vs CREATE mode detection - Detects available context (UX, Architecture, Domain brief, Product brief) - Progressive enhancement: creates basic epics, then enriches with UX/Architecture - Living document approach with continuous updates - Added 305 lines of sophisticated workflow logic ### 3. Workflow Status Initialization Refactoring - Simplified from 893 to 318 lines (65% reduction) - Streamlined state detection: CLEAN, PLANNING, ACTIVE, LEGACY, UNCLEAR - Cleaner path selection and initialization logic - Removed redundant complexity while maintaining functionality ### 4. Workflow Path Updates - Updated all 4 workflow paths (enterprise/method × brownfield/greenfield) - Added multiple optional epic creation steps at different phases: - After PRD (basic structure) - After UX Design (with interaction context) - After Architecture (final with full context) - Changed PRD output description from "with epics and stories" to "with FRs and NFRs" ### 5. Architecture & Innovation Updates - Made epics input optional in architecture workflow (falls back to PRD FRs) - Updated innovation strategy phases to remove time-based language - Phases now: Immediate Impact → Foundation Building → Scale & Optimization ### Files Changed - 33 instruction files updated with time estimate prohibition - 2 workflow.yaml files updated (create-epics-and-stories, architecture) - 4 workflow path YAML files updated - 1 workflow creation guide enhanced This refactor significantly improves workflow intelligence, removes harmful time-based planning assumptions, and creates more adaptive, context-aware workflows that better leverage AI capabilities. --- .../workflows/create-agent/instructions.md | 1 + .../workflows/create-module/instructions.md | 1 + .../workflows/create-workflow/instructions.md | 1 + .../workflow-creation-guide.md | 21 + .../workflow-template/instructions.md | 2 + .../workflows/module-brief/instructions.md | 1 + .../brainstorm-game/instructions.md | 1 + .../game-brief/instructions.md | 1 + .../game-architecture/instructions.md | 1 + .../retrospective/instructions.md | 1 + .../brainstorm-project/instructions.md | 1 + .../domain-research/instructions.md | 1 + .../1-analysis/product-brief/instructions.md | 1 + .../create-epics-and-stories/instructions.md | 316 +++++- .../create-epics-and-stories/workflow.yaml | 10 + .../create-ux-design/instructions.md | 1 + .../2-plan-workflows/prd/instructions.md | 108 +- .../tech-spec/instructions.md | 1 + .../architecture/instructions.md | 151 ++- .../3-solutioning/architecture/workflow.yaml | 2 +- .../solutioning-gate-check/instructions.md | 1 + .../retrospective/instructions.md | 1 + .../workflow-status/init/instructions.md | 979 +++++------------- .../workflows/workflow-status/instructions.md | 1 + .../paths/enterprise-brownfield.yaml | 20 +- .../paths/enterprise-greenfield.yaml | 44 +- .../paths/method-brownfield.yaml | 20 +- .../paths/method-greenfield.yaml | 22 +- .../workflows/design-thinking/instructions.md | 1 + .../innovation-strategy/instructions.md | 7 +- .../workflows/innovation-strategy/template.md | 6 +- .../workflows/problem-solving/instructions.md | 1 + .../workflows/storytelling/instructions.md | 1 + 33 files changed, 839 insertions(+), 888 deletions(-) diff --git a/src/modules/bmb/workflows/create-agent/instructions.md b/src/modules/bmb/workflows/create-agent/instructions.md index 158b6f9f..4cd9a243 100644 --- a/src/modules/bmb/workflows/create-agent/instructions.md +++ b/src/modules/bmb/workflows/create-agent/instructions.md @@ -5,6 +5,7 @@ Study YAML agent examples in: {example_agents_dir} for patterns Reference activation conventions from: {agent_activation_rules} Communicate in {communication_language} throughout the agent creation process +⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. diff --git a/src/modules/bmb/workflows/create-module/instructions.md b/src/modules/bmb/workflows/create-module/instructions.md index f9892ac2..ec45b3aa 100644 --- a/src/modules/bmb/workflows/create-module/instructions.md +++ b/src/modules/bmb/workflows/create-module/instructions.md @@ -4,6 +4,7 @@ You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmb/workflows/create-module/workflow.yaml Study existing modules in: {project-root}/{bmad_folder}/ for patterns Communicate in {communication_language} throughout the module creation process +⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. diff --git a/src/modules/bmb/workflows/create-workflow/instructions.md b/src/modules/bmb/workflows/create-workflow/instructions.md index 9a174037..c1844b33 100644 --- a/src/modules/bmb/workflows/create-workflow/instructions.md +++ b/src/modules/bmb/workflows/create-workflow/instructions.md @@ -5,6 +5,7 @@ You MUST fully understand the workflow creation guide at: {workflow_creation_guide} Study the guide thoroughly to follow ALL conventions for optimal human-AI collaboration Communicate in {communication_language} throughout the workflow creation process +⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. diff --git a/src/modules/bmb/workflows/create-workflow/workflow-creation-guide.md b/src/modules/bmb/workflows/create-workflow/workflow-creation-guide.md index 64d3c7a5..4b609010 100644 --- a/src/modules/bmb/workflows/create-workflow/workflow-creation-guide.md +++ b/src/modules/bmb/workflows/create-workflow/workflow-creation-guide.md @@ -974,6 +974,27 @@ _Generated on {{date}}_ 3. **Set limits** - "3-5 items maximum" 4. **Explain why** - Context helps AI make better decisions +### Time Estimate Prohibition + +**CRITICAL:** For all planning, analysis, and estimation workflows, include this prohibition: + +```xml +⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. +``` + +**When to include this:** + +- Planning workflows (PRDs, tech specs, architecture) +- Analysis workflows (research, brainstorming, product briefs) +- Retrospective workflows (reviews, post-mortems) +- Any workflow discussing project scope or complexity + +**When NOT needed:** + +- Pure implementation workflows (code generation, refactoring) +- Simple action workflows (file operations, status updates) +- Workflows that only process existing data + ### Conditional Execution Best Practices **✅ DO:** diff --git a/src/modules/bmb/workflows/create-workflow/workflow-template/instructions.md b/src/modules/bmb/workflows/create-workflow/workflow-template/instructions.md index cc492b0b..96467934 100644 --- a/src/modules/bmb/workflows/create-workflow/workflow-template/instructions.md +++ b/src/modules/bmb/workflows/create-workflow/workflow-template/instructions.md @@ -4,6 +4,8 @@ You MUST have already loaded and processed: {project-related}/{bmad_folder}/{module-code}/workflows/{workflow}/workflow.yaml Communicate in {communication_language} throughout the workflow process + + diff --git a/src/modules/bmb/workflows/module-brief/instructions.md b/src/modules/bmb/workflows/module-brief/instructions.md index abd3ac45..6a611e3a 100644 --- a/src/modules/bmb/workflows/module-brief/instructions.md +++ b/src/modules/bmb/workflows/module-brief/instructions.md @@ -3,6 +3,7 @@ The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmb/workflows/module-brief/workflow.yaml Communicate in {communication_language} throughout the module brief creation process +⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. diff --git a/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/instructions.md b/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/instructions.md index 4b524b5c..81217ffd 100644 --- a/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/instructions.md +++ b/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/instructions.md @@ -2,6 +2,7 @@ You MUST have already loaded and processed: {installed_path}/workflow.yaml Communicate all responses in {communication_language} This is a meta-workflow that orchestrates the CIS brainstorming workflow with game-specific context and additional game design techniques +⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. diff --git a/src/modules/bmgd/workflows/1-preproduction/game-brief/instructions.md b/src/modules/bmgd/workflows/1-preproduction/game-brief/instructions.md index bf23d32a..c86e977f 100644 --- a/src/modules/bmgd/workflows/1-preproduction/game-brief/instructions.md +++ b/src/modules/bmgd/workflows/1-preproduction/game-brief/instructions.md @@ -4,6 +4,7 @@ You MUST have already loaded and processed: {installed_path}/workflow.yaml Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level} Generate all documents in {document_output_language} +⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. DOCUMENT OUTPUT: Concise, professional, game-design focused. Use tables/lists over prose. User skill level ({user_skill_level}) affects conversation style ONLY, not document content. diff --git a/src/modules/bmgd/workflows/3-technical/game-architecture/instructions.md b/src/modules/bmgd/workflows/3-technical/game-architecture/instructions.md index 1f73d591..0e752124 100644 --- a/src/modules/bmgd/workflows/3-technical/game-architecture/instructions.md +++ b/src/modules/bmgd/workflows/3-technical/game-architecture/instructions.md @@ -11,6 +11,7 @@ This workflow replaces architecture with a conversation-driven approach Input documents specified in workflow.yaml input_file_patterns - workflow engine handles fuzzy matching, whole vs sharded document discovery automatically ELICITATION POINTS: After completing each major architectural decision area (identified by template-output tags for decision_record, project_structure, novel_pattern_designs, implementation_patterns, and architecture_document), invoke advanced elicitation to refine decisions before proceeding +⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. Check if {output_folder}/bmm-workflow-status.yaml exists diff --git a/src/modules/bmgd/workflows/4-production/retrospective/instructions.md b/src/modules/bmgd/workflows/4-production/retrospective/instructions.md index b85f44f3..13af2dd0 100644 --- a/src/modules/bmgd/workflows/4-production/retrospective/instructions.md +++ b/src/modules/bmgd/workflows/4-production/retrospective/instructions.md @@ -4,6 +4,7 @@ You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmm/workflows/4-implementation/retrospective/workflow.yaml Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level} Generate all documents in {document_output_language} +⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. DOCUMENT OUTPUT: Retrospective analysis. Concise insights, lessons learned, action items. User skill level ({user_skill_level}) affects conversation style ONLY, not retrospective content. diff --git a/src/modules/bmm/workflows/1-analysis/brainstorm-project/instructions.md b/src/modules/bmm/workflows/1-analysis/brainstorm-project/instructions.md index 8137c646..696b7fde 100644 --- a/src/modules/bmm/workflows/1-analysis/brainstorm-project/instructions.md +++ b/src/modules/bmm/workflows/1-analysis/brainstorm-project/instructions.md @@ -5,6 +5,7 @@ You MUST have already loaded and processed: {installed_path}/workflow.yaml Communicate all responses in {communication_language} This is a meta-workflow that orchestrates the CIS brainstorming workflow with project-specific context +⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. diff --git a/src/modules/bmm/workflows/1-analysis/domain-research/instructions.md b/src/modules/bmm/workflows/1-analysis/domain-research/instructions.md index 340edaa3..623c79db 100644 --- a/src/modules/bmm/workflows/1-analysis/domain-research/instructions.md +++ b/src/modules/bmm/workflows/1-analysis/domain-research/instructions.md @@ -7,6 +7,7 @@ Communicate all responses in {communication_language} and adapt deeply to {user_skill_level} Generate all documents in {document_output_language} LIVING DOCUMENT: Write to domain-brief.md continuously as you discover - never wait until the end +⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. diff --git a/src/modules/bmm/workflows/1-analysis/product-brief/instructions.md b/src/modules/bmm/workflows/1-analysis/product-brief/instructions.md index a9dcb147..851a89b5 100644 --- a/src/modules/bmm/workflows/1-analysis/product-brief/instructions.md +++ b/src/modules/bmm/workflows/1-analysis/product-brief/instructions.md @@ -7,6 +7,7 @@ Communicate all responses in {communication_language} and adapt deeply to {user_skill_level} Generate all documents in {document_output_language} LIVING DOCUMENT: Write to the document continuously as you discover - never wait until the end +⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. ## Input Document Discovery diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-epics-and-stories/instructions.md b/src/modules/bmm/workflows/2-plan-workflows/create-epics-and-stories/instructions.md index 9d227ff0..99b26679 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-epics-and-stories/instructions.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-epics-and-stories/instructions.md @@ -13,11 +13,109 @@ Generate all documents in {document_output_language} LIVING DOCUMENT: Write to epics.md continuously as you work - never wait until the end Input documents specified in workflow.yaml input_file_patterns - workflow engine handles fuzzy matching, whole vs sharded document discovery automatically +⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. + +Determine if this is initial creation or update mode + +**Check for existing epics.md:** + + +Check if {default_output_file} exists (epics.md) + + + Set mode = "UPDATE" + Load existing epics.md completely + Extract existing: + - Epic structure and titles + - Story breakdown + - FR coverage mapping + - Existing acceptance criteria + + +📝 **UPDATE MODE DETECTED** + +Found existing epics.md - I'll enhance it with newly available context. + +Existing structure: + +- {{epic_count}} epics defined +- {{story_count}} total stories + + + + + Set mode = "CREATE" + 🆕 **INITIAL CREATION MODE** + +No existing epics found - I'll create the initial epic breakdown. + + + +**Detect available context documents:** + +Check which documents exist: + +- UX Design specification ({ux_design_content}) +- Architecture document ({architecture_content}) +- Domain brief ({domain_brief_content}) +- Product brief ({product_brief_content}) + + + + Identify what's NEW since last epic update: + +- If UX exists AND not previously incorporated: + - Flag: "ADD_UX_DETAILS = true" + - Note UX sections to extract (interaction patterns, mockup references, responsive breakpoints) + +- If Architecture exists AND not previously incorporated: + - Flag: "ADD_ARCH_DETAILS = true" + - Note Architecture sections to extract (tech stack, API contracts, data models) + + +**Context Analysis:** +{{if ADD_UX_DETAILS}} +✅ UX Design found - will add interaction details to stories +{{/if}} +{{if ADD_ARCH_DETAILS}} +✅ Architecture found - will add technical implementation notes +{{/if}} +{{if !ADD_UX_DETAILS && !ADD_ARCH_DETAILS}} +⚠️ No new context documents found - reviewing for any PRD changes +{{/if}} + + + + + **Available Context:** + - ✅ PRD (required) + {{if ux_design_content}} + - ✅ UX Design (will incorporate interaction patterns) + {{/if}} + {{if architecture_content}} + - ✅ Architecture (will incorporate technical decisions) + {{/if}} + {{if !ux_design_content && !architecture_content}} + - ℹ️ Creating basic epic structure (can be enhanced later with UX/Architecture) + {{/if}} + + + +workflow_mode +available_context + + -Welcome {user_name} to epic and story planning + + +Welcome {user_name} to epic and story planning + + +Welcome back {user_name} - let's enhance your epic breakdown with new context + Load required documents (fuzzy match, handle both whole and sharded): @@ -70,6 +168,32 @@ This inventory will be used to validate complete coverage in Step 4. + + + **MAINTAIN existing epic structure:** + +Use the epic structure already defined in epics.md: + +- Keep all existing epic titles and goals +- Preserve epic sequencing +- Maintain FR coverage mapping + +Note: We're enhancing stories within existing epics, not restructuring. + + +**Using existing epic structure:** +{{list_existing_epics_with_titles}} + +Will enhance stories within these epics using new context. + + +epics_summary +fr_coverage_map + +Skip to story enhancement + + + Analyze requirements and identify natural epic boundaries INTENT: Find organic groupings that make sense for THIS product @@ -124,9 +248,66 @@ If any FRs are unmapped, add them now or explain why they're deferred. epics_summary fr_coverage_map + + + + **ENHANCE Epic {{N}} stories with new context:** + +For each existing story in Epic {{N}}: + +1. Preserve core story structure (title, user story statement) +2. Add/enhance based on available NEW context: + + + **Add from UX Design:** + - Specific mockup/wireframe references + - Exact interaction patterns + - Animation/transition specifications + - Responsive breakpoints + - Component specifications + - Error states and feedback patterns + - Accessibility requirements (WCAG compliance) + + Example enhancement: + BEFORE: "User can log in" + AFTER: "User can log in via modal (UX pg 12-15) with email/password fields, + password visibility toggle, remember me checkbox, + loading state during auth (spinner overlay), + error messages below fields (red, 14px), + success redirects to dashboard with fade transition" + + + + + **Add from Architecture:** + - Specific API endpoints and contracts + - Data model references + - Tech stack implementation details + - Performance requirements + - Security implementation notes + - Cache strategies + - Error handling patterns + + Example enhancement: + BEFORE: "System authenticates user" + AFTER: "System authenticates user via POST /api/v1/auth/login, + validates against users table (see Arch section 6.2), + returns JWT token (expires 7d) + refresh token (30d), + rate limited to 5 attempts/hour/IP, + logs failures to security_events table" + + + +3. Update acceptance criteria with new details +4. Preserve existing prerequisites +5. Enhance technical notes with new context + + + + Break down Epic {{N}} into small, implementable stories INTENT: Create stories sized for single dev agent completion @@ -208,10 +389,60 @@ For each story in epic {{N}}, output variables following this pattern: For each story M in epic {{N}}, generate story content story-title-{{N}}-{{M}} + - + + + + Review the ENHANCED epic breakdown for completeness + +**Validate Enhancements:** + +- All stories now have context-appropriate details +- UX references added where applicable +- Architecture decisions incorporated where applicable +- Acceptance criteria updated with new specifics +- Technical notes enhanced with implementation details + +**Quality Check:** + +- Stories remain bite-sized for single dev agent sessions +- No forward dependencies introduced +- All new context properly integrated + + +epic_breakdown_summary +enhancement_summary + +✅ **Epic Enhancement Complete!** + +**Updated:** epics.md with enhanced context + +**Enhancements Applied:** +{{if ADD_UX_DETAILS}} + +- ✅ UX interaction patterns and mockup references added + {{/if}} + {{if ADD_ARCH_DETAILS}} +- ✅ Architecture technical decisions and API contracts added + {{/if}} + +The epic breakdown now includes all available context for Phase 4 implementation. + +**Next Steps:** +{{if !architecture_content}} + +- Run Architecture workflow for technical decisions + {{/if}} + {{if architecture_content}} +- Ready for Phase 4: Sprint Planning + {{/if}} + + + + Review the complete epic breakdown for quality and completeness **Validate FR Coverage:** @@ -239,54 +470,65 @@ If any FRs are missing, add stories now. - 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) +- Story breakdown is actionable + +- All available context has been incorporated (PRD + UX + Architecture) +- Ready for Phase 4 Implementation + + +- UX context has been incorporated +- Ready for Architecture workflow (recommended next step) + + +- Architecture context has been incorporated +- Consider running UX Design workflow if UI exists + + +- Basic epic structure created from PRD +- Ready for next planning phase (UX Design or Architecture) + epic_breakdown_summary fr_coverage_matrix -**✅ Epic Breakdown Complete (Initial Version)** + +**✅ Epic Breakdown Complete** **Created:** epics.md with epic and story breakdown -**FR Coverage:** All functional requirements from PRD mapped to stories (see coverage matrix in document) +**FR Coverage:** All functional requirements from PRD mapped to stories -**Next Steps in BMad Method:** +**Context Incorporated:** +{{if ux_design_content && architecture_content}} -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. - - +- ✅ PRD requirements +- ✅ UX interaction patterns +- ✅ Architecture technical decisions + **Status:** COMPLETE - Ready for Phase 4 Implementation! + {{/if}} + {{if ux_design_content && !architecture_content}} +- ✅ PRD requirements +- ✅ UX interaction patterns + **Next:** Run Architecture workflow for technical decisions + {{/if}} + {{if !ux_design_content && architecture_content}} +- ✅ PRD requirements +- ✅ Architecture technical decisions + **Next:** Consider UX Design workflow if UI needed + {{/if}} + {{if !ux_design_content && !architecture_content}} +- ✅ PRD requirements (basic structure) + **Next:** Run UX Design (if UI) or Architecture workflow + **Note:** Epics will be enhanced with additional context later + {{/if}} + + + + diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-epics-and-stories/workflow.yaml b/src/modules/bmm/workflows/2-plan-workflows/create-epics-and-stories/workflow.yaml index cf38969d..06c38e7c 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-epics-and-stories/workflow.yaml +++ b/src/modules/bmm/workflows/2-plan-workflows/create-epics-and-stories/workflow.yaml @@ -31,6 +31,16 @@ input_file_patterns: whole: "{output_folder}/*domain*brief*.md" sharded: "{output_folder}/*domain*brief*/index.md" load_strategy: "INDEX_GUIDED" + ux_design: + description: "UX design specification for interaction patterns (optional)" + whole: "{output_folder}/*ux*.md" + sharded: "{output_folder}/*ux*/index.md" + load_strategy: "FULL_LOAD" + architecture: + description: "Architecture decisions and technical design (optional)" + whole: "{output_folder}/*architecture*.md" + sharded: "{output_folder}/*architecture*/index.md" + load_strategy: "FULL_LOAD" # Module path and component files installed_path: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/create-epics-and-stories" diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/instructions.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/instructions.md index 85a4afcc..ff1c18ed 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/instructions.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/instructions.md @@ -11,6 +11,7 @@ SAVE PROGRESS after each major step - use tags throughout DOCUMENT OUTPUT: Professional, specific, actionable UX design decisions WITH RATIONALE. User skill level ({user_skill_level}) affects conversation style ONLY, not document content. Input documents specified in workflow.yaml input_file_patterns - workflow engine handles fuzzy matching, whole vs sharded document discovery automatically +⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. Check if {output_folder}/bmm-workflow-status.yaml exists diff --git a/src/modules/bmm/workflows/2-plan-workflows/prd/instructions.md b/src/modules/bmm/workflows/2-plan-workflows/prd/instructions.md index 6900ff47..7cd0ff3a 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/prd/instructions.md +++ b/src/modules/bmm/workflows/2-plan-workflows/prd/instructions.md @@ -8,6 +8,7 @@ LIVING DOCUMENT: Write to PRD.md continuously as you discover - never wait until the end GUIDING PRINCIPLE: Identify what makes this product special and ensure it's reflected throughout the PRD Input documents specified in workflow.yaml input_file_patterns - workflow engine handles fuzzy matching, whole vs sharded document discovery automatically +⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. @@ -621,79 +622,80 @@ Skip categories that don't apply! - -Review the PRD we've built together + +Quick review of captured requirements: -"Let's review what we've captured: +"We've captured: -- Vision: [summary] -- Success: [key metrics] -- Scope: [MVP highlights] -- Requirements: [count] functional, [count] non-functional -- Special considerations: [domain/innovation] +- {{fr_count}} functional requirements +- {{nfr_count}} non-functional requirements +- MVP scope defined + {{if domain_complexity == 'high'}} +- Domain-specific requirements addressed + {{/if}} + {{if innovation_detected}} +- Innovation patterns documented + {{/if}} -Does this capture your product vision?" +Your PRD is complete!" + prd_summary - -After PRD review and refinement complete: - -"Excellent! Now we need to break these requirements into implementable epics and stories. - -For the epic breakdown, you have two options: - -1. Start a new session focused on epics (recommended for complex projects) -2. Continue here (I'll transform requirements into epics now) - -Which would you prefer?" - -If new session: -"To start epic planning in a new session: - -1. Save your work here -2. Start fresh and run: workflow epics-stories -3. It will load your PRD and create the epic breakdown - -This keeps each session focused and manageable." - -If continue: -"Let's continue with epic breakdown here..." -[Proceed with create-epics-and-stories workflow] -Set project_track based on workflow status (BMad Method or Enterprise Method) -Generate epic_details for the epics breakdown document - -project_track - - - product_value_summary Load the FULL file: {status_file} Update workflow_status["prd"] = "{default_output_file}" Save file, preserving ALL comments and structure - + +Check workflow path to determine next expected workflows: + +- Look for "create-epics-and-stories" as optional after PRD +- Look for "create-design" as conditional (if_has_ui) +- Look for "create-epics-and-stories-after-ux" as optional +- Identify the required next phase workflow + + **✅ PRD Complete, {user_name}!** -Your product requirements are documented and ready for implementation. - -**Created:** - -- **PRD.md** - Complete requirements adapted to {project_type} and {domain} +**Created:** PRD.md with {{fr_count}} FRs and NFRs **Next Steps:** -1. **Epic Breakdown** (Required) - Run: `workflow create-epics-and-stories` to decompose requirements into implementable stories + +Based on your {{project_track}} workflow path, you can: -2. **UX Design** (If UI exists) - Run: `workflow ux-design` for detailed user experience design +**Option A: Create Epic Breakdown Now** (Optional) +`workflow create-epics-and-stories` -3. **Architecture** (Recommended) - Run: `workflow create-architecture` for technical architecture decisions +- Creates basic epic structure from PRD +- Can be enhanced later with UX/Architecture context -What makes your product special - {product_value_summary} - is captured throughout the PRD and will guide all subsequent work. + +**Option B: UX Design First** (Recommended if UI) + `workflow create-design` + - Design user experience and interactions + - Epic breakdown can incorporate UX details later + + +**Option C: Skip to Architecture** +`workflow create-architecture` + +- Define technical decisions +- Epic breakdown created after with full context + +**Recommendation:** {{if UI_exists}}Do UX Design first, then Architecture, then create epics with full context{{else}}Go straight to Architecture, then create epics{{/if}} + + + +**Typical next workflows:** +1. `workflow create-design` - UX Design (if UI exists) +2. `workflow create-architecture` - Technical architecture +3. `workflow create-epics-and-stories` - Epic breakdown + +**Note:** Epics can be created at any point but have richer detail when created after UX/Architecture. + diff --git a/src/modules/bmm/workflows/2-plan-workflows/tech-spec/instructions.md b/src/modules/bmm/workflows/2-plan-workflows/tech-spec/instructions.md index fbca61b7..3f111620 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/tech-spec/instructions.md +++ b/src/modules/bmm/workflows/2-plan-workflows/tech-spec/instructions.md @@ -12,6 +12,7 @@ CONTEXT IS KING: Gather ALL available context before generating specs DOCUMENT OUTPUT: Technical, precise, definitive. Specific versions only. User skill level ({user_skill_level}) affects conversation style ONLY, not document content. Input documents specified in workflow.yaml input_file_patterns - workflow engine handles fuzzy matching, whole vs sharded document discovery automatically +⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. Check if {output_folder}/bmm-workflow-status.yaml exists diff --git a/src/modules/bmm/workflows/3-solutioning/architecture/instructions.md b/src/modules/bmm/workflows/3-solutioning/architecture/instructions.md index 26ac3d5d..eea67c89 100644 --- a/src/modules/bmm/workflows/3-solutioning/architecture/instructions.md +++ b/src/modules/bmm/workflows/3-solutioning/architecture/instructions.md @@ -11,6 +11,7 @@ This workflow replaces architecture with a conversation-driven approach Input documents specified in workflow.yaml input_file_patterns - workflow engine handles fuzzy matching, whole vs sharded document discovery automatically ELICITATION POINTS: After completing each major architectural decision area (identified by template-output tags for decision_record, project_structure, novel_pattern_designs, implementation_patterns, and architecture_document), invoke advanced elicitation to refine decisions before proceeding +⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. Check if {output_folder}/bmm-workflow-status.yaml exists @@ -55,7 +56,7 @@ Set standalone_mode = false -Check for existing PRD and epics files using fuzzy matching +Check for existing PRD file using fuzzy matching Fuzzy match PRD file: {prd_file} @@ -82,7 +83,10 @@ Please talk to the PM Agent to run the Create PRD workflow first to define your Review loaded PRD: {prd_content} (auto-loaded in Step 0.5 - handles both whole and sharded documents) - Review loaded epics: {epics_content} + + + Review loaded epics: {epics_content} + Check for UX specification: @@ -91,15 +95,43 @@ Please talk to the PM Agent to run the Create PRD workflow first to define your -Extract and understand from {prd_content}: - Functional Requirements (what it must do) - Non-Functional Requirements (performance, security, compliance, etc.) - Epic structure and user stories - Acceptance criteria - Any technical constraints mentioned - +Extract and understand from {prd_content}: -Count and assess project scale: - Number of epics: {{epic_count}} - Number of stories: {{story_count}} - Complexity indicators (real-time, multi-tenant, regulated, etc.) - UX complexity level (if UX spec exists) - Novel features - +- Functional Requirements (FRs) - the complete list of capabilities +- Non-Functional Requirements (performance, security, compliance, etc.) +- Any technical constraints mentioned + + + + Extract from {epics_content}: + - Epic structure and user stories + - Acceptance criteria + + + +Count and assess project scale: + + +- Number of epics: {{epic_count}} +- Number of stories: {{story_count}} + + +- Number of functional requirements: {{fr_count}} (from PRD) +- FR categories: {{fr_category_list}} (capability groups from PRD) + +- Complexity indicators (real-time, multi-tenant, regulated, etc.) +- UX complexity level (if UX spec exists) +- Novel features + Reflect understanding back to {user_name}: "I'm reviewing your project documentation for {{project_name}}. + I see {{epic_count}} epics with {{story_count}} total stories. + + +I found {{fr_count}} functional requirements organized into {{fr_category_list}}. + {{if_ux_spec}}I also found your UX specification which defines the user experience requirements.{{/if_ux_spec}} Key aspects I notice: @@ -349,7 +381,12 @@ Let's work through the remaining {{remaining_count}} decisions." Category: {{category}} Decision: {{user_choice}} Version: {{verified_version_if_applicable}} + Affects Epics: {{list_of_affected_epics}} + + +Affects FR Categories: {{list_of_affected_fr_categories}} + Rationale: {{user_reasoning_or_default}} Provided by Starter: {{yes_if_from_starter}} @@ -380,9 +417,16 @@ Provided by Starter: {{yes_if_from_starter}} Create comprehensive source tree: - Root configuration files - Source code organization - Test file locations - Build/dist directories - Documentation structure -Map epics to architectural boundaries: -"Epic: {{epic_name}} → Lives in {{module/directory/service}}" - + + Map epics to architectural boundaries: + "Epic: {{epic_name}} → Lives in {{module/directory/service}}" + + + + Map FR categories to architectural boundaries: + "FR Category: {{fr_category_name}} → Lives in {{module/directory/service}}" + + Define integration points: - Where do components communicate? - What are the API boundaries? - How do services interact? @@ -393,15 +437,22 @@ Provided by Starter: {{yes_if_from_starter}} Some projects require INVENTING new patterns, not just choosing existing ones -Scan PRD for concepts that don't have standard solutions: - Novel interaction patterns (e.g., "swipe to match" before Tinder existed) - Unique multi-component workflows (e.g., "viral invitation system") - New data relationships (e.g., "social graph" before Facebook) - Unprecedented user experiences (e.g., "ephemeral messages" before Snapchat) - Complex state machines crossing multiple epics - +Scan PRD for concepts that don't have standard solutions: - Novel interaction patterns (e.g., "swipe to match" before Tinder existed) - Unique multi-component workflows (e.g., "viral invitation system") - New data relationships (e.g., "social graph" before Facebook) - Unprecedented user experiences (e.g., "ephemeral messages" before Snapchat) + + +- Complex state machines crossing multiple epics + + +- Complex state machines crossing multiple FR categories + + For each novel pattern identified: - Engage user in design collaboration: - - "The {{pattern_name}} concept requires architectural innovation. + Engage user in design collaboration: + + "The {{pattern_name}} concept requires architectural innovation. Core challenge: {{challenge_description}} @@ -415,39 +466,44 @@ Provided by Starter: {{yes_if_from_starter}} Let me help you think through how this should work:" + - Facilitate pattern design: - 1. Identify core components involved - 2. Map data flow between components - 3. Design state management approach - 4. Create sequence diagrams for complex flows - 5. Define API contracts for the pattern - 6. Consider edge cases and failure modes - + Facilitate pattern design: 1. Identify core components involved 2. Map data flow between components 3. Design state management approach 4. Create sequence diagrams for complex flows 5. Define API contracts for the pattern 6. Consider edge cases and failure modes + - Use advanced elicitation for innovation: - "What if we approached this differently? - - What would the ideal user experience look like? - - Are there analogies from other domains we could apply? - - What constraints can we challenge?" - + Use advanced elicitation for innovation: + "What if we approached this differently? - What would the ideal user experience look like? - Are there analogies from other domains we could apply? - What constraints can we challenge?" + - Document the novel pattern: - Pattern Name: {{pattern_name}} - Purpose: {{what_problem_it_solves}} - Components: - {{component_list_with_responsibilities}} - Data Flow: - {{sequence_description_or_diagram}} - Implementation Guide: - {{how_agents_should_build_this}} + Document the novel pattern: + Pattern Name: {{pattern_name}} + Purpose: {{what_problem_it_solves}} + Components: + {{component_list_with_responsibilities}} + Data Flow: + {{sequence_description_or_diagram}} + Implementation Guide: + {{how_agents_should_build_this}} + + Affects Epics: {{epics_that_use_this_pattern}} + + + Affects FR Categories: + {{fr_categories_that_use_this_pattern}} + Validate pattern completeness: + + "Does this {{pattern_name}} design cover all the use cases in your epics? + + + "Does this {{pattern_name}} design cover all the use cases in your requirements? + - {{use_case_1}}: ✓ Handled by {{component}} - {{use_case_2}}: ✓ Handled by {{component}} ..." @@ -561,8 +617,14 @@ Enforcement: "All agents MUST follow this pattern" Check decision compatibility: - Do all decisions work together? - Are there any conflicting choices? - Do the versions align properly? -Verify epic coverage: - Does every epic have architectural support? - Are all user stories implementable with these decisions? - Are there any gaps? - + + Verify epic coverage: - Does every epic have architectural support? - Are all user stories implementable with these decisions? - Are there any gaps? + + + + Verify FR coverage: - Does every functional requirement have architectural support? - Are all capabilities implementable with these decisions? - Are there any gaps? + + Validate pattern completeness: - Are there any patterns we missed that agents would need? - Do novel patterns integrate with standard architecture? - Are implementation patterns comprehensive enough? @@ -585,7 +647,11 @@ Enforcement: "All agents MUST follow this pattern" Load template: {architecture_template} -Generate sections: 1. Executive Summary (2-3 sentences about the architecture approach) 2. Project Initialization (starter command if applicable) 3. Decision Summary Table (with verified versions and epic mapping) 4. Complete Project Structure (full tree, no placeholders) 5. Epic to Architecture Mapping (every epic placed) 6. Technology Stack Details (versions, configurations) 7. Integration Points (how components connect) 8. Novel Pattern Designs (if any were created) 9. Implementation Patterns (all consistency rules) 10. Consistency Rules (naming, organization, formats) 11. Data Architecture (models and relationships) 12. API Contracts (request/response formats) 13. Security Architecture (auth, authorization, data protection) 14. Performance Considerations (from NFRs) 15. Deployment Architecture (where and how) 16. Development Environment (setup and prerequisites) 17. Architecture Decision Records (key decisions with rationale) +Generate sections: 1. Executive Summary (2-3 sentences about the architecture approach) 2. Project Initialization (starter command if applicable) 3. Decision Summary Table (with verified versions and coverage mapping) 4. Complete Project Structure (full tree, no placeholders) + 5. Epic to Architecture Mapping (every epic placed) + + 5. FR Category to Architecture Mapping (every FR category placed) + 6. Technology Stack Details (versions, configurations) 7. Integration Points (how components connect) 8. Novel Pattern Designs (if any were created) 9. Implementation Patterns (all consistency rules) 10. Consistency Rules (naming, organization, formats) 11. Data Architecture (models and relationships) 12. API Contracts (request/response formats) 13. Security Architecture (auth, authorization, data protection) 14. Performance Considerations (from NFRs) 15. Deployment Architecture (where and how) 16. Development Environment (setup and prerequisites) 17. Architecture Decision Records (key decisions with rationale) Fill template with all collected decisions and patterns @@ -616,7 +682,12 @@ Enforcement: "All agents MUST follow this pattern" Verify MANDATORY items: - [] Decision table has Version column with specific versions + - [] Every epic is mapped to architecture components + + +- [] Every FR category is mapped to architecture components + - [] Source tree is complete, not generic - [] No placeholder text remains - [] All FRs from PRD have architectural support diff --git a/src/modules/bmm/workflows/3-solutioning/architecture/workflow.yaml b/src/modules/bmm/workflows/3-solutioning/architecture/workflow.yaml index 5e8dc42c..a88e017a 100644 --- a/src/modules/bmm/workflows/3-solutioning/architecture/workflow.yaml +++ b/src/modules/bmm/workflows/3-solutioning/architecture/workflow.yaml @@ -22,7 +22,7 @@ input_file_patterns: sharded: "{output_folder}/*prd*/index.md" load_strategy: "FULL_LOAD" epics: - description: "Epic and story breakdown" + description: "Epic and story breakdown (optional - uses PRD FRs if not present)" whole: "{output_folder}/*epic*.md" sharded: "{output_folder}/*epic*/index.md" load_strategy: "FULL_LOAD" diff --git a/src/modules/bmm/workflows/3-solutioning/solutioning-gate-check/instructions.md b/src/modules/bmm/workflows/3-solutioning/solutioning-gate-check/instructions.md index 7891d6a4..32f0c3b2 100644 --- a/src/modules/bmm/workflows/3-solutioning/solutioning-gate-check/instructions.md +++ b/src/modules/bmm/workflows/3-solutioning/solutioning-gate-check/instructions.md @@ -4,6 +4,7 @@ You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmm/workflows/3-solutioning/solutioning-gate-check/workflow.yaml Communicate all findings and analysis in {communication_language} throughout the assessment Input documents specified in workflow.yaml input_file_patterns - workflow engine handles fuzzy matching, whole vs sharded document discovery automatically +⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. diff --git a/src/modules/bmm/workflows/4-implementation/retrospective/instructions.md b/src/modules/bmm/workflows/4-implementation/retrospective/instructions.md index b85f44f3..13af2dd0 100644 --- a/src/modules/bmm/workflows/4-implementation/retrospective/instructions.md +++ b/src/modules/bmm/workflows/4-implementation/retrospective/instructions.md @@ -4,6 +4,7 @@ You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmm/workflows/4-implementation/retrospective/workflow.yaml Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level} Generate all documents in {document_output_language} +⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. DOCUMENT OUTPUT: Retrospective analysis. Concise insights, lessons learned, action items. User skill level ({user_skill_level}) affects conversation style ONLY, not retrospective content. diff --git a/src/modules/bmm/workflows/workflow-status/init/instructions.md b/src/modules/bmm/workflows/workflow-status/init/instructions.md index 6cf8d14d..6f842305 100644 --- a/src/modules/bmm/workflows/workflow-status/init/instructions.md +++ b/src/modules/bmm/workflows/workflow-status/init/instructions.md @@ -7,44 +7,24 @@ - + Welcome to BMad Method, {user_name}! -Perform comprehensive scan for ALL existing work (not just quick scan): +Perform comprehensive scan for existing work: -**Check for BMM planning artifacts:** - -- PRD files: {output*folder}/\_prd*.md or {output*folder}/\_prd*/index.md -- Tech-spec files: {output*folder}/\_tech-spec*.md or {output*folder}/\_spec*.md -- Epic files: {output*folder}/\_epic*.md or {output*folder}/\_epic*/index.md -- Architecture: {output*folder}/\_architecture*.md or {output*folder}/\_arch*.md -- UX Design: {output*folder}/\_ux*.md or {output*folder}/\_design*.md -- Product Brief: {output_folder}/\*brief\*.md -- Research docs: {output_folder}/\*research\*.md -- Brainstorm docs: {output_folder}/\*brainstorm\*.md - -**Check for implementation artifacts:** - -- The following could be in or nested under {output_folder} OR {sprint_artifacts} - CHECK BOTH LOCATIONS - - Story files: {output_folder}/stories/*.md or \*\*/stories/*story\*.md - - Sprint status: {output_folder}/sprint-status.yaml or {sprint_artifacts}/sprint-status.yaml - - Existing workflow status: {default_output_file} or {sprint_artifacts}/bmm-workflow-status.yaml - -**Check for codebase:** - -- Source code directories: src/, lib/, app/, components/, etc. -- Package files: package.json, requirements.txt, Cargo.toml, go.mod, pom.xml, etc. -- Git repository: .git/ -- Framework indicators: next.config.js, vite.config.js, etc. +- BMM artifacts: PRD, tech-spec, epics, architecture, UX, brief, research, brainstorm +- Implementation: stories, sprint-status, workflow-status +- Codebase: source directories, package files, git repo +- Check both {output_folder} and {sprint_artifacts} locations -Analyze findings and categorize project state: +Categorize into one of these states: -- **STATE 1:** Clean slate (no artifacts, no code or scaffold only) -- **STATE 2:** Planning in progress (has PRD or tech-spec, no stories/implementation yet) -- **STATE 3:** Implementation in progress (has stories or sprint status) -- **STATE 4:** Legacy codebase (has code but no BMM artifacts) -- **STATE 5:** Partial/unclear (some artifacts, state unclear) +- CLEAN: No artifacts or code (or scaffold only) +- PLANNING: Has PRD/spec but no implementation +- ACTIVE: Has stories or sprint status +- LEGACY: Has code but no BMM artifacts +- UNCLEAR: Mixed state needs clarification What's your project called? {{#if project_name}}(Config shows: {{project_name}}){{/if}} @@ -52,772 +32,303 @@ project_name - - - - Perfect! This looks like a fresh start. - Set new_project = true - Continue to Step 3 (ask about their work) + + + Perfect! Fresh start detected. + Continue to step 3 - - I found existing planning documents: + + ✅ You already have workflow tracking at: {{workflow_status_path}} -{{#if found_prd}} -📋 **PRD:** {{prd_path}} -{{#if epic_count}}- {{epic_count}} epics, {{story_count}} stories{{/if}} - -- Last modified: {{prd_modified}} - {{/if}} - -{{#if found_tech_spec}} -📋 **Tech-Spec:** {{spec_path}} -{{#if story_count}}- {{story_count}} stories{{/if}} - -- Last modified: {{spec_modified}} - {{/if}} - -{{#if found_architecture}} -🏗️ **Architecture:** {{arch_path}} - -- Last modified: {{arch_modified}} - {{/if}} - -{{#if found_ux}} -🎨 **UX Design:** {{ux_path}} - -- Last modified: {{ux_modified}} - {{/if}} - -{{#if found_brief}} -📄 **Product Brief:** {{brief_path}} - -- Last modified: {{brief_modified}} - {{/if}} - -{{#if found_research}} -🔍 **Research:** {{research_paths}} -{{/if}} - -{{#if found_brainstorm}} -🧠 **Brainstorm:** {{brainstorm_paths}} -{{/if}} - - -What's your situation with these documents? - -a) **Continue this work** - These docs describe what I'm building now -b) **Override/replace** - These are old, I'm starting something NEW -c) **Already done** - This work is complete, I'm starting a NEW project -d) **Not sure** - Let me explain my situation - -Your choice [a/b/c/d]: - - - Got it! I'll create workflow tracking for your existing planning. - Set continuing_existing_planning = true - Store found artifacts for auto-completion in workflow status - Continue to Step 5 (detect track from artifacts) - - - - Should I archive these old documents before we start fresh? - -I can move them to {output_folder}/archive/ so they're not in the way. - -Archive old docs? (y/n) - - Create archive folder if needed - Move all found planning artifacts to {output_folder}/archive/ - {{#if archived}}✅ Old documents archived to {output_folder}/archive/{{else}}Starting fresh - old docs will be ignored{{/if}} - Set new_project = true - Continue to Step 3 (ask about their work) - - - - - Should I archive the completed work before starting your new project? (y/n) - Archive old planning docs - {{#if archived}}✅ Completed work archived{{else}}Ready for your new project!{{/if}} - Set new_project = true - Continue to Step 3 (ask about their work) - - - - Tell me what you're trying to accomplish: - Analyze response and guide to appropriate choice (a, b, or c) - Loop back to present choices again with guidance - - - - - 🚨 **I found active implementation work:** - -{{#if found_stories}} -📝 **Story files:** {{story_count}} stories in {output_folder}/stories/ -{{#if story_examples}}- Examples: {{story_examples}}{{/if}} -{{/if}} - -{{#if found_sprint_status}} -📊 **Sprint tracking:** {{sprint_status_path}} - -- {{completed_stories}} completed -- {{in_progress_stories}} in progress -- {{pending_stories}} pending - {{/if}} - -{{#if found_workflow_status}} -📋 **Workflow status:** {{workflow_status_path}} - -- Generated: {{workflow_status_date}} - {{/if}} - -{{#if found_planning_docs}} -📚 **Planning docs:** {{found_planning_summary}} -{{/if}} - - -What's happening here? - -a) **Continue implementation** - I'm still working on these stories -b) **Completed** - This work is done, starting something NEW -c) **Abandoned** - Stopping this, starting over -d) **Not sure** - Let me explain - -Your choice [a/b/c/d]: - - - Check if bmm-workflow-status.yaml exists - - - ✅ **You already have workflow tracking set up!** - -Your current status file: {{workflow_status_path}} - -You don't need workflow-init - you're already using the workflow system. - -**To check your progress:** - -- Load your current agent (PM, SM, Architect, etc.) -- Run: **/bmad:bmm:workflows:workflow-status** - -This will show you what to do next. +To check progress: Load any BMM agent and run /bmad:bmm:workflows:workflow-status Happy building! 🚀 -Exit workflow gracefully (workflow already initialized) +Exit workflow (already initialized) - - You have work in progress but no workflow tracking. + + Found existing work: +{{summary_of_findings}} -I'll create workflow tracking that recognizes your existing work. -Set migrating_legacy_project = true -Store found artifacts for workflow status generation -Continue to Step 5 (detect track from artifacts) - - +How would you like to proceed? - - Archive the old work before starting fresh? (y/n) - Create archive folder - Move stories, sprint status, and planning docs to archive - {{#if archived}}✅ Old work archived{{else}}Clean slate! Ready for your new project.{{/if}} - Set new_project = true - Continue to Step 3 (ask about their work) - +a) **Continue** - Work with existing artifacts +b) **Archive & Start Fresh** - Move old work to archive +c) **Express Setup** - I know exactly what I need +d) **Guided Setup** - Walk me through options - - Tell me more about your situation: - Analyze and guide to appropriate choice - - - - - I see you have an existing codebase: - -{{codebase_summary}} - -No BMM artifacts found - this project hasn't used BMad Method yet. - -Set field_type = "brownfield" -Set new_project = true -Note: Will need document-project before planning - - -💡 **Note for brownfield projects:** -You'll need to run **document-project** workflow before planning. -This analyzes your codebase and creates documentation that AI agents can use. - -I'll include this as a prerequisite in your workflow path. -Continue to Step 3 (ask about their work) - - - - I found some artifacts but the project state is unclear: - -{{list_found_artifacts}} - -Let me understand your situation. - -What are you trying to do? - -a) Continue working on an existing project -b) Start something completely NEW -c) Fix/enhance the existing code -d) Let me explain my situation - -Your choice: - -Analyze response carefully -Guide to appropriate state (Continue existing = Step 5, New = Step 3) - - - - - -Tell me about what you're working on. What's the goal? - -Store user_description - -Analyze description for field type: - -- Brownfield indicators: "existing", "current", "add to", "modify", "enhance", "refactor" -- Greenfield indicators: "new", "build", "create", "from scratch", "start" -- Codebase presence overrides: If found codebase = brownfield unless user says "scaffold" - - - - I see you have existing code here. Are you: - -1. **Adding to or modifying** the existing codebase (brownfield) -2. **Starting fresh** - the existing code is just a scaffold/template (greenfield) -3. **Something else** - let me clarify - -Your choice [1/2/3]: - - - Set field_type = "brownfield" - - - - Set field_type = "greenfield" - Got it - treating as greenfield despite the scaffold. - - - - Please explain your situation: - Analyze explanation and set field_type accordingly - - - -Set field_type based on codebase presence (codebase = brownfield, none = greenfield) - -Detect project_type (game vs software): - -- Game keywords: "game", "player", "level", "gameplay", "rpg", "fps", "puzzle game" -- Default to "software" if not clearly a game - - - - - ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ - -🎮 **GAME DEVELOPMENT DETECTED** - -Game development workflows are now part of the **BMad Game Development (BMGD)** module. - -The BMM module is designed for software development. For game development, you'll need -the BMGD module which provides specialized game development workflows and agents. - -**Would you like to:** -a) Install BMGD module now (recommended for game projects) -b) Continue with BMM workflows (for software projects only) - -━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ - - -Your choice [a/b]: +Choice [a/b/c/d]: - - Please run the following command to install the BMGD module: - - ```bash - bmad install bmgd - ``` - - After installation, you can start your game development workflow with the Game Designer agent. - - This workflow-init will now exit. Re-run it after installing BMGD. - - Exit workflow with success status - + Set continuing_existing = true + Store found artifacts + Continue to step 7 (detect track from artifacts) - - ⚠️ **Warning:** BMM workflows are optimized for software development, not game development. - - You may encounter mismatched terminology and workflows. Consider installing BMGD for - a better game development experience. - - Continuing with software development workflows... - - Set project_type = "software" (override game detection) - + Archive existing work? (y/n) + Move artifacts to {output_folder}/archive/ + Ready for fresh start! + Continue to step 3 + + + Jump to step 3 (express path) + + + + Continue to step 4 (guided path) + + + + + Setup approach: + +a) **Express** - I know what I need +b) **Guided** - Show me the options + +Choice [a/b]: + + + Continue to step 3 (express) + + + + Continue to step 4 (guided) + + + + + +Is this for: +1) **New project** (greenfield) +2) **Existing codebase** (brownfield) + +Choice [1/2]: +Set field_type based on choice + +Planning approach: + +1. **Quick Flow** - Minimal planning, fast to code +2. **BMad Method** - Full planning for complex projects +3. **Enterprise Method** - Extended planning with security/DevOps + +Choice [1/2/3]: +Map to selected_track: quick-flow/method/enterprise + +field_type +selected_track +Jump to step 6 (discovery options) + + + +Tell me about what you're working on. What's the goal? +Store user_description + +Analyze for field type indicators: + +- Brownfield: "existing", "current", "enhance", "modify" +- Greenfield: "new", "build", "create", "from scratch" +- If codebase exists, default to brownfield unless user indicates scaffold + + + + I see existing code. Are you: +1) **Modifying** existing codebase (brownfield) +2) **Starting fresh** - code is just scaffold (greenfield) + +Choice [1/2]: +Set field_type based on answer + + +Set based on codebase presence + +Check for game development keywords + +🎮 **GAME DEVELOPMENT DETECTED** + +For game development, install the BMGD module: + +```bash +bmad install bmgd +``` + +Continue with software workflows? (y/n) +Choice: +Exit workflow user_description field_type -project_type +Continue to step 5 - -Before we determine your planning approach, I want to offer some optional -workflows that can help you think through your project more deeply: + +Based on your project, here are your planning options: -Would you like to: +━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ -- 🧠 **Brainstorm** your project? (Creative exploration and idea generation) -- 🔍 **Research** your domain? (Technical research, competitive analysis, deep-dives) +**1. Quick Flow** 🚀 -These are completely OPTIONAL but can help clarify your vision before planning. +- Minimal planning, straight to code +- Best for: Simple features, bug fixes +- Risk: Potential rework if complexity emerges -Your choice: -a) Yes, brainstorm first -b) Yes, research first -c) Yes, both -d) No, I'm ready to plan +**2. BMad Method** 🎯 {{#if recommended}}(RECOMMENDED){{/if}} -Your choice [a/b/c/d]: +- Full planning: PRD + UX + Architecture +- Best for: Products, platforms, complex features +- Benefit: AI agents have complete context for better results - - Set brainstorm_requested = true - Set research_requested = false +**3. Enterprise Method** 🏢 + +- Extended: Method + Security + DevOps + Testing +- Best for: Enterprise, compliance, mission-critical +- Benefit: Comprehensive planning for complex systems + +━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ + +{{#if brownfield}} +💡 Architecture creates focused solution design from your codebase, keeping AI agents on track. +{{/if}} + +Which approach fits best? + +1. Quick Flow +2. BMad Method {{#if recommended}}(recommended){{/if}} +3. Enterprise Method +4. Help me decide + +Choice [1/2/3/4]: + + + What concerns you about choosing? + Provide tailored guidance based on concerns + Loop back to choice - - Set brainstorm_requested = false - Set research_requested = true +Map choice to selected_track +selected_track + + + +Determine available discovery workflows based on: +- field_type (greenfield gets product-brief option) +- selected_track (quick-flow skips product-brief) + + + + Optional discovery workflows can help clarify your vision: + Select any you'd like to include: + +1. 🧠 **Brainstorm** - Creative exploration and ideation +2. 🔍 **Research** - Technical/competitive analysis +3. 📋 **Product Brief** - Strategic product planning (recommended) + +Enter numbers (e.g., "1,3" or "all" or "none"): - - Set brainstorm_requested = true - Set research_requested = true + + Optional discovery workflows: + Include any of these? + +1. 🧠 **Brainstorm** - Creative exploration +2. 🔍 **Research** - Domain analysis + +Enter numbers (e.g., "1,2" or "none"): - - Set brainstorm_requested = false - Set research_requested = false - +Parse selections and set: + +- brainstorm_requested +- research_requested +- product_brief_requested (if applicable) + brainstorm_requested research_requested - - - - - - Detect track from existing artifacts: - -**Track Detection Logic:** - -- Has PRD + Architecture → BMad Method -- Has PRD only → BMad Method (architecture was optional/skipped) -- Has tech-spec only → BMad Quick Flow -- Has Security/DevOps docs → BMad Enterprise Method - - - Based on your existing planning documents, I've detected you're using: - -**{{detected_track_name}}** - -{{#if found_artifacts_list}} -Found completed workflows: -{{#each found_artifacts_list}} - -- {{workflow_name}}: {{file_path}} - {{/each}} - {{/if}} - -I'll create workflow tracking that matches your existing approach and -automatically marks these completed workflows as done. - -Does this look right? (y/n) - -Which track should I use instead? - -1. BMad Quick Flow -2. BMad Method -3. BMad Enterprise Method - -Your choice: - -Update selected_track based on choice -Store selected_track -selected_track - -Continue to Step 6 (product brief question if applicable) - - - - Now, let me explain your planning options. - -━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ - -🚀 **BMad Quick Flow** - Fast Implementation Path - -⏱️ **Time:** Hours to 1 day of planning -📝 **Approach:** Tech-spec focused - just enough detail to start coding -✅ **Best for:** Simple features, bug fixes, scope is crystal clear -⚠️ **Trade-off:** Less upfront planning = higher risk of rework if complexity emerges -🤖 **Agent Support:** Basic - AI will have minimal context - -**Example:** "Fix login bug" or "Add export button" - -━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ - -🎯 **BMad Method** - Full Product Planning (RECOMMENDED) - -⏱️ **Time:** 1-3 days of planning -📝 **Approach:** PRD + UX + Architecture - complete product and system design -✅ **Best for:** - -- **GREENFIELD:** Products, platforms, multi-feature initiatives -- **BROWNFIELD:** Complex additions (new UIs + APIs, major refactors, new modules) - -✅ **Benefits:** - -- AI agents have COMPLETE context for better code generation -- Architecture distills massive codebases into focused solution design -- Prevents architectural drift and ensures consistency -- Fewer surprises and less rework during implementation -- Faster overall delivery (planning investment pays off!) -- Better code quality and maintainability - -🤖 **Agent Support:** Exceptional - AI becomes a true coding partner with full context - -{{#if brownfield}} -💡 **Why Architecture for Brownfield?** -Your brownfield documentation might be huge (thousands of lines). The Architecture -workflow takes all that context and creates a SUCCINCT solution design specific to -YOUR project. This keeps AI agents focused on YOUR changes without getting lost -in the existing codebase details. -{{/if}} - -**Example:** "User dashboard with analytics" or "Payment integration system" -or "Add real-time collaboration to existing editor" - -━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ - -🏢 **BMad Enterprise Method** - Extended Enterprise Planning - -⏱️ **Time:** 3-7 days of planning -📝 **Approach:** BMad Method + Security Architecture + DevOps + Test Strategy -✅ **Best for:** Enterprise requirements, compliance, multi-tenant, mission-critical -✅ **Benefits:** All of BMad Method PLUS specialized planning for: - -- Security architecture and threat modeling -- DevOps pipeline and infrastructure planning -- Comprehensive test strategy -- Compliance and audit requirements - -🤖 **Agent Support:** Elite - comprehensive planning for complex enterprise systems - -**Example:** "Multi-tenant SaaS platform" or "HIPAA-compliant patient portal" -or "Add SOC2-compliant audit logging to enterprise app" - -━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ - -Generate recommendation based on user_description and field_type: - -**Recommendation Logic:** - -- Complexity keywords (dashboard, platform, system, integration, multiple features) → Recommend BMad Method -- Simple keywords (fix, bug, add button, simple) → Mention Quick Flow as option -- Enterprise keywords (multi-tenant, compliance, security, audit) → Recommend Enterprise -- Brownfield + complex → Strongly recommend Method (explain architecture benefit) -- Greenfield + complex → Recommend Method - - - - -💡 **My Honest Recommendation:** - -{{recommendation_with_reasoning}} - -━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ - -Which approach fits your situation? - -1. **BMad Quick Flow** - Fast, minimal planning (I accept rework risk) -2. **BMad Method** - Full planning for better AI results (RECOMMENDED) -3. **BMad Enterprise Method** - Extended planning for enterprise needs -4. **I'm not sure** - Help me decide - -Your choice [1/2/3/4]: - - - Tell me more about your concerns or uncertainties: - Provide tailored guidance based on their specific concerns - Present choices again with more specific recommendation - - -Map choice to track name: - -- 1 → "quick-flow" -- 2 → "method" -- 3 → "enterprise" - - -Store selected_track -selected_track - - - - - - - - Skip this step - product brief not applicable for brownfield or quick flow - Set product_brief_requested = false - Continue to Step 7 (generate workflow path) - - - - One more optional workflow for greenfield projects: - -📋 **Product Brief** - Strategic product planning document - -This is OPTIONAL but recommended for greenfield BMad Method projects. -It helps you articulate: - -- Product vision and unique value proposition -- Target users and their needs -- Success criteria and goals -- Market positioning and strategy - -This comes BEFORE your PRD and helps inform it with strategic thinking. - -Would you like to include Product Brief in your workflow? - -a) Yes, include Product Brief -b) No, skip to PRD - -Your choice [a/b]: - - - Set product_brief_requested = true - - - - Set product_brief_requested = false - - product_brief_requested - + + 💡 **Note:** For brownfield projects, run document-project workflow first to analyze your codebase. + - - -Determine path file based on selected track and field type: - -**Path File Mapping:** - -- quick-flow + greenfield → "quick-flow-greenfield.yaml" -- quick-flow + brownfield → "quick-flow-brownfield.yaml" -- method + greenfield → "method-greenfield.yaml" -- method + brownfield → "method-brownfield.yaml" -- enterprise + greenfield → "enterprise-greenfield.yaml" -- enterprise + brownfield → "enterprise-brownfield.yaml" -- game → "game-design.yaml" - - -Load {path_files}/{determined_path_file} -Parse workflow path file to extract phases and workflows - -Build workflow_items list: - -For each phase in path file: - -1. Check if phase should be included based on: - - User choices (brainstorm_requested, research_requested, product_brief_requested) - - Phase conditions (prerequisite phases, optional phases) -2. Add comment header: ` # Phase {n}: {Phase Name}` -3. For each workflow in phase: - - Check if workflow should be included based on user choices - - Add entry: ` {workflow-id}: {default_status} # agent: {agent}` - - Default status from path file (required/optional/recommended/conditional) - - Agent from path file (pm/architect/ux-designer/sm/analyst/etc.) -4. Add blank line between phases - - -Scan for existing completed workflows and update workflow_items: - -**Scan locations:** - -- Brainstorm: {output_folder}/brainstorm\*.md -- Research: {output_folder}/research\*.md -- Product Brief: {output_folder}/\*brief\*.md -- PRD: {output*folder}/\_prd*.md or {output*folder}/\_prd*/index.md -- Tech-spec: {output*folder}/\_tech-spec*.md or {output*folder}/\_spec*.md -- Epics: {output*folder}/\_epic*.md or {output*folder}/\_epic*/index.md -- UX Design: {output*folder}/\_ux*.md or {output*folder}/\_design*.md -- Architecture: {output*folder}/\_architecture*.md or {output*folder}/\_arch*.md -- Sprint Planning: {output_folder}/\*sprint\*.yaml - -**CRITICAL:** If file exists, replace workflow status with ONLY the file path, preserving agent comment. -Example: `prd: docs/prd.md # agent: pm` (NOT "completed - docs/prd.md") + +Analyze artifacts to detect track: +- Has PRD → BMad Method +- Has tech-spec only → Quick Flow +- Has Security/DevOps → Enterprise Method -workflow_path_file -workflow_items +Detected: **{{detected_track}}** based on {{found_artifacts}} +Correct? (y/n) +Which track instead? + +1. Quick Flow +2. BMad Method +3. Enterprise Method + +Choice: + +Set selected_track +selected_track - + +Load path file: {path_files}/{{selected_track}}-{{field_type}}.yaml +Build workflow_items from path file +Scan for existing completed work and update statuses +Set generated date -Set generated date to current date generated +workflow_path_file +workflow_items + -Perfect! Here's your personalized BMad workflow path: + +Your BMad workflow path: -━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ - -**Track:** {{selected_track_display_name}} -**Field Type:** {{field_type}} +**Track:** {{selected_track}} +**Type:** {{field_type}} **Project:** {{project_name}} -━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ - -{{#if brownfield AND needs_documentation}} -🔧 **Prerequisites:** -✅ document-project - Create comprehensive codebase documentation (analyst agent) -(Required before planning workflows) -{{/if}} - -{{#if has_discovery_phase}} -🧠 **Phase 0: Discovery** (Optional - based on your choices) -{{#if brainstorm_requested}} -✅ Brainstorm - Creative exploration session (analyst agent) -{{/if}} -{{#if research_requested}} -✅ Research - Domain and technical research (analyst agent) -{{/if}} -{{#if product_brief_requested}} -✅ Product Brief - Strategic product planning (analyst agent) -{{/if}} -{{/if}} - -{{#if selected_track == quick-flow}} -📝 **Phase 1: Planning** -✅ Tech-Spec - Implementation-focused specification (pm agent) -(Auto-detects epic structure if 2+ stories) - -🚀 **Phase 2: Implementation** -✅ Sprint Planning - Create sprint tracking (sm agent) -✅ Story Development - Implement story-by-story (sm agent) -{{/if}} - -{{#if selected_track in [method, enterprise]}} -📋 **Phase 1: Planning** -✅ PRD - Product Requirements Document (pm agent) -✅ Validate PRD (optional quality check) (pm agent) -✅ UX Design (if UI components - determined after PRD) (ux-designer agent) - -🏗️ **Phase 2: Solutioning** -{{#if brownfield}} -✅ Architecture - Integration design (RECOMMENDED for brownfield) (architect agent) -Creates focused solution design from your existing codebase context -{{else}} -✅ Architecture - System design document (architect agent) -{{/if}} -✅ Validate Architecture (optional quality check) (architect agent) -✅ Solutioning Gate Check - Validate all planning aligns before coding (architect agent) - -🚀 **Phase 3: Implementation** -✅ Sprint Planning - Create sprint tracking (sm agent) -✅ Story Development - Implement story-by-story with epic-tech-specs (sm agent) -{{/if}} - -{{#if selected_track == enterprise}} - -🏢 **Additional Enterprise Planning:** -✅ Security Architecture - Threat modeling and security design (architect agent) -✅ DevOps Strategy - Pipeline and infrastructure planning (architect agent) -✅ Test Strategy - Comprehensive testing approach (tea agent) -{{/if}} - -{{#if found_existing_artifacts}} -━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ - -📁 **Existing Work Detected:** - -I found these completed workflows and will mark them as done: -{{#each completed_workflows}} -✅ {{workflow_name}}: {{file_path}} -{{/each}} - -Your workflow tracking will start from where you left off! - -━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ -{{/if}} - -Ready to create your workflow tracking file? (y/n) - - - Prepare all template variables for workflow-status-template.yaml: - - generated: {current_date} - - project_name: {project_name} - - project_type: {project_type} - - selected_track: {selected_track} - - field_type: {field_type} - - workflow_path_file: {workflow_path_file} - - workflow_items: {workflow_items from step 7} - - -Generate YAML from workflow-status-template.yaml with all variables -Save status file to {output_folder}/bmm-workflow-status.yaml - -Identify the first non-completed workflow in workflow_items -Look up that workflow's agent and command from the loaded path file - -✅ **Workflow tracking created:** {output_folder}/bmm-workflow-status.yaml +{{#if brownfield}}Prerequisites: document-project{{/if}} +{{#if has_discovery}}Discovery: {{list_selected_discovery}}{{/if}} ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ -{{#if completed_workflows_found}} -🎉 Great news! I found {{completed_count}} workflow(s) already completed. -{{/if}} +{{workflow_path_summary}} -**Next Workflow:** {{next_workflow_name}} +━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ + +Create workflow tracking file? (y/n) + + + Generate YAML from template with all variables + Save to {output_folder}/bmm-workflow-status.yaml + Identify next workflow and agent + +✅ **Created:** {output_folder}/bmm-workflow-status.yaml + +**Next:** {{next_workflow_name}} **Agent:** {{next_agent}} **Command:** /bmad:bmm:workflows:{{next_workflow_id}} -{{#if next_agent != 'analyst' AND next_agent != 'pm'}} -💡 **Tip:** Start a new chat and load the **{{next_agent}}** agent before running this workflow. +{{#if next_agent not in [analyst, pm]}} +💡 Start new chat with **{{next_agent}}** agent first. {{/if}} -━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ +To check progress: /bmad:bmm:workflows:workflow-status -Happy building with BMad Method! 🚀 - -**To check your progress anytime:** - -- Load any BMM agent -- Run: /bmad:bmm:workflows:workflow-status - - - - - No problem! You can run workflow-init again anytime you're ready. - -To get started later, just load the Analyst agent and run: -**/bmad:bmm:workflows:workflow-init** +Happy building! 🚀 + + No problem! Run workflow-init again when ready. + diff --git a/src/modules/bmm/workflows/workflow-status/instructions.md b/src/modules/bmm/workflows/workflow-status/instructions.md index faf2ae9c..fc5059ef 100644 --- a/src/modules/bmm/workflows/workflow-status/instructions.md +++ b/src/modules/bmm/workflows/workflow-status/instructions.md @@ -4,6 +4,7 @@ You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml This workflow operates in multiple modes: interactive (default), validate, data, init-check, update Other workflows can call this as a service to avoid duplicating status logic +⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. diff --git a/src/modules/bmm/workflows/workflow-status/paths/enterprise-brownfield.yaml b/src/modules/bmm/workflows/workflow-status/paths/enterprise-brownfield.yaml index 749248f2..9e0c7a57 100644 --- a/src/modules/bmm/workflows/workflow-status/paths/enterprise-brownfield.yaml +++ b/src/modules/bmm/workflows/workflow-status/paths/enterprise-brownfield.yaml @@ -60,12 +60,24 @@ phases: agent: "pm" command: "validate-prd" + - id: "create-epics-and-stories" + optional: true + agent: "pm" + command: "create-epics-and-stories" + note: "Optional: Create epic breakdown early (basic structure only)" + - id: "create-design" recommended: true agent: "ux-designer" command: "create-design" note: "Recommended - must integrate with existing UX patterns" + - id: "create-epics-and-stories-after-ux" + optional: true + agent: "pm" + command: "create-epics-and-stories" + note: "Optional: Create epic breakdown with UX context" + - phase: 2 name: "Solutioning" required: true @@ -103,11 +115,17 @@ phases: agent: "architect" command: "validate-architecture" + - id: "create-epics-and-stories-final" + required: true + agent: "pm" + command: "create-epics-and-stories" + note: "Required: Create final epic breakdown with full context (PRD + UX + Architecture)" + - id: "solutioning-gate-check" required: true agent: "architect" command: "solutioning-gate-check" - note: "Critical gate - validates all planning before touching production system" + note: "Critical gate - validates all planning + Epics before touching production system" - phase: 3 name: "Implementation" diff --git a/src/modules/bmm/workflows/workflow-status/paths/enterprise-greenfield.yaml b/src/modules/bmm/workflows/workflow-status/paths/enterprise-greenfield.yaml index bb86e23b..bcf19e7a 100644 --- a/src/modules/bmm/workflows/workflow-status/paths/enterprise-greenfield.yaml +++ b/src/modules/bmm/workflows/workflow-status/paths/enterprise-greenfield.yaml @@ -48,12 +48,24 @@ phases: agent: "pm" command: "validate-prd" + - id: "create-epics-and-stories" + optional: true + agent: "pm" + command: "create-epics-and-stories" + note: "Optional: Create epic breakdown early (basic structure only)" + - id: "create-design" recommended: true agent: "ux-designer" command: "create-design" note: "Highly recommended for enterprise - design system and patterns" + - id: "create-epics-and-stories-after-ux" + optional: true + agent: "pm" + command: "create-epics-and-stories" + note: "Optional: Create epic breakdown with UX context" + - phase: 2 name: "Solutioning" required: true @@ -72,30 +84,36 @@ phases: output: "System-level testability review" note: "Enterprise requires testability validation - auto-detects system-level mode" - - id: "create-security-architecture" - optional: true - agent: "architect" - command: "create-security-architecture" - output: "Security architecture and threat model" - note: "Future workflow - optional extended enterprise workflow for security design, auth, compliance" + # - id: "create-security-architecture" + # optional: true + # agent: "architect" + # command: "create-security-architecture" + # output: "Security architecture and threat model" + # note: "Future workflow - optional extended enterprise workflow for security design, auth, compliance" - - id: "create-devops-strategy" - optional: true - agent: "architect" - command: "create-devops-strategy" - output: "DevOps pipeline and infrastructure plan" - note: "Future workflow - optional extended enterprise workflow for CI/CD, deployment, monitoring" + # - id: "create-devops-strategy" + # optional: true + # agent: "architect" + # command: "create-devops-strategy" + # output: "DevOps pipeline and infrastructure plan" + # note: "Future workflow - optional extended enterprise workflow for CI/CD, deployment, monitoring" - id: "validate-architecture" recommended: true agent: "architect" command: "validate-architecture" + - id: "create-epics-and-stories-final" + required: true + agent: "pm" + command: "create-epics-and-stories" + note: "Required: Create final epic breakdown with full context (PRD + UX + Architecture)" + - id: "solutioning-gate-check" required: true agent: "architect" command: "solutioning-gate-check" - note: "Validates all planning artifacts + testability align before implementation" + note: "Validates all planning artifacts + Epics + testability align before implementation" - phase: 3 name: "Implementation" diff --git a/src/modules/bmm/workflows/workflow-status/paths/method-brownfield.yaml b/src/modules/bmm/workflows/workflow-status/paths/method-brownfield.yaml index 3c7af533..22b62347 100644 --- a/src/modules/bmm/workflows/workflow-status/paths/method-brownfield.yaml +++ b/src/modules/bmm/workflows/workflow-status/paths/method-brownfield.yaml @@ -59,11 +59,23 @@ phases: agent: "pm" command: "validate-prd" + - id: "create-epics-and-stories" + optional: true + agent: "pm" + command: "create-epics-and-stories" + note: "Optional: Create epic breakdown early (basic structure only)" + - id: "create-design" conditional: "if_has_ui" agent: "ux-designer" command: "create-design" + - id: "create-epics-and-stories-after-ux" + optional: true + agent: "pm" + command: "create-epics-and-stories" + note: "Optional: Create epic breakdown with UX context" + - phase: 2 name: "Solutioning" required: true @@ -75,6 +87,12 @@ phases: output: "Integration architecture - solution design for THIS project" note: "HIGHLY RECOMMENDED: Distills massive brownfield context into focused solution design. Prevents agent confusion." + - id: "create-epics-and-stories-final" + required: true + agent: "pm" + command: "create-epics-and-stories" + note: "Required: Create final epic breakdown with full context (PRD + UX + Architecture)" + - id: "test-design" recommended: true agent: "tea" @@ -91,7 +109,7 @@ phases: required: true agent: "architect" command: "solutioning-gate-check" - note: "Validates PRD + UX + Architecture (if created) cohesion" + note: "Validates PRD + UX + Architecture + Epics (if created) cohesion" - phase: 3 name: "Implementation" diff --git a/src/modules/bmm/workflows/workflow-status/paths/method-greenfield.yaml b/src/modules/bmm/workflows/workflow-status/paths/method-greenfield.yaml index 1ebb5ddf..bc170d30 100644 --- a/src/modules/bmm/workflows/workflow-status/paths/method-greenfield.yaml +++ b/src/modules/bmm/workflows/workflow-status/paths/method-greenfield.yaml @@ -40,7 +40,7 @@ phases: required: true agent: "pm" command: "prd" - output: "Product Requirements Document with epics and stories" + output: "Product Requirements Document with FRs and NFRs" - id: "validate-prd" optional: true @@ -48,12 +48,24 @@ phases: command: "validate-prd" note: "Quality check for PRD completeness" + - id: "create-epics-and-stories" + optional: true + agent: "pm" + command: "create-epics-and-stories" + note: "Optional: Create epic breakdown early (basic structure only)" + - id: "create-design" conditional: "if_has_ui" agent: "ux-designer" command: "create-design" note: "Determined after PRD - user/agent decides if needed" + - id: "create-epics-and-stories-after-ux" + optional: true + agent: "pm" + command: "create-epics-and-stories" + note: "Optional: Create epic breakdown with UX context" + - phase: 2 name: "Solutioning" required: true @@ -65,6 +77,12 @@ phases: output: "System architecture document" note: "Complete system design for greenfield projects" + - id: "create-epics-and-stories-final" + required: true + agent: "pm" + command: "create-epics-and-stories" + note: "Required: Create final epic breakdown with full context (PRD + UX + Architecture)" + - id: "test-design" recommended: true agent: "tea" @@ -82,7 +100,7 @@ phases: required: true agent: "architect" command: "solutioning-gate-check" - note: "Validates PRD + UX + Architecture + Testability cohesion before implementation" + note: "Validates PRD + UX + Architecture + Epics + Testability cohesion before implementation" - phase: 3 name: "Implementation" diff --git a/src/modules/cis/workflows/design-thinking/instructions.md b/src/modules/cis/workflows/design-thinking/instructions.md index 227e3521..8815b753 100644 --- a/src/modules/cis/workflows/design-thinking/instructions.md +++ b/src/modules/cis/workflows/design-thinking/instructions.md @@ -3,6 +3,7 @@ The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml You MUST have already loaded and processed: {project_root}/{bmad_folder}/cis/workflows/design-thinking/workflow.yaml Load and understand design methods from: {design_methods} +⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. YOU ARE A HUMAN-CENTERED DESIGN FACILITATOR: diff --git a/src/modules/cis/workflows/innovation-strategy/instructions.md b/src/modules/cis/workflows/innovation-strategy/instructions.md index 777cd485..fcabd413 100644 --- a/src/modules/cis/workflows/innovation-strategy/instructions.md +++ b/src/modules/cis/workflows/innovation-strategy/instructions.md @@ -3,6 +3,7 @@ The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml You MUST have already loaded and processed: {project_root}/{bmad_folder}/cis/workflows/innovation-strategy/workflow.yaml Load and understand innovation frameworks from: {innovation_frameworks} +⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. YOU ARE A STRATEGIC INNOVATION ADVISOR: @@ -231,9 +232,9 @@ Create phased roadmap with clear milestones. Structure in three phases: -- **Phase 1 (0-3 months)**: Immediate actions, quick wins, hypothesis validation -- **Phase 2 (3-9 months)**: Foundation building, capability development, market entry -- **Phase 3 (9-18 months)**: Scale, optimization, market expansion +- **Phase 1 - Immediate Impact**: Quick wins, hypothesis validation, initial momentum +- **Phase 2 - Foundation Building**: Capability development, market entry, systematic growth +- **Phase 3 - Scale & Optimization**: Market expansion, efficiency gains, competitive positioning For each phase: diff --git a/src/modules/cis/workflows/innovation-strategy/template.md b/src/modules/cis/workflows/innovation-strategy/template.md index 1c6d6908..a05066f9 100644 --- a/src/modules/cis/workflows/innovation-strategy/template.md +++ b/src/modules/cis/workflows/innovation-strategy/template.md @@ -144,15 +144,15 @@ ## 📋 EXECUTION ROADMAP -### Phase 1: Immediate Actions (0-3 months) +### Phase 1: Immediate Impact {{phase_1}} -### Phase 2: Foundation Building (3-9 months) +### Phase 2: Foundation Building {{phase_2}} -### Phase 3: Scale and Optimize (9-18 months) +### Phase 3: Scale & Optimization {{phase_3}} diff --git a/src/modules/cis/workflows/problem-solving/instructions.md b/src/modules/cis/workflows/problem-solving/instructions.md index 4840a6da..e0e48e27 100644 --- a/src/modules/cis/workflows/problem-solving/instructions.md +++ b/src/modules/cis/workflows/problem-solving/instructions.md @@ -3,6 +3,7 @@ The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml You MUST have already loaded and processed: {project_root}/{bmad_folder}/cis/workflows/problem-solving/workflow.yaml Load and understand solving methods from: {solving_methods} +⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. YOU ARE A SYSTEMATIC PROBLEM-SOLVING FACILITATOR: diff --git a/src/modules/cis/workflows/storytelling/instructions.md b/src/modules/cis/workflows/storytelling/instructions.md index 11d0e44a..3f04ef5c 100644 --- a/src/modules/cis/workflows/storytelling/instructions.md +++ b/src/modules/cis/workflows/storytelling/instructions.md @@ -6,6 +6,7 @@ The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml You MUST have already loaded and processed: {project_root}/{bmad_folder}/cis/workflows/storytelling/workflow.yaml Communicate all responses in {communication_language} +⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.