bmad-method 6.0.0-alpha.0 → 6.0.0-alpha.10

package/src/modules/bmm/workflows/3-solutioning/project-types/mobile-questions.md

@@ -1,110 +0,0 @@
-# Mobile Project Architecture Questions
-
-## Platform
-
-1. **Target platforms:**
-   - iOS only
-   - Android only
-   - Both iOS + Android
-
-2. **Framework choice:**
-   - React Native (JavaScript/TypeScript, large ecosystem)
-   - Flutter (Dart, high performance, beautiful UI)
-   - Native (Swift for iOS, Kotlin for Android)
-   - Expo (React Native with managed workflow)
-   - Other: **\_\_\_**
-
-3. **If React Native - workflow:**
-   - Expo (managed, easier, some limitations)
-   - React Native CLI (bare workflow, full control)
-
-## Backend & Data
-
-4. **Backend approach:**
-   - Firebase (BaaS, real-time, easy)
-   - Supabase (BaaS, PostgreSQL, open-source)
-   - Custom API (REST/GraphQL)
-   - AWS Amplify
-   - Other BaaS: **\_\_\_**
-
-5. **Local data persistence:**
-   - AsyncStorage (simple key-value)
-   - SQLite (relational, offline-first)
-   - Realm (NoSQL, sync)
-   - WatermelonDB (reactive, performance)
-   - MMKV (fast key-value)
-
-6. **State management:**
-   - Redux Toolkit
-   - Zustand
-   - MobX
-   - Context API + useReducer
-   - Jotai/Recoil
-   - React Query (server state)
-
-## Navigation
-
-7. **Navigation library:**
-   - React Navigation (standard for RN)
-   - Expo Router (file-based)
-   - React Native Navigation (native navigation)
-
-## Authentication
-
-8. **Auth approach:**
-   - Firebase Auth
-   - Supabase Auth
-   - Auth0
-   - Social auth (Google, Apple, Facebook)
-   - Custom
-   - None
-
-## Push Notifications
-
-9. **Push notifications:** (if needed)
-   - Firebase Cloud Messaging
-   - Expo Notifications
-   - OneSignal
-   - AWS SNS
-   - None needed
-
-## Payments (if applicable)
-
-10. **In-app purchases:**
-    - RevenueCat (cross-platform, subscriptions)
-    - expo-in-app-purchases
-    - react-native-iap
-    - Stripe (external payments)
-    - None needed
-
-## Additional
-
-11. **Maps integration:** (if needed)
-    - Google Maps
-    - Apple Maps
-    - Mapbox
-    - None needed
-
-12. **Analytics:**
-    - Firebase Analytics
-    - Amplitude
-    - Mixpanel
-    - PostHog
-    - None needed
-
-13. **Crash reporting:**
-    - Sentry
-    - Firebase Crashlytics
-    - Bugsnag
-    - None needed
-
-14. **Offline-first requirement:**
-    - Yes (sync when online)
-    - No (online-only)
-    - Partial (some features offline)
-
-15. **App distribution:**
-    - App Store + Google Play (public)
-    - TestFlight + Internal Testing (beta)
-    - Enterprise distribution
-    - Expo EAS Build

package/src/modules/bmm/workflows/3-solutioning/project-types/project-types.csv

