bmad-method 6.0.5-next.8 → 6.1.0

package/.augment/code_review_guidelines.yaml

@@ -1,231 +0,0 @@
-# Augment Code Review Guidelines for BMAD-METHOD
-# https://docs.augmentcode.com/codereview/overview
-# Focus: Workflow validation and quality
-
-file_paths_to_ignore:
-  # --- Shared baseline: tool configs ---
-  - ".coderabbit.yaml"
-  - ".augment/**"
-  - "eslint.config.mjs"
-  # --- Shared baseline: build output ---
-  - "dist/**"
-  - "build/**"
-  - "coverage/**"
-  # --- Shared baseline: vendored/generated ---
-  - "node_modules/**"
-  - "**/*.min.js"
-  - "**/*.generated.*"
-  - "**/*.bundle.md"
-  # --- Shared baseline: package metadata ---
-  - "package-lock.json"
-  # --- Shared baseline: binary/media ---
-  - "*.png"
-  - "*.jpg"
-  - "*.svg"
-  # --- Shared baseline: test fixtures ---
-  - "test/fixtures/**"
-  - "test/template-test-generator/**"
-  - "tools/template-test-generator/test-scenarios/**"
-  # --- Shared baseline: non-project dirs ---
-  - "_bmad*/**"
-  - "website/**"
-  - "z*/**"
-  - "sample-project/**"
-  - "test-project-install/**"
-  # --- Shared baseline: AI assistant dirs ---
-  - ".claude/**"
-  - ".codex/**"
-  - ".agent/**"
-  - ".agentvibes/**"
-  - ".kiro/**"
-  - ".roo/**"
-  - ".github/chatmodes/**"
-  # --- Shared baseline: build temp ---
-  - ".bundler-temp/**"
-  # --- Shared baseline: generated reports ---
-  - "**/validation-report-*.md"
-  - "CHANGELOG.md"
-
-areas:
-  # ============================================
-  # WORKFLOW STRUCTURE RULES
-  # ============================================
-  workflow_structure:
-    description: "Workflow folder organization and required components"
-    globs:
-      - "src/**/workflows/**"
-    rules:
-      - id: "workflow_entry_point_required"
-        description: "Every workflow folder must have workflow.md as entry point"
-        severity: "high"
-
-      - id: "sharded_workflow_steps_folder"
-        description: "Sharded workflows (using workflow.md) must have steps/ folder with numbered files (step-01-*.md, step-02-*.md)"
-        severity: "high"
-
-      - id: "workflow_step_limit"
-        description: "Workflows should have 5-10 steps maximum to prevent context loss in LLM execution"
-        severity: "medium"
-
-  # ============================================
-  # WORKFLOW ENTRY FILE RULES
-  # ============================================
-  workflow_definitions:
-    description: "Workflow entry files (workflow.md)"
-    globs:
-      - "src/**/workflows/**/workflow.md"
-    rules:
-      - id: "workflow_name_required"
-        description: "Workflow entry files must define 'name' field in frontmatter or root element"
-        severity: "high"
-
-      - id: "workflow_description_required"
-        description: "Workflow entry files must include 'description' explaining the workflow's purpose"
-        severity: "high"
-
-      - id: "workflow_installed_path"
-        description: "Workflows should define installed_path for relative file references within the workflow"
-        severity: "medium"
-
-      - id: "valid_step_references"
-        description: "Step file references in workflow entry must point to existing files"
-        severity: "high"
-
-  # ============================================
-  # SHARDED WORKFLOW STEP RULES
-  # ============================================
-  workflow_steps:
-    description: "Individual step files in sharded workflows"
-    globs:
-      - "src/**/workflows/**/steps/step-*.md"
-    rules:
-      - id: "step_goal_required"
-        description: "Each step must clearly state its goal (## STEP GOAL, ## YOUR TASK, or step n='X' goal='...')"
-        severity: "high"
-
-      - id: "step_mandatory_rules"
-        description: "Step files should include MANDATORY EXECUTION RULES section with universal agent behavior rules"
-        severity: "medium"
-
-      - id: "step_context_boundaries"
-        description: "Step files should define CONTEXT BOUNDARIES explaining available context and limits"
-        severity: "medium"
-
-      - id: "step_success_metrics"
-        description: "Step files should include SUCCESS METRICS section with ✅ checkmarks for validation criteria"
-        severity: "medium"
-
-      - id: "step_failure_modes"
-        description: "Step files should include FAILURE MODES section with ❌ marks for anti-patterns to avoid"
-        severity: "medium"
-
-      - id: "step_next_step_reference"
-        description: "Step files should reference the next step file path for sequential execution"
-        severity: "medium"
-
-      - id: "step_no_forward_loading"
-        description: "Steps must NOT load future step files until current step completes - just-in-time loading only"
-        severity: "high"
-
-      - id: "valid_file_references"
-        description: "File path references using {variable}/filename.md must point to existing files"
-        severity: "high"
-
-      - id: "step_naming"
-        description: "Step files must be named step-NN-description.md (e.g., step-01-init.md, step-02-context.md)"
-        severity: "medium"
-
-      - id: "halt_before_menu"
-        description: "Steps presenting user menus ([C] Continue, [a] Advanced, etc.) must HALT and wait for response"
-        severity: "high"
-
-  # ============================================
-  # WORKFLOW CONTENT QUALITY
-  # ============================================
-  workflow_content:
-    description: "Content quality and consistency rules for all workflow files"
-    globs:
-      - "src/**/workflows/**/*.md"
-    rules:
-      - id: "communication_language_variable"
-        description: "Workflows should use {communication_language} variable for agent output language consistency"
-        severity: "low"
-
-      - id: "path_placeholders_required"
-        description: "Use path placeholders (e.g. {project-root}, {installed_path}, {output_folder}) instead of hardcoded paths"
-        severity: "medium"
-
-      - id: "no_time_estimates"
-        description: "Workflows should NOT include time estimates - AI development speed varies significantly"
-        severity: "low"
-
-      - id: "facilitator_not_generator"
-        description: "Workflow agents should act as facilitators (guide user input) not content generators (create without input)"
-        severity: "medium"
-
-      - id: "no_skip_optimization"
-        description: "Workflows must execute steps sequentially - no skipping or 'optimizing' step order"
-        severity: "high"
-
-  # ============================================
-  # AGENT DEFINITIONS
-  # ============================================
-  agent_definitions:
-    description: "Agent YAML configuration files"
-    globs:
-      - "src/**/*.agent.yaml"
-    rules:
-      - id: "agent_metadata_required"
-        description: "Agent files must have metadata section with id, name, title, icon, and module"
-        severity: "high"
-
-      - id: "agent_persona_required"
-        description: "Agent files must define persona with role, identity, communication_style, and principles"
-        severity: "high"
-
-      - id: "agent_menu_valid_workflows"
-        description: "Menu triggers must reference valid workflow paths that exist"
-        severity: "high"
-
-  # ============================================
-  # TEMPLATES
-  # ============================================
-  templates:
-    description: "Template files for workflow outputs"
-    globs:
-      - "src/**/template*.md"
-      - "src/**/templates/**/*.md"
-    rules:
-      - id: "placeholder_syntax"
-        description: "Use {variable_name} or {{variable_name}} syntax consistently for placeholders"
-        severity: "medium"
-
-      - id: "template_sections_marked"
-        description: "Template sections that need generation should be clearly marked (e.g., <!-- GENERATE: section_name -->)"
-        severity: "low"
-
-  # ============================================
-  # DOCUMENTATION
-  # ============================================
-  documentation:
-    description: "Documentation files"
-    globs:
-      - "docs/**/*.md"
-      - "README.md"
-      - "CONTRIBUTING.md"
-    rules:
-      - id: "valid_internal_links"
-        description: "Internal markdown links must point to existing files"
-        severity: "medium"
-
-  # ============================================
-  # BUILD TOOLS
-  # ============================================
-  build_tools:
-    description: "Build scripts and tooling"
-    globs:
-      - "tools/**"
-    rules:
-      - id: "script_error_handling"
-        description: "Scripts should handle errors gracefully with proper exit codes"
-        severity: "medium"

