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

package/src/modules/{bmm/workflows/2-plan-workflows → bmgd/workflows/2-design}/narrative/instructions-narrative.md

@@ -2,28 +2,49 @@
 
 <workflow>
 
-<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
+<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
 <critical>You MUST have already completed the GDD workflow</critical>
 <critical>Communicate all responses in {communication_language}</critical>
 <critical>This workflow creates detailed narrative content for story-driven games</critical>
 <critical>Uses narrative_template for output</critical>
 <critical>If users mention gameplay mechanics, note them but keep focus on narrative</critical>
 <critical>Facilitate good brainstorming techniques throughout with the user, pushing them to come up with much of the narrative you will help weave together. The goal is for the user to feel that they crafted the narrative and story arc unless they push you to do it all or indicate YOLO</critical>
+<critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>
 
-<step n="0" goal="Check for workflow status">
+<step n="0" goal="Check for workflow status" tag="workflow-status">
+<action>Check if {output_folder}/bmm-workflow-status.yaml exists</action>
 
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
-  <param>mode: init-check</param>
-</invoke-workflow>
-
-<check if="status_exists == true">
-  <action>Store {{status_file_path}} for later updates</action>
-  <action>Set tracking_mode = true</action>
+<check if="status file not found">
+  <output>No workflow status file found. Narrative workflow is optional - you can continue without status tracking.</output>
+  <action>Set standalone_mode = true</action>
 </check>
 
-<check if="status_exists == false">
-  <action>Set tracking_mode = false</action>
-  <output>Note: Running without workflow tracking. Run `workflow-init` to enable progress tracking.</output>
+<check if="status file found">
+  <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
+  <action>Parse workflow_status section</action>
+  <action>Check status of "narrative" workflow</action>
+  <action>Get project_level from YAML metadata</action>
+  <action>Find first non-completed workflow (next expected workflow)</action>
+
+  <check if="narrative status is file path (already completed)">
+    <output>⚠️ Narrative Design Document already completed: {{narrative status}}</output>
+    <ask>Re-running will overwrite the existing narrative document. Continue? (y/n)</ask>
+    <check if="n">
+      <output>Exiting. Use workflow-status to see your next step.</output>
+      <action>Exit workflow</action>
+    </check>
+  </check>
+
+  <check if="narrative is not the next expected workflow (latter items are completed already in the list)">
+    <output>⚠️ Next expected workflow: {{next_workflow}}. Narrative is out of sequence.</output>
+    <ask>Continue with Narrative Design anyway? (y/n)</ask>
+    <check if="n">
+      <output>Exiting. Run {{next_workflow}} instead.</output>
+      <action>Exit workflow</action>
+    </check>
+  </check>
+
+<action>Set standalone_mode = false</action>
 </check>
 </step>
 
@@ -123,7 +144,6 @@ For 3-Act:
 Describe each act/section for your game:</ask>
 
 <template-output>act_breakdown</template-output>
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 
@@ -142,7 +162,6 @@ Format:
 Your story beats:</ask>
 
 <template-output>story_beats</template-output>
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 <ask>Describe the pacing and flow of your narrative.
 
@@ -175,7 +194,6 @@ For each protagonist include:
 Your protagonist(s):</ask>
 
 <template-output>protagonists</template-output>
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 
@@ -213,7 +231,6 @@ For each character include:
 Your supporting characters:</ask>
 
 <template-output>supporting_characters</template-output>
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 
@@ -261,7 +278,6 @@ Your world:</ask>
 Your history:</ask>
 
 <template-output>history_backstory</template-output>
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 
@@ -539,19 +555,50 @@ Which would you like?</ask>
 
 </step>
 
-<step n="17" goal="Update status if tracking enabled">
+<step n="17" goal="Update status if tracking enabled" tag="workflow-status">
 
-<check if="tracking_mode == true">
-  <invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
-    <param>mode: update</param>
-    <param>action: complete_workflow</param>
-    <param>workflow_name: narrative</param>
-  </invoke-workflow>
+<check if="standalone_mode != true">
+  <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
+  <action>Find workflow_status key "narrative"</action>
+  <critical>ONLY write the file path as the status value - no other text, notes, or metadata</critical>
+  <action>Update workflow_status["narrative"] = "{output_folder}/bmm-narrative-{{game_name}}-{{date}}.md"</action>
+  <action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
 
-  <check if="success == true">
-    <output>✅ Status updated! Next: {{next_workflow}}</output>
-  </check>
+<action>Find first non-completed workflow in workflow_status (next workflow to do)</action>
+<action>Determine next agent from path file based on next workflow</action>
 </check>