@@ -1,12 +0,0 @@
-project_type_id,display_name,question_file,description,characteristics,typical_stacks,detection_keywords
-web,Web Application,web-questions.md,"Web applications with frontend and/or backend components","has_ui,server_side,browser_based","Next.js+Supabase, React+Django, Vue+Rails","website,web app,frontend,backend,browser,responsive,SPA,SSR,API"
-mobile,Mobile Application,mobile-questions.md,"Native or cross-platform mobile applications for iOS/Android","has_ui,native_app,mobile_platform","React Native+Firebase, Flutter+Supabase","mobile,iOS,Android,app store,react native,flutter,smartphone,tablet"
-embedded,Embedded System,embedded-questions.md,"Embedded systems, IoT devices, and firmware","hardware,firmware,microcontroller,iot","ESP32+FreeRTOS+MQTT, STM32+Bare Metal","embedded,IoT,microcontroller,firmware,sensor,ESP32,Arduino,hardware,MQTT,real-time"
-game,Game,game-questions.md,"Video games for PC, console, mobile, or web","has_ui,real_time,game_engine,interactive","Unity+Photon+PlayFab, Godot+Nakama","game,unity,unreal,godot,multiplayer,gameplay,3D,2D,player,level"
-library,Library/SDK,library-questions.md,"Reusable libraries, SDKs, and packages","no_ui,package,reusable,developer_tool","TypeScript+tsup+npm, Python+pip","library,SDK,package,npm,pip,gem,cargo,reusable,API wrapper,utility"
-desktop,Desktop Application,desktop-questions.md,"Native desktop applications for Windows/Mac/Linux","has_ui,native_app,cross_platform,installable","Electron+React, Tauri+Svelte, .NET MAUI","desktop,Electron,Tauri,Windows,macOS,Linux,installer,native app,system tray"
-cli,Command-Line Tool,cli-questions.md,"Command-line tools and terminal applications","no_ui,terminal,executable,developer_tool","Go+cobra, Rust+clap, Python+click","CLI,command line,terminal,bash,shell,tool,utility,script,console"
-backend,Backend/API Service,backend-questions.md,"Backend services and APIs (no frontend)","no_ui,server_side,api,microservices","Node.js+Express+PostgreSQL, FastAPI+Redis","API,backend,microservice,REST,GraphQL,gRPC,server,service,endpoint,database"
-data,Data/Analytics/ML,data-questions.md,"Data pipelines, analytics, machine learning projects","data_pipeline,analytics,ml,batch_processing","Airflow+Spark+Snowflake, PyTorch+MLflow","ETL,data pipeline,analytics,machine learning,ML,AI,Spark,Airflow,model,dataset,training"
-extension,Browser Extension,extension-questions.md,"Browser extensions for Chrome, Firefox, Safari, etc.","has_ui,browser_specific,client_side","React+Manifest V3, Plasmo+TypeScript","browser extension,Chrome extension,Firefox addon,manifest,content script,popup"
-infra,Infrastructure/DevOps,infra-questions.md,"Infrastructure as Code, K8s operators, CI/CD plugins","automation,infrastructure,devops,tooling","Terraform+AWS, Kubernetes Operator (Go), GitHub Actions","Terraform,Kubernetes,operator,IaC,infrastructure,CI/CD,DevOps,automation,deployment"

package/src/modules/bmm/workflows/3-solutioning/project-types/web-questions.md

