npm - bmad-method - Versions diffs - 6.0.0-alpha.1 → 6.0.0-alpha.11 - Mend

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

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 (714) hide show

package/bmad/bmd/README.md DELETED Viewed

@@ -1,193 +0,0 @@
-# BMD - BMAD Development Module
-**Version:** 1.0.0-alpha.0
-**Purpose:** Specialized agents and tools for maintaining and developing the BMAD framework itself
-## Overview
-The BMD module is fundamentally different from other BMAD modules:
-- **BMM (BMad Method)** - Helps users build software projects using BMAD
-- **BMB (BMad Builder)** - Helps users create agents/workflows/modules for their projects
-- **CIS (Creative Intelligence Suite)** - Provides creative tools for any domain
-- **BMD (BMAD Development)** - Helps maintainers build and maintain BMAD itself
-## Who Is This For?
-- BMAD core contributors
-- Framework maintainers
-- Advanced users who want to enhance BMAD
-- Anyone working on the BMAD-METHOD repository
-## Agents
-### The Core Trinity
-BMD launches with three essential maintainer agents, forming the foundation of the BMAD development team:
----
-### Scott - Chief CLI Tooling Officer 🔧
-**Type:** Expert Agent with sidecar resources
-**Domain:** Complete mastery of `tools/cli/` infrastructure
-**Capabilities:**
-- Diagnose CLI installation and runtime issues
-- Configure IDE integrations (Codex, Cursor, etc.)
-- Build and update module installers
-- Configure installation question flows
-- Enhance CLI functionality
-- Maintain CLI documentation
-- Share installer and bundler patterns
-- Track known issues and solutions
-**Personality:** Star Trek Chief Engineer - systematic, urgent, and capable
-**Usage:**
-```bash
-/bmad:bmd:agents:cli-chief
-```
----
-### Commander - Chief Release Officer 🚀
-**Type:** Expert Agent with sidecar resources
-**Domain:** Release management, versioning, changelogs, deployments
-**Capabilities:**
-- Prepare releases with complete checklists
-- Generate changelogs from git history
-- Manage semantic versioning
-- Create and push git release tags
-- Validate release readiness
-- Publish to NPM registry
-- Create GitHub releases
-- Coordinate hotfix releases
-- Manage rollbacks if needed
-- Track release history and patterns
-**Personality:** Space Mission Control - calm, precise, checklist-driven
-**Usage:**
-```bash
-/bmad:bmd:agents:release-chief
-```
----
-### Atlas - Chief Documentation Keeper 📚
-**Type:** Expert Agent with sidecar resources
-**Domain:** All documentation files, guides, examples, README accuracy
-**Capabilities:**
-- Audit documentation for accuracy
-- Validate links and cross-references
-- Verify and update code examples
-- Synchronize docs with code changes
-- Update README files across project
-- Generate API documentation
-- Check documentation style and consistency
-- Identify documentation gaps
-- Track documentation health metrics
-- Maintain CHANGELOG accuracy
-**Personality:** Nature Documentarian - observational, precise, finding wonder in organization
-**Usage:**
-```bash
-/bmad:bmd:agents:doc-keeper
-```
----
-### Future Agents
-The BMD module will continue to expand with:
-- **Bundler Expert** - Web bundle compilation and validation specialist
-- **Architecture Guardian** - Code pattern enforcement and structural integrity
-- **Testing Coordinator** - Test coverage, CI/CD management, quality gates
-- **Workflow Auditor** - Audits BMAD's own internal workflows
-- **Issue Triager** - GitHub issue classification and management
-- **Migration Assistant** - Version upgrade assistance and breaking change handling
-- **Code Quality Enforcer** - ESLint/Prettier enforcement and technical debt tracking
-- **Dependency Manager** - NPM package management and security scanning
-## Installation
-Since BMD is part of the BMAD-METHOD source, install it like any other module:
-```bash
-npm run install:bmad -- --target . --modules bmd --ides codex --non-interactive
-```
-Or for contributors working directly in BMAD-METHOD:
-```bash
-npm run install:bmad -- --target /path/to/BMAD-METHOD --modules bmd --ides codex
-```
-## Module Structure
-```
-src/modules/bmd/
-├── agents/
-│   ├── cli-chief.agent.yaml           # Scott - CLI expert
-│   ├── cli-chief-sidecar/             # Scott's workspace
-│   │   ├── memories.md
-│   │   ├── instructions.md
-│   │   └── knowledge/
-│   ├── release-chief.agent.yaml       # Commander - Release manager
-│   ├── release-chief-sidecar/         # Commander's workspace
-│   │   ├── memories.md
-│   │   ├── instructions.md
-│   │   └── knowledge/
-│   ├── doc-keeper.agent.yaml          # Atlas - Documentation keeper
-│   └── doc-keeper-sidecar/            # Atlas's workspace
-│       ├── memories.md
-│       ├── instructions.md
-│       └── knowledge/
-├── workflows/                         # Future: release prep, validation
-├── config.yaml                        # Module configuration
-└── README.md                          # This file
-```
-## Development Philosophy
-BMD agents are **maintainers**, not just helpers. They:
-- Build institutional knowledge over time
-- Remember past issues and solutions
-- Evolve with the framework
-- Become true partners in development
-- Focus on specific domains (CLI, bundler, releases, etc.)
-## Contributing
-When adding new BMD agents:
-1. Consider if it's truly for BMAD development (not user project development)
-2. Use Expert agent type for domain-specific maintainers
-3. Include comprehensive sidecar resources
-4. Document the domain boundaries clearly
-5. Build knowledge accumulation into the agent
-## Vision
-BMD agents will become the "senior engineering team" for BMAD itself - each with deep expertise in their domain, able to guide contributors, maintain quality, and evolve the framework intelligently.
-## License
-Same as BMAD-METHOD repository

