bmad-method 6.0.3 → 6.0.5-next.0

package/docs/reference/commands.md

@@ -1,111 +1,113 @@
 ---
-title: Commands
-description: Reference for BMad slash commands — what they are, how they work, and where to find them.
+title: Skills
+description: Reference for BMad skills — what they are, how they work, and where to find them.
 sidebar:
   order: 3
 ---
 
-Slash commands are pre-built prompts that load agents, run workflows, or execute tasks inside your IDE. The BMad installer generates them from your installed modules at install time. If you later add, remove, or change modules, re-run the installer to keep commands in sync (see [Troubleshooting](#troubleshooting)).
+Skills are pre-built prompts that load agents, run workflows, or execute tasks inside your IDE. The BMad installer generates them from your installed modules at install time. If you later add, remove, or change modules, re-run the installer to keep skills in sync (see [Troubleshooting](#troubleshooting)).
 
-## Commands vs. Agent Menu Triggers
+## Skills vs. Agent Menu Triggers
 
 BMad offers two ways to start work, and they serve different purposes.
 
 | Mechanism | How you invoke it | What happens |
 | --- | --- | --- |
-| **Slash command** | Type `/bmad-...` in your IDE | Directly loads an agent, runs a workflow, or executes a task |
+| **Skill** | Type the skill name (e.g. `bmad-help`) in your IDE | Directly loads an agent, runs a workflow, or executes a task |
 | **Agent menu trigger** | Load an agent first, then type a short code (e.g. `DS`) | The agent interprets the code and starts the matching workflow while staying in character |
 
-Agent menu triggers require an active agent session. Use slash commands when you know which workflow you want. Use triggers when you are already working with an agent and want to switch tasks without leaving the conversation.
+Agent menu triggers require an active agent session. Use skills when you know which workflow you want. Use triggers when you are already working with an agent and want to switch tasks without leaving the conversation.
 
-## How Commands Are Generated
+## How Skills Are Generated
 
-When you run `npx bmad-method install`, the installer reads the manifests for every selected module and writes one command file per agent, workflow, task, and tool. Each file is a short markdown prompt that instructs the AI to load the corresponding source file and follow its instructions.
+When you run `npx bmad-method install`, the installer reads the manifests for every selected module and writes one skill per agent, workflow, task, and tool. Each skill is a directory containing a `SKILL.md` file that instructs the AI to load the corresponding source file and follow its instructions.
 
-The installer uses templates for each command type:
+The installer uses templates for each skill type:
 
-| Command type | What the generated file does |
+| Skill type | What the generated file does |
 | --- | --- |
 | **Agent launcher** | Loads the agent persona file, activates its menu, and stays in character |
-| **Workflow command** | Loads the workflow engine (`workflow.xml`) and passes the workflow config |
-| **Task command** | Loads a standalone task file and follows its instructions |
-| **Tool command** | Loads a standalone tool file and follows its instructions |
+| **Workflow skill** | Loads the workflow config and follows its steps |
+| **Task skill** | Loads a standalone task file and follows its instructions |
+| **Tool skill** | Loads a standalone tool file and follows its instructions |
 
 :::note[Re-running the installer]
-If you add or remove modules, run the installer again. It regenerates all command files to match your current module selection.
+If you add or remove modules, run the installer again. It regenerates all skill files to match your current module selection.
 :::
 
-## Where Command Files Live
+## Where Skill Files Live
 
-The installer writes command files into an IDE-specific directory inside your project. The exact path depends on which IDE you selected during installation.
+The installer writes skill files into an IDE-specific directory inside your project. The exact path depends on which IDE you selected during installation.
 
-| IDE / CLI | Command directory |
+| IDE / CLI | Skills directory |
 | --- | --- |
-| Claude Code | `.claude/commands/` |
-| Cursor | `.cursor/commands/` |
-| Windsurf | `.windsurf/workflows/` |
+| Claude Code | `.claude/skills/` |
+| Cursor | `.cursor/skills/` |
+| Windsurf | `.windsurf/skills/` |
 | Other IDEs | See the installer output for the target path |
 
-All IDEs receive a flat set of command files in their command directory. For example, a Claude Code installation looks like:
+Each skill is a directory containing a `SKILL.md` file. For example, a Claude Code installation looks like:
 
 ```text
-.claude/commands/
-├── bmad-agent-bmm-dev.md
-├── bmad-agent-bmm-pm.md
-├── bmad-bmm-create-prd.md
-├── bmad-editorial-review-prose.md
-├── bmad-help.md
+.claude/skills/
+├── bmad-help/
+│   └── SKILL.md
+├── bmad-create-prd/
+│   └── SKILL.md
+├── bmad-dev/
+│   └── SKILL.md
 └── ...
 ```
 
-The filename determines the slash command name in your IDE. For example, the file `bmad-agent-bmm-dev.md` registers the command `/bmad-agent-bmm-dev`.
+The directory name determines the skill name in your IDE. For example, the directory `bmad-dev/` registers the skill `bmad-dev`.
 
-## How to Discover Your Commands
+## How to Discover Your Skills
 
-Type `/bmad` in your IDE and use autocomplete to browse available commands.
+Type the skill name in your IDE to invoke it. Some platforms require you to enable skills in settings before they appear.
 
-Run `/bmad-help` for context-aware guidance on your next step.
+Run `bmad-help` for context-aware guidance on your next step.
 
 :::tip[Quick discovery]
-The generated command folders in your project are the canonical list. Open them in your file explorer to see every command with its description.
+The generated skill directories in your project are the canonical list. Open them in your file explorer to see every skill with its description.
 :::
 
-## Command Categories
+## Skill Categories
 
-### Agent Commands
+### Agent Skills
 
-Agent commands load a specialized AI persona with a defined role, communication style, and menu of workflows. Once loaded, the agent stays in character and responds to menu triggers.
+Agent skills load a specialized AI persona with a defined role, communication style, and menu of workflows. Once loaded, the agent stays in character and responds to menu triggers.
 
-| Example command | Agent | Role |
+| Example skill | Agent | Role |
 | --- | --- | --- |
-| `/bmad-agent-bmm-dev` | Amelia (Developer) | Implements stories with strict adherence to specs |
-| `/bmad-agent-bmm-pm` | John (Product Manager) | Creates and validates PRDs |
-| `/bmad-agent-bmm-architect` | Winston (Architect) | Designs system architecture |
-| `/bmad-agent-bmm-sm` | Bob (Scrum Master) | Manages sprints and stories |
+| `bmad-dev` | Amelia (Developer) | Implements stories with strict adherence to specs |
+| `bmad-pm` | John (Product Manager) | Creates and validates PRDs |
+| `bmad-architect` | Winston (Architect) | Designs system architecture |
+| `bmad-sm` | Bob (Scrum Master) | Manages sprints and stories |
 
 See [Agents](./agents.md) for the full list of default agents and their triggers.
 
-### Workflow Commands
+### Workflow Skills
 
-Workflow commands run a structured, multi-step process without loading an agent persona first. They load the workflow engine and pass a specific workflow configuration.
+Workflow skills run a structured, multi-step process without loading an agent persona first. They load a workflow configuration and follow its steps.
 
-| Example command | Purpose |
+| Example skill | Purpose |
 | --- | --- |
-| `/bmad-bmm-create-prd` | Create a Product Requirements Document |
-| `/bmad-bmm-create-architecture` | Design system architecture |
-| `/bmad-bmm-dev-story` | Implement a story |
-| `/bmad-bmm-code-review` | Run a code review |
-| `/bmad-bmm-quick-spec` | Define an ad-hoc change (Quick Flow) |
+| `bmad-create-prd` | Create a Product Requirements Document |
+| `bmad-create-architecture` | Design system architecture |
+| `bmad-create-epics-and-stories` | Create epics and stories |
+| `bmad-dev-story` | Implement a story |
+| `bmad-code-review` | Run a code review |
+| `bmad-quick-spec` | Define an ad-hoc change (Quick Flow) |
 
 See [Workflow Map](./workflow-map.md) for the complete workflow reference organized by phase.
 
-### Task and Tool Commands
+### Task and Tool Skills
 
 Tasks and tools are standalone operations that do not require an agent or workflow context.
 
 #### BMad-Help: Your Intelligent Guide
 
-**`/bmad-help`** is your primary interface for discovering what to do next. It's not just a lookup tool — it's an intelligent assistant that:
+**`bmad-help`** is your primary interface for discovering what to do next. It's not just a lookup tool — it's an intelligent assistant that:
 
 - **Inspects your project** to see what's already been done
 - **Understands natural language queries** — ask questions in plain English
@@ -116,36 +118,28 @@ Tasks and tools are standalone operations that do not require an agent or workfl
 **Examples:**
 
 ```
-/bmad-help
-/bmad-help I have a SaaS idea and know all the features. Where do I start?
-/bmad-help What are my options for UX design?
-/bmad-help I'm stuck on the PRD workflow
+bmad-help
+bmad-help I have a SaaS idea and know all the features. Where do I start?
+bmad-help What are my options for UX design?
+bmad-help I'm stuck on the PRD workflow
 ```
 
 #### Other Tasks and Tools
 
-| Example command | Purpose |
+| Example skill | Purpose |
 | --- | --- |
-| `/bmad-shard-doc` | Split a large markdown file into smaller sections |
-| `/bmad-index-docs` | Index project documentation |
-| `/bmad-editorial-review-prose` | Review document prose quality |
+| `bmad-shard-doc` | Split a large markdown file into smaller sections |
+| `bmad-index-docs` | Index project documentation |
+| `bmad-editorial-review-prose` | Review document prose quality |
 
 ## Naming Convention
 
-Command names follow a predictable pattern.
-
-| Pattern | Meaning | Example |
-| --- | --- | --- |
-| `bmad-agent-<module>-<name>` | Agent launcher | `bmad-agent-bmm-dev` |
-| `bmad-<module>-<workflow>` | Workflow command | `bmad-bmm-create-prd` |
-| `bmad-<name>` | Core task or tool | `bmad-help` |
-
-Module codes: `bmm` (Agile suite), `bmb` (Builder), `tea` (Test Architect), `cis` (Creative Intelligence), `gds` (Game Dev Studio). See [Modules](./modules.md) for descriptions.
+All skills use the `bmad-` prefix followed by a descriptive name (e.g., `bmad-dev`, `bmad-create-prd`, `bmad-help`). See [Modules](./modules.md) for available modules.
 
 ## Troubleshooting
 
-**Commands not appearing after install.** Restart your IDE or reload the window. Some IDEs cache the command list and require a refresh to pick up new files.
+**Skills not appearing after install.** Some platforms require skills to be explicitly enabled in settings. Check your IDE's documentation or ask your AI assistant how to enable skills. You may also need to restart your IDE or reload the window.
 
-**Expected commands are missing.** The installer only generates commands for modules you selected. Run `npx bmad-method install` again and verify your module selection. Check that the command files exist in the expected directory.
+**Expected skills are missing.** The installer only generates skills for modules you selected. Run `npx bmad-method install` again and verify your module selection. Check that the skill files exist in the expected directory.
 
-**Commands from a removed module still appear.** The installer does not delete old command files automatically. Remove the stale files from your IDE's command directory, or delete the entire command directory and re-run the installer for a clean set.
+**Skills from a removed module still appear.** The installer does not delete old skill files automatically. Remove the stale directories from your IDE's skills directory, or delete the entire skills directory and re-run the installer for a clean set.

package/docs/reference/testing.md

@@ -26,7 +26,7 @@ Most projects should start with Quinn. If you later need test strategy, quality
 
 Quinn is the built-in QA agent in the BMM (Agile suite) module. It generates working tests quickly using your project's existing test framework -- no configuration or additional installation required.
 
-**Trigger:** `QA` or `bmad-bmm-qa-automate`
+**Trigger:** `QA` or `bmad-qa-generate-e2e-tests`
 
 ### What Quinn Does
 

package/docs/reference/workflow-map.md

@@ -9,9 +9,9 @@ The BMad Method (BMM) is a module in the BMad Ecosystem, targeted at following t
 
 The rationale and concepts come from agile methodologies that have been used across the industry with great success as a mental framework.
 
-If at any time you are unsure what to do, the `/bmad-help` command will help you stay on track or know what to do next. You can always refer to this for reference also - but /bmad-help is fully interactive and much quicker if you have already installed the BMad Method. Additionally, if you are using different modules that have extended the BMad Method or added other complementary non-extension modules - the /bmad-help evolves to know all that is available to give you the best in-the-moment advice.
+If at any time you are unsure what to do, the `bmad-help` skill will help you stay on track or know what to do next. You can always refer to this for reference also - but `bmad-help` is fully interactive and much quicker if you have already installed the BMad Method. Additionally, if you are using different modules that have extended the BMad Method or added other complementary non-extension modules - `bmad-help` evolves to know all that is available to give you the best in-the-moment advice.
 
-Final important note: Every workflow below can be run directly with your tool of choice via slash command or by loading an agent first and using the entry from the agents menu.
+Final important note: Every workflow below can be run directly with your tool of choice via skill or by loading an agent first and using the entry from the agents menu.
 
 <iframe src="/workflow-map-diagram.html" title="BMad Method Workflow Map Diagram" width="100%" height="100%" style="border-radius: 8px; border: 1px solid #334155; min-height: 900px;"></iframe>
 
@@ -26,8 +26,8 @@ Explore the problem space and validate ideas before committing to planning.
 | Workflow                        | Purpose                                                                    | Produces                  |
 | ------------------------------- | -------------------------------------------------------------------------- | ------------------------- |
 | `bmad-brainstorming`            | Brainstorm Project Ideas with guided facilitation of a brainstorming coach | `brainstorming-report.md` |
-| `bmad-bmm-research`             | Validate market, technical, or domain assumptions                          | Research findings         |
-| `bmad-bmm-create-product-brief` | Capture strategic vision                                                   | `product-brief.md`        |
+| `bmad-domain-research`, `bmad-market-research`, `bmad-technical-research` | Validate market, technical, or domain assumptions | Research findings |
+| `bmad-create-product-brief`     | Capture strategic vision                                                   | `product-brief.md`        |
 
 ## Phase 2: Planning
 
@@ -35,8 +35,8 @@ Define what to build and for whom.
 
 | Workflow                    | Purpose                                  | Produces     |
 | --------------------------- | ---------------------------------------- | ------------ |
-| `bmad-bmm-create-prd`       | Define requirements (FRs/NFRs)           | `PRD.md`     |
-| `bmad-bmm-create-ux-design` | Design user experience (when UX matters) | `ux-spec.md` |
+| `bmad-create-prd`    | Define requirements (FRs/NFRs)           | `PRD.md`     |
+| `bmad-create-ux-design`  | Design user experience (when UX matters) | `ux-spec.md` |
 
 ## Phase 3: Solutioning
 
@@ -44,9 +44,9 @@ Decide how to build it and break work into stories.
 
 | Workflow                                  | Purpose                                    | Produces                    |
 | ----------------------------------------- | ------------------------------------------ | --------------------------- |
-| `bmad-bmm-create-architecture`            | Make technical decisions explicit          | `architecture.md` with ADRs |
-| `bmad-bmm-create-epics-and-stories`       | Break requirements into implementable work | Epic files with stories     |
-| `bmad-bmm-check-implementation-readiness` | Gate check before implementation           | PASS/CONCERNS/FAIL decision |
+| `bmad-create-architecture`            | Make technical decisions explicit          | `architecture.md` with ADRs |
+| `bmad-create-epics-and-stories`       | Break requirements into implementable work | Epic files with stories     |
+| `bmad-check-implementation-readiness` | Gate check before implementation           | PASS/CONCERNS/FAIL decision |
 
 ## Phase 4: Implementation
 
@@ -54,13 +54,13 @@ Build it, one story at a time. Coming soon, full phase 4 automation!
 
 | Workflow                   | Purpose                                                                  | Produces                         |
 | -------------------------- | ------------------------------------------------------------------------ | -------------------------------- |
-| `bmad-bmm-sprint-planning` | Initialize tracking (once per project to sequence the dev cycle)         | `sprint-status.yaml`             |
-| `bmad-bmm-create-story`    | Prepare next story for implementation                                    | `story-[slug].md`                |
-| `bmad-bmm-dev-story`       | Implement the story                                                      | Working code + tests             |
-| `bmad-bmm-code-review`     | Validate implementation quality                                          | Approved or changes requested    |
-| `bmad-bmm-correct-course`  | Handle significant mid-sprint changes                                    | Updated plan or re-routing       |
-| `bmad-bmm-automate`        | Generate tests for existing features - Use after a full epic is complete | End to End UI Focused Test suite |
-| `bmad-bmm-retrospective`   | Review after epic completion                                             | Lessons learned                  |
+| `bmad-sprint-planning` | Initialize tracking (once per project to sequence the dev cycle)         | `sprint-status.yaml`          |
+| `bmad-create-story`    | Prepare next story for implementation                                    | `story-[slug].md`             |
+| `bmad-dev-story`       | Implement the story                                                      | Working code + tests          |
+| `bmad-code-review`     | Validate implementation quality                                          | Approved or changes requested |
+| `bmad-correct-course`  | Handle significant mid-sprint changes                                    | Updated plan or re-routing    |
+| `bmad-sprint-status`   | Track sprint progress and story status                                   | Sprint status update          |
+| `bmad-retrospective`   | Review after epic completion                                             | Lessons learned               |
 
 ## Quick Flow (Parallel Track)
 
@@ -68,8 +68,8 @@ Skip phases 1-3 for small, well-understood work.
 
 | Workflow              | Purpose                                    | Produces                                      |
 | --------------------- | ------------------------------------------ | --------------------------------------------- |
-| `bmad-bmm-quick-spec` | Define an ad-hoc change                    | `tech-spec.md` (story file for small changes) |
-| `bmad-bmm-quick-dev`  | Implement from spec or direct instructions | Working code + tests                          |
+| `bmad-quick-spec` | Define an ad-hoc change                    | `tech-spec.md` (story file for small changes) |
+| `bmad-quick-dev`  | Implement from spec or direct instructions | Working code + tests                          |
 
 ## Context Management
 
@@ -84,6 +84,6 @@ Create `project-context.md` to ensure AI agents follow your project's rules and
 **How to create it:**
 
 - **Manually** — Create `_bmad-output/project-context.md` with your technology stack and implementation rules
-- **Generate it** — Run `/bmad-bmm-generate-project-context` to auto-generate from your architecture or codebase
+- **Generate it** — Run `bmad-generate-project-context` to auto-generate from your architecture or codebase
 
 [**Learn more about project-context.md**](../explanation/project-context.md)

package/docs/tutorials/getting-started.md

@@ -37,16 +37,16 @@ Build software faster using AI-powered workflows with specialized agents that gu
 
 ### How to Use BMad-Help
 
-Run it in your AI IDE with just the slash command:
+Run it in your AI IDE by invoking the skill:
 
 ```
-/bmad-help
+bmad-help
 ```
 
 Or combine it with a question for context-aware guidance:
 
 ```
-/bmad-help I have an idea for a SaaS product, I already know all the features I want. where do I get started?
+bmad-help I have an idea for a SaaS product, I already know all the features I want. where do I get started?
 ```
 
 BMad-Help will respond with:
@@ -112,7 +112,7 @@ BMad-Help will detect what you've completed and recommend exactly what to do nex
 :::
 
 :::note[How to Load Agents and Run Workflows]
-Each workflow has a **slash command** you run in your IDE (e.g., `/bmad-bmm-create-prd`). Running a workflow command automatically loads the appropriate agent — you don't need to load agents separately. You can also load an agent directly for general conversation (e.g., `/bmad-agent-bmm-pm` for the PM agent).
+Each workflow has a **skill** you invoke in your IDE (e.g., `/bmad-create-prd`). Running a workflow skill automatically loads the appropriate agent — you don't need to load agents separately. You can also invoke an agent directly for general conversation (e.g., `/bmad-pm` for the PM agent).
 :::
 
 :::caution[Fresh Chats]
@@ -126,35 +126,35 @@ Work through phases 1-3. **Use fresh chats for each workflow.**
 :::tip[Project Context (Optional)]
 Before starting, consider creating `project-context.md` to document your technical preferences and implementation rules. This ensures all AI agents follow your conventions throughout the project.
 
-Create it manually at `_bmad-output/project-context.md` or generate it after architecture using `/bmad-bmm-generate-project-context`. [Learn more](../explanation/project-context.md).
+Create it manually at `_bmad-output/project-context.md` or generate it after architecture using `/bmad-generate-project-context`. [Learn more](../explanation/project-context.md).
 :::
 
 ### Phase 1: Analysis (Optional)
 
 All workflows in this phase are optional:
 - **brainstorming** (`/bmad-brainstorming`) — Guided ideation
-- **research** (`/bmad-bmm-research`) — Market and technical research
-- **create-product-brief** (`/bmad-bmm-create-product-brief`) — Recommended foundation document
+- **research** (`/bmad-research`) — Market and technical research
+- **create-product-brief** (`/bmad-create-product-brief`) — Recommended foundation document
 
 ### Phase 2: Planning (Required)
 
 **For BMad Method and Enterprise tracks:**
-1. Load the **PM agent** (`/bmad-agent-bmm-pm`) in a new chat
-2. Run the `prd` workflow (`/bmad-bmm-create-prd`)
+1. Invoke the **PM agent** (`/bmad-pm`) in a new chat
+2. Run the `bmad-create-prd` workflow (`/bmad-create-prd`)
 3. Output: `PRD.md`
 
 **For Quick Flow track:**
-- Use the `quick-spec` workflow (`/bmad-bmm-quick-spec`) instead of PRD, then skip to implementation
+- Use the `bmad-quick-spec` workflow (`/bmad-quick-spec`) instead of PRD, then skip to implementation
 
 :::note[UX Design (Optional)]
-If your project has a user interface, load the **UX-Designer agent** (`/bmad-agent-bmm-ux-designer`) and run the UX design workflow (`/bmad-bmm-create-ux-design`) after creating your PRD.
+If your project has a user interface, invoke the **UX-Designer agent** (`/bmad-ux-designer`) and run the UX design workflow (`/bmad-create-ux-design`) after creating your PRD.
 :::
 
 ### Phase 3: Solutioning (BMad Method/Enterprise)
 
 **Create Architecture**
-1. Load the **Architect agent** (`/bmad-agent-bmm-architect`) in a new chat
-2. Run `create-architecture` (`/bmad-bmm-create-architecture`)
+1. Invoke the **Architect agent** (`/bmad-architect`) in a new chat
+2. Run `bmad-create-architecture` (`/bmad-create-architecture`)
 3. Output: Architecture document with technical decisions
 
 **Create Epics and Stories**
@@ -163,13 +163,13 @@ If your project has a user interface, load the **UX-Designer agent** (`/bmad-age
 Epics and stories are now created *after* architecture. This produces better quality stories because architecture decisions (database, API patterns, tech stack) directly affect how work should be broken down.
 :::
 
-1. Load the **PM agent** (`/bmad-agent-bmm-pm`) in a new chat
-2. Run `create-epics-and-stories` (`/bmad-bmm-create-epics-and-stories`)
+1. Invoke the **PM agent** (`/bmad-pm`) in a new chat
+2. Run `bmad-create-epics-and-stories` (`/bmad-create-epics-and-stories`)
 3. The workflow uses both PRD and Architecture to create technically-informed stories
 
 **Implementation Readiness Check** *(Highly Recommended)*
-1. Load the **Architect agent** (`/bmad-agent-bmm-architect`) in a new chat
-2. Run `check-implementation-readiness` (`/bmad-bmm-check-implementation-readiness`)
+1. Invoke the **Architect agent** (`/bmad-architect`) in a new chat
+2. Run `bmad-check-implementation-readiness` (`/bmad-check-implementation-readiness`)
 3. Validates cohesion across all planning documents
 
 ## Step 2: Build Your Project
@@ -178,7 +178,7 @@ Once planning is complete, move to implementation. **Each workflow should run in
 
 ### Initialize Sprint Planning
 
-Load the **SM agent** (`/bmad-agent-bmm-sm`) and run `sprint-planning` (`/bmad-bmm-sprint-planning`). This creates `sprint-status.yaml` to track all epics and stories.
+Invoke the **SM agent** (`/bmad-sm`) and run `bmad-sprint-planning` (`/bmad-sprint-planning`). This creates `sprint-status.yaml` to track all epics and stories.
 
 ### The Build Cycle
 
@@ -186,11 +186,11 @@ For each story, repeat this cycle with fresh chats:
 
 | Step | Agent | Workflow       | Command                    | Purpose                            |
 | ---- | ----- | -------------- | -------------------------- | ---------------------------------- |
-| 1    | SM    | `create-story` | `/bmad-bmm-create-story`  | Create story file from epic        |
-| 2    | DEV   | `dev-story`    | `/bmad-bmm-dev-story`     | Implement the story                |
-| 3    | DEV   | `code-review`  | `/bmad-bmm-code-review`   | Quality validation *(recommended)* |
+| 1    | SM    | `bmad-create-story` | `/bmad-create-story`  | Create story file from epic        |
+| 2    | DEV   | `bmad-dev-story`    | `/bmad-dev-story`     | Implement the story                |
+| 3    | DEV   | `bmad-code-review`  | `/bmad-code-review`   | Quality validation *(recommended)* |
 
-After completing all stories in an epic, load the **SM agent** (`/bmad-agent-bmm-sm`) and run `retrospective` (`/bmad-bmm-retrospective`).
+After completing all stories in an epic, invoke the **SM agent** (`/bmad-sm`) and run `bmad-retrospective` (`/bmad-retrospective`).
 
 ## What You've Accomplished
 
@@ -221,16 +221,16 @@ your-project/
 
 | Workflow                              | Command                                    | Agent     | Purpose                                         |
 | ------------------------------------- | ------------------------------------------ | --------- | ----------------------------------------------- |
-| **`help`** ⭐                         | `/bmad-help`                               | Any       | **Your intelligent guide — ask anything!**      |
-| `prd`                                 | `/bmad-bmm-create-prd`                     | PM        | Create Product Requirements Document            |
-| `create-architecture`                 | `/bmad-bmm-create-architecture`            | Architect | Create architecture document                     |
-| `generate-project-context`            | `/bmad-bmm-generate-project-context`       | Analyst   | Create project context file                     |
-| `create-epics-and-stories`       | `/bmad-bmm-create-epics-and-stories`       | PM        | Break down PRD into epics            |
-| `check-implementation-readiness` | `/bmad-bmm-check-implementation-readiness` | Architect | Validate planning cohesion           |
-| `sprint-planning`                | `/bmad-bmm-sprint-planning`                | SM        | Initialize sprint tracking           |
-| `create-story`                   | `/bmad-bmm-create-story`                   | SM        | Create a story file                  |
-| `dev-story`                      | `/bmad-bmm-dev-story`                      | DEV       | Implement a story                    |
-| `code-review`                    | `/bmad-bmm-code-review`                    | DEV       | Review implemented code              |
+| **`bmad-help`** ⭐                    | `/bmad-help`                               | Any       | **Your intelligent guide — ask anything!**      |
+| `bmad-create-prd`                | `/bmad-create-prd`                     | PM        | Create Product Requirements Document            |
+| `bmad-create-architecture`            | `/bmad-create-architecture`            | Architect | Create architecture document                     |
+| `bmad-generate-project-context`       | `/bmad-generate-project-context`           | Analyst   | Create project context file                     |
+| `bmad-create-epics-and-stories`       | `/bmad-create-epics-and-stories`       | PM        | Break down PRD into epics            |
+| `bmad-check-implementation-readiness` | `/bmad-check-implementation-readiness` | Architect | Validate planning cohesion           |
+| `bmad-sprint-planning`                | `/bmad-sprint-planning`                | SM        | Initialize sprint tracking           |
+| `bmad-create-story`                   | `/bmad-create-story`                   | SM        | Create a story file                  |
+| `bmad-dev-story`                      | `/bmad-dev-story`                      | DEV       | Implement a story                    |
+| `bmad-code-review`                    | `/bmad-code-review`                    | DEV       | Review implemented code              |
 
 ## Common Questions
 
@@ -238,10 +238,10 @@ your-project/
 Only for BMad Method and Enterprise tracks. Quick Flow skips from tech-spec to implementation.
 
 **Can I change my plan later?**
-Yes. The SM agent has a `correct-course` workflow (`/bmad-bmm-correct-course`) for handling scope changes.
+Yes. The SM agent has a `bmad-correct-course` workflow (`/bmad-correct-course`) for handling scope changes.
 
 **What if I want to brainstorm first?**
-Load the Analyst agent (`/bmad-agent-bmm-analyst`) and run `brainstorming` (`/bmad-brainstorming`) before starting your PRD.
+Invoke the Analyst agent (`/bmad-analyst`) and run `bmad-brainstorming` (`/bmad-brainstorming`) before starting your PRD.
 
 **Do I need to follow a strict order?**
 Not strictly. Once you learn the flow, you can run workflows directly using the Quick Reference above.

package/docs/zh-cn/404.md

@@ -0,0 +1,9 @@
+---
+title: 页面未找到
+template: splash
+---
+
+
+您查找的页面不存在或已被移动。
+
+[返回首页](./index.md)