bmad-method 6.0.0-alpha.1 → 6.0.0-alpha.11

package/src/modules/bmm/workflows/2-plan-workflows/tech-spec/tech-spec-template.md

@@ -3,21 +3,97 @@
 **Author:** {{user_name}}
 **Date:** {{date}}
 **Project Level:** {{project_level}}
-**Project Type:** {{project_type}}
+**Change Type:** {{change_type}}
 **Development Context:** {{development_context}}
 
 ---
 
-## Source Tree Structure
+## Context
 
-{{source_tree}}
+### Available Documents
+
+{{loaded_documents_summary}}
+
+### Project Stack
+
+{{project_stack_summary}}
+
+### Existing Codebase Structure
+
+{{existing_structure_summary}}
+
+---
+
+## The Change
+
+### Problem Statement
+
+{{problem_statement}}
+
+### Proposed Solution
+
+{{solution_overview}}
+
+### Scope
+
+**In Scope:**
+
+{{scope_in}}
+
+**Out of Scope:**
+
+{{scope_out}}
 
 ---
 
-## Technical Approach
+## Implementation Details
+
+### Source Tree Changes
+
+{{source_tree_changes}}
+
+### Technical Approach
 
 {{technical_approach}}
 
+### Existing Patterns to Follow
+
+{{existing_patterns}}
+
+### Integration Points
+
+{{integration_points}}
+
+---
+
+## Development Context
+
+### Relevant Existing Code
+
+{{existing_code_references}}
+
+### Dependencies
+
+**Framework/Libraries:**
+
+{{framework_dependencies}}
+
+**Internal Modules:**
+
+{{internal_dependencies}}
+
+### Configuration Changes
+
+{{configuration_changes}}
+
+### Existing Conventions (Brownfield)
+
+{{existing_conventions}}
+
+### Test Framework & Standards
+
+{{test_framework_info}}
+
 ---
 
 ## Implementation Stack
@@ -40,7 +116,47 @@
 
 ## Implementation Guide
 
-{{implementation_guide}}
+### Setup Steps
+
+{{setup_steps}}
+
+### Implementation Steps
+
+{{implementation_steps}}
+
+### Testing Strategy
+
+{{testing_strategy}}
+
+### Acceptance Criteria
+
+{{acceptance_criteria}}
+
+---
+
+## Developer Resources
+
+### File Paths Reference
+
+{{file_paths_complete}}
+
+### Key Code Locations
+
+{{key_code_locations}}
+
+### Testing Locations
+
+{{testing_locations}}
+
+### Documentation to Update
+
+{{documentation_updates}}
+
+---
+
+## UX/UI Considerations
+
+{{ux_ui_considerations}}
 
 ---
 
@@ -52,4 +168,14 @@
 
 ## Deployment Strategy
 
-{{deployment_strategy}}
+### Deployment Steps
+
+{{deployment_steps}}
+
+### Rollback Plan
+
+{{rollback_plan}}
+
+### Monitoring
+
+{{monitoring_approach}}

package/src/modules/bmm/workflows/2-plan-workflows/tech-spec/user-story-template.md

@@ -1,22 +1,32 @@
-# Story: {{story_title}}
+# Story {{N}}.{{M}}: {{story_title}}
 
-Status: Draft
+**Status:** Draft
 
-## Story
+---
 
-As a {{role}},
+## User Story
+
+As a {{user_type}},
 I want {{capability}},
-so that {{benefit}}.
+So that {{value_benefit}}.
+
+---
 
 ## Acceptance Criteria
 
-{{acceptance_criteria}}
+**Given** {{precondition}}
+**When** {{action}}
+**Then** {{expected_outcome}}
 
-## Tasks / Subtasks
+**And** {{additional_criteria}}
 
-{{tasks_subtasks}}
+---
+
+## Implementation Details
+
+### Tasks / Subtasks
 
-## Dev Notes
+{{tasks_subtasks}}
 
 ### Technical Summary
 
@@ -24,20 +34,34 @@ so that {{benefit}}.
 
 ### Project Structure Notes
 
-- Files to modify: {{files_to_modify}}
-- Expected test locations: {{test_locations}}
-- Estimated effort: {{story_points}} story points ({{time_estimate}})
+- **Files to modify:** {{files_to_modify}}
+- **Expected test locations:** {{test_locations}}
+- **Estimated effort:** {{story_points}} story points ({{time_estimate}})
+- **Prerequisites:** {{dependencies}}
 
