bmad-method 6.0.0-alpha.8 → 6.0.1

package/src/modules/bmm/workflows/3-solutioning/solutioning-gate-check/template.md

@@ -1,146 +0,0 @@
-# Implementation Readiness Assessment Report
-
-**Date:** {{date}}
-**Project:** {{project_name}}
-**Assessed By:** {{user_name}}
-**Assessment Type:** Phase 3 to Phase 4 Transition Validation
-
----
-
-## Executive Summary
-
-{{readiness_assessment}}
-
----
-
-## Project Context
-
-{{project_context}}
-
----
-
-## Document Inventory
-
-### Documents Reviewed
-
-{{document_inventory}}
-
-### Document Analysis Summary
-
-{{document_analysis}}
-
----
-
-## Alignment Validation Results
-
-### Cross-Reference Analysis
-
-{{alignment_validation}}
-
----
-
-## Gap and Risk Analysis
-
-### Critical Findings
-
-{{gap_risk_analysis}}
-
----
-
-## UX and Special Concerns
-
-{{ux_validation}}
-
----
-
-## Detailed Findings
-
-### 🔴 Critical Issues
-
-_Must be resolved before proceeding to implementation_
-
-{{critical_issues}}
-
-### 🟠 High Priority Concerns
-
-_Should be addressed to reduce implementation risk_
-
-{{high_priority_concerns}}
-
-### 🟡 Medium Priority Observations
-
-_Consider addressing for smoother implementation_
-
-{{medium_priority_observations}}
-
-### 🟢 Low Priority Notes
-
-_Minor items for consideration_
-
-{{low_priority_notes}}
-
----
-
-## Positive Findings
-
-### ✅ Well-Executed Areas
-
-{{positive_findings}}
-
----
-
-## Recommendations
-
-### Immediate Actions Required
-
-{{immediate_actions}}
-
-### Suggested Improvements
-
-{{suggested_improvements}}
-
-### Sequencing Adjustments
-
-{{sequencing_adjustments}}
-
----
-
-## Readiness Decision
-
-### Overall Assessment: {{overall_readiness_status}}
-
-{{readiness_rationale}}
-
-### Conditions for Proceeding (if applicable)
-
-{{conditions_for_proceeding}}
-
----
-
-## Next Steps
-
-{{recommended_next_steps}}
-
-### Workflow Status Update
-
-{{status_update_result}}
-
----
-
-## Appendices
-
-### A. Validation Criteria Applied
-
-{{validation_criteria_used}}
-
-### B. Traceability Matrix
-
-{{traceability_matrix}}
-
-### C. Risk Mitigation Strategies
-
-{{risk_mitigation_strategies}}
-
----
-
-_This readiness assessment was generated using the BMad Method Implementation Ready Check workflow (v6-alpha)_

package/src/modules/bmm/workflows/3-solutioning/solutioning-gate-check/validation-criteria.yaml

