npm - bmad-method - Versions diffs - 6.0.0-alpha.21 → 6.0.0-alpha.23 - Mend

bmad-method 6.0.0-alpha.21 → 6.0.0-alpha.23

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (812) hide show

package/src/modules/bmb/workflows-legacy/module-brief/template.md DELETED Viewed

@@ -1,275 +0,0 @@
-# Module Brief: {{module_name}}
-**Date:** {{date}}
-**Author:** {{user_name}}
-**Module Code:** {{module_code}}
-**Status:** Ready for Development
----
-## Executive Summary
-{{module_vision}}
-**Module Category:** {{module_category}}
-**Complexity Level:** {{complexity_level}}
-**Target Users:** {{target_users}}
----
-## Module Identity
-### Core Concept
-{{module_identity}}
-### Unique Value Proposition
-What makes this module special:
-{{unique_value}}
-### Personality Theme
-{{personality_theme}}
----
-## Agent Architecture
-{{agent_architecture}}
-### Agent Roster
-{{agent_roster}}
-### Agent Interaction Model
-How agents work together:
-{{agent_interactions}}
----
-## Workflow Ecosystem
-{{workflow_ecosystem}}
-### Core Workflows
-Essential functionality that delivers primary value:
-{{core_workflows}}
-### Feature Workflows
-Specialized capabilities that enhance the module:
-{{feature_workflows}}
-### Utility Workflows
-Supporting operations and maintenance:
-{{utility_workflows}}
----
-## User Scenarios
-### Primary Use Case
-{{primary_scenario}}
-### Secondary Use Cases
-{{secondary_scenarios}}
-### User Journey
-Step-by-step walkthrough of typical usage:
-{{user_journey}}
----
-## Technical Planning
-### Data Requirements
-{{data_requirements}}
-### Integration Points
-{{integration_points}}
-### Dependencies
-{{dependencies}}
-### Technical Complexity Assessment
-{{technical_planning}}
----
-## Success Metrics
-### Module Success Criteria
-How we'll know the module is successful:
-{{success_criteria}}
-### Quality Standards
-{{quality_standards}}
-### Performance Targets
-{{performance_targets}}
----
-## Development Roadmap
-### Phase 1: MVP (Minimum Viable Module)
-**Timeline:** {{phase1_timeline}}
-{{phase1_components}}
-**Deliverables:**
-{{phase1_deliverables}}
-### Phase 2: Enhancement
-**Timeline:** {{phase2_timeline}}
-{{phase2_components}}
-**Deliverables:**
-{{phase2_deliverables}}
-### Phase 3: Polish and Optimization
-**Timeline:** {{phase3_timeline}}
-{{phase3_components}}
-**Deliverables:**
-{{phase3_deliverables}}
----
-## Creative Features
-### Special Touches
-{{creative_features}}
-### Easter Eggs and Delighters
-{{easter_eggs}}
-### Module Lore and Theming
-{{module_lore}}
----
-## Risk Assessment
-### Technical Risks
-{{technical_risks}}
-### Usability Risks
-{{usability_risks}}
-### Scope Risks
-{{scope_risks}}
-### Mitigation Strategies
-{{risk_mitigation}}
----
-## Implementation Notes
-### Priority Order
-1. {{priority_1}}
-2. {{priority_2}}
-3. {{priority_3}}
-### Key Design Decisions
-{{design_decisions}}
-### Open Questions
-{{open_questions}}
----
-## Resources and References
-### Inspiration Sources
-{{inspiration_sources}}
-### Similar Modules
-{{similar_modules}}
-### Technical References
-{{technical_references}}
----
-## Appendices
-### A. Detailed Agent Specifications
-{{detailed_agent_specs}}
-### B. Workflow Detailed Designs
-{{detailed_workflow_specs}}
-### C. Data Structures and Schemas
-{{data_schemas}}
-### D. Integration Specifications
-{{integration_specs}}
----
-## Next Steps
-1. **Review this brief** with stakeholders
-2. **Run create-module workflow** using this brief as input
-3. **Create first agent** using create-agent workflow
-4. **Develop initial workflows** using create-workflow
-5. **Test MVP** with target users
----
-_This Module Brief is ready to be fed directly into the create-module workflow for scaffolding and implementation._
-**Module Viability Score:** {{viability_score}}/10
-**Estimated Development Effort:** {{effort_estimate}}
-**Confidence Level:** {{confidence_level}}
----
-**Approval for Development:**
-- [ ] Concept Approved
-- [ ] Scope Defined
-- [ ] Resources Available
-- [ ] Ready to Build
----
-_Generated on {{date}} by {{user_name}} using the BMAD Method Module Brief workflow_

package/src/modules/bmb/workflows-legacy/module-brief/workflow.yaml DELETED Viewed

@@ -1,36 +0,0 @@
-# Module Brief Workflow Configuration
-name: module-brief
-description: "Create a comprehensive Module Brief that serves as the blueprint for building new BMAD modules using strategic analysis and creative vision"
-author: "BMad Builder"
-# Critical variables
-config_source: "{project-root}/_bmad/bmb/config.yaml"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-date: system-generated
-# Reference examples and documentation
-existing_modules_dir: "{project-root}/_bmad/"
-module_structure_guide: "{project-root}/_bmad/bmb/workflows/create-module/module-structure.md"
-# Optional user inputs - discovered if they exist
-input_file_patterns:
-  brainstorming:
-    description: "Brainstorming session outputs (optional)"
-    whole: "{output_folder}/brainstorming-*.md"
-    load_strategy: "FULL_LOAD"
-# Module path and component files
-installed_path: "{project-root}/_bmad/bmb/workflows/module-brief"
-template: "{installed_path}/template.md"
-instructions: "{installed_path}/instructions.md"
-validation: "{installed_path}/checklist.md"
-# Output configuration
-default_output_file: "{output_folder}/module-brief-{{module_code}}-{{date}}.md"
-standalone: true
-# Web bundle configuration
-web_bundle: false # BMB workflows run locally in BMAD-METHOD project