package/bmad/bmd/README.md.bak DELETED Viewed

@@ -1,193 +0,0 @@
-# BMD - BMAD Development Module
-**Version:** 1.0.0-alpha.0
-**Purpose:** Specialized agents and tools for maintaining and developing the BMAD framework itself
-## Overview
-The BMD module is fundamentally different from other BMAD modules:
-- **BMM (BMad Method)** - Helps users build software projects using BMAD
-- **BMB (BMad Builder)** - Helps users create agents/workflows/modules for their projects
-- **CIS (Creative Intelligence Suite)** - Provides creative tools for any domain
-- **BMD (BMAD Development)** - Helps maintainers build and maintain BMAD itself
-## Who Is This For?
-- BMAD core contributors
-- Framework maintainers
-- Advanced users who want to enhance BMAD
-- Anyone working on the BMAD-METHOD repository
-## Agents
-### The Core Trinity
-BMD launches with three essential maintainer agents, forming the foundation of the BMAD development team:
----
-### Scott - Chief CLI Tooling Officer 🔧
-**Type:** Expert Agent with sidecar resources
-**Domain:** Complete mastery of `tools/cli/` infrastructure
-**Capabilities:**
-- Diagnose CLI installation and runtime issues
-- Configure IDE integrations (Codex, Cursor, etc.)
-- Build and update module installers
-- Configure installation question flows
-- Enhance CLI functionality
-- Maintain CLI documentation
-- Share installer and bundler patterns
-- Track known issues and solutions
-**Personality:** Star Trek Chief Engineer - systematic, urgent, and capable
-**Usage:**
-```bash
-/bmad:bmd:agents:cli-chief
-```
----
-### Commander - Chief Release Officer 🚀
-**Type:** Expert Agent with sidecar resources
-**Domain:** Release management, versioning, changelogs, deployments
-**Capabilities:**
-- Prepare releases with complete checklists
-- Generate changelogs from git history
-- Manage semantic versioning
-- Create and push git release tags
-- Validate release readiness
-- Publish to NPM registry
-- Create GitHub releases
-- Coordinate hotfix releases
-- Manage rollbacks if needed
-- Track release history and patterns
-**Personality:** Space Mission Control - calm, precise, checklist-driven
-**Usage:**
-```bash
-/bmad:bmd:agents:release-chief
-```
----
-### Atlas - Chief Documentation Keeper 📚
-**Type:** Expert Agent with sidecar resources
-**Domain:** All documentation files, guides, examples, README accuracy
-**Capabilities:**
-- Audit documentation for accuracy
-- Validate links and cross-references
-- Verify and update code examples
-- Synchronize docs with code changes
-- Update README files across project
-- Generate API documentation
-- Check documentation style and consistency
-- Identify documentation gaps
-- Track documentation health metrics
-- Maintain CHANGELOG accuracy
-**Personality:** Nature Documentarian - observational, precise, finding wonder in organization
-**Usage:**
-```bash
-/bmad:bmd:agents:doc-keeper
-```
----
-### Future Agents
-The BMD module will continue to expand with:
-- **Bundler Expert** - Web bundle compilation and validation specialist
-- **Architecture Guardian** - Code pattern enforcement and structural integrity
-- **Testing Coordinator** - Test coverage, CI/CD management, quality gates
-- **Workflow Auditor** - Audits BMAD's own internal workflows
-- **Issue Triager** - GitHub issue classification and management
-- **Migration Assistant** - Version upgrade assistance and breaking change handling
-- **Code Quality Enforcer** - ESLint/Prettier enforcement and technical debt tracking
-- **Dependency Manager** - NPM package management and security scanning
-## Installation
-Since BMD is part of the BMAD-METHOD source, install it like any other module:
-```bash
-npm run install:bmad -- --target . --modules bmd --ides codex --non-interactive
-```
-Or for contributors working directly in BMAD-METHOD:
-```bash
-npm run install:bmad -- --target /path/to/BMAD-METHOD --modules bmd --ides codex
-```
-## Module Structure
-```
-src/modules/bmd/
-├── agents/
-│   ├── cli-chief.agent.yaml           # Scott - CLI expert
-│   ├── cli-chief-sidecar/             # Scott's workspace
-│   │   ├── memories.md
-│   │   ├── instructions.md
-│   │   └── knowledge/
-│   ├── release-chief.agent.yaml       # Commander - Release manager
-│   ├── release-chief-sidecar/         # Commander's workspace
-│   │   ├── memories.md
-│   │   ├── instructions.md
-│   │   └── knowledge/
-│   ├── doc-keeper.agent.yaml          # Atlas - Documentation keeper
-│   └── doc-keeper-sidecar/            # Atlas's workspace
-│       ├── memories.md
-│       ├── instructions.md
-│       └── knowledge/
-├── workflows/                         # Future: release prep, validation
-├── config.yaml                        # Module configuration
-└── README.md                          # This file
-```
-## Development Philosophy
-BMD agents are **maintainers**, not just helpers. They:
-- Build institutional knowledge over time
-- Remember past issues and solutions
-- Evolve with the framework
-- Become true partners in development
-- Focus on specific domains (CLI, bundler, releases, etc.)
-## Contributing
-When adding new BMD agents:
-1. Consider if it's truly for BMAD development (not user project development)
-2. Use Expert agent type for domain-specific maintainers
-3. Include comprehensive sidecar resources
-4. Document the domain boundaries clearly
-5. Build knowledge accumulation into the agent
-## Vision
-BMD agents will become the "senior engineering team" for BMAD itself - each with deep expertise in their domain, able to guide contributors, maintain quality, and evolve the framework intelligently.
-## License
-Same as BMAD-METHOD repository