-</step>
+
+<output>**✅ Narrative Design Complete, {user_name}!**
+
+**Narrative Document:**
+
+- Narrative design saved to {output_folder}/bmm-narrative-{{game_name}}-{{date}}.md
+
+{{#if standalone_mode != true}}
+**Status Updated:**
+
+- Progress tracking updated: narrative marked complete
+- Next workflow: {{next_workflow}}
+  {{else}}
+  **Note:** Running in standalone mode (no progress tracking)
+  {{/if}}
+
+**Next Steps:**
+
+{{#if standalone_mode != true}}
+
+- **Next workflow:** {{next_workflow}} ({{next_agent}} agent)
+- **Optional:** Review narrative with writing team or stakeholders
+
+Check status anytime with: `workflow-status`
+{{else}}
+Since no workflow is in progress:
+
+- Review narrative design with team
+- Refer to the BMM workflow guide if unsure what to do next
+- Or run `workflow-init` to create a workflow path and get guided next steps
+  {{/if}}
+  </output>
+  </step>
 
 </workflow>

package/src/modules/{bmm/workflows/2-plan-workflows → bmgd/workflows/2-design}/narrative/workflow.yaml

@@ -4,35 +4,29 @@ description: "Narrative design workflow for story-driven games and applications.
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/bmad/bmm/config.yaml"
+config_source: "{project-root}/{bmad_folder}/bmgd/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"
-user_skill_level: "{config_source}:user_skill_level"
+game_dev_experience: "{config_source}:game_dev_experience"
 date: system-generated
 
 # Workflow components
-installed_path: "{project-root}/bmad/bmm/workflows/2-plan-workflows/narrative"
+installed_path: "{project-root}/{bmad_folder}/bmgd/workflows/2-design/narrative"
 instructions: "{installed_path}/instructions-narrative.md"
 template: "{installed_path}/narrative-template.md"
 
 # Output configuration
 default_output_file: "{output_folder}/narrative-design.md"
 
-# Recommended input documents
-recommended_inputs:
-  - game_brief: "{output_folder}/game-brief.md"
-  - gdd: "{output_folder}/GDD.md"
-  - product_brief: "{output_folder}/product-brief.md"
-
 standalone: true
 
 web_bundle:
   name: "narrative"
   description: "Narrative design workflow for story-driven games and applications. Creates comprehensive narrative documentation including story structure, character arcs, dialogue systems, and narrative implementation guidance."
   author: "BMad"
-  instructions: "bmad/bmm/workflows/2-plan-workflows/narrative/instructions-narrative.md"
+  instructions: "{bmad_folder}/bmgd/workflows/2-design/narrative/instructions-narrative.md"
   web_bundle_files:
-    - "bmad/bmm/workflows/2-plan-workflows/narrative/instructions-narrative.md"
-    - "bmad/bmm/workflows/2-plan-workflows/narrative/narrative-template.md"
+    - "{bmad_folder}/bmgd/workflows/2-design/narrative/instructions-narrative.md"
+    - "{bmad_folder}/bmgd/workflows/2-design/narrative/narrative-template.md"

package/src/modules/bmgd/workflows/3-technical/game-architecture/architecture-patterns.yaml

@@ -0,0 +1,321 @@
+# Architecture Patterns - Common patterns identified from requirements
+
+requirement_patterns:
+  realtime_collaboration:
+    triggers:
+      - "real-time"
+      - "collaborative"
+      - "live updates"
+      - "multi-user"
+      - "simultaneous editing"
+    decisions_needed:
+      - websocket_solution
+      - conflict_resolution
+      - state_synchronization
+      - presence_tracking
+      - optimistic_updates
+    suggested_stack:
+      - "Socket.io or WebSocket native"
+      - "Redis for pub/sub"
+      - "Operational Transforms or CRDTs for conflict resolution"
+      - "PostgreSQL for persistence"
+
+  ecommerce:
+    triggers:
+      - "shopping cart"
+      - "checkout"
+      - "payments"
+      - "inventory"
+      - "product catalog"
+    decisions_needed:
+      - payment_processor
+      - cart_persistence
+      - inventory_management
+      - order_workflow
+      - tax_calculation
+    suggested_stack:
+      - "Stripe or PayPal for payments"
+      - "PostgreSQL for products and orders"
+      - "Redis for cart sessions"
+      - "BullMQ for order processing"
+
+  saas_platform:
+    triggers:
+      - "multi-tenant"
+      - "subscription"
+      - "billing"
+      - "team management"
+      - "roles and permissions"
+    decisions_needed:
+      - tenancy_model
+      - subscription_billing
+      - permission_system
+      - team_collaboration
+      - usage_tracking
+    suggested_stack:
+      - "PostgreSQL with Row Level Security"
+      - "Stripe Billing for subscriptions"
+      - "RBAC or ABAC for permissions"
+      - "NextAuth or Clerk for auth"
+
+  content_platform:
+    triggers:
+      - "CMS"
+      - "blog"
+      - "publishing"
+      - "content management"
+      - "editorial workflow"
+    decisions_needed:
+      - content_storage
+      - rich_text_editor
+      - media_handling
+      - version_control
+      - publishing_workflow
+    suggested_stack:
+      - "PostgreSQL for structured content"
+      - "S3 or Cloudinary for media"
+      - "Tiptap or Slate for rich text"
+      - "Algolia for search"
+
+  data_analytics:
+    triggers:
+      - "dashboards"
+      - "reporting"
+      - "metrics"
+      - "analytics"
+      - "data visualization"
+    decisions_needed:
+      - data_warehouse
+      - etl_pipeline
+      - visualization_library
+      - query_optimization
+      - caching_strategy
+    suggested_stack:
+      - "PostgreSQL or ClickHouse"
+      - "Apache Airflow or Temporal for ETL"
+      - "Chart.js or D3 for visualization"
+      - "Redis for query caching"
+
+  social_platform:
+    triggers:
+      - "social network"
+      - "feed"
+      - "following"
+      - "likes"
+      - "comments"
+    decisions_needed:
+      - graph_relationships
+      - feed_algorithm
+      - notification_system
+      - content_moderation
+      - privacy_controls
+    suggested_stack:
+      - "PostgreSQL with graph extensions or Neo4j"
+      - "Redis for feed caching"
+      - "Elasticsearch for user search"
+      - "WebSockets for notifications"
+
+  marketplace:
+    triggers:
+      - "marketplace"
+      - "vendors"
+      - "buyers and sellers"
+      - "transactions"
+      - "escrow"
+    decisions_needed:
+      - payment_splitting
+      - escrow_handling
+      - vendor_management
+      - dispute_resolution
+      - commission_model
+    suggested_stack:
+      - "Stripe Connect for payments"
+      - "PostgreSQL for transactions"
+      - "BullMQ for async processing"
+      - "S3 for vendor assets"
+
+  streaming_platform:
+    triggers:
+      - "video streaming"
+      - "live streaming"
+      - "media delivery"
+      - "broadcast"
+    decisions_needed:
+      - video_encoding
+      - cdn_strategy
+      - streaming_protocol
+      - bandwidth_optimization
+      - drm_protection
+    suggested_stack:
+      - "AWS MediaConvert or Mux"
+      - "CloudFront or Fastly CDN"
+      - "HLS or DASH protocol"
+      - "S3 for video storage"
+
+  iot_platform:
+    triggers:
+      - "IoT"
+      - "sensors"
+      - "device management"
+      - "telemetry"
+      - "edge computing"
+    decisions_needed:
+      - message_protocol
+      - time_series_database
+      - device_authentication
+      - data_ingestion
+      - edge_processing
+    suggested_stack:
+      - "MQTT or CoAP protocol"
+      - "TimescaleDB or InfluxDB"
+      - "Apache Kafka for ingestion"
+      - "Grafana for monitoring"
+
+  ai_application:
+    triggers:
+      - "machine learning"
+      - "AI features"
+      - "LLM integration"
+      - "computer vision"
+      - "NLP"
+    decisions_needed:
+      - model_serving
+      - vector_database
+      - prompt_management
+      - token_optimization
+      - fallback_strategy
+    suggested_stack:
+      - "OpenAI or Anthropic API"
+      - "Pinecone or pgvector for embeddings"
+      - "Redis for prompt caching"
+      - "Langchain or LlamaIndex"
+
+# Quality attribute patterns
+quality_attributes:
+  high_availability:
+    triggers:
+      - "99.9% uptime"
+      - "high availability"
+      - "fault tolerance"
+      - "disaster recovery"
+    architectural_needs:
+      - load_balancing
+      - database_replication
+      - health_checks
+      - circuit_breakers
+      - graceful_degradation
+
+  high_performance:
+    triggers:
+      - "millisecond response"
+      - "high throughput"
+      - "low latency"
+      - "performance critical"
+    architectural_needs:
+      - caching_layers
+      - database_optimization
+      - cdn_strategy
+      - code_splitting
+      - lazy_loading
+
+  high_security:
+    triggers:
+      - "compliance"
+      - "HIPAA"
+      - "GDPR"
+      - "financial data"
+      - "PCI DSS"
+    architectural_needs:
+      - encryption_at_rest
+      - encryption_in_transit
+      - audit_logging
+      - access_controls
+      - data_isolation
+
+  scalability:
+    triggers:
+      - "millions of users"
+      - "elastic scale"
+      - "global reach"
+      - "viral growth"
+    architectural_needs:
+      - horizontal_scaling
+      - database_sharding
+      - microservices
+      - queue_systems
+      - auto_scaling
+
+# Integration patterns
+integration_requirements:
+  payment_processing:
+    common_choices:
+      - "Stripe - most developer friendly"
+      - "PayPal - widest consumer adoption"
+      - "Square - best for in-person + online"
+    considerations:
+      - transaction_fees
+      - international_support
+      - subscription_handling
+      - marketplace_capabilities
+
+  email_service:
+    common_choices:
+      - "Resend - modern, developer friendly"
+      - "SendGrid - mature, scalable"
+      - "Amazon SES - cost effective at scale"
+      - "Postmark - transactional focus"
+    considerations:
+      - deliverability
+      - template_management
+      - analytics_needs
+      - cost_per_email
+
+  sms_notifications:
+    common_choices:
+      - "Twilio - most comprehensive"
+      - "Amazon SNS - AWS integrated"
+      - "Vonage - competitive pricing"
+    considerations:
+      - international_coverage
+      - delivery_rates
+      - two_way_messaging
+      - cost_per_message
+
+  authentication_providers:
+    social_providers:
+      - "Google - highest adoption"
+      - "GitHub - developer focused"
+      - "Microsoft - enterprise"
+      - "Apple - iOS users"
+    enterprise_providers:
+      - "SAML 2.0"
+      - "OAuth 2.0"
+      - "OpenID Connect"
+      - "Active Directory"
+
+# Decision heuristics
+decision_rules:
+  database_selection:
+    if_requirements_include:
+      - complex_relationships: "PostgreSQL"
+      - flexible_schema: "MongoDB"
+      - time_series: "TimescaleDB"
+      - graph_data: "Neo4j or PostgreSQL with extensions"
+      - key_value: "Redis"
+      - wide_column: "Cassandra"
+
+  api_pattern_selection:
+    if_requirements_include:
+      - simple_crud: "REST"
+      - complex_queries: "GraphQL"
+      - type_safety_critical: "tRPC"
+      - microservices: "gRPC"
+      - public_api: "REST with OpenAPI"
+
+  deployment_selection:
+    if_requirements_include:
+      - nextjs_only: "Vercel"
+      - complex_infrastructure: "AWS"
+      - quick_prototype: "Railway"
+      - global_edge: "Fly.io"
+      - kubernetes_needed: "GCP or AWS EKS"

package/src/modules/bmgd/workflows/3-technical/game-architecture/architecture-template.md

@@ -0,0 +1,103 @@
+# Architecture
+
+## Executive Summary
+
+{{executive_summary}}
+
+{{project_initialization_section}}
+
+## Decision Summary
+
+| Category | Decision | Version | Affects Epics | Rationale |
+| -------- | -------- | ------- | ------------- | --------- |
+
+{{decision_table_rows}}
+
+## Project Structure
+
+```
+{{project_root}}/
+{{source_tree}}
+```
+
+## Epic to Architecture Mapping
+
+{{epic_mapping_table}}
+
+## Technology Stack Details
+
+### Core Technologies
+
+{{core_stack_details}}
+
+### Integration Points
+
+{{integration_details}}
+
+{{novel_pattern_designs_section}}
+
+## Implementation Patterns
+
+These patterns ensure consistent implementation across all AI agents:
+
+{{implementation_patterns}}
+
+## Consistency Rules
+
+### Naming Conventions
+
+{{naming_conventions}}
+
+### Code Organization
+
+{{code_organization_patterns}}
+
+### Error Handling
+
+{{error_handling_approach}}
+
+### Logging Strategy
+
+{{logging_approach}}
+
+## Data Architecture
+
+{{data_models_and_relationships}}
+
+## API Contracts
+
+{{api_specifications}}
+
+## Security Architecture
+
+{{security_approach}}
+
+## Performance Considerations
+
+{{performance_strategies}}
+
+## Deployment Architecture
+
+{{deployment_approach}}
+
+## Development Environment
+
+### Prerequisites
+
+{{development_prerequisites}}
+
+### Setup Commands
+
+```bash
+{{setup_commands}}
+```
+
+## Architecture Decision Records (ADRs)
+
+{{key_architecture_decisions}}
+
+---
+
+_Generated by BMAD Decision Architecture Workflow v1.0_
+_Date: {{date}}_
+_For: {{user_name}}_