bmad-method 6.0.0-alpha.5 → 6.0.0-alpha.7

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

@@ -1,181 +0,0 @@
-# {{project_name}} - Technical Specification
-
-**Author:** {{user_name}}
-**Date:** {{date}}
-**Project Level:** {{project_level}}
-**Change Type:** {{change_type}}
-**Development Context:** {{development_context}}
-
----
-
-## Context
-
-### 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}}
-
----
-
-## 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
-
-{{implementation_stack}}
-
----
-
-## Technical Details
-
-{{technical_details}}
-
----
-
-## Development Setup
-
-{{development_setup}}
-
----
-
-## 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}}
-
----
-
-## Testing Approach
-
-{{testing_approach}}
-
----
-
-## Deployment Strategy
-
-### Deployment Steps
-
-{{deployment_steps}}
-
-### Rollback Plan
-
-{{rollback_plan}}
-
-### Monitoring
-
-{{monitoring_approach}}

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

@@ -1,87 +0,0 @@
-# Story: {{story_title}}
-
-Status: Draft
-
-## Story
-
-As a {{role}},
-I want {{capability}},
-so that {{benefit}}.
-
-## Acceptance Criteria
-
-{{acceptance_criteria}}
-
-## Tasks / Subtasks
-
-{{tasks_subtasks}}
-
-## Dev Notes
-
-### Technical Summary
-
-{{technical_summary}}
-
-### Tech-Spec Reference
-
-**Full details:** See [tech-spec.md](../tech-spec.md)
-
-The tech-spec contains comprehensive context including:
-
-- Brownfield codebase analysis (if applicable)
-- Framework and library details with versions
-- Existing patterns to follow
-- Integration points and dependencies
-- Complete implementation guidance
-
-### Project Structure Notes
-
-- **Files to modify:** {{files_to_modify}}
-- **Expected test locations:** {{test_locations}}
-- **Estimated effort:** {{story_points}} story points ({{time_estimate}})
-- **Dependencies:** {{dependencies}}
-
-### Key Code References
-
-{{existing_code_references}}
-
-### References
-
-- **Tech Spec:** [tech-spec.md](../tech-spec.md) - Primary context document
-- **Architecture:** {{architecture_references}}
-
----
-
-## Dev Agent Record
-
-### Context Reference
-
-**Primary Context:** [tech-spec.md](../tech-spec.md) - Contains all brownfield analysis, framework details, and implementation guidance
-
-<!-- Additional context XML paths will be added here if story-context workflow is run -->
-
-### Agent Model Used
-
-<!-- Will be populated during dev-story execution -->
-
-### Debug Log References
-
-<!-- Will be populated during dev-story execution -->
-
-### Completion Notes List
-
-<!-- Will be populated during dev-story execution -->
-
-### File List
-
-<!-- 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/bmad/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml

@@ -1,60 +0,0 @@
-# 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."
-author: "BMad"
-
-# Critical variables from config
-config_source: "{project-root}/bmad/bmm/config.yaml"
-project_name: "{config_source}:project_name"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-document_output_language: "{config_source}:document_output_language"
-user_skill_level: "{config_source}:user_skill_level"
-date: system-generated
-
-# Runtime variables (captured during workflow execution)
-project_level: runtime-captured
-project_type: runtime-captured
-development_context: runtime-captured
-change_type: runtime-captured
-field_type: runtime-captured
-
-# Workflow components
-installed_path: "{project-root}/bmad/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
-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"
-
-# Smart input file references - handles both whole docs and sharded docs
-# Priority: Whole document first, then sharded version
-input_file_patterns:
-  product_brief:
-    whole: "{output_folder}/*brief*.md"
-    sharded: "{output_folder}/*brief*/index.md"
-
-  research:
-    whole: "{output_folder}/*research*.md"
-    sharded: "{output_folder}/*research*/index.md"
-
-  document_project:
-    sharded: "{output_folder}/docs/index.md"
-
-standalone: true

package/bmad/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml.bak

@@ -1,60 +0,0 @@
-# Technical Specification Workflow (Level 0)
-name: tech-spec
-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."
-author: "BMad"
-
-# Critical variables from config
-config_source: "{project-root}/bmad/bmm/config.yaml"
-project_name: "{config_source}:project_name"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-document_output_language: "{config_source}:document_output_language"
-user_skill_level: "{config_source}:user_skill_level"
-date: system-generated
-
-# Runtime variables (captured during workflow execution)
-project_level: runtime-captured
-project_type: runtime-captured
-development_context: runtime-captured
-change_type: runtime-captured
-field_type: runtime-captured
-
-# Workflow components
-installed_path: "{project-root}/bmad/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
-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"
-
-# Smart input file references - handles both whole docs and sharded docs
-# Priority: Whole document first, then sharded version
-input_file_patterns:
-  product_brief:
-    whole: "{output_folder}/*brief*.md"
-    sharded: "{output_folder}/*brief*/index.md"
-
-  research:
-    whole: "{output_folder}/*research*.md"
-    sharded: "{output_folder}/*research*/index.md"
-
-  document_project:
-    sharded: "{output_folder}/docs/index.md"
-
-standalone: true

package/bmad/bmm/workflows/3-solutioning/solutioning-gate-check/checklist.md