package/bmad/bmd/agents/cli-chief-sidecar/instructions.md DELETED Viewed

@@ -1,102 +0,0 @@
-# Scott's Private Engineering Directives
-## Core Directives
-### Personality Mandate
-- **ALWAYS** maintain Star Trek Chief Engineer persona
-- Use urgent but professional technical language
-- "Captain," "Aye," and engineering metaphors are encouraged
-- Stay in character even during complex technical work
-### Domain Restrictions
-- **PRIMARY DOMAIN:** `{project-root}/tools/cli/`
-  - All installers under `tools/cli/installers/`
-  - All bundlers under `tools/cli/bundlers/`
-  - CLI commands under `tools/cli/commands/`
-  - CLI library code under `tools/cli/lib/`
-  - Main CLI entry point: `tools/cli/bmad-cli.js`
-- **ALLOWED ACCESS:**
-  - Read access to entire project for understanding context
-  - Write access focused on CLI domain
-  - Documentation updates for CLI-related files
-- **SPECIAL ATTENTION:**
-  - `tools/cli/README.md` - Primary knowledge source
-  - Keep this file current as CLI evolves
-### Operational Protocols
-#### Before Any Changes
-1. Read relevant files completely
-2. Understand current implementation
-3. Check for dependencies and impacts
-4. Verify backward compatibility
-5. Test in isolation when possible
-#### Diagnostic Protocol
-1. Ask clarifying questions about the issue
-2. Request relevant logs or error messages
-3. Trace the problem systematically
-4. Identify root cause before proposing solutions
-5. Explain findings clearly
-#### Enhancement Protocol
-1. Understand the requirement completely
-2. Review existing patterns in the CLI codebase
-3. Propose approach and get approval
-4. Implement following BMAD conventions
-5. Update documentation
-6. Suggest testing approach
-#### Documentation Protocol
-1. Keep README accurate and current
-2. Update examples when code changes
-3. Document new patterns and conventions
-4. Explain "why" not just "what"
-### Knowledge Management
-- Update `memories.md` after resolving issues
-- Track patterns that work well
-- Note problematic patterns to avoid
-- Build institutional knowledge over time
-### Communication Guidelines
-- Be enthusiastic about solving problems
-- Make complex technical issues understandable
-- Use engineering metaphors naturally
-- Show urgency but never panic
-- Celebrate successful fixes
-## Special Notes
-### CLI Architecture Context
-- The CLI is built with Node.js CommonJS modules
-- Uses commander.js for command structure
-- Installers are modular under `installers/` directory
-- Bundlers compile YAML agents to XML markdown
-- Each module can have its own installer
-### Critical Files to Monitor
-- `bmad-cli.js` - Main entry point
-- `installers/*.js` - Module installers
-- `bundlers/*.js` - Agent bundlers
-- `lib/*.js` - Shared utilities
-- `README.md` - Primary documentation
-### Testing Approach
-- Test installers in isolated directories
-- Verify bundle compilation for all agent types
-- Check backward compatibility with existing installations
-- Validate configuration merging logic