@@ -1,136 +0,0 @@
-# Web Project Architecture Questions
-
-## Frontend
-
-1. **Framework choice:**
-   - Next.js (React, App Router, SSR)
-   - React (SPA, client-only)
-   - Vue 3 + Nuxt
-   - Svelte + SvelteKit
-   - Other: **\_\_\_**
-
-2. **Styling approach:**
-   - Tailwind CSS (utility-first)
-   - CSS Modules
-   - Styled Components (CSS-in-JS)
-   - Sass/SCSS
-   - Other: **\_\_\_**
-
-3. **State management:** (if complex client state)
-   - Zustand (lightweight)
-   - Redux Toolkit
-   - Jotai/Recoil (atomic)
-   - Context API only
-   - Server state only (React Query/SWR)
-
-## Backend
-
-4. **Backend approach:**
-   - Next.js API Routes (integrated)
-   - Express.js (Node.js)
-   - Nest.js (Node.js, structured)
-   - FastAPI (Python)
-   - Django (Python)
-   - Rails (Ruby)
-   - Other: **\_\_\_**
-
-5. **API paradigm:**
-   - REST
-   - GraphQL (Apollo, Relay)
-   - tRPC (type-safe)
-   - gRPC
-   - Mix: **\_\_\_**
-
-## Database
-
-6. **Primary database:**
-   - PostgreSQL (relational, ACID)
-   - MySQL
-   - MongoDB (document)
-   - Supabase (PostgreSQL + backend services)
-   - Firebase Firestore
-   - Other: **\_\_\_**
-
-7. **ORM/Query builder:**
-   - Prisma (type-safe, modern)
-   - Drizzle ORM
-   - TypeORM
-   - Sequelize
-   - Mongoose (for MongoDB)
-   - Raw SQL
-   - Database client directly (Supabase SDK)
-
-## Authentication
-
-8. **Auth approach:**
-   - Supabase Auth (managed, built-in)
-   - Auth0 (managed, enterprise)
-   - Clerk (managed, developer-friendly)
-   - NextAuth.js (self-hosted)
-   - Firebase Auth
-   - Custom JWT implementation
-   - Passport.js
-
-## Deployment
-
-9. **Hosting platform:**
-   - Vercel (optimal for Next.js)
-   - Netlify
-   - AWS (EC2, ECS, Lambda)
-   - Google Cloud
-   - Heroku
-   - Railway
-   - Self-hosted
-
-10. **CI/CD:**
-    - GitHub Actions
-    - GitLab CI
-    - CircleCI
-    - Vercel/Netlify auto-deploy
-    - Other: **\_\_\_**
-
-## Additional Services (if applicable)
-
-11. **Email service:** (if transactional emails needed)
-    - Resend (developer-friendly, modern)
-    - SendGrid
-    - AWS SES
-    - Postmark
-    - None needed
-
-12. **Payment processing:** (if e-commerce/subscriptions)
-    - Stripe (comprehensive)
-    - Lemon Squeezy (SaaS-focused)
-    - PayPal
-    - Square
-    - None needed
-
-13. **File storage:** (if user uploads)
-    - Supabase Storage
-    - AWS S3
-    - Cloudflare R2
-    - Vercel Blob
-    - Uploadthing
-    - None needed
-
-14. **Search:** (if full-text search beyond database)
-    - Elasticsearch
-    - Algolia
-    - Meilisearch
-    - Typesense
-    - Database full-text (PostgreSQL)
-    - None needed
-
-15. **Caching:** (if performance critical)
-    - Redis (external cache)
-    - In-memory (Node.js cache)
-    - CDN caching (Cloudflare/Vercel)
-    - None needed
-
-16. **Monitoring/Error Tracking:**
-    - Sentry (error tracking)
-    - PostHog (product analytics)
-    - Datadog
-    - LogRocket
-    - Vercel Analytics
-    - None needed

package/src/modules/bmm/workflows/3-solutioning/tech-spec/README.md