-### References
+### Key Code References
 
-- **Tech Spec:** See tech-spec.md for detailed implementation
-- **Architecture:** {{architecture_references}}
+{{existing_code_references}}
 
-## Dev Agent Record
+---
+
+## Context References
+
+**Tech-Spec:** [tech-spec.md](../tech-spec.md) - Primary context document containing:
+
+- Brownfield codebase analysis (if applicable)
+- Framework and library details with versions
+- Existing patterns to follow
+- Integration points and dependencies
+- Complete implementation guidance
 
-### Context Reference
+**Architecture:** {{architecture_references}}
 
-<!-- Path(s) to story context XML will be added here by context workflow -->
+<!-- Additional context XML paths will be added here if story-context workflow is run -->
+
+---
+
+## Dev Agent Record
 
 ### Agent Model Used
 
@@ -47,10 +71,20 @@ so that {{benefit}}.
 
 <!-- Will be populated during dev-story execution -->
 
-### Completion Notes List
+### Completion Notes
 
 <!-- Will be populated during dev-story execution -->
 
-### File List
+### Files Modified
 
 <!-- Will be populated during dev-story execution -->
+
+### Test Results
+
+<!-- Will be populated during dev-story execution -->
+
+---
+
+## Review Notes
+
+<!-- Will be populated during code review -->

package/src/modules/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml

@@ -1,10 +1,10 @@
-# Technical Specification Workflow (Level 0)
-name: tech-spec-sm
-description: "Technical specification workflow for Level 0 projects (single atomic changes). Creates focused tech spec for bug fixes, single endpoint additions, or small isolated changes. Tech-spec only - no PRD needed."
+# Technical Specification
+name: tech-spec
+description: "Technical specification workflow for quick-flow projects. Creates focused tech spec and generates epic + stories (1 story for simple changes, 2-5 stories for features). Tech-spec only - no PRD needed."
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/bmad/bmm/config.yaml"
+config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
 project_name: "{config_source}:project_name"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
@@ -13,40 +13,48 @@ document_output_language: "{config_source}:document_output_language"
 user_skill_level: "{config_source}:user_skill_level"
 date: system-generated
 
+workflow-status: "{output_folder}/bmm-workflow-status.yaml"
+
+# Runtime variables (captured during workflow execution)
+story_count: runtime-captured
+epic_slug: runtime-captured
+change_type: runtime-captured
+field_type: runtime-captured
+
 # Workflow components
-installed_path: "{project-root}/bmad/bmm/workflows/2-plan-workflows/tech-spec"
+installed_path: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/tech-spec"
 instructions: "{installed_path}/instructions.md"
 template: "{installed_path}/tech-spec-template.md"
 
-# Story generation instructions (invoked based on level)
-instructions_level0_story: "{installed_path}/instructions-level0-story.md"
-instructions_level1_stories: "{installed_path}/instructions-level1-stories.md"
-
-# Templates
+# Story generation (unified approach - always generates epic + stories)
+instructions_generate_stories: "{installed_path}/instructions-generate-stories.md"
 user_story_template: "{installed_path}/user-story-template.md"
 epics_template: "{installed_path}/epics-template.md"
 
 # Output configuration
 default_output_file: "{output_folder}/tech-spec.md"
-user_story_file: "{output_folder}/user-story.md"
 epics_file: "{output_folder}/epics.md"
-
-# Recommended input documents (optional for Level 0)
-recommended_inputs:
-  - bug_report: "Bug description or issue ticket"
-  - feature_request: "Brief feature description"
+sprint_artifacts: "{output_folder}/sprint_artifacts"
+
+# Smart input file references - handles both whole docs and sharded docs
+# Priority: Whole document first, then sharded version
+# Strategy: How to load sharded documents (FULL_LOAD, SELECTIVE_LOAD, INDEX_GUIDED)
+input_file_patterns:
+  product_brief:
+    description: "Product vision and goals (optional)"
+    whole: "{output_folder}/*brief*.md"
+    sharded: "{output_folder}/*brief*/index.md"
+    load_strategy: "FULL_LOAD"
+  research:
+    description: "Market or domain research (optional)"
+    whole: "{output_folder}/*research*.md"
+    sharded: "{output_folder}/*research*/index.md"
+    load_strategy: "FULL_LOAD"
+  document_project:
+    description: "Brownfield project documentation (optional)"
+    sharded: "{output_folder}/index.md"
+    load_strategy: "INDEX_GUIDED"
 
 standalone: true
 