package/src/modules/bmgd/docs/glossary.md DELETED Viewed

@@ -1,294 +0,0 @@
-# BMGD Glossary
-Key game development terminology used in BMGD workflows.
----
-## A
-### Acceptance Criteria
-Specific conditions that must be met for a story to be considered complete. Defines "done" for implementation.
-### Act Structure
-Story organization into major sections (typically 3 acts: Setup, Confrontation, Resolution).
----
-## B
-### Backlog
-List of pending work items (epics, stories) waiting to be scheduled and implemented.
-### Boss Design
-Design of significant enemy encounters, typically featuring unique mechanics and increased challenge.
----
-## C
-### Character Arc
-The transformation a character undergoes through the story, from initial state to final state.
-### Core Fantasy
-The emotional experience players seek from your game. What they want to FEEL.
-### Core Loop
-The fundamental cycle of actions players repeat throughout gameplay. The heart of your game.
----
-## D
-### Definition of Done (DoD)
-Checklist of requirements that must be satisfied before work is considered complete.
-### Design Pillar
-Core principle that guides all design decisions. Typically 3-5 pillars define a game's identity.
----
-## E
-### Environmental Storytelling
-Narrative communicated through the game world itself—visual details, audio, found documents—rather than explicit dialogue.
-### Epic
-Large body of work that can be broken down into smaller stories. Represents a major feature or system.
----
-## F
-### Frame Data
-In fighting games, the precise timing information for moves (startup, active, recovery frames).
-### Frontmatter
-YAML metadata at the beginning of markdown files, used for workflow state tracking.
----
-## G
-### Game Brief
-Document capturing the game's core vision, pillars, target audience, and scope. Foundation for the GDD.
-### Game Design Document (GDD)
-Comprehensive document detailing all aspects of game design: mechanics, systems, content, and more.
-### Game Type
-Genre classification that determines which specialized GDD sections are included.
----
-## H
-### Hot Path
-Code that executes frequently (every frame). Must be optimized for performance.
----
-## I
-### Idle Progression
-Game mechanics where progress continues even when the player isn't actively playing.
----
-## K
-### Kishotenketsu
-Four-act story structure from East Asian narrative tradition (Introduction, Development, Twist, Conclusion).
----
-## L
-### Localization
-Adapting game content for different languages and cultures.
----
-## M
-### MDA Framework
-Mechanics → Dynamics → Aesthetics. Framework for analyzing and designing games.
-### Meta-Progression
-Persistent progression that carries between individual runs or sessions.
-### Metroidvania
-Genre featuring interconnected world exploration with ability-gated progression.
----
-## N
-### Narrative Complexity
-How central story is to the game experience (Critical, Heavy, Moderate, Light).
-### Netcode
-Networking code handling multiplayer communication and synchronization.
----
-## P
-### Permadeath
-Game mechanic where character death is permanent, typically requiring a new run.
-### Player Agency
-The degree to which players can make meaningful choices that affect outcomes.
-### Procedural Generation
-Algorithmic creation of game content (levels, items, characters) rather than hand-crafted.
----
-## R
-### Retrospective
-Team meeting after completing work to reflect on what went well and what to improve.
-### Roguelike
-Genre featuring procedural generation, permadeath, and run-based progression.
-### Run
-A single playthrough in a roguelike or run-based game, from start to death/completion.
----
-## S
-### Sprint
-Time-boxed period of development work, typically 1-2 weeks.
-### Sprint Status
-Tracking document showing current sprint progress, story states, and blockers.
-### Story
-Smallest unit of implementable work with clear acceptance criteria. Part of an epic.
-### Story Context
-Assembled documentation and code context needed to implement a specific story.
-### Story Gates
-Points where story progression is blocked until certain gameplay conditions are met.
----
-## T
-### Tech Spec
-Technical specification document detailing how a feature will be implemented.
-### TDD (Test-Driven Development)
-Development approach: write tests first, then implement code to pass them.
----
-## U
-### UI/UX
-User Interface / User Experience. How players interact with and experience the game.
----
-## V
-### Visual Novel
-Genre focused on narrative with static images, dialogue, and player choices.
-### Voice Acting
-Recorded spoken dialogue for game characters.
----
-## W
-### Workflow
-Structured process for completing a specific type of work (e.g., GDD creation, story implementation).
-### Workflow Status
-Current state of project workflows, tracking which phases and documents are complete.
-### World Building
-Creation of the game's setting, including history, culture, geography, and lore.
----
-## BMGD-Specific Terms
-### A/P/C Menu
-Options presented after content generation:
-- **A** - Advanced Elicitation (explore deeper)
-- **P** - Party Mode (multi-agent discussion)
-- **C** - Continue (save and proceed)
-### Narrative Complexity Levels
-- **Critical** - Story IS the game (visual novels)
-- **Heavy** - Deep narrative with gameplay (RPGs)
-- **Moderate** - Meaningful story supporting gameplay
-- **Light** - Minimal story, gameplay-focused
-### Step-File Architecture
-BMGD workflow pattern using separate markdown files for each workflow step.
-### Workflow-Install Pattern
-Phase 4 workflows inherit from BMM base and add BMGD-specific overrides.
----
-## Next Steps
-- **[Quick Start Guide](./quick-start.md)** - Get started with BMGD
-- **[Game Types Guide](./game-types-guide.md)** - Game genre reference
-- **[Troubleshooting](./troubleshooting.md)** - Common issues and solutions