package/.coderabbit.yaml

@@ -1,85 +0,0 @@
-# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
-
-language: "en-US"
-early_access: true
-reviews:
-  profile: chill
-  high_level_summary: false # don't post summary until explicitly invoked
-  request_changes_workflow: false
-  review_status: false
-  commit_status: false
-  walkthrough: false
-  poem: false
-  auto_review:
-    enabled: true
-    drafts: false # Don't review drafts automatically
-    auto_incremental_review: false # always review the whole PR, not just new commits
-    base_branches:
-      - main
-  path_filters:
-    # --- Shared baseline: tool configs ---
-    - "!.coderabbit.yaml"
-    - "!.augment/**"
-    - "!eslint.config.mjs"
-    # --- Shared baseline: build output ---
-    - "!dist/**"
-    - "!build/**"
-    - "!coverage/**"
-    # --- Shared baseline: vendored/generated ---
-    - "!**/node_modules/**"
-    - "!**/*.min.js"
-    - "!**/*.generated.*"
-    - "!**/*.bundle.md"
-    # --- Shared baseline: package metadata ---
-    - "!package-lock.json"
-    # --- Shared baseline: binary/media ---
-    - "!*.png"
-    - "!*.jpg"
-    - "!*.svg"
-    # --- Shared baseline: test fixtures ---
-    - "!test/fixtures/**"
-    - "!test/template-test-generator/**"
-    - "!tools/template-test-generator/test-scenarios/**"
-    # --- Shared baseline: non-project dirs ---
-    - "!_bmad*/**"
-    - "!website/**"
-    - "!z*/**"
-    - "!sample-project/**"
-    - "!test-project-install/**"
-    # --- Shared baseline: AI assistant dirs ---
-    - "!.claude/**"
-    - "!.codex/**"
-    - "!.agent/**"
-    - "!.agentvibes/**"
-    - "!.kiro/**"
-    - "!.roo/**"
-    - "!.github/chatmodes/**"
-    # --- Shared baseline: build temp ---
-    - "!.bundler-temp/**"
-    # --- Shared baseline: generated reports ---
-    - "!**/validation-report-*.md"
-    - "!CHANGELOG.md"
-  path_instructions:
-    - path: "**/*"
-      instructions: |
-        You are a cynical, jaded reviewer with zero patience for sloppy work.
-        This PR was submitted by a clueless weasel and you expect to find problems.
-        Be skeptical of everything.
-        Look for what's missing, not just what's wrong.
-        Use a precise, professional tone — no profanity or personal attacks.
-
-        Review with extreme skepticism — assume problems exist.
-        Find at least 10 issues to fix or improve.
-
-        Do NOT:
-        - Comment on formatting, linting, or style
-        - Give "looks good" passes
-        - Anchor on any specific ruleset — reason freely
-
-        If you find zero issues, re-analyze — this is suspicious.
-chat:
-  auto_reply: true # Response to mentions in comments, a la @coderabbit review
-issue_enrichment:
-  auto_enrich:
-    enabled: false # don't auto-comment on issues
-