@@ -1,195 +0,0 @@
-# Technical Specification Workflow
-
-## Overview
-
-Generate a comprehensive Technical Specification from PRD and Architecture with acceptance criteria and traceability mapping. Creates detailed implementation guidance that bridges business requirements with technical execution.
-
-## Key Features
-
-- **PRD-Architecture Integration** - Synthesizes business requirements with technical constraints
-- **Traceability Mapping** - Links acceptance criteria to technical components and tests
-- **Multi-Input Support** - Leverages PRD, architecture, front-end specs, and brownfield notes
-- **Implementation Focus** - Provides concrete technical guidance for development teams
-- **Testing Integration** - Includes test strategy aligned with acceptance criteria
-- **Validation Ready** - Generates specifications suitable for architectural review
-
-## Usage
-
-### Basic Invocation
-
-```bash
-workflow tech-spec
-```
-
-### With Input Documents
-
-```bash
-# With specific PRD and architecture
-workflow tech-spec --input prd.md --input architecture.md
-
-# With comprehensive inputs
-workflow tech-spec --input prd.md --input architecture.md --input front-end-spec.md
-```
-
-### Configuration
-
-- **output_folder**: Location for generated technical specification
-- **epic_id**: Used in output filename (extracted from PRD or prompted)
-- **recommended_inputs**: PRD, architecture, front-end spec, brownfield notes
-
-## Workflow Structure
-
-### Files Included
-
-```
-tech-spec/
-├── workflow.yaml           # Configuration and metadata
-├── instructions.md         # Step-by-step execution guide
-├── template.md            # Technical specification structure
-├── checklist.md           # Validation criteria
-└── README.md              # This file
-```
-
-## Workflow Process
-
-### Phase 1: Input Collection and Analysis (Steps 1-2)
-
-- **Document Discovery**: Locates PRD and Architecture documents
-- **Epic Extraction**: Identifies epic title and ID from PRD content
-- **Template Initialization**: Creates tech-spec document from template
-- **Context Analysis**: Reviews complete PRD and architecture for alignment
-
-### Phase 2: Technical Design Specification (Step 3)
-
-- **Service Architecture**: Defines services/modules with responsibilities and interfaces
-- **Data Modeling**: Specifies entities, schemas, and relationships
-- **API Design**: Documents endpoints, request/response models, and error handling
-- **Workflow Definition**: Details sequence flows and data processing patterns
-
-### Phase 3: Non-Functional Requirements (Step 4)
-
-- **Performance Specs**: Defines measurable latency, throughput, and scalability targets
-- **Security Requirements**: Specifies authentication, authorization, and data protection
-- **Reliability Standards**: Documents availability, recovery, and degradation behavior
-- **Observability Framework**: Defines logging, metrics, and tracing requirements
-
-### Phase 4: Dependencies and Integration (Step 5)
-
-- **Dependency Analysis**: Scans repository for package manifests and frameworks
-- **Integration Mapping**: Identifies external systems and API dependencies
-- **Version Management**: Documents version constraints and compatibility requirements
-- **Infrastructure Needs**: Specifies deployment and runtime dependencies
-
-### Phase 5: Acceptance and Testing (Step 6)
-
-- **Criteria Normalization**: Extracts and refines acceptance criteria from PRD
-- **Traceability Matrix**: Maps acceptance criteria to technical components
-- **Test Strategy**: Defines testing approach for each acceptance criterion
-- **Component Mapping**: Links requirements to specific APIs and modules
-
-### Phase 6: Risk and Validation (Steps 7-8)
-
-- **Risk Assessment**: Identifies technical risks, assumptions, and open questions
-- **Mitigation Planning**: Provides strategies for addressing identified risks
-- **Quality Validation**: Ensures specification meets completeness criteria
-- **Checklist Verification**: Validates against workflow quality standards
-
-## Output
-
-### Generated Files
-
-- **Primary output**: tech-spec-{epic_id}-{date}.md
-- **Traceability data**: Embedded mapping tables linking requirements to implementation
-
-### Output Structure
-
-1. **Overview and Scope** - Project context and boundaries
-2. **System Architecture Alignment** - Connection to high-level architecture
-3. **Detailed Design** - Services, data models, APIs, and workflows
-4. **Non-Functional Requirements** - Performance, security, reliability, observability
-5. **Dependencies and Integrations** - External systems and technical dependencies
-6. **Acceptance Criteria** - Testable requirements from PRD
-7. **Traceability Mapping** - Requirements-to-implementation mapping
-8. **Test Strategy** - Testing approach and framework alignment
-9. **Risks and Assumptions** - Technical risks and mitigation strategies
-
-## Requirements
-
-- **PRD Document**: Product Requirements Document with clear acceptance criteria
-- **Architecture Document**: High-level architecture or technical design
-- **Repository Access**: For dependency analysis and framework detection
-- **Epic Context**: Clear epic identification and scope definition
-
-## Best Practices
-
-### Before Starting
-
-1. **Validate Inputs**: Ensure PRD and architecture documents are complete and current
-2. **Review Requirements**: Confirm acceptance criteria are specific and testable
-3. **Check Dependencies**: Verify repository structure supports automated dependency analysis
-
-### During Execution
-
-1. **Maintain Traceability**: Ensure every acceptance criterion maps to implementation
-2. **Be Implementation-Specific**: Provide concrete technical guidance, not high-level concepts
-3. **Consider Constraints**: Factor in existing system limitations and brownfield challenges
-
-### After Completion
-
-1. **Architect Review**: Have technical lead validate design decisions
-2. **Developer Walkthrough**: Ensure implementation team understands specifications
-3. **Test Planning**: Use traceability matrix for test case development
-
-## Troubleshooting
-
-### Common Issues
-
-**Issue**: Missing or incomplete technical details
-
-- **Solution**: Review architecture document for implementation specifics
-- **Check**: Ensure PRD contains sufficient functional requirements detail
-
-**Issue**: Acceptance criteria don't map cleanly to technical components
-
-- **Solution**: Break down complex criteria into atomic, testable statements
-- **Check**: Verify PRD acceptance criteria are properly structured
-
-**Issue**: Dependency analysis fails or is incomplete
-
-- **Solution**: Check repository structure and manifest file locations
-- **Check**: Verify repository contains standard dependency files (package.json, etc.)
-
-**Issue**: Non-functional requirements are too vague
-
-- **Solution**: Extract specific performance and quality targets from architecture
-- **Check**: Ensure architecture document contains measurable NFR specifications
-
-## Customization
-
-To customize this workflow:
-
-1. **Modify Template**: Update template.md to match organizational technical spec standards
-2. **Extend Dependencies**: Add support for additional package managers or frameworks
-3. **Enhance Validation**: Extend checklist.md with company-specific technical criteria
-4. **Add Sections**: Include additional technical concerns like DevOps or monitoring
-
-## Version History
-
-- **v6.0.0** - Comprehensive technical specification with traceability
-  - PRD-Architecture integration
-  - Automated dependency detection
-  - Traceability mapping
-  - Test strategy alignment
-
-## Support
-
-For issues or questions:
-
-- Review the workflow creation guide at `/bmad/bmb/workflows/build-workflow/workflow-creation-guide.md`
-- Validate output using `checklist.md`
-- Ensure PRD and architecture documents are complete before starting
-- Consult BMAD documentation for technical specification standards
-
----
-
-_Part of the BMad Method v6 - BMM (Method) Module_

