bmad-method 6.0.5-next.8 → 6.1.0

package/CNAME

@@ -1 +0,0 @@
-docs.bmad-method.org

package/CONTRIBUTING.md

@@ -1,176 +0,0 @@
-# Contributing to BMad
-
-Thank you for considering contributing! We believe in **Human Amplification, Not Replacement** — bringing out the best thinking in both humans and AI through guided collaboration.
-
-💬 **Discord**: [Join our community](https://discord.gg/gk8jAdXWmj) for real-time discussions, questions, and collaboration.
-
----
-
-## Our Philosophy
-
-BMad strengthens human-AI collaboration through specialized agents and guided workflows. Every contribution should answer: **"Does this make humans and AI better together?"**
-
-**✅ What we welcome:**
-- Enhanced collaboration patterns and workflows
-- Improved agent personas and prompts
-- Domain-specific modules leveraging BMad Core
-- Better planning and context continuity
-
-**❌ What doesn't fit:**
-- Purely automated solutions that sideline humans
-- Complexity that creates barriers to adoption
-- Features that fragment BMad Core's foundation
-
----
-
-## Reporting Issues
-
-**ALL bug reports and feature requests MUST go through GitHub Issues.**
-
-### Before Creating an Issue
-
-1. **Search existing issues** — Use the GitHub issue search to check if your bug or feature has already been reported
-2. **Search closed issues** — Your issue may have been fixed or addressed previously
-3. **Check discussions** — Some conversations happen in [GitHub Discussions](https://github.com/bmad-code-org/BMAD-METHOD/discussions)
-
-### Bug Reports
-
-After searching, if the bug is unreported, use the [bug report template](https://github.com/bmad-code-org/BMAD-METHOD/issues/new?template=bug_report.md) and include:
-
-- Clear description of the problem
-- Steps to reproduce
-- Expected vs actual behavior
-- Your environment (model, IDE, BMad version)
-- Screenshots or error messages if applicable
-
-### Feature Requests
-
-After searching, use the [feature request template](https://github.com/bmad-code-org/BMAD-METHOD/issues/new?template=feature_request.md) and explain:
-
-- What the feature is
-- Why it would benefit the BMad community
-- How it strengthens human-AI collaboration
-
-**For community modules**, review [TRADEMARK.md](TRADEMARK.md) for proper naming conventions (e.g., "My Module (BMad Community Module)").
-
----
-
-## Before Starting Work
-
-⚠️ **Required before submitting PRs:**
-
-| Work Type     | Requirement                                    |
-| ------------- | ---------------------------------------------- |
-| Bug fix       | An open issue (create one if it doesn't exist) |
-| Feature       | An open feature request issue                  |
-| Large changes | Discussion via issue first                     |
-
-**Why?** This prevents wasted effort on work that may not align with project direction.
-
----
-
-## Pull Request Guidelines
-
-### Target Branch
-
-Submit PRs to the `main` branch. We use trunk-based development. Every push to `main` auto-publishes to `npm` under the `next` tag. Stable releases are cut ~weekly to the `latest` tag.
-
-### PR Size
-
-- **Ideal**: 200-400 lines of code changes
-- **Maximum**: 800 lines (excluding generated files)
-- **One feature/fix per PR**
-
-If your change exceeds 800 lines, break it into smaller PRs that can be reviewed independently.
-
-### New to Pull Requests?
-
-1. **Fork** the repository
-2. **Clone** your fork: `git clone https://github.com/YOUR-USERNAME/bmad-method.git`
-3. **Create a branch**: `git checkout -b fix/description` or `git checkout -b feature/description`
-4. **Make changes** — keep them focused
-5. **Commit**: `git commit -m "fix: correct typo in README"`
-6. **Push**: `git push origin fix/description`
-7. **Open PR** from your fork on GitHub
-
-### PR Description Template
-
-```markdown
-## What
-[1-2 sentences describing WHAT changed]
-
-## Why
-[1-2 sentences explaining WHY this change is needed]
-Fixes #[issue number]
-
-## How
-- [2-3 bullets listing HOW you implemented it]
--
-
-## Testing
-[1-2 sentences on how you tested this]
-```
-
-**Keep it under 200 words.**
-
-### Commit Messages
-
-Use conventional commits:
-
-- `feat:` New feature
-- `fix:` Bug fix
-- `docs:` Documentation only
-- `refactor:` Code change (no bug/feature)
-- `test:` Adding tests
-- `chore:` Build/tools changes
-
-Keep messages under 72 characters. Each commit = one logical change.
-
----
-
-## What Makes a Good PR?
-
-| ✅ Do                        | ❌ Don't                      |
-| --------------------------- | ---------------------------- |
-| Change one thing per PR     | Mix unrelated changes        |
-| Clear title and description | Vague or missing explanation |
-| Reference related issues    | Reformat entire files        |
-| Small, focused commits      | Copy your whole project      |
-| Work on a branch            | Work directly on `main`      |
-
----
-
-## Prompt & Agent Guidelines
-
-- Keep dev agents lean — focus on coding context, not documentation
-- Web/planning agents can be larger with complex tasks
-- Everything is natural language (markdown) — no code in core framework
-- Use BMad modules for domain-specific features
-- Validate YAML schemas: `npm run validate:schemas`
-- Validate file references: `npm run validate:refs`
-
-### File-Pattern-to-Validator Mapping
-
-| File Pattern | Validator | Extraction Function |
-| ------------ | --------- | ------------------- |
-| `*.yaml`, `*.yml` | `validate-file-refs.js` | `extractYamlRefs` |
-| `*.md`, `*.xml` | `validate-file-refs.js` | `extractMarkdownRefs` |
-| `*.csv` | `validate-file-refs.js` | `extractCsvRefs` |
-
----
-
-## Need Help?
-
-- 💬 **Discord**: [Join the community](https://discord.gg/gk8jAdXWmj)
-- 🐛 **Bugs**: Use the [bug report template](https://github.com/bmad-code-org/BMAD-METHOD/issues/new?template=bug_report.md)
-- 💡 **Features**: Use the [feature request template](https://github.com/bmad-code-org/BMAD-METHOD/issues/new?template=feature_request.md)
-
----
-
-## Code of Conduct
-
-By participating, you agree to abide by our [Code of Conduct](.github/CODE_OF_CONDUCT.md).
-
-## License
-
-By contributing, your contributions are licensed under the same MIT License. See [CONTRIBUTORS.md](CONTRIBUTORS.md) for contributor attribution.

package/CONTRIBUTORS.md

@@ -1,32 +0,0 @@
-# Contributors
-
-BMad Core, BMad Method and BMad and Community BMad Modules are made possible by contributions from our community. We gratefully acknowledge everyone who has helped improve this project.
-
-## How We Credit Contributors
-
-- **Git history** — Every contribution is preserved in the project's commit history
-- **Contributors badge** — See the dynamic contributors list on our [README](README.md)
-- **GitHub contributors graph** — Visual representation at <https://github.com/bmad-code-org/BMAD-METHOD/graphs/contributors>
-
-## Becoming a Contributor
-
-Anyone who submits a pull request that is merged becomes a contributor. Contributions include:
-
-- Bug fixes
-- New features or workflows
-- Documentation improvements
-- Bug reports and issue triaging
-- Code reviews
-- Helping others in discussions
-
-There are no minimum contribution requirements — whether it's a one-character typo fix or a major feature, we value all contributions.
-
-## Copyright
-
-The BMad Method project is copyrighted by BMad Code, LLC. Individual contributions are licensed under the same MIT License as the project. Contributors retain authorship credit through Git history and the contributors graph.
-
----
-
-**Thank you to everyone who has helped make BMad Method better!**
-
-For contribution guidelines, see [CONTRIBUTING.md](CONTRIBUTING.md).

package/SECURITY.md

@@ -1,85 +0,0 @@
-# Security Policy
-
-## Supported Versions
-
-We release security patches for the following versions:
-
-| Version | Supported          |
-| ------- | ------------------ |
-| Latest  | :white_check_mark: |
-| < Latest | :x:               |
-
-We recommend always using the latest version of BMad Method to ensure you have the most recent security updates.
-
-## Reporting a Vulnerability
-
-We take security vulnerabilities seriously. If you discover a security issue, please report it responsibly.
-
-### How to Report
-
-**Do NOT report security vulnerabilities through public GitHub issues.**
-
-Instead, please report them via one of these methods:
-
-1. **GitHub Security Advisories** (Preferred): Use [GitHub's private vulnerability reporting](https://github.com/bmad-code-org/BMAD-METHOD/security/advisories/new) to submit a confidential report.
-
-2. **Discord**: Contact a maintainer directly via DM on our [Discord server](https://discord.gg/gk8jAdXWmj).
-
-### What to Include
-
-Please include as much of the following information as possible:
-
-- Type of vulnerability (e.g., prompt injection, path traversal, etc.)
-- Full paths of source file(s) related to the vulnerability
-- Step-by-step instructions to reproduce the issue
-- Proof-of-concept or exploit code (if available)
-- Impact assessment of the vulnerability
-
-### Response Timeline
-
-- **Initial Response**: Within 48 hours of receiving your report
-- **Status Update**: Within 7 days with our assessment
-- **Resolution Target**: Critical issues within 30 days; other issues within 90 days
-
-### What to Expect
-
-1. We will acknowledge receipt of your report
-2. We will investigate and validate the vulnerability
-3. We will work on a fix and coordinate disclosure timing with you
-4. We will credit you in the security advisory (unless you prefer to remain anonymous)
-
-## Security Scope
-
-### In Scope
-
-- Vulnerabilities in BMad Method core framework code
-- Security issues in agent definitions or workflows that could lead to unintended behavior
-- Path traversal or file system access issues
-- Prompt injection vulnerabilities that bypass intended agent behavior
-- Supply chain vulnerabilities in dependencies
-
-### Out of Scope
-
-- Security issues in user-created custom agents or modules
-- Vulnerabilities in third-party AI providers (Claude, GPT, etc.)
-- Issues that require physical access to a user's machine
-- Social engineering attacks
-- Denial of service attacks that don't exploit a specific vulnerability
-
-## Security Best Practices for Users
-
-When using BMad Method:
-
-1. **Review Agent Outputs**: Always review AI-generated code before executing it
-2. **Limit File Access**: Configure your AI IDE to limit file system access where possible
-3. **Keep Updated**: Regularly update to the latest version
-4. **Validate Dependencies**: Review any dependencies added by generated code
-5. **Environment Isolation**: Consider running AI-assisted development in isolated environments
-
-## Acknowledgments
-
-We appreciate the security research community's efforts in helping keep BMad Method secure. Contributors who report valid security issues will be acknowledged in our security advisories.
-
----
-
-Thank you for helping keep BMad Method and our community safe.

package/TRADEMARK.md

@@ -1,55 +0,0 @@
-# Trademark Notice & Guidelines
-
-## Trademark Ownership
-
-The following names and logos are trademarks of BMad Code, LLC:
-
-- **BMad** (word mark, all casings: BMad, bmad, BMAD)
-- **BMad Method** (word mark, includes BMadMethod, BMAD-METHOD, and all variations)
-- **BMad Core** (word mark, includes BMadCore, BMAD-CORE, and all variations)
-- **BMad Code** (word mark)
-- BMad Method logo and visual branding
-- The "Build More, Architect Dreams" tagline
-
-**All casings, stylings, and variations** of the above names (with or without hyphens, spaces, or specific capitalization) are covered by these trademarks.
-
-These trademarks are protected under trademark law and are **not** licensed under the MIT License. The MIT License applies to the software code only, not to the BMad brand identity.
-
-## What This Means
-
-You may:
-
-- Use the BMad software under the terms of the MIT License
-- Refer to BMad to accurately describe compatibility or integration (e.g., "Compatible with BMad Method v6")
-- Link to <https://github.com/bmad-code-org/BMAD-METHOD>
-- Fork the software and distribute your own version under a different name
-
-You may **not**:
-
-- Use "BMad" or any confusingly similar variation as your product name, service name, company name, or domain name
-- Present your product as officially endorsed, approved, or certified by BMad Code, LLC when it is not, without written consent from an authorized representative of BMad Code, LLC
-- Use BMad logos or branding in a way that suggests your product is an official or endorsed BMad product
-- Register domain names, social media handles, or trademarks that incorporate BMad branding
-
-## Examples
-
-| Permitted                                              | Not Permitted                                |
-| ------------------------------------------------------ | -------------------------------------------- |
-| "My workflow tool, compatible with BMad Method"        | "BMadFlow" or "BMad Studio"                  |
-| "An alternative implementation inspired by BMad"       | "BMad Pro" or "BMad Enterprise"              |
-| "My Awesome Healthcare Module (Bmad Community Module)" | "The Official BMad Core Healthcare Module"   |
-| Accurately stating you use BMad as a dependency        | Implying official endorsement or partnership |
-
-## Commercial Use
-
-You may sell products that incorporate or work with BMad software. However:
-
-- Your product must have its own distinct name and branding
-- You must not use BMad trademarks in your marketing, domain names, or product identity
-- You may truthfully describe technical compatibility (e.g., "Works with BMad Method")
-
-## Questions?
-
-If you have questions about trademark usage or would like to discuss official partnership or endorsement opportunities, please reach out:
-
-- **Email**: <contact@bmadcode.com>

package/docs/404.md

@@ -1,9 +0,0 @@
----
-title: Page Not Found
-template: splash
----
-
-
-The page you're looking for doesn't exist or has been moved.
-
-[Return to Home](./index.md)