wizz-method 1.0.2 → 1.0.3

package/build/artifacts/llms-full.txt

@@ -1,16 +1,16 @@
-# BMAD Method Documentation (Full)
+# WIZZ Method Documentation (Full)
 
 > Complete documentation for AI consumption
-> Generated: 2026-06-19
-> Repository: https://github.com/bmad-code-org/BMAD-METHOD
+> Generated: 2026-06-24
+> Repository: https://github.com/bmad-code-org/WIZZ-METHOD
 
 <document path="index.md">
 The **Wizz Method** is an AI-driven agency development and production method. It follows the work from start to finish: from idea and planning all the way through agent-assisted implementation. It provides specialized agents, guided workflows, and planning that adapts to your project's complexity, whether you're shipping a small fix or an entire platform.
 
 If you're comfortable working with AI assistants like Claude, Cursor, or GitHub Copilot, you're ready to get started.
 
-:::note[Independent fork of the BMad Method]
-The Wizz Method is an independent fork of the [BMad Method](https://github.com/bmad-code-org/BMAD-METHOD), maintained by Wizz! comms. The engine is still BMAD (credited in the repository's `TRADEMARK.md`); the Wizz layer adds agency routing through `wizz-maestro`, a standardized closeout (✅ what I did, ➡️ next step, 🎯 command), and Portuguese-friendly defaults for the agency's skills.
+:::note[Independent fork of the Wizz Method]
+The Wizz Method is an independent fork of the [Wizz Method](https://github.com/bmad-code-org/WIZZ-METHOD), maintained by Wizz! comms. The engine is still BMAD (credited in the repository's `TRADEMARK.md`); the Wizz layer adds agency routing through `wizz-maestro`, a standardized closeout (✅ what I did, ➡️ next step, 🎯 command), and Portuguese-friendly defaults for the agency's skills.
 :::
 
 ## Getting Started
@@ -176,7 +176,7 @@ Wizz-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 **skill** you invoke by name in your IDE (e.g., `wizz-prd`). Your AI tool will recognize the `bmad-*` name and run it — you don't need to load agents separately. You can also invoke an agent skill directly for general conversation (e.g., `wizz-agent-pm` for the PM agent).
+Each workflow has a **skill** you invoke by name in your IDE (e.g., `wizz-prd`). Your AI tool will recognize the `wizz-*` name and run it — you don't need to load agents separately. You can also invoke an agent skill directly for general conversation (e.g., `wizz-agent-pm` for the PM agent).
 :::
 
 :::caution[Fresh Chats]
@@ -336,7 +336,7 @@ Wizz-Help inspects your project, detects what you've completed, and tells you ex
 :::
 
 - **During workflows** — Agents guide you with questions and explanations
-- **Community** — [Discord](https://discord.gg/gk8jAdXWmj) (#bmad-method-help, #report-bugs-and-issues)
+- **Community** — [Discord](https://discord.gg/gk8jAdXWmj) (#wizz-method-help, #report-bugs-and-issues)
 
 ## Key Takeaways
 
@@ -351,7 +351,7 @@ Wizz-Help inspects your project, detects what you've completed, and tells you ex
 Ready to start? Install the Wizz Method, invoke `wizz-help`, and let your intelligent guide lead the way.
 </document>
 
-<document path="how-to/customize-bmad.md">
+<document path="how-to/customize-wizz.md">
 Tailor agent personas, inject domain context, add capabilities, and configure workflow behavior -- all without modifying installed files. Your customizations survive every update.
 
 :::tip[Don't want to hand-author TOML? Use `wizz-customize`]
@@ -368,7 +368,7 @@ The `wizz-customize` skill is a guided authoring helper for the **per-skill agen
 
 :::note[Prerequisites]
 
-- Wizz Method installed in your project (see [How to Install Wizz Method](./install-bmad.md))
+- Wizz Method installed in your project (see [How to Install Wizz Method](./install-wizz.md))
 - Python 3.11+ on your PATH (for the resolver script -- uses stdlib `tomllib`, no `pip install`, no `uv`, no virtualenv)
 - A text editor for TOML files
 :::
@@ -707,7 +707,7 @@ The override wins over whatever each developer answered during their local insta
 | Need | Use |
 |---|---|
 | Add MCP tool calls to every dev workflow | Per-skill: `_wizz/custom/wizz-agent-dev.toml` `persistent_facts` |
-| Add a menu item to an agent | Per-skill: `_wizz/custom/bmad-agent-{role}.toml` `[[agent.menu]]` |
+| Add a menu item to an agent | Per-skill: `_wizz/custom/wizz-agent-{role}.toml` `[[agent.menu]]` |
 | Swap a workflow's output template | Per-skill: `_wizz/custom/{workflow}.toml` scalar override |
 | Rebrand an agent's public descriptor | **Central**: `_wizz/custom/config.toml` `[agents.<code>]` |
 | Add a custom or fictional agent to the roster | **Central**: `_wizz/custom/config.*.toml` new `[agents.<code>]` entry |
@@ -717,7 +717,7 @@ Use both surfaces in the same project as needed.
 
 ## Worked Examples
 
-For enterprise-oriented recipes (shaping an agent across every workflow it dispatches, enforcing org conventions, publishing outputs to Confluence and Jira, customizing the agent roster, and swapping in your own output templates), see [How to Expand the Wizz Method for Your Organization](./expand-bmad-for-your-org.md).
+For enterprise-oriented recipes (shaping an agent across every workflow it dispatches, enforcing org conventions, publishing outputs to Confluence and Jira, customizing the agent roster, and swapping in your own output templates), see [How to Expand the Wizz Method for Your Organization](./expand-wizz-for-your-org.md).
 
 ## Troubleshooting
 
@@ -857,13 +857,13 @@ Pay close attention here to prevent reinventing the wheel or making decisions th
 - **[Established Projects FAQ](../explanation/established-projects-faq.md)** - Common questions about working on established projects
 </document>
 
-<document path="how-to/expand-bmad-for-your-org.md">
+<document path="how-to/expand-wizz-for-your-org.md">
 The Wizz Method's customization surface lets an organization reshape behavior without editing installed files or forking skills. This guide walks through six recipes that cover most enterprise needs.
 
 :::note[Prerequisites]
 
-- Wizz Method installed in your project (see [How to Install Wizz Method](./install-bmad.md))
-- Familiarity with the customization model (see [How to Customize Wizz Method](./customize-bmad.md))
+- Wizz Method installed in your project (see [How to Install Wizz Method](./install-wizz.md))
+- Familiarity with the customization model (see [How to Customize Wizz Method](./customize-wizz.md))
 - Python 3.11+ on PATH (for the resolver — stdlib only, no `pip install`)
 :::
 
@@ -877,7 +877,7 @@ Before picking a recipe, know where your override lands:
 
 | Layer | Where overrides live | Scope |
 |---|---|---|
-| **Agent** (e.g. Amelia, Mary, John) | `[agent]` section of `_wizz/custom/bmad-agent-{role}.toml` | Travels with the persona into **every workflow the agent dispatches** |
+| **Agent** (e.g. Amelia, Mary, John) | `[agent]` section of `_wizz/custom/wizz-agent-{role}.toml` | Travels with the persona into **every workflow the agent dispatches** |
 | **Workflow** (e.g. product-brief, create-prd) | `[workflow]` section of `_wizz/custom/{workflow-name}.toml` | Applies only to that workflow's run |
 | **Central config** | `[agents.*]`, `[core]`, `[modules.*]` in `_wizz/custom/config.toml` | Agent roster (who's available for party-mode, retrospective, elicitation), install-time settings pinned org-wide |
 
@@ -1174,14 +1174,14 @@ Result: Mary loads the regulatory-review rule at persona activation. When the us
 
 ## Troubleshooting
 
-**Override not taking effect?** Check that the file is under `_wizz/custom/` with the exact skill directory name (e.g. `wizz-agent-dev.toml`, not `bmad-dev.toml`). See [How to Customize Wizz Method](./customize-bmad.md#troubleshooting).
+**Override not taking effect?** Check that the file is under `_wizz/custom/` with the exact skill directory name (e.g. `wizz-agent-dev.toml`, not `wizz-dev.toml`). See [How to Customize Wizz Method](./customize-wizz.md#troubleshooting).
 
 **MCP tool name unknown?** Use the exact name the MCP server exposes in the current session. Ask Claude Code to list available MCP tools if unsure. Hardcoded names in `persistent_facts` or `on_complete` won't work if the MCP server isn't connected.
 
 **Pattern doesn't apply to my setup?** The recipes above are illustrative. The underlying machinery (three-layer merge, structural rules, agent-spans-workflow) supports many more patterns; compose them as needed.
 </document>
 
-<document path="how-to/get-answers-about-bmad.md">
+<document path="how-to/get-answers-about-wizz.md">
 Use the Wizz Method's built-in help, source docs, or the community to get answers, from quickest to most thorough.
 
 ## 1. Ask Wizz-Help
@@ -1257,7 +1257,184 @@ _today?_
 _—Claude_
 </document>
 
-<document path="how-to/install-bmad.md">
+<document path="how-to/install-custom-modules.md">
+Use the Wizz Method installer to add modules from the community registry, third-party Git repositories, or local file paths.
+
+## When to Use This
+
+- Installing a community-contributed module from the Wizz Method registry
+- Installing a module from a third-party Git repository (GitHub, GitLab, Bitbucket, self-hosted)
+- Testing a module you are developing locally with Wizz Builder
+- Installing modules from a private or self-hosted Git server
+
+:::note[Prerequisites]
+Requires [Node.js](https://nodejs.org) v20.12+ and `npx` (included with npm). Custom and community modules can be selected during a fresh install or added to an existing installation.
+:::
+
+## Community Modules
+
+Community modules are curated in the [Wizz Method plugins marketplace](https://github.com/wizzcomms/wizz-method). They are organized by category and are pinned to an approved commit for safety.
+
+### 1. Run the Installer
+
+```bash
+npx wizz-method install
+```
+
+### 2. Browse the Community Catalog
+
+After selecting official modules, the installer asks:
+
+```
+Would you like to browse community modules?
+```
+
+Select **Yes** to enter the catalog browser. You can:
+
+- Browse by category
+- View featured modules
+- View all available modules
+- Search by keyword
+
+### 3. Select Modules
+
+Pick modules from any category. The installer shows descriptions, versions, and trust tiers. Already-installed modules are pre-checked for update.
+
+### 4. Continue with Installation
+
+After selecting community modules, the installer proceeds to custom sources, then tool/IDE configuration and the rest of the install flow.
+
+## Custom Sources (Git URLs and Local Paths)
+
+Custom modules can come from any Git repository or a local directory on your machine. The installer resolves the source, analyzes the module structure, and installs it alongside your other modules.
+
+### Interactive Installation
+
+During installation, after the community module step, the installer asks:
+
+```
+Would you like to install from a custom source (Git URL or local path)?
+```
+
+Select **Yes**, then provide a source:
+
+| Input Type            | Example                                           |
+| --------------------- | ------------------------------------------------- |
+| HTTPS URL (any host)  | `https://github.com/org/repo`                     |
+| HTTP URL (any host)   | `http://host/org/repo`                            |
+| HTTPS URL with subdir | `https://github.com/org/repo/tree/main/my-module` |
+| SSH URL               | `git@github.com:org/repo.git`                     |
+| Local path            | `/Users/me/projects/my-module`                    |
+| Local path with tilde | `~/projects/my-module`                            |
+
+The installer clones the repository (for URLs) or reads directly from disk (for local paths), then presents the discovered modules for selection.
+
+### Non-Interactive Installation
+
+Use the `--custom-source` flag to install custom modules from the command line:
+
+```bash
+npx wizz-method install \
+  --directory . \
+  --custom-source /path/to/my-module \
+  --tools claude-code \
+  --yes
+```
+
+When `--custom-source` is provided without `--modules`, only core and the custom modules are installed. To include official modules as well, add `--modules`:
+
+```bash
+npx wizz-method install \
+  --directory . \
+  --modules bmm \
+  --custom-source https://gitlab.com/myorg/my-module \
+  --tools claude-code \
+  --yes
+```
+
+Multiple sources can be comma-separated:
+
+```bash
+--custom-source /path/one,https://github.com/org/repo,/path/two
+```
+
+## How Module Discovery Works
+
+The installer uses two modes to find installable modules in a source:
+
+| Mode      | Trigger                                           | Behavior                                                                                     |
+| --------- | ------------------------------------------------- | -------------------------------------------------------------------------------------------- |
+| Discovery | Source contains `.claude-plugin/marketplace.json` | Lists all plugins from the manifest; you pick which to install                               |
+| Direct    | No marketplace.json found                         | Scans the directory for skills (subdirectories with `SKILL.md`), resolves as a single module |
+
+Discovery mode is typical for published modules. Direct mode is convenient when pointing at a skills directory during local development.
+
+:::note[About `.claude-plugin/`]
+The `.claude-plugin/marketplace.json` path is a standard convention adopted across multiple AI tool installers for plugin discoverability. It does not require Claude, does not use Claude APIs, and has no effect on which AI tool you use. Any module with this file can be discovered by any installer that follows the convention.
+:::
+
+## Local Development Workflow
+
+If you are building a module with [Wizz Builder](https://github.com/wizzcomms/wizz-method), you can install it directly from your working directory:
+
+```bash
+npx wizz-method install \
+  --directory ~/my-project \
+  --custom-source ~/my-module-repo/skills \
+  --tools claude-code \
+  --yes
+```
+
+Local sources are referenced by path, not copied to a cache. When you update your module source and reinstall, the installer picks up the latest changes.
+
+:::caution[Source Removal]
+If you delete the local source directory after installation, the installed module files in `_wizz/` are preserved. The module will be skipped during updates until the source path is restored.
+:::
+
+## What You Get
+
+After installation, custom modules appear in `_wizz/` alongside official modules:
+
+```
+your-project/
+├── _wizz/
+│   ├── core/              # Built-in core module
+│   ├── bmm/               # Official module (if selected)
+│   ├── my-module/         # Your custom module
+│   │   ├── my-skill/
+│   │   │   └── SKILL.md
+│   │   └── module-help.csv
+│   └── _config/
+│       └── manifest.yaml  # Tracks all modules, versions, and sources
+└── ...
+```
+
+The manifest records the source of each custom module (`repoUrl` for Git sources, `localPath` for local sources) so that quick updates can locate the source again.
+
+## Updating Custom Modules
+
+Custom modules participate in the normal update flow:
+
+- **Quick update** (`--action quick-update`): Refreshes all modules from their original sources. Git-based modules are re-fetched; local modules are re-read from their source path.
+- **Full update**: Re-runs module selection so you can add or remove custom modules.
+
+## Creating Your Own Modules
+
+Use [Wizz Builder](https://github.com/wizzcomms/wizz-method) to create modules that others can install:
+
+1. Run `bmad-module-builder` to scaffold your module structure
+2. Add skills, agents, and workflows with the various wizz builder tools
+3. Publish to a Git repository or share the folder collection
+4. Others install with `--custom-source <your-repo-url>`
+
+For modules to support discovery mode, include a `.claude-plugin/marketplace.json` in your repository root (this is a cross-tool convention, not Claude-specific). See the [Wizz Builder documentation](https://github.com/wizzcomms/wizz-method) for the marketplace.json format.
+
+:::tip[Testing Locally First]
+During development, install your module with a local path to iterate quickly before publishing to a Git repository.
+:::
+</document>
+
+<document path="how-to/install-wizz.md">
 Use `npx wizz-method install` to set up the Wizz Method in your project. One command handles first installs, upgrades, channel switching, and scripted CI runs. This page covers all of it.
 
 ## When to Use This
@@ -1318,7 +1495,7 @@ Channels are per-module. You can run bmb on `next` while leaving cis on `stable`
 
 ### Axis 2: installer binary version
 
-The `bmad-method` npm package itself has two dist-tags:
+The `wizz-method` npm package itself has two dist-tags:
 
 | Command                               | What you get                                                      |
 | ------------------------------------- | ----------------------------------------------------------------- |
@@ -1333,7 +1510,7 @@ They're stapled to the installer binary you ran:
 
 - `npx wizz-method install` → latest stable core and bmm
 - `npx bmad-method@next install` → prerelease core and bmm
-- `node /path/to/local-checkout/tools/installer/bmad-cli.js install` → whatever your local checkout has
+- `node /path/to/local-checkout/tools/installer/wizz-cli.js install` → whatever your local checkout has
 
 `--pin bmm=v6.3.0` and `--next=bmm` are silently ineffective against bundled modules, and the installer warns you when you try. A future release extracts bmm from the installer package; once that ships, bmm gets a proper channel selector like bmb has today.
 
@@ -1468,7 +1645,7 @@ npx wizz-method install --list-options bmm
 The legacy core shortcuts (`--user-name`, `--output-folder`, etc.) still work and remain documented for backward compatibility, but `--set core.user_name=...` is equivalent.
 
 :::note[Works with quick-update]
-`--set` is a post-install patch, so it applies the same way regardless of action type. Under `bmad install --action quick-update` (or `--yes` against an existing install, where quick-update is the default), `--set` patches the central config files at the end just like a regular install.
+`--set` is a post-install patch, so it applies the same way regardless of action type. Under `wizz install --action quick-update` (or `--yes` against an existing install, where quick-update is the default), `--set` patches the central config files at the end just like a regular install.
 :::
 
 :::caution[Rate limit on shared IPs]
@@ -1519,186 +1696,9 @@ Pinned installs don't upgrade. Quick-update applies patches and minors on stable
 bmm is a bundled module — `--pin` and `--next=` don't apply. Use `npx bmad-method@next install` for a prerelease core/bmm, or check out the bmad-bmm repo and run the installer locally to get unreleased changes.
 </document>
 
-<document path="how-to/install-custom-modules.md">
-Use the Wizz Method installer to add modules from the community registry, third-party Git repositories, or local file paths.
-
-## When to Use This
-
-- Installing a community-contributed module from the Wizz Method registry
-- Installing a module from a third-party Git repository (GitHub, GitLab, Bitbucket, self-hosted)
-- Testing a module you are developing locally with Wizz Builder
-- Installing modules from a private or self-hosted Git server
-
-:::note[Prerequisites]
-Requires [Node.js](https://nodejs.org) v20.12+ and `npx` (included with npm). Custom and community modules can be selected during a fresh install or added to an existing installation.
-:::
-
-## Community Modules
-
-Community modules are curated in the [Wizz Method plugins marketplace](https://github.com/wizzcomms/wizz-method). They are organized by category and are pinned to an approved commit for safety.
-
-### 1. Run the Installer
-
-```bash
-npx wizz-method install
-```
-
-### 2. Browse the Community Catalog
-
-After selecting official modules, the installer asks:
-
-```
-Would you like to browse community modules?
-```
-
-Select **Yes** to enter the catalog browser. You can:
-
-- Browse by category
-- View featured modules
-- View all available modules
-- Search by keyword
-
-### 3. Select Modules
-
-Pick modules from any category. The installer shows descriptions, versions, and trust tiers. Already-installed modules are pre-checked for update.
-
-### 4. Continue with Installation
-
-After selecting community modules, the installer proceeds to custom sources, then tool/IDE configuration and the rest of the install flow.
-
-## Custom Sources (Git URLs and Local Paths)
-
-Custom modules can come from any Git repository or a local directory on your machine. The installer resolves the source, analyzes the module structure, and installs it alongside your other modules.
-
-### Interactive Installation
-
-During installation, after the community module step, the installer asks:
-
-```
-Would you like to install from a custom source (Git URL or local path)?
-```
-
-Select **Yes**, then provide a source:
-
-| Input Type            | Example                                           |
-| --------------------- | ------------------------------------------------- |
-| HTTPS URL (any host)  | `https://github.com/org/repo`                     |
-| HTTP URL (any host)   | `http://host/org/repo`                            |
-| HTTPS URL with subdir | `https://github.com/org/repo/tree/main/my-module` |
-| SSH URL               | `git@github.com:org/repo.git`                     |
-| Local path            | `/Users/me/projects/my-module`                    |
-| Local path with tilde | `~/projects/my-module`                            |
-
-The installer clones the repository (for URLs) or reads directly from disk (for local paths), then presents the discovered modules for selection.
-
-### Non-Interactive Installation
-
-Use the `--custom-source` flag to install custom modules from the command line:
-
-```bash
-npx wizz-method install \
-  --directory . \
-  --custom-source /path/to/my-module \
-  --tools claude-code \
-  --yes
-```
-
-When `--custom-source` is provided without `--modules`, only core and the custom modules are installed. To include official modules as well, add `--modules`:
-
-```bash
-npx wizz-method install \
-  --directory . \
-  --modules bmm \
-  --custom-source https://gitlab.com/myorg/my-module \
-  --tools claude-code \
-  --yes
-```
-
-Multiple sources can be comma-separated:
-
-```bash
---custom-source /path/one,https://github.com/org/repo,/path/two
-```
-
-## How Module Discovery Works
-
-The installer uses two modes to find installable modules in a source:
-
-| Mode      | Trigger                                           | Behavior                                                                                     |
-| --------- | ------------------------------------------------- | -------------------------------------------------------------------------------------------- |
-| Discovery | Source contains `.claude-plugin/marketplace.json` | Lists all plugins from the manifest; you pick which to install                               |
-| Direct    | No marketplace.json found                         | Scans the directory for skills (subdirectories with `SKILL.md`), resolves as a single module |
-
-Discovery mode is typical for published modules. Direct mode is convenient when pointing at a skills directory during local development.
-
-:::note[About `.claude-plugin/`]
-The `.claude-plugin/marketplace.json` path is a standard convention adopted across multiple AI tool installers for plugin discoverability. It does not require Claude, does not use Claude APIs, and has no effect on which AI tool you use. Any module with this file can be discovered by any installer that follows the convention.
-:::
-
-## Local Development Workflow
-
-If you are building a module with [Wizz Builder](https://github.com/wizzcomms/wizz-method), you can install it directly from your working directory:
-
-```bash
-npx wizz-method install \
-  --directory ~/my-project \
-  --custom-source ~/my-module-repo/skills \
-  --tools claude-code \
-  --yes
-```
-
-Local sources are referenced by path, not copied to a cache. When you update your module source and reinstall, the installer picks up the latest changes.
-
-:::caution[Source Removal]
-If you delete the local source directory after installation, the installed module files in `_wizz/` are preserved. The module will be skipped during updates until the source path is restored.
-:::
-
-## What You Get
-
-After installation, custom modules appear in `_wizz/` alongside official modules:
-
-```
-your-project/
-├── _wizz/
-│   ├── core/              # Built-in core module
-│   ├── bmm/               # Official module (if selected)
-│   ├── my-module/         # Your custom module
-│   │   ├── my-skill/
-│   │   │   └── SKILL.md
-│   │   └── module-help.csv
-│   └── _config/
-│       └── manifest.yaml  # Tracks all modules, versions, and sources
-└── ...
-```
-
-The manifest records the source of each custom module (`repoUrl` for Git sources, `localPath` for local sources) so that quick updates can locate the source again.
-
-## Updating Custom Modules
-
-Custom modules participate in the normal update flow:
-
-- **Quick update** (`--action quick-update`): Refreshes all modules from their original sources. Git-based modules are re-fetched; local modules are re-read from their source path.
-- **Full update**: Re-runs module selection so you can add or remove custom modules.
-
-## Creating Your Own Modules
-
-Use [Wizz Builder](https://github.com/wizzcomms/wizz-method) to create modules that others can install:
-
-1. Run `bmad-module-builder` to scaffold your module structure
-2. Add skills, agents, and workflows with the various bmad builder tools
-3. Publish to a Git repository or share the folder collection
-4. Others install with `--custom-source <your-repo-url>`
-
-For modules to support discovery mode, include a `.claude-plugin/marketplace.json` in your repository root (this is a cross-tool convention, not Claude-specific). See the [Wizz Builder documentation](https://github.com/wizzcomms/wizz-method) for the marketplace.json format.
-
-:::tip[Testing Locally First]
-During development, install your module with a local path to iterate quickly before publishing to a Git repository.
-:::
-</document>
-
 <document path="how-to/non-interactive-installation.md">
 :::note[This page has moved]
-Headless and CI install flags, channel selection, and pinning now live in the unified [How to Install Wizz Method](./install-bmad.md) guide. Jump to the [Headless / CI installs](./install-bmad.md#headless-ci-installs) section for the flag reference and copy-paste recipes.
+Headless and CI install flags, channel selection, and pinning now live in the unified [How to Install Wizz Method](./install-wizz.md) guide. Jump to the [Headless / CI installs](./install-wizz.md#headless-ci-installs) section for the flag reference and copy-paste recipes.
 :::
 </document>
 
@@ -2001,7 +2001,7 @@ Use the Wizz Method installer to upgrade from v4 to v6, which includes automatic
 
 ## When to Use This
 
-- You have Wizz Method v4 installed (`.bmad-method` folder)
+- You have Wizz Method v4 installed (`.wizz-method` folder)
 - You want to migrate to the new v6 architecture
 - You have existing planning artifacts to preserve
 
@@ -2015,20 +2015,20 @@ Use the Wizz Method installer to upgrade from v4 to v6, which includes automatic
 
 ### 1. Run the Installer
 
-Follow the [Installer Instructions](./install-bmad.md).
+Follow the [Installer Instructions](./install-wizz.md).
 
 ### 2. Handle Legacy Installation
 
 When v4 is detected, you can:
 
-- Allow the installer to back up and remove `.bmad-method`
+- Allow the installer to back up and remove `.wizz-method`
 - Exit and handle cleanup manually
 
-If you named your bmad method folder something else - you will need to manually remove the folder yourself.
+If you named your wizz method folder something else - you will need to manually remove the folder yourself.
 
 ### 3. Clean Up IDE Skills
 
-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:
+Manually remove legacy v4 IDE commands/skills - for example if you have Claude Code, look for any nested folders that start with wizz and remove them:
 
 - `.claude/commands/`
 
@@ -2077,11 +2077,11 @@ your-project/
 
 | v4 Module                     | v6 Status                                 |
 | ----------------------------- | ----------------------------------------- |
-| `.bmad-2d-phaser-game-dev`    | Integrated into BMGD Module               |
-| `.bmad-2d-unity-game-dev`     | Integrated into BMGD Module               |
-| `.bmad-godot-game-dev`        | Integrated into BMGD Module               |
-| `.bmad-infrastructure-devops` | Deprecated — new DevOps agent coming soon |
-| `.bmad-creative-writing`      | Not adapted — new v6 module coming soon   |
+| `.wizz-2d-phaser-game-dev`    | Integrated into BMGD Module               |
+| `.wizz-2d-unity-game-dev`     | Integrated into BMGD Module               |
+| `.wizz-godot-game-dev`        | Integrated into BMGD Module               |
+| `.wizz-infrastructure-devops` | Deprecated — new DevOps agent coming soon |
+| `.wizz-creative-writing`      | Not adapted — new v6 module coming soon   |
 
 ## Key Changes
 
@@ -2560,7 +2560,7 @@ The Wizz Method's agent model rests on three primitives that compose:
 | Primitive | What it provides | Where it lives |
 |---|---|---|
 | **Skill** | Capability — a discrete thing the assistant can do (brainstorm, draft a PRD, implement a story) | `.claude/skills/{skill-name}/SKILL.md` (or your IDE's equivalent) |
-| **Named agent** | Persona continuity — a recognizable identity that wraps a menu of related skills with consistent voice, principles, and visual cues | Skills whose directory starts with `bmad-agent-*` |
+| **Named agent** | Persona continuity — a recognizable identity that wraps a menu of related skills with consistent voice, principles, and visual cues | Skills whose directory starts with `wizz-agent-*` |
 | **Customization** | Makes it yours — overrides that reshape an agent's behavior, add MCP integrations, swap templates, layer in org conventions | `_wizz/custom/{skill-name}.toml` (committed team overrides) and `.user.toml` (personal, gitignored) |
 
 Pull any leg away and the experience collapses:
@@ -2617,7 +2617,7 @@ Named agents add structure without closing off freedom. The persona stays consis
 
 The customization model is what lets this scale beyond a single developer.
 
-Every agent ships a `customize.toml` with sensible defaults. Teams commit overrides to `_wizz/custom/bmad-agent-{role}.toml`. Individuals can layer personal preferences in `.user.toml` (gitignored). The resolver merges all three at activation time with predictable structural rules.
+Every agent ships a `customize.toml` with sensible defaults. Teams commit overrides to `_wizz/custom/wizz-agent-{role}.toml`. Individuals can layer personal preferences in `.user.toml` (gitignored). The resolver merges all three at activation time with predictable structural rules.
 
 Most users never hand-author these files. The `wizz-customize` skill walks through picking the target, choosing agent vs workflow scope, authoring the override, and verifying the merge — so the customization surface stays accessible to anyone who understands their intent, not just those fluent in TOML.
 
@@ -2627,8 +2627,8 @@ There's also a second customization surface for *cross-cutting* concerns: the ce
 
 For the full customization surface and worked examples, see:
 
-- [How to Customize Wizz Method](../how-to/customize-bmad.md) — the reference for what's customizable and how merge works
-- [How to Expand Wizz Method for Your Organization](../how-to/expand-bmad-for-your-org.md) — five worked recipes spanning agent-wide rules, workflow conventions, external publishing, template swaps, and agent roster customization
+- [How to Customize Wizz Method](../how-to/customize-wizz.md) — the reference for what's customizable and how merge works
+- [How to Expand Wizz Method for Your Organization](../how-to/expand-wizz-for-your-org.md) — five worked recipes spanning agent-wide rules, workflow conventions, external publishing, template swaps, and agent roster customization
 - `wizz-customize` skill — the guided authoring helper that turns intent into a correctly-placed, verified override file
 
 ## The Bigger Idea
@@ -2701,7 +2701,7 @@ Start a party with `--mode subagent` (or `auto`, `agent-team`, `session`) to ove
 
 ## Custom parties
 
-Out of the box, a party uses your installed Wizz Method agents. The larger use is building your own cast from any set of personas you can describe, then saving it to reuse. You author a party through the same skill. It detects whether you want to run one or build one, and writes the result to your overrides through [wizz-customize](../how-to/customize-bmad.md).
+Out of the box, a party uses your installed Wizz Method agents. The larger use is building your own cast from any set of personas you can describe, then saving it to reuse. You author a party through the same skill. It detects whether you want to run one or build one, and writes the result to your overrides through [wizz-customize](../how-to/customize-wizz.md).
 
 Party mode is customizable like every Wizz Method skill. Run `/wizz-customize wizz-party-mode` to set its defaults directly: pin any group you've built as the default party so it loads without a flag, choose which mode it starts in, and set any house rules the room should hold for the whole session.
 
@@ -3427,7 +3427,7 @@ The core module includes 12 built-in tools — specs, reviews, brainstorming, cu
 
 ## Naming Convention
 
-All skills use the `bmad-` prefix followed by a descriptive name (e.g., `wizz-agent-dev`, `wizz-prd`, `wizz-help`). See [Modules](./modules.md) for available modules.
+All skills use the `wizz-` prefix followed by a descriptive name (e.g., `wizz-agent-dev`, `wizz-prd`, `wizz-help`). See [Modules](./modules.md) for available modules.
 
 ## Troubleshooting
 
@@ -3752,7 +3752,7 @@ Run both `wizz-review-adversarial-general` and `wizz-review-edge-case-hunter` to
 
 **Output:** TOML override files under `_wizz/custom/`
 
-For a detailed guide on customizing the Wizz Method, see [How to Customize Wizz Method](../how-to/customize-bmad.md).
+For a detailed guide on customizing the Wizz Method, see [How to Customize Wizz Method](../how-to/customize-wizz.md).
 </document>
 
 <document path="reference/modules.md">
@@ -3783,7 +3783,7 @@ AI-powered tools for structured creativity, ideation, and innovation during earl
 
 - **Code:** `cis`
 - **npm:** [`bmad-creative-intelligence-suite`](https://www.npmjs.com/package/bmad-creative-intelligence-suite)
-- **GitHub:** [bmad-code-org/bmad-module-creative-intelligence-suite](https://github.com/bmad-code-org/bmad-module-creative-intelligence-suite)
+- **GitHub:** [bmad-code-org/wizz-module-creative-intelligence-suite](https://github.com/bmad-code-org/wizz-module-creative-intelligence-suite)
 
 **Provides:**
 
@@ -3798,7 +3798,7 @@ Structured game development workflows adapted for Unity, Unreal, Godot, and cust
 
 - **Code:** `gds`
 - **npm:** [`bmad-game-dev-studio`](https://www.npmjs.com/package/bmad-game-dev-studio)
-- **GitHub:** [bmad-code-org/bmad-module-game-dev-studio](https://github.com/bmad-code-org/bmad-module-game-dev-studio)
+- **GitHub:** [bmad-code-org/wizz-module-game-dev-studio](https://github.com/bmad-code-org/wizz-module-game-dev-studio)
 
 **Provides:**
 

package/build/artifacts/llms.txt

@@ -1,15 +1,15 @@
-# BMAD Method Documentation
+# WIZZ Method Documentation
 
 > AI-driven agile development with specialized agents and workflows that scale from bug fixes to enterprise platforms.
 
 Documentation: http://localhost:3000
-Repository: https://github.com/bmad-code-org/BMAD-METHOD
+Repository: https://github.com/bmad-code-org/WIZZ-METHOD
 Full docs: http://localhost:3000/llms-full.txt
 
 ## Quick Start
 
-- **[Getting Started](http://localhost:3000/tutorials/getting-started/)** - Tutorial: install and learn how BMad works
-- **[Installation](http://localhost:3000/how-to/install-bmad/)** - How to install BMad Method
+- **[Getting Started](http://localhost:3000/tutorials/getting-started/)** - Tutorial: install and learn how Wizz works
+- **[Installation](http://localhost:3000/how-to/install-wizz/)** - How to install Wizz Method
 
 ## Core Concepts