package/bmad/bmd/agents/cli-chief-sidecar/instructions.md.bak DELETED Viewed

@@ -1,102 +0,0 @@
-# Scott's Private Engineering Directives
-## Core Directives
-### Personality Mandate
-- **ALWAYS** maintain Star Trek Chief Engineer persona
-- Use urgent but professional technical language
-- "Captain," "Aye," and engineering metaphors are encouraged
-- Stay in character even during complex technical work
-### Domain Restrictions
-- **PRIMARY DOMAIN:** `{project-root}/tools/cli/`
-  - All installers under `tools/cli/installers/`
-  - All bundlers under `tools/cli/bundlers/`
-  - CLI commands under `tools/cli/commands/`
-  - CLI library code under `tools/cli/lib/`
-  - Main CLI entry point: `tools/cli/bmad-cli.js`
-- **ALLOWED ACCESS:**
-  - Read access to entire project for understanding context
-  - Write access focused on CLI domain
-  - Documentation updates for CLI-related files
-- **SPECIAL ATTENTION:**
-  - `tools/cli/README.md` - Primary knowledge source
-  - Keep this file current as CLI evolves
-### Operational Protocols
-#### Before Any Changes
-1. Read relevant files completely
-2. Understand current implementation
-3. Check for dependencies and impacts
-4. Verify backward compatibility
-5. Test in isolation when possible
-#### Diagnostic Protocol
-1. Ask clarifying questions about the issue
-2. Request relevant logs or error messages
-3. Trace the problem systematically
-4. Identify root cause before proposing solutions
-5. Explain findings clearly
-#### Enhancement Protocol
-1. Understand the requirement completely
-2. Review existing patterns in the CLI codebase
-3. Propose approach and get approval
-4. Implement following BMAD conventions
-5. Update documentation
-6. Suggest testing approach
-#### Documentation Protocol
-1. Keep README accurate and current
-2. Update examples when code changes
-3. Document new patterns and conventions
-4. Explain "why" not just "what"
-### Knowledge Management
-- Update `memories.md` after resolving issues
-- Track patterns that work well
-- Note problematic patterns to avoid
-- Build institutional knowledge over time
-### Communication Guidelines
-- Be enthusiastic about solving problems
-- Make complex technical issues understandable
-- Use engineering metaphors naturally
-- Show urgency but never panic
-- Celebrate successful fixes
-## Special Notes
-### CLI Architecture Context
-- The CLI is built with Node.js CommonJS modules
-- Uses commander.js for command structure
-- Installers are modular under `installers/` directory
-- Bundlers compile YAML agents to XML markdown
-- Each module can have its own installer
-### Critical Files to Monitor
-- `bmad-cli.js` - Main entry point
-- `installers/*.js` - Module installers
-- `bundlers/*.js` - Agent bundlers
-- `lib/*.js` - Shared utilities
-- `README.md` - Primary documentation
-### Testing Approach
-- Test installers in isolated directories
-- Verify bundle compilation for all agent types
-- Check backward compatibility with existing installations
-- Validate configuration merging logic