@@ -1,189 +0,0 @@
-# Implementation Readiness Validation Criteria
-# Defines systematic validation rules by project level
-
-validation_rules:
-  # Level 0-1 Projects (Simple, minimal planning)
-  level_0_1:
-    required_documents:
-      - tech_spec
-      - stories_or_tasks
-
-    validations:
-      - name: "Tech Spec Completeness"
-        checks:
-          - "All features defined with implementation approach"
-          - "Technical dependencies identified"
-          - "API contracts defined if applicable"
-          - "Data models specified"
-
-      - name: "Story Coverage"
-        checks:
-          - "All tech spec features have corresponding stories"
-          - "Stories are sequenced logically"
-          - "Technical tasks are defined"
-          - "No critical gaps in coverage"
-
-  # Level 2 Projects (PRD + Tech Spec, no separate architecture)
-  level_2:
-    required_documents:
-      - prd
-      - tech_spec # Includes architecture decisions
-      - epics_and_stories
-
-    validations:
-      - name: "PRD to Tech Spec Alignment"
-        checks:
-          - "All PRD requirements addressed in tech spec"
-          - "Architecture embedded in tech spec covers PRD needs"
-          - "Non-functional requirements are specified"
-          - "Technical approach supports business goals"
-
-      - name: "Story Coverage and Alignment"
-        checks:
-          - "Every PRD requirement has story coverage"
-          - "Stories align with tech spec approach"
-          - "Epic breakdown is complete"
-          - "Acceptance criteria match PRD success criteria"
-
-      - name: "Sequencing Validation"
-        checks:
-          - "Foundation stories come first"
-          - "Dependencies are properly ordered"
-          - "Iterative delivery is possible"
-          - "No circular dependencies"
-
-  # Level 3-4 Projects (Full planning with separate architecture)
-  level_3_4:
-    required_documents:
-      - prd
-      - architecture
-      - epics_and_stories
-
-    validations:
-      - name: "PRD Completeness"
-        checks:
-          - "User requirements fully documented"
-          - "Success criteria are measurable"
-          - "Scope boundaries clearly defined"
-          - "Priorities are assigned"
-
-      - name: "Architecture Coverage"
-        checks:
-          - "All PRD requirements have architectural support"
-          - "System design is complete"
-          - "Integration points defined"
-          - "Security architecture specified"
-          - "Performance considerations addressed"
-          - "If architecture.md: Implementation patterns defined"
-          - "If architecture.md: Technology versions verified and current"
-          - "If architecture.md: Starter template command documented (if applicable)"
-
-      - name: "PRD-Architecture Alignment"
-        checks:
-          - "No architecture gold-plating beyond PRD"
-          - "NFRs from PRD reflected in architecture"
-          - "Technology choices support requirements"
-          - "Scalability matches expected growth"
-          - "If UX spec exists: Architecture supports UX requirements"
-          - "If UX spec exists: Component library supports interaction patterns"
-
-      - name: "Story Implementation Coverage"
-        checks:
-          - "All architectural components have stories"
-          - "Infrastructure setup stories exist"
-          - "Integration implementation planned"
-          - "Security implementation stories present"
-
-      - name: "Comprehensive Sequencing"
-        checks:
-          - "Infrastructure before features"
-          - "Authentication before protected resources"
-          - "Core features before enhancements"
-          - "Dependencies properly ordered"
-          - "Allows for iterative releases"
-
-# Special validation contexts
-special_contexts:
-  greenfield:
-    additional_checks:
-      - "Project initialization stories exist"
-      - "If using architecture.md: First story is starter template initialization"
-      - "Development environment setup documented"
-      - "CI/CD pipeline stories included"
-      - "Initial data/schema setup planned"
-      - "Deployment infrastructure stories present"
-
-  ux_workflow_active:
-    additional_checks:
-      - "UX requirements in PRD"
-      - "UX implementation stories exist"
-      - "Accessibility requirements covered"
-      - "Responsive design addressed"
-      - "User flow continuity maintained"
-
-  api_heavy:
-    additional_checks:
-      - "API contracts fully defined"
-      - "Versioning strategy documented"
-      - "Authentication/authorization specified"
-      - "Rate limiting considered"
-      - "API documentation stories included"
-
-# Severity definitions
-severity_levels:
-  critical:
-    description: "Must be resolved before implementation"
-    examples:
-      - "Missing stories for core requirements"
-      - "Conflicting technical approaches"
-      - "No infrastructure setup for greenfield"
-      - "Security requirements not addressed"
-
-  high:
-    description: "Should be addressed to reduce risk"
-    examples:
-      - "Incomplete acceptance criteria"
-      - "Unclear story dependencies"
-      - "Missing error handling coverage"
-      - "Performance requirements not validated"
-
-  medium:
-    description: "Consider addressing for smoother implementation"
-    examples:
-      - "Documentation gaps"
-      - "Test strategy not defined"
-      - "Monitoring approach unclear"
-      - "Minor sequencing improvements possible"
-
-  low:
-    description: "Minor improvements for consideration"
-    examples:
-      - "Formatting inconsistencies"
-      - "Optional enhancements identified"
-      - "Style guide compliance"
-      - "Nice-to-have features noted"
-
-# Readiness decision criteria
-readiness_decisions:
-  ready:
-    criteria:
-      - "No critical issues found"
-      - "All required documents present"
-      - "Core alignments validated"
-      - "Story sequencing logical"
-      - "Team can begin implementation"
-
-  ready_with_conditions:
-    criteria:
-      - "Only high/medium issues found"
-      - "Mitigation plans identified"
-      - "Core path to MVP clear"
-      - "Issues won't block initial stories"
-
-  not_ready:
-    criteria:
-      - "Critical issues identified"
-      - "Major gaps in coverage"
-      - "Conflicting approaches found"
-      - "Required documents missing"
-      - "Blocking dependencies unresolved"