package/src/modules/bmm/workflows/3-solutioning/tech-spec/instructions.md

@@ -1,73 +0,0 @@
-<!-- BMAD BMM Tech Spec Workflow Instructions (v6) -->
-
-```xml
-<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
-<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
-<critical>This workflow generates a comprehensive Technical Specification from PRD and Architecture, including detailed design, NFRs, acceptance criteria, and traceability mapping.</critical>
-<critical>Default execution mode: #yolo (non-interactive). If required inputs cannot be auto-discovered and {{non_interactive}} == true, HALT with a clear message listing missing documents; do not prompt.</critical>
-
-<workflow>
-  <step n="1" goal="Collect inputs and initialize">
-    <action>Identify PRD and Architecture documents from recommended_inputs. Attempt to auto-discover at default paths.</action>
-    <ask optional="true" if="{{non_interactive}} == false">If inputs are missing, ask the user for file paths.</ask>
-    <check>If inputs are missing and {{non_interactive}} == true → HALT with a clear message listing missing documents.</check>
-    <action>Extract {{epic_title}} and {{epic_id}} from PRD (or ASK if not present).</action>
-    <action>Resolve output file path using workflow variables and initialize by writing the template.</action>
-  </step>
-
-  <step n="2" goal="Overview and scope">
-    <action>Read COMPLETE PRD and Architecture files.</action>
-    <template-output file="{default_output_file}">
-      Replace {{overview}} with a concise 1-2 paragraph summary referencing PRD context and goals
-      Replace {{objectives_scope}} with explicit in-scope and out-of-scope bullets
-      Replace {{system_arch_alignment}} with a short alignment summary to the architecture (components referenced, constraints)
-    </template-output>
-  </step>
-
-  <step n="3" goal="Detailed design">
-    <action>Derive concrete implementation specifics from Architecture and PRD (NO invention).</action>
-    <template-output file="{default_output_file}">
-      Replace {{services_modules}} with a table or bullets listing services/modules with responsibilities, inputs/outputs, and owners
-      Replace {{data_models}} with normalized data model definitions (entities, fields, types, relationships); include schema snippets where available
-      Replace {{apis_interfaces}} with API endpoint specs or interface signatures (method, path, request/response models, error codes)
-      Replace {{workflows_sequencing}} with sequence notes or diagrams-as-text (steps, actors, data flow)
-    </template-output>
-  </step>
-
-  <step n="4" goal="Non-functional requirements">
-    <template-output file="{default_output_file}">
-      Replace {{nfr_performance}} with measurable targets (latency, throughput); link to any performance requirements in PRD/Architecture
-      Replace {{nfr_security}} with authn/z requirements, data handling, threat notes; cite source sections
-      Replace {{nfr_reliability}} with availability, recovery, and degradation behavior
-      Replace {{nfr_observability}} with logging, metrics, tracing requirements; name required signals
-    </template-output>
-  </step>
-
-  <step n="5" goal="Dependencies and integrations">
-    <action>Scan repository for dependency manifests (e.g., package.json, pyproject.toml, go.mod, Unity Packages/manifest.json).</action>
-    <template-output file="{default_output_file}">
-      Replace {{dependencies_integrations}} with a structured list of dependencies and integration points with version or commit constraints when known
-    </template-output>
-  </step>
-
-  <step n="6" goal="Acceptance criteria and traceability">
-    <action>Extract acceptance criteria from PRD; normalize into atomic, testable statements.</action>
-    <template-output file="{default_output_file}">
-      Replace {{acceptance_criteria}} with a numbered list of testable acceptance criteria
-      Replace {{traceability_mapping}} with a table mapping: AC → Spec Section(s) → Component(s)/API(s) → Test Idea
-    </template-output>
-  </step>
-
-  <step n="7" goal="Risks and test strategy">
-    <template-output file="{default_output_file}">
-      Replace {{risks_assumptions_questions}} with explicit list (each item labeled as Risk/Assumption/Question) with mitigation or next step
-      Replace {{test_strategy}} with a brief plan (test levels, frameworks, coverage of ACs, edge cases)
-    </template-output>
-  </step>
-
-  <step n="8" goal="Validate">
-    <invoke-task>Validate against checklist at {installed_path}/checklist.md using bmad/core/tasks/validate-workflow.md</invoke-task>
-  </step>
-
-</workflow>
-```