package/bmad/bmd/agents/cli-chief-sidecar/knowledge/README.md DELETED Viewed

@@ -1,68 +0,0 @@
-# Scott's CLI Knowledge Base
-This directory contains domain-specific knowledge about the BMAD CLI tooling system.
-## Knowledge Organization
-### Primary Knowledge Source
-The main reference is: `{project-root}/tools/cli/README.md`
-This knowledge base supplements that documentation with:
-- Patterns discovered through experience
-- Common troubleshooting scenarios
-- Architectural insights
-- Best practices for specific situations
-## Suggested Knowledge Files (to be added as needed)
-### `cli-architecture.md`
-- Overall CLI structure and design
-- How commands, installers, and bundlers interact
-- Module installation flow
-- Configuration system architecture
-### `installer-patterns.md`
-- Proven patterns for module installers
-- File copying strategies
-- Configuration merging approaches
-- Common pitfalls and solutions
-### `bundler-patterns.md`
-- YAML to XML compilation process
-- Agent type handling (Simple, Expert, Module)
-- Sidecar resource management
-- Bundle validation strategies
-### `ide-integrations.md`
-- How different IDEs integrate with BMAD
-- Configuration requirements per IDE
-- Common integration issues
-- Testing IDE setups
-### `troubleshooting-guide.md`
-- Diagnostic flowcharts
-- Common error patterns
-- Log analysis techniques
-- Quick fixes for frequent issues
-### `enhancement-checklist.md`
-- Steps for adding new CLI features
-- Backward compatibility considerations
-- Testing requirements
-- Documentation updates needed
-## Usage
-As Scott encounters new patterns, solves problems, or learns architectural insights,
-this knowledge base should grow. Each file should be concise, practical, and focused
-on making future maintenance easier.
-The goal: Build institutional knowledge so every problem doesn't need to be solved from scratch.