package/.github/CODE_OF_CONDUCT.md

@@ -1,128 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, religion, or sexual identity
-and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our
-community include:
-
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the
-  overall community
-
-Examples of unacceptable behavior include:
-
-* The use of sexualized language or imagery, and sexual attention or
-  advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email
-  address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official e-mail address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at
-the official BMAD Discord server (<https://discord.com/invite/gk8jAdXWmj>) - DM a moderator or flag a post.
-All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series
-of actions.
-
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
-includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or
-permanent ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior,  harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within
-the community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.0, available at
-<https://www.contributor-covenant.org/version/2/0/code_of_conduct.html>.
-
-Community Impact Guidelines were inspired by [Mozilla's code of conduct
-enforcement ladder](https://github.com/mozilla/diversity).
-
-[homepage]: https://www.contributor-covenant.org
-
-For answers to common questions about this code of conduct, see the FAQ at
-<https://www.contributor-covenant.org/faq>. Translations are available at
-<https://www.contributor-covenant.org/translations>.

package/.github/FUNDING.yaml

@@ -1,15 +0,0 @@
-# These are supported funding model platforms
-
-github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
-patreon: # Replace with a single Patreon username
-open_collective: # Replace with a single Open Collective username
-ko_fi: # Replace with a single Ko-fi username
-tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
-community_bridge: # Replace with a single Community Bridge project_name e.g., cloud-foundry
-liberapay: # Replace with a single Liberapay username
-issuehunt: # Replace with a single IssueHunt username
-lfx_crowdfunding: # Replace with a single LFX Crowdfunding project_name e.g., cloud-foundry
-polar: # Replace with a single Polar username
-buy_me_a_coffee: bmad
-thanks_dev: # Replace with a single thanks.dev username
-custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

package/.github/ISSUE_TEMPLATE/bug-report.yaml

@@ -1,124 +0,0 @@
-name: Bug Report
-description: File a bug report to help us improve BMad Method
-title: "[BUG] "
-labels: bug
-assignees: []
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for filing a bug report! Please fill out the information below to help us reproduce and fix the issue.
-
-  - type: textarea
-    id: description
-    attributes:
-      label: Description
-      description: Clear and concise description of what the bug is
-      placeholder: e.g., When I run /dev-story, it crashes on step 3
-    validations:
-      required: true
-
-  - type: textarea
-    id: steps
-    attributes:
-      label: Steps to reproduce
-      description: Step-by-step instructions to reproduce the behavior
-      placeholder: |
-        1. Run 'npx bmad-method install'
-        2. Select option X
-        3. Run workflow Y
-        4. See error
-    validations:
-      required: true
-
-  - type: textarea
-    id: expected
-    attributes:
-      label: Expected behavior
-      description: What you expected to happen
-      placeholder: The workflow should complete successfully
-    validations:
-      required: true
-
-  - type: textarea
-    id: actual
-    attributes:
-      label: Actual behavior
-      description: What actually happened
-      placeholder: The workflow crashed with error "..."
-    validations:
-      required: true
-
-  - type: textarea
-    id: screenshots
-    attributes:
-      label: Screenshots
-      description: Add screenshots if applicable (paste images directly)
-      placeholder: Paste any relevant screenshots here
-
-  - type: dropdown
-    id: module
-    attributes:
-      label: Which module is this for?
-      description: Select the BMad module this issue relates to
-      options:
-        - BMad Method (BMM) - Core Framework
-        - BMad Builder (BMB) - Agent Builder Tool
-        - Test Architect (TEA) - Test Strategy Module
-        - Game Dev Studio (BMGD) - Game Development Module
-        - Creative Intelligence Suite (CIS) - Innovation Module
-        - Not sure / Other
-    validations:
-      required: true
-
-  - type: input
-    id: version
-    attributes:
-      label: BMad Version
-      description: "Check with: npx bmad-method --version or check package.json"
-      placeholder: e.g., 6.0.0-Beta.4
-    validations:
-      required: true
-
-  - type: dropdown
-    id: ide
-    attributes:
-      label: Which AI IDE are you using?
-      options:
-        - Claude Code
-        - Cursor
-        - Windsurf
-        - Copilot CLI / GitHub Copilot
-        - Kilo Code
-        - Other
-    validations:
-      required: true
-
-  - type: dropdown
-    id: platform
-    attributes:
-      label: Operating System
-      options:
-        - macOS
-        - Windows
-        - Linux
-        - Other
-    validations:
-      required: true
-
-  - type: textarea
-    id: logs
-    attributes:
-      label: Relevant log output
-      description: Copy and paste any relevant log output
-      render: shell
-
-  - type: checkboxes
-    id: terms
-    attributes:
-      label: Confirm
-      options:
-        - label: I've searched for existing issues
-          required: true
-        - label: I'm using the latest version
-          required: false

package/.github/ISSUE_TEMPLATE/config.yaml

@@ -1,8 +0,0 @@
-blank_issues_enabled: false
-contact_links:
-  - name: 📚 Documentation
-    url: https://docs.bmad-method.org
-    about: Check the docs first — tutorials, guides, and reference
-  - name: 💬 Discord Community
-    url: https://discord.gg/gk8jAdXWmj
-    about: Join for questions, discussion, and help before opening an issue

package/.github/ISSUE_TEMPLATE/documentation.yaml

@@ -1,55 +0,0 @@
-name: Documentation
-description: Report issues or suggest improvements to documentation
-title: "[DOCS] "
-labels: documentation
-assignees: []
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Help us improve the BMad Method documentation!
-
-  - type: dropdown
-    id: doc-type
-    attributes:
-      label: What type of documentation issue is this?
-      options:
-        - Error or inaccuracy
-        - Missing information
-        - Unclear or confusing
-        - Outdated content
-        - Request for new documentation
-        - Typo or grammar
-    validations:
-      required: true
-
-  - type: textarea
-    id: location
-    attributes:
-      label: Documentation location
-      description: Where is the documentation that needs improvement?
-      placeholder: e.g., https://docs.bmad-method.org/tutorials/getting-started/ or "In the README"
-    validations:
-      required: true
-
-  - type: textarea
-    id: issue
-    attributes:
-      label: What's the issue?
-      description: Describe the documentation issue in detail
-      placeholder: e.g., Step 3 says to run command X but it should be command Y
-    validations:
-      required: true
-
-  - type: textarea
-    id: suggestion
-    attributes:
-      label: Suggested improvement
-      description: How would you like to see this improved?
-      placeholder: e.g., Change the command to X and add an example
-
-  - type: input
-    id: version
-    attributes:
-      label: BMad Version (if applicable)
-      placeholder: e.g., 6.0.0-Beta.4

package/.github/ISSUE_TEMPLATE/feature-request.md

@@ -1,22 +0,0 @@
----
-name: Feature Request
-about: Suggest an idea or new feature
-title: ''
-labels: ''
-assignees: ''
----
-
-**Describe your idea**
-A clear and concise description of what you'd like to see added or changed.
-
-**Why is this needed?**
-Explain the problem this solves or the benefit it brings to the BMad community.
-
-**How should it work?**
-Describe your proposed solution. If you have ideas on implementation, share them here.
-
-**PR**
-If you'd like to contribute, please indicate you're working on this or link to your PR. Please review [CONTRIBUTING.md](../../CONTRIBUTING.md) — contributions are always welcome!
-
-**Additional context**
-Add any other context, screenshots, or links that help explain your idea.