package/src/modules/bmm/workflows/3-solutioning/tech-spec/workflow.yaml

@@ -1,51 +0,0 @@
-name: tech-spec
-description: "Generate a comprehensive Technical Specification from PRD and Architecture with acceptance criteria and traceability mapping"
-author: "BMAD BMM"
-
-# Critical variables
-config_source: "{project-root}/bmad/bmm/config.yaml"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-date: system-generated
-
-# Inputs expected (ask user if missing)
-recommended_inputs:
-  - prd: "{project-root}/docs/prd.md"
-  - architecture: "{project-root}/docs/architecture.md"
-  - frontend_spec: "{project-root}/docs/front-end-spec.md"
-  - brownfield_notes: "{project-root}/docs/brownfield-notes.md"
-
-# Workflow components
-installed_path: "{project-root}/bmad/bmm/workflows/3-solutioning/tech-spec"
-template: "{installed_path}/template.md"
-instructions: "{installed_path}/instructions.md"
-validation: "{installed_path}/checklist.md"
-
-# Output configuration
-default_output_file: "{project-root}/docs/tech-spec-epic-{{epic_id}}.md"
-
-# Required tools
-required_tools:
-  - list_files
-  - file_info
-  - read_file
-  - write_file
-  - search_repo
-  - glob
-  - parse_markdown
-
-tags:
-  - tech-spec
-  - architecture
-  - planning
-  - bmad-v6
-
-execution_hints:
-  interactive: false
-  autonomous: true
-  iterative: true
-
-# Variables
-variables:
-  non_interactive: true

package/src/modules/bmm/workflows/3-solutioning/templates/backend-service-architecture.md

@@ -1,66 +0,0 @@
-# {{TITLE}} Architecture Document
-
-**Project:** {{project_name}}
-**Date:** {{date}}
-**Author:** {{user_name}}
-
-## Executive Summary
-
-{{executive_summary}}
-
-## 1. Technology Stack & Decisions
-
-### 1.1 Technology & Library Decision Table
-
-{{technology_table}}
-
-## 2. Architecture Overview
-
-{{architecture_overview}}
-
-## 3. Data Architecture
-
-{{data_architecture}}
-
-## 4. Component & Integration Overview
-
-{{component_overview}}
-
-## 5. Architecture Decision Records
-
-{{architecture_decisions}}
-
-## 6. Implementation Guidance
-
-{{implementation_guidance}}
-
-## 7. Proposed Source Tree
-
-```
-{{source_tree}}
-```
-
-## 8. Testing Strategy
-
-{{testing_strategy}}
-{{testing_specialist_section}}
-
-## 9. Deployment & Operations
-
-{{deployment_operations}}
-{{devops_specialist_section}}
-
-## 10. Security
-
-{{security}}
-{{security_specialist_section}}
-
----
-
-## Specialist Sections
-
-{{specialist_sections_summary}}
-
----
-
-_Generated using BMad Method Solution Architecture workflow_