-web_bundle:
-  name: "tech-spec-sm"
-  description: "Technical specification workflow for Level 0-1 projects. Creates focused tech spec with story generation. Level 0: tech-spec + user story. Level 1: tech-spec + epic/stories."
-  author: "BMad"
-  instructions: "bmad/bmm/workflows/2-plan-workflows/tech-spec/instructions.md"
-  web_bundle_files:
-    - "bmad/bmm/workflows/2-plan-workflows/tech-spec/instructions.md"
-    - "bmad/bmm/workflows/2-plan-workflows/tech-spec/instructions-level0-story.md"
-    - "bmad/bmm/workflows/2-plan-workflows/tech-spec/instructions-level1-stories.md"
-    - "bmad/bmm/workflows/2-plan-workflows/tech-spec/tech-spec-template.md"
-    - "bmad/bmm/workflows/2-plan-workflows/tech-spec/user-story-template.md"
-    - "bmad/bmm/workflows/2-plan-workflows/tech-spec/epics-template.md"
+web_bundle: false

package/src/modules/bmm/workflows/3-solutioning/architecture/architecture-patterns.yaml

@@ -319,29 +319,3 @@ decision_rules:
       - quick_prototype: "Railway"
       - global_edge: "Fly.io"
       - kubernetes_needed: "GCP or AWS EKS"
-
-# Anti-patterns to avoid
-anti_patterns:
-  overengineering:
-    signs:
-      - "Microservices for < 10k users"
-      - "Kubernetes for single app"
-      - "GraphQL for 5 endpoints"
-      - "Event sourcing for CRUD app"
-    recommendation: "Start simple, evolve as needed"
-
-  underengineering:
-    signs:
-      - "No authentication strategy"
-      - "No error handling plan"
-      - "No monitoring approach"
-      - "No backup strategy"
-    recommendation: "Cover the fundamentals"
-
-  technology_soup:
-    signs:
-      - "5+ different databases"
-      - "Multiple frontend frameworks"
-      - "Inconsistent patterns"
-      - "Too many languages"
-    recommendation: "Maintain consistency"

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

@@ -1,4 +1,4 @@
-# Decision Architecture
+# Architecture
 
 ## Executive Summary
 

package/src/modules/bmm/workflows/3-solutioning/architecture/checklist.md

@@ -2,7 +2,7 @@
 
 **Purpose**: Validate the architecture document itself is complete, implementable, and provides clear guidance for AI agents.
 
-**Note**: This checklist validates the ARCHITECTURE DOCUMENT only. For cross-workflow validation (PRD → Architecture → Stories alignment), use the solutioning-gate-check workflow.
+**Note**: This checklist validates the ARCHITECTURE DOCUMENT only. For cross-workflow validation (PRD → Architecture → Stories alignment), use the implementation-readiness workflow.
 
 ---
 
@@ -225,20 +225,16 @@
 
 ### Critical Issues Found
 
-- [ ] Issue 1: **\*\***\_\_\_**\*\***
-- [ ] Issue 2: **\*\***\_\_\_**\*\***
-- [ ] Issue 3: **\*\***\_\_\_**\*\***
+<!-- replace with list of critical issues found, or N/A -->
 
 ### Recommended Actions Before Implementation
 
-1. ***
-2. ***
-3. ***
+<!-- replace with list of recommended actions, or N/A -->
 
 ---
 
-**Next Step**: Run the **solutioning-gate-check** workflow to validate alignment between PRD, Architecture, and Stories before beginning implementation.
+**Next Step**: Run the **implementation-readiness** workflow to validate alignment between PRD, UX, Architecture, and Stories before beginning implementation.
 
 ---
 
-_This checklist validates architecture document quality only. Use solutioning-gate-check for comprehensive readiness validation._
+_This checklist validates architecture document quality only. Use implementation-readiness for comprehensive readiness validation._