package/src/modules/bmm/workflows/3-solutioning/solutioning-gate-check/workflow.yaml

@@ -1,66 +0,0 @@
-# Implementation Ready Check - Workflow Configuration
-name: solutioning-gate-check
-description: "Systematically validate that all planning and solutioning phases are complete and properly aligned before transitioning to Phase 4 implementation. Ensures PRD, architecture, and stories are cohesive with no gaps or contradictions."
-author: "BMad Builder"
-
-# Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
-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"
-date: system-generated
-
-# Workflow status integration
-workflow_status_workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml"
-workflow_paths_dir: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/paths"
-
-# Module path and component files
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/solutioning-gate-check"
-template: "{installed_path}/template.md"
-instructions: "{installed_path}/instructions.md"
-validation: "{installed_path}/checklist.md"
-
-# Output configuration
-default_output_file: "{output_folder}/implementation-readiness-report-{{date}}.md"
-
-# Input requirements
-recommended_inputs:
-  - prd: "Product Requirements Document with FRs and NFRs"
-  - architecture: "System Architecture with decisions and patterns"
-  - tech_spec: "Technical Specification (for Quick Flow track)"
-  - epics: "Epic breakdown with user stories"
-  - ux_design: "UX design specification (if UI components)"
-
-# 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"
-
-  epics:
-    whole: "{output_folder}/*epic*.md"
-    sharded: "{output_folder}/*epic*/index.md"
-
-  architecture:
-    whole: "{output_folder}/*architecture*.md"
-    sharded: "{output_folder}/*architecture*/index.md"
-
-  ux_design:
-    whole: "{output_folder}/*ux*.md"
-    sharded: "{output_folder}/*ux*/index.md"
-
-  tech_spec:
-    whole: "{output_folder}/*tech-spec*.md"
-    sharded: "{output_folder}/*tech-spec*/index.md"
-
-  document_project:
-    sharded: "{output_folder}/docs/index.md"
-
-# Validation criteria data
-validation_criteria: "{installed_path}/validation-criteria.yaml"
-
-standalone: true
-
-web_bundle: false

package/src/modules/bmm/workflows/4-implementation/code-review/backlog_template.md

@@ -1,12 +0,0 @@
-# Engineering Backlog
-
-This backlog collects cross-cutting or future action items that emerge from reviews and planning.
-
-Routing guidance:
-
-- Use this file for non-urgent optimizations, refactors, or follow-ups that span multiple stories/epics.
-- Must-fix items to ship a story belong in that story’s `Tasks / Subtasks`.
-- Same-epic improvements may also be captured under the epic Tech Spec `Post-Review Follow-ups` section.
-
-| Date | Story | Epic | Type | Severity | Owner | Status | Notes |
-| ---- | ----- | ---- | ---- | -------- | ----- | ------ | ----- |

package/src/modules/bmm/workflows/4-implementation/code-review/checklist.md

@@ -1,22 +0,0 @@
-# Senior Developer Review - Validation Checklist
-
-- [ ] Story file loaded from `{{story_path}}`
-- [ ] Story Status verified as one of: {{allow_status_values}}
-- [ ] Epic and Story IDs resolved ({{epic_num}}.{{story_num}})
-- [ ] Story Context located or warning recorded
-- [ ] Epic Tech Spec located or warning recorded
-- [ ] Architecture/standards docs loaded (as available)
-- [ ] Tech stack detected and documented
-- [ ] MCP doc search performed (or web fallback) and references captured
-- [ ] Acceptance Criteria cross-checked against implementation
-- [ ] File List reviewed and validated for completeness
-- [ ] Tests identified and mapped to ACs; gaps noted
-- [ ] Code quality review performed on changed files
-- [ ] Security review performed on changed files and dependencies
-- [ ] Outcome decided (Approve/Changes Requested/Blocked)
-- [ ] Review notes appended under "Senior Developer Review (AI)"
-- [ ] Change Log updated with review entry
-- [ ] Status updated according to settings (if enabled)
-- [ ] Story saved successfully
-
-_Reviewer: {{user_name}} on {{date}}_