bmad-method 6.0.3 → 6.0.5-next.0

package/README_CN.md

@@ -0,0 +1,121 @@
+![BMad Method](banner-bmad-method.png)
+
+[![Version](https://img.shields.io/npm/v/bmad-method?color=blue&label=version)](https://www.npmjs.com/package/bmad-method)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
+[![Node.js Version](https://img.shields.io/badge/node-%3E%3D20.0.0-brightgreen)](https://nodejs.org)
+[![Discord](https://img.shields.io/badge/Discord-Join%20Community-7289da?logo=discord&logoColor=white)](https://discord.gg/gk8jAdXWmj)
+
+**突破性敏捷 AI 驱动开发方法** — 简称 “BMAD 方法论” ，BMAD方法论是由多个模块生态构成的AI驱动敏捷开发模块系统，这是最佳且最全面的敏捷 AI 驱动开发框架，具备真正的规模自适应人工智能，可适应快速开发，适应企业规模化开发。
+
+**100% 免费且开源。** 无付费。无内容门槛。无封闭 Discord。我们赋能每个人，我们将为全球现在在人工智能领域发展的普通人提供公平的学习机会。
+
+## 为什么选择 BMad 方法？
+
+传统 AI 工具替你思考，产生平庸的结果。BMad 智能体和辅助工作流充当专家协作者，引导你通过结构化流程，与 AI 的合作发挥最佳思维，产出最有效优秀的结果。
+
+- **AI 智能帮助** — 随时使用 `/bmad-help` 获取下一步指导
+- **规模-领域自适应** — 根据项目复杂度自动调整规划深度
+- **结构化工作流** — 基于分析、规划、架构和实施的敏捷最佳实践
+- **专业智能体** — 12+ 领域专家（PM、架构师、开发者、UX、Scrum Master 等）
+- **派对模式** — 将多个智能体角色带入一个会话进行协作和讨论
+- **完整生命周期** — 从想法开始（头脑风暴）到部署发布
+
+[在 **docs.bmad-method.org** 了解更多](http://docs.bmad-method.org)
+
+---
+
+## 🚀 BMad 的下一步是什么？
+
+**V6 已到来，我们才刚刚开始！** BMad 方法正在快速发展，包括跨平台智能体团队和子智能体集成、技能架构、BMad Builder v1、开发循环自动化等优化，以及更多正在开发中的功能。
+
+**[📍 查看完整路线图 →](http://docs.bmad-method.org/roadmap/)**
+
+---
+
+## 快速开始
+
+**先决条件**：[Node.js](https://nodejs.org) v20+
+
+```bash
+npx bmad-method install
+```
+
+> 如果你获得的是过时的测试版，请使用：`npx bmad-method@6.0.1 install`
+
+按照安装程序提示操作，然后在项目文件夹中打开你的 AI IDE（Claude Code、Cursor 等）。
+
+**非交互式安装**（用于 CI/CD）：
+
+```bash
+npx bmad-method install --directory /path/to/project --modules bmm --tools claude-code --yes
+```
+
+[查看所有安装选项](http://docs.bmad-method.org/how-to/non-interactive-installation/)
+
+> **不确定该做什么？** 运行 `/bmad-help` — 它会准确告诉你下一步做什么以及什么是可选的。你也可以问诸如 `/bmad-help 我刚刚完成了架构设计，接下来该做什么？` 之类的问题。
+
+## 模块
+
+BMad 方法通过官方模块扩展到专业领域。可在安装期间或之后的任何时间使用。
+
+| Module                                                                                                            | Purpose                                           |
+| ----------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- |
+| **[BMad Method (BMM)](https://github.com/bmad-code-org/BMAD-METHOD)**                                             | 包含 34+ 工作流的核心框架                         |
+| **[BMad Builder (BMB)](https://github.com/bmad-code-org/bmad-builder)**                                           | 创建自定义 BMad 智能体和工作流                     |
+| **[Test Architect (TEA)](https://github.com/bmad-code-org/tea)**                                                  | 基于风险的测试策略和自动化                         |
+| **[Game Dev Studio (BMGD)](https://github.com/bmad-code-org/bmad-module-game-dev-studio)**                        | 游戏开发工作流（Unity、Unreal、Godot）             |
+| **[Creative Intelligence Suite (CIS)](https://github.com/bmad-code-org/bmad-module-creative-intelligence-suite)** | 创新、头脑风暴、设计思维                           |
+
+## 文档
+
+[BMad 方法文档站点](http://docs.bmad-method.org) — 教程、指南、概念和参考
+
+**快速链接：**
+- [入门教程](http://docs.bmad-method.org/tutorials/getting-started/)
+- [从先前版本升级](http://docs.bmad-method.org/how-to/upgrade-to-v6/)
+- [测试架构师文档](https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/)
+
+
+## 社区
+
+- [Discord](https://discord.gg/gk8jAdXWmj) — 获取帮助、分享想法、协作
+- [在 YouTube 上订阅](https://www.youtube.com/@BMadCode) — 教程、大师课和播客（2025 年 2 月推出）
+- [GitHub Issues](https://github.com/bmad-code-org/BMAD-METHOD/issues) — 错误报告和功能请求
+- [讨论](https://github.com/bmad-code-org/BMAD-METHOD/discussions) — 社区对话
+
+## 支持 BMad
+
+BMad 对每个人都是免费的 — 并且永远如此。如果你想支持开发：
+
+- ⭐ 请点击此页面右上角附近的项目星标图标
+- ☕ [请我喝咖啡](https://buymeacoffee.com/bmad) — 为开发提供动力
+- 🏢 企业赞助 — 在 Discord 上私信
+- 🎤 演讲与媒体 — 可参加会议、播客、采访（在 Discord 上联系 BM）
+
+## 贡献
+
+我们欢迎贡献！请参阅 [CONTRIBUTING.md](CONTRIBUTING.md) 了解指南。
+
+## 许可证
+
+MIT 许可证 — 详见 [LICENSE](LICENSE)。
+
+---
+
+**BMad** 和 **BMAD-METHOD** 是 BMad Code, LLC 的商标。详见 [TRADEMARK.md](TRADEMARK.md)。
+
+[![Contributors](https://contrib.rocks/image?repo=bmad-code-org/BMAD-METHOD)](https://github.com/bmad-code-org/BMAD-METHOD/graphs/contributors)
+
+请参阅 [CONTRIBUTORS.md](CONTRIBUTORS.md) 了解贡献者信息。
+
+---
+## 术语说明
+
+- **agent**：智能体。在人工智能与编程文档中，指具备自主决策或执行能力的单元。
+- **workflow**：工作流。指一系列有序的任务或步骤，用于完成特定目标。
+- **CI/CD**：持续集成/持续部署。一种自动化软件开发实践，用于频繁集成代码更改并自动部署。
+- **IDE**：集成开发环境。提供代码编辑、调试、构建等功能的软件开发工具。
+- **PM**：产品经理。负责产品规划、需求管理和团队协调的角色。
+- **UX**：用户体验。指用户在使用产品或服务过程中的整体感受和交互体验。
+- **Scrum Master**：Scrum 主管。敏捷开发 Scrum 框架中的角色，负责促进团队遵循 Scrum 流程。
+- **PRD**：产品需求文档。详细描述产品功能、需求和规格的文档。

package/docs/_STYLE_GUIDE.md

@@ -59,13 +59,13 @@ Critical warnings only — data loss, security issues
 | 2     | Planning | Requirements — PRD or tech-spec *(required)* |
 ```
 
-**Commands:**
+**Skills:**
 
 ```md
-| Command      | Agent   | Purpose                              |
+| Skill        | Agent   | Purpose                              |
 | ------------ | ------- | ------------------------------------ |
-| `brainstorm` | Analyst | Brainstorm a new project             |
-| `prd`        | PM      | Create Product Requirements Document |
+| `bmad-brainstorming` | Analyst | Brainstorm a new project             |
+| `bmad-create-prd`        | PM      | Create Product Requirements Document |
 ```
 
 ## Folder Structure Blocks
@@ -99,7 +99,7 @@ your-project/
 9. Step 2: [Second Major Task]
 10. Step 3: [Third Major Task]
 11. What You've Accomplished (summary + folder structure)
-12. Quick Reference (commands table)
+12. Quick Reference (skills table)
 13. Common Questions (FAQ format)
 14. Getting Help (community links)
 15. Key Takeaways (tip admonition)
@@ -111,7 +111,7 @@ your-project/
 - [ ] "What You'll Learn" section present
 - [ ] Prerequisites in admonition
 - [ ] Quick Path TL;DR admonition at top
-- [ ] Tables for phases, commands, agents
+- [ ] Tables for phases, skills, agents
 - [ ] "What You've Accomplished" section present
 - [ ] Quick Reference table present
 - [ ] Common Questions section present
@@ -243,7 +243,7 @@ your-project/
 1. Title + Hook
 2. Items (## for each item)
    - Brief description (one sentence)
-   - **Commands:** or **Key Info:** as flat list
+   - **Skills:** or **Key Info:** as flat list
 3. Universal/Shared (## section) (optional)
 ```
 
@@ -252,7 +252,7 @@ your-project/
 ```text
 1. Title + Hook (one sentence purpose)
 2. Quick Facts (optional note admonition)
-   - Module, Command, Input, Output as list
+   - Module, Skill, Input, Output as list
 3. Purpose/Overview (## section)
 4. How to Invoke (code block)
 5. Key Sections (## for each aspect)
@@ -280,7 +280,7 @@ your-project/
    - Diagram or table showing organization
 3. Major Sections (## for each phase/category)
    - Items (### for each item)
-   - Standardized fields: Command, Agent, Input, Output, Description
+   - Standardized fields: Skill, Agent, Input, Output, Description
 4. Next Steps (optional)
 ```
 
@@ -353,7 +353,7 @@ Only for BMad Method and Enterprise tracks. Quick Flow skips to implementation.
 
 ### Can I change my plan later?
 
-Yes. The SM agent has a `correct-course` workflow for handling scope changes.
+Yes. The SM agent has a `bmad-correct-course` workflow for handling scope changes.
 
 **Have a question not answered here?** [Open an issue](...) or ask in [Discord](...).
 ```

package/docs/explanation/brainstorming.md

@@ -9,7 +9,7 @@ Unlock your creativity through guided exploration.
 
 ## What is Brainstorming?
 
-Run `brainstorming` and you've got a creative facilitator pulling ideas out of you - not generating them for you. The AI acts as coach and guide, using proven techniques to create conditions where your best thinking emerges.
+Run `bmad-brainstorming` and you've got a creative facilitator pulling ideas out of you - not generating them for you. The AI acts as coach and guide, using proven techniques to create conditions where your best thinking emerges.
 
 **Good for:**
 

package/docs/explanation/party-mode.md

@@ -9,7 +9,7 @@ Get all your AI agents in one conversation.
 
 ## What is Party Mode?
 
-Run `party-mode` and you've got your whole AI team in one room - PM, Architect, Dev, UX Designer, whoever you need. BMad Master orchestrates, picking relevant agents per message. Agents respond in character, agree, disagree, and build on each other's ideas.
+Run `bmad-party-mode` and you've got your whole AI team in one room - PM, Architect, Dev, UX Designer, whoever you need. BMad Master orchestrates, picking relevant agents per message. Agents respond in character, agree, disagree, and build on each other's ideas.
 
 The conversation continues as long as you want. Ask follow-ups, push back on answers, redirect the discussion - it's a real back-and-forth with your agents until you're done.
 

package/docs/explanation/preventing-agent-conflicts.md

@@ -108,5 +108,5 @@ Common decisions that prevent conflicts:
 - Document decisions that cross epic boundaries
 - Focus on conflict-prone areas
 - Update architecture as you learn
-- Use `correct-course` for significant changes
+- Use `bmad-correct-course` for significant changes
 :::

package/docs/explanation/project-context.md

@@ -21,12 +21,12 @@ The `project-context.md` file solves this by documenting what agents need to kno
 Every implementation workflow automatically loads `project-context.md` if it exists. The architect workflow also loads it to respect your technical preferences when designing the architecture.
 
 **Loaded by these workflows:**
-- `create-architecture` — respects technical preferences during solutioning
-- `create-story` — informs story creation with project patterns
-- `dev-story` — guides implementation decisions
-- `code-review` — validates against project standards
-- `quick-dev` — applies patterns when implementing tech-specs
-- `sprint-planning`, `retrospective`, `correct-course` — provides project-wide context
+- `bmad-create-architecture` — respects technical preferences during solutioning
+- `bmad-create-story` — informs story creation with project patterns
+- `bmad-dev-story` — guides implementation decisions
+- `bmad-code-review` — validates against project standards
+- `bmad-quick-dev` — applies patterns when implementing tech-specs
+- `bmad-sprint-planning`, `bmad-retrospective`, `bmad-correct-course` — provides project-wide context
 
 ## When to Create It
 
@@ -34,10 +34,10 @@ The `project-context.md` file is useful at any stage of a project:
 
 | Scenario | When to Create | Purpose |
 |----------|----------------|---------|
-| **New project, before architecture** | Manually, before `create-architecture` | Document your technical preferences so the architect respects them |
-| **New project, after architecture** | Via `generate-project-context` or manually | Capture architecture decisions for implementation agents |
-| **Existing project** | Via `generate-project-context` | Discover existing patterns so agents follow established conventions |
-| **Quick Flow project** | Before or during `quick-dev` | Ensure quick implementation respects your patterns |
+| **New project, before architecture** | Manually, before `bmad-create-architecture` | Document your technical preferences so the architect respects them |
+| **New project, after architecture** | Via `bmad-generate-project-context` or manually | Capture architecture decisions for implementation agents |
+| **Existing project** | Via `bmad-generate-project-context` | Discover existing patterns so agents follow established conventions |
+| **Quick Flow project** | Before or during `bmad-quick-dev` | Ensure quick implementation respects your patterns |
 
 :::tip[Recommended]
 For new projects, create it manually before architecture if you have strong technical preferences. Otherwise, generate it after architecture to capture those decisions.
@@ -107,20 +107,20 @@ Edit it with your technology stack and implementation rules. The architect and i
 
 ### Generate After Architecture
 
-Run the `generate-project-context` workflow after completing your architecture:
+Run the `bmad-generate-project-context` workflow after completing your architecture:
 
 ```bash
-/bmad-bmm-generate-project-context
+bmad-generate-project-context
 ```
 
 This scans your architecture document and project files to generate a context file capturing the decisions made.
 
 ### Generate for Existing Projects
 
-For existing projects, run `generate-project-context` to discover existing patterns:
+For existing projects, run `bmad-generate-project-context` to discover existing patterns:
 
 ```bash
-/bmad-bmm-generate-project-context
+bmad-generate-project-context
 ```
 
 The workflow analyzes your codebase to identify conventions, then generates a context file you can review and refine.
@@ -150,7 +150,7 @@ The `project-context.md` file is a living document. Update it when:
 - Patterns evolve during implementation
 - You identify gaps from agent behavior
 
-You can edit it manually at any time, or re-run `generate-project-context` to update it after significant changes.
+You can edit it manually at any time, or re-run `bmad-generate-project-context` to update it after significant changes.
 
 :::note[File Location]
 The default location is `_bmad-output/project-context.md`. Workflows search for it there, and also check `**/project-context.md` anywhere in your project.

package/docs/explanation/quick-flow.md

@@ -5,7 +5,7 @@ sidebar:
   order: 1
 ---
 
-Skip the ceremony. Quick Flow takes you from idea to working code in two commands - no Product Brief, no PRD, no Architecture doc.
+Skip the ceremony. Quick Flow takes you from idea to working code in two skills - no Product Brief, no PRD, no Architecture doc.
 
 ## When to Use It
 
@@ -23,16 +23,16 @@ Skip the ceremony. Quick Flow takes you from idea to working code in two command
 - Anything where requirements are unclear or contested
 
 :::caution[Scope Creep]
-If you start a Quick Flow and realize the scope is bigger than expected, `quick-dev` will detect this and offer to escalate. You can switch to a full PRD workflow at any point without losing your work.
+If you start a Quick Flow and realize the scope is bigger than expected, `bmad-quick-dev` will detect this and offer to escalate. You can switch to a full PRD workflow at any point without losing your work.
 :::
 
 ## How It Works
 
-Quick Flow has two commands, each backed by a structured workflow. You can run them together or independently.
+Quick Flow has two skills, each backed by a structured workflow. You can run them together or independently.
 
 ### quick-spec: Plan
 
-Run `quick-spec` and Barry (the Quick Flow agent) walks you through a conversational discovery process:
+Run `bmad-quick-spec` and Barry (the Quick Flow agent) walks you through a conversational discovery process:
 
 1. **Understand** - You describe what you want to build. Barry scans the codebase to ask informed questions, then captures a problem statement, solution approach, and scope boundaries.
 2. **Investigate** - Barry reads relevant files, maps code patterns, identifies files to modify, and documents the technical context.
@@ -43,15 +43,15 @@ The output is a `tech-spec-{slug}.md` file saved to your project's implementatio
 
 ### quick-dev: Build
 
-Run `quick-dev` and Barry implements the work. It operates in two modes:
+Run `bmad-quick-dev` and Barry implements the work. It operates in two modes:
 
 - **Tech-spec mode** - Point it at a spec file (`quick-dev tech-spec-auth.md`) and it executes every task in order, writes tests, and verifies acceptance criteria.
 - **Direct mode** - Give it instructions directly (`quick-dev "refactor the auth middleware"`) and it gathers context, builds a mental plan, and executes.
 
-After implementation, `quick-dev` runs a self-check audit against all tasks and acceptance criteria, then triggers an adversarial code review of the diff. Findings are presented for you to resolve before wrapping up.
+After implementation, `bmad-quick-dev` runs a self-check audit against all tasks and acceptance criteria, then triggers an adversarial code review of the diff. Findings are presented for you to resolve before wrapping up.
 
 :::tip[Fresh Context]
-For best results, run `quick-dev` in a new conversation after finishing `quick-spec`. This gives the implementation agent clean context focused solely on building.
+For best results, run `bmad-quick-dev` in a new conversation after finishing `bmad-quick-spec`. This gives the implementation agent clean context focused solely on building.
 :::
 
 ## What Quick Flow Skips
@@ -65,9 +65,9 @@ The full BMad Method produces a Product Brief, PRD, Architecture doc, and Epic/S
 
 ## Escalating to Full BMad Method
 
-Quick Flow includes built-in guardrails for scope detection. When you run `quick-dev` with a direct request, it evaluates signals like multi-component mentions, system-level language, and uncertainty about approach. If it detects the work is bigger than a quick flow:
+Quick Flow includes built-in guardrails for scope detection. When you run `bmad-quick-dev` with a direct request, it evaluates signals like multi-component mentions, system-level language, and uncertainty about approach. If it detects the work is bigger than a quick flow:
 
-- **Light escalation** - Recommends running `quick-spec` first to create a plan
+- **Light escalation** - Recommends running `bmad-quick-spec` first to create a plan
 - **Heavy escalation** - Recommends switching to the full BMad Method PRD process
 
 You can also escalate manually at any time. Your tech-spec work carries forward - it becomes input for the broader planning process rather than being discarded.

package/docs/how-to/established-projects.md

@@ -32,7 +32,7 @@ Generate `project-context.md` to capture your existing codebase patterns and con
 Run the generate project context workflow:
 
 ```bash
-/bmad-bmm-generate-project-context
+bmad-generate-project-context
 ```
 
 This scans your codebase to identify:
@@ -55,22 +55,22 @@ Your `docs/` folder should contain succinct, well-organized documentation that a
 - Architecture
 - Any other relevant project information
 
-For complex projects, consider using the `document-project` workflow. It offers runtime variants that will scan your entire project and document its actual current state.
+For complex projects, consider using the `bmad-document-project` workflow. It offers runtime variants that will scan your entire project and document its actual current state.
 
 ## Step 3: Get Help
 
 ### BMad-Help: Your Starting Point
 
-**Run `/bmad-help` anytime you're unsure what to do next.** This intelligent guide:
+**Run `bmad-help` anytime you're unsure what to do next.** This intelligent guide:
 
 - Inspects your project to see what's already been done
 - Shows options based on your installed modules
 - Understands natural language queries
 
 ```
-/bmad-help I have an existing Rails app, where should I start?
-/bmad-help What's the difference between quick-flow and full method?
-/bmad-help Show me what workflows are available
+bmad-help I have an existing Rails app, where should I start?
+bmad-help What's the difference between quick-flow and full method?
+bmad-help Show me what workflows are available
 ```
 
 BMad-Help also **automatically runs at the end of every workflow**, providing clear guidance on exactly what to do next.
@@ -81,7 +81,7 @@ You have two primary options depending on the scope of changes:
 
 | Scope                          | Recommended Approach                                                                                                          |
 | ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------- |
-| **Small updates or additions** | Use `quick-flow-solo-dev` to create a tech-spec and implement the change. The full four-phase BMad Method is likely overkill. |
+| **Small updates or additions** | Use `bmad-quick-flow-solo-dev` to create a tech-spec and implement the change. The full four-phase BMad Method is likely overkill. |
 | **Major changes or additions** | Start with the BMad Method, applying as much or as little rigor as needed.                                                    |
 
 ### During PRD Creation

package/docs/how-to/get-answers-about-bmad.md

@@ -18,7 +18,7 @@ BMad-Help is more than a lookup tool — it:
 
 ### How to Use BMad-Help
 
-Run it with just the slash command:
+Run it with just the skill name:
 
 ```
 /bmad-help
@@ -81,7 +81,7 @@ https://bmad-code-org.github.io/BMAD-METHOD/llms-full.txt
 :::note[Example]
 **Q:** "Tell me the fastest way to build something with BMad"
 
-**A:** Use Quick Flow: Run `quick-spec` to write a technical specification, then `quick-dev` to implement it—skipping the full planning phases.
+**A:** Use Quick Flow: Run `bmad-quick-spec` to write a technical specification, then `bmad-quick-dev` to implement it—skipping the full planning phases.
 :::
 
 ## What You Get

package/docs/how-to/install-bmad.md

@@ -51,7 +51,11 @@ Pick which AI tools you use:
 - Cursor
 - Others
 
-Each tool has its own way of integrating commands. The installer creates tiny prompt files to activate workflows and agents — it just puts them where your tool expects to find them.
+Each tool has its own way of integrating skills. The installer creates tiny prompt files to activate workflows and agents — it just puts them where your tool expects to find them.
+
+:::note[Enabling Skills]
+Some platforms require skills to be explicitly enabled in settings before they appear. If you install BMad and don't see the skills, check your platform's settings or ask your AI assistant how to enable skills.
+:::
 
 ### 4. Choose Modules
 
@@ -71,13 +75,19 @@ your-project/
 │   ├── core/           # Required core module
 │   └── ...
 ├── _bmad-output/       # Generated artifacts
-├── .claude/            # Claude Code commands (if using Claude Code)
-└── .kiro/              # Kiro steering files (if using Kiro)
+├── .claude/            # Claude Code skills (if using Claude Code)
+│   └── skills/
+│       ├── bmad-help/
+│       ├── bmad-persona/
+│       └── ...
+└── .cursor/            # Cursor skills (if using Cursor)
+    └── skills/
+        └── ...
 ```
 
 ## Verify Installation
 
-Run `/bmad-help` to verify everything works and see what to do next.
+Run `bmad-help` to verify everything works and see what to do next.
 
 **BMad-Help is your intelligent guide** that will:
 - Confirm your installation is working
@@ -86,8 +96,8 @@ Run `/bmad-help` to verify everything works and see what to do next.
 
 You can also ask it questions:
 ```
-/bmad-help I just installed, what should I do first?
-/bmad-help What are my options for a SaaS project?
+bmad-help I just installed, what should I do first?
+bmad-help What are my options for a SaaS project?
 ```
 
 ## Troubleshooting

package/docs/how-to/project-context.md

@@ -77,7 +77,7 @@ sections_completed: ['technology_stack', 'critical_rules']
 Run the workflow in a fresh chat:
 
 ```bash
-/bmad-bmm-generate-project-context
+bmad-generate-project-context
 ```
 
 The workflow scans your architecture document and project files to generate a context file capturing the decisions made.
@@ -87,7 +87,7 @@ The workflow scans your architecture document and project files to generate a co
 For existing projects, run:
 
 ```bash
-/bmad-bmm-generate-project-context
+bmad-generate-project-context
 ```
 
 The workflow analyzes your codebase to identify conventions, then generates a context file you can review and refine.

package/docs/how-to/quick-fixes.md

@@ -30,18 +30,18 @@ If you are unsure, start with the DEV agent. You can always escalate to Quick Fl
 
 ## Steps
 
-### 1. Load the DEV Agent
+### 1. Invoke the DEV Agent
 
-Start a **fresh chat** in your AI IDE and load the DEV agent with its slash command:
+Start a **fresh chat** in your AI IDE and invoke the DEV agent skill:
 
 ```text
-/bmad-agent-bmm-dev
+bmad-dev
 ```
 
-This loads the agent's persona and capabilities into the session. If you decide you need Quick Flow instead, load the **Quick Flow Solo Dev** agent in a fresh chat:
+This loads the agent's persona and capabilities into the session. If you decide you need Quick Flow instead, invoke the **Quick Flow Solo Dev** agent skill in a fresh chat:
 
 ```text
-/bmad-agent-bmm-quick-flow-solo-dev
+bmad-quick-flow-solo-dev
 ```
 
 Once the Solo Dev agent is loaded, describe your change and ask it to create a **quick-spec**. The agent drafts a lightweight spec capturing what you want to change and how. After you approve the quick-spec, tell the agent to start the **Quick Flow dev cycle** -- it will implement the change, run tests, and perform a self-review, all guided by the spec you just approved.

package/docs/how-to/shard-large-documents.md

@@ -5,7 +5,7 @@ sidebar:
   order: 8
 ---
 
-Use the `shard-doc` tool if you need to split large markdown files into smaller, organized files for better context management.
+Use the `bmad-shard-doc` tool if you need to split large markdown files into smaller, organized files for better context management.
 
 :::caution[Deprecated]
 This is no longer recommended, and soon with updated workflows and most major LLMs and tools supporting subprocesses this will be unnecessary.

package/docs/how-to/upgrade-to-v6.md

@@ -33,12 +33,15 @@ When v4 is detected, you can:
 
 If you named your bmad method folder something else - you will need to manually remove the folder yourself.
 
-### 3. Clean Up IDE Commands
+### 3. Clean Up IDE Skills
 
-Manually remove legacy v4 IDE commands - for example if you have claude, look for any nested folders that start with bmad and remove them:
+Manually remove legacy v4 IDE commands/skills - for example if you have Claude Code, look for any nested folders that start with bmad and remove them:
 
-- `.claude/commands/BMad/agents`
-- `.claude/commands/BMad/tasks`
+- `.claude/commands/`
+
+The new v6 skills are installed to:
+
+- `.claude/skills/`
 
 ### 4. Migrate Planning Artifacts
 
@@ -58,7 +61,7 @@ If you have stories created or implemented:
 
 1. Complete the v6 installation
 2. Place `epics.md` or `epics/epic*.md` in `_bmad-output/planning-artifacts/`
-3. Run the Scrum Master's `sprint-planning` workflow
+3. Run the Scrum Master's `bmad-sprint-planning` workflow
 4. Tell the SM which epics/stories are already complete
 
 ## What You Get

package/docs/index.md

@@ -3,7 +3,7 @@ title: Welcome to the BMad Method
 description: AI-driven development framework with specialized agents, guided workflows, and intelligent planning
 ---
 
-The BMad Method (**B**reakthrough **M**ethod of **A**gile AI **D**riven Development) is an AI-driven development framework module within the BMad Method Ecosystem that helps you build software through the whole process from ideation and planning all the way through agentic implementation. It provides specialized AI agents, guided workflows, and intelligent planning that adapts to your project's complexity, whether you're fixing a bug or building an enterprise platform.
+The BMad Method (**B**uild **M**ore **A**rchitect **D**reams) is an AI-driven development framework module within the BMad Method Ecosystem that helps you build software through the whole process from ideation and planning all the way through agentic implementation. It provides specialized AI agents, guided workflows, and intelligent planning that adapts to your project's complexity, whether you're fixing a bug or building an enterprise platform.
 
 If you're comfortable working with AI coding assistants like Claude, Cursor, or GitHub Copilot, you're ready to get started.
 
@@ -19,7 +19,7 @@ The fastest way to understand BMad is to try it.
 - **[Workflow Map](./reference/workflow-map.md)** — Visual overview of BMM phases, workflows, and context management
 
 :::tip[Just Want to Dive In?]
-Install BMad and run `/bmad-help` — it will guide you through everything based on your project and installed modules.
+Install BMad and use the `bmad-help` skill — it will guide you through everything based on your project and installed modules.
 :::
 
 ## How to Use These Docs

package/docs/reference/agents.md

@@ -1,28 +1,28 @@
 ---
 title: Agents
-description: Default BMM agents with their menu triggers and primary workflows
+description: Default BMM agents with their skill IDs, menu triggers, and primary workflows
 sidebar:
   order: 2
 ---
 
 ## Default Agents
 
-This page lists the default BMM (Agile suite) agents that install with BMad Method, along with their menu triggers and primary workflows.
+This page lists the default BMM (Agile suite) agents that install with BMad Method, along with their skill IDs, menu triggers, and primary workflows. Each agent is invoked as a skill.
 
 ## Notes
 
+- Each agent is available as a skill, generated by the installer. The skill ID (e.g., `bmad-dev`) is used to invoke the agent.
 - Triggers are the short menu codes (e.g., `CP`) and fuzzy matches shown in each agent menu.
-- Slash commands are generated separately. See [Commands](./commands.md) for the slash command list and where they are defined.
 - QA (Quinn) is the lightweight test automation agent in BMM. The full Test Architect (TEA) lives in its own module.
 
-| Agent                       | Triggers                           | Primary workflows                                                                                   |
-| --------------------------- | ---------------------------------- | --------------------------------------------------------------------------------------------------- |
-| Analyst (Mary)              | `BP`, `RS`, `CB`, `DP`             | Brainstorm Project, Research, Create Brief, Document Project                                        |
-| Product Manager (John)      | `CP`, `VP`, `EP`, `CE`, `IR`, `CC` | Create/Validate/Edit PRD, Create Epics and Stories, Implementation Readiness, Correct Course        |
-| Architect (Winston)         | `CA`, `IR`                         | Create Architecture, Implementation Readiness                                                       |
-| Scrum Master (Bob)          | `SP`, `CS`, `ER`, `CC`             | Sprint Planning, Create Story, Epic Retrospective, Correct Course                                   |
-| Developer (Amelia)          | `DS`, `CR`                         | Dev Story, Code Review                                                                              |
-| QA Engineer (Quinn)         | `QA`                               | Automate (generate tests for existing features)                                                     |
-| Quick Flow Solo Dev (Barry) | `QS`, `QD`, `CR`                   | Quick Spec, Quick Dev, Code Review                                                                  |
-| UX Designer (Sally)         | `CU`                               | Create UX Design                                                                                    |
-| Technical Writer (Paige)    | `DP`, `WD`, `US`, `MG`, `VD`, `EC` | Document Project, Write Document, Update Standards, Mermaid Generate, Validate Doc, Explain Concept |
+| Agent                       | Skill ID             | Triggers                           | Primary workflows                                                                                   |
+| --------------------------- | -------------------- | ---------------------------------- | --------------------------------------------------------------------------------------------------- |
+| Analyst (Mary)              | `bmad-analyst`       | `BP`, `RS`, `CB`, `DP`             | Brainstorm Project, Research, Create Brief, Document Project                                        |
+| Product Manager (John)      | `bmad-pm`            | `CP`, `VP`, `EP`, `CE`, `IR`, `CC` | Create/Validate/Edit PRD, Create Epics and Stories, Implementation Readiness, Correct Course        |
+| Architect (Winston)         | `bmad-architect`     | `CA`, `IR`                         | Create Architecture, Implementation Readiness                                                       |
+| Scrum Master (Bob)          | `bmad-sm`            | `SP`, `CS`, `ER`, `CC`             | Sprint Planning, Create Story, Epic Retrospective, Correct Course                                   |
+| Developer (Amelia)          | `bmad-dev`           | `DS`, `CR`                         | Dev Story, Code Review                                                                              |
+| QA Engineer (Quinn)         | `bmad-qa`            | `QA`                               | Automate (generate tests for existing features)                                                     |
+| Quick Flow Solo Dev (Barry) | `bmad-master`        | `QS`, `QD`, `CR`                   | Quick Spec, Quick Dev, Code Review                                                                  |
+| UX Designer (Sally)         | `bmad-ux-designer`   | `CU`                               | Create UX Design                                                                                    |
+| Technical Writer (Paige)    | `bmad-tech-writer`   | `DP`, `WD`, `US`, `MG`, `VD`, `EC` | Document Project, Write Document, Update Standards, Mermaid Generate, Validate Doc, Explain Concept |