@@ -1,175 +0,0 @@
-# Implementation Readiness Validation Checklist
-
-## Document Completeness
-
-### Core Planning Documents
-
-- [ ] PRD exists and is complete (Level 2-4 projects)
-- [ ] PRD contains measurable success criteria
-- [ ] PRD defines clear scope boundaries and exclusions
-- [ ] Architecture document exists (architecture\*.md) (Level 3-4 projects)
-- [ ] Technical Specification exists with implementation details
-- [ ] Epic and story breakdown document exists
-- [ ] All documents are dated and versioned
-
-### Document Quality
-
-- [ ] No placeholder sections remain in any document
-- [ ] All documents use consistent terminology
-- [ ] Technical decisions include rationale and trade-offs
-- [ ] Assumptions and risks are explicitly documented
-- [ ] Dependencies are clearly identified and documented
-
-## Alignment Verification
-
-### PRD to Architecture Alignment (Level 3-4)
-
-- [ ] Every functional requirement in PRD has architectural support documented
-- [ ] All non-functional requirements from PRD are addressed in architecture
-- [ ] Architecture doesn't introduce features beyond PRD scope
-- [ ] Performance requirements from PRD match architecture capabilities
-- [ ] Security requirements from PRD are fully addressed in architecture
-- [ ] If architecture.md: Implementation patterns are defined for consistency
-- [ ] If architecture.md: All technology choices have verified versions
-- [ ] If UX spec exists: Architecture supports UX requirements
-
-### PRD to Stories Coverage (Level 2-4)
-
-- [ ] Every PRD requirement maps to at least one story
-- [ ] All user journeys in PRD have complete story coverage
-- [ ] Story acceptance criteria align with PRD success criteria
-- [ ] Priority levels in stories match PRD feature priorities
-- [ ] No stories exist without PRD requirement traceability
-
-### Architecture to Stories Implementation
-
-- [ ] All architectural components have implementation stories
-- [ ] Infrastructure setup stories exist for each architectural layer
-- [ ] Integration points defined in architecture have corresponding stories
-- [ ] Data migration/setup stories exist if required by architecture
-- [ ] Security implementation stories cover all architecture security decisions
-
-## Story and Sequencing Quality
-
-### Story Completeness
-
-- [ ] All stories have clear acceptance criteria
-- [ ] Technical tasks are defined within relevant stories
-- [ ] Stories include error handling and edge cases
-- [ ] Each story has clear definition of done
-- [ ] Stories are appropriately sized (no epic-level stories remaining)
-
-### Sequencing and Dependencies
-
-- [ ] Stories are sequenced in logical implementation order
-- [ ] Dependencies between stories are explicitly documented
-- [ ] No circular dependencies exist
-- [ ] Prerequisite technical tasks precede dependent stories
-- [ ] Foundation/infrastructure stories come before feature stories
-
-### Greenfield Project Specifics
-
-- [ ] Initial project setup and configuration stories exist
-- [ ] If using architecture.md: First story is starter template initialization command
-- [ ] Development environment setup is documented
-- [ ] CI/CD pipeline stories are included early in sequence
-- [ ] Database/storage initialization stories are properly placed
-- [ ] Authentication/authorization stories precede protected features
-
-## Risk and Gap Assessment
-
-### Critical Gaps
-
-- [ ] No core PRD requirements lack story coverage
-- [ ] No architectural decisions lack implementation stories
-- [ ] All integration points have implementation plans
-- [ ] Error handling strategy is defined and implemented
-- [ ] Security concerns are all addressed
-
-### Technical Risks
-
-- [ ] No conflicting technical approaches between stories
-- [ ] Technology choices are consistent across all documents
-- [ ] Performance requirements are achievable with chosen architecture
-- [ ] Scalability concerns are addressed if applicable
-- [ ] Third-party dependencies are identified with fallback plans
-
-## UX and Special Concerns (if applicable)
-
-### UX Coverage
-
-- [ ] UX requirements are documented in PRD
-- [ ] UX implementation tasks exist in relevant stories
-- [ ] Accessibility requirements have story coverage
-- [ ] Responsive design requirements are addressed
-- [ ] User flow continuity is maintained across stories
-
-### Special Considerations
-
-- [ ] Compliance requirements are fully addressed
-- [ ] Internationalization needs are covered if required
-- [ ] Performance benchmarks are defined and measurable
-- [ ] Monitoring and observability stories exist
-- [ ] Documentation stories are included where needed
-
-## Overall Readiness
-
-### Ready to Proceed Criteria
-
-- [ ] All critical issues have been resolved
-- [ ] High priority concerns have mitigation plans
-- [ ] Story sequencing supports iterative delivery
-- [ ] Team has necessary skills for implementation
-- [ ] No blocking dependencies remain unresolved
-
-### Quality Indicators
-
-- [ ] Documents demonstrate thorough analysis
-- [ ] Clear traceability exists across all artifacts
-- [ ] Consistent level of detail throughout documents
-- [ ] Risks are identified with mitigation strategies
-- [ ] Success criteria are measurable and achievable
-
-## Assessment Completion
-
-### Report Quality
-
-- [ ] All findings are supported by specific examples
-- [ ] Recommendations are actionable and specific
-- [ ] Severity levels are appropriately assigned
-- [ ] Positive findings are highlighted
-- [ ] Next steps are clearly defined
-
-### Process Validation
-
-- [ ] All expected documents were reviewed
-- [ ] Cross-references were systematically checked
-- [ ] Project level considerations were applied correctly
-- [ ] Workflow status was checked and considered
-- [ ] Output folder was thoroughly searched for artifacts
-
----
-
-## Issue Log
-
-### Critical Issues Found
-
-- [ ] ***
-- [ ] ***
-- [ ] ***
-
-### High Priority Issues Found
-
-- [ ] ***
-- [ ] ***
-- [ ] ***
-
-### Medium Priority Issues Found
-
-- [ ] ***
-- [ ] ***
-- [ ] ***
-
----
-
-_Use this checklist to ensure comprehensive validation of implementation readiness_