wizz-method 1.0.0 → 1.0.2

package/src/bmm-skills/1-analysis/{bmad-prfaq → wizz-prfaq}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: bmad-prfaq
+name: wizz-prfaq
 description: Working Backwards PRFAQ challenge to forge product concepts. Use when the user requests to 'create a PRFAQ', 'work backwards', or 'run the PRFAQ challenge'.
 ---
 
@@ -30,13 +30,13 @@ The PRFAQ forces customer-first clarity: write the press release announcing the
 
 ### Step 1: Resolve the Workflow Block
 
-Run: `python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`
+Run: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow`
 
 **If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
 
 1. `{skill-root}/customize.toml` — defaults
-2. `{project-root}/_bmad/custom/{skill-name}.toml` — team overrides
-3. `{project-root}/_bmad/custom/{skill-name}.user.toml` — personal overrides
+2. `{project-root}/_wizz/custom/{skill-name}.toml` — team overrides
+3. `{project-root}/_wizz/custom/{skill-name}.user.toml` — personal overrides
 
 Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
 
@@ -50,7 +50,7 @@ Treat every entry in `{workflow.persistent_facts}` as foundational context you c
 
 ### Step 4: Load Config
 
-Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+Load config from `{project-root}/_wizz/bmm/config.yaml` and resolve:
 - Use `{user_name}` for greeting
 - Use `{communication_language}` for all communications
 - Use `{document_output_language}` for output documents
@@ -107,7 +107,7 @@ When the user gets stuck, offer concrete suggestions based on what they've share
 
 **Fast-track:** If the user provides all four essentials in their opening message (or via structured input), acknowledge and confirm understanding, then move directly to document creation and Stage 2 without extended discovery.
 
-**Graceful redirect:** If after 2-3 exchanges the user can't articulate a customer or problem, don't force it — suggest the idea may need more exploration first and recommend they invoke the `bmad-brainstorming` skill to develop it further.
+**Graceful redirect:** If after 2-3 exchanges the user can't articulate a customer or problem, don't force it — suggest the idea may need more exploration first and recommend they invoke the `wizz-brainstorming` skill to develop it further.
 
 **Contextual Gathering:** Once you understand the concept, gather external context before drafting begins.
 

package/src/bmm-skills/1-analysis/{bmad-prfaq → wizz-prfaq}/customize.toml

@@ -1,6 +1,6 @@
 # DO NOT EDIT -- overwritten on every update.
 #
-# Workflow customization surface for bmad-prfaq. Mirrors the
+# Workflow customization surface for wizz-prfaq. Mirrors the
 # agent customization shape under the [workflow] namespace.
 
 [workflow]

package/src/bmm-skills/1-analysis/{bmad-prfaq → wizz-prfaq}/references/verdict.md

@@ -78,6 +78,6 @@ purpose: "Token-efficient context for downstream PRD creation"
 
 This is the terminal stage. If the user wants to revise, loop back to the relevant stage. Otherwise, the workflow is done.
 
-Run: `python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete`
+Run: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete`
 
 If the resolved `workflow.on_complete` is non-empty, follow it as the final terminal instruction before exiting.

package/src/bmm-skills/1-analysis/{bmad-product-brief → wizz-product-brief}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: bmad-product-brief
+name: wizz-product-brief
 description: Create, update, or validate a product brief. Use when the user wants help producing, editing, or validating a brief.
 ---
 
@@ -11,15 +11,15 @@ You are not in a hurry. You will not do the thinking for them. Coach, do not qui
 
 Briefs produced here are honest, right-sized to purpose, and built for what comes next — they do not pad, they do not fabricate moats, they surface what is unknown alongside what is known - the user must feel that it is their own creation.
 
-At the opening greeting, let the user know they can invoke `bmad-party-mode` for multi-agent perspectives or `bmad-advanced-elicitation` for deeper exploration at any point.
+At the opening greeting, let the user know they can invoke `wizz-party-mode` for multi-agent perspectives or `wizz-advanced-elicitation` for deeper exploration at any point.
 
 ## On Activation
 
-1. Resolve customization: `python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}/customize.toml` directly and use defaults.
+1. Resolve customization: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}/customize.toml` directly and use defaults.
 2. Execute each entry in `{workflow.activation_steps_prepend}` in order.
 3. Treat every entry in `{workflow.persistent_facts}` as foundational context for the rest of the run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.
 4. `{workflow.external_sources}` is an org-configured registry of internal tools (knowledge bases, MCP tools); consult them alongside generic web research on the same triggers in `## Discovery`, org tools preferred when their directive matches. If a named tool is unavailable at runtime, fall back to standard behavior and note the gap when relevant.
-5. Load `{project-root}/_bmad/bmm/config.yaml` (and `config.user.yaml` if present). Resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{planning_artifacts}`, `{project_name}`, `{date}`.
+5. Load `{project-root}/_wizz/bmm/config.yaml` (and `config.user.yaml` if present). Resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{planning_artifacts}`, `{project_name}`, `{date}`.
 6. Greet `{user_name}` in `{communication_language}` — and stay in `{communication_language}` for every turn for the entire run, not just the greeting. Detect intent (create / update / validate). If interactive and intent is unclear, ask; for headless behavior see `## Headless Mode`.
 
 Execute each entry in `{workflow.activation_steps_append}` in order.
@@ -64,7 +64,7 @@ Omit keys for artifacts that were not produced.
 
 ## Discovery
 
-Conversationally surface what the user brings, why this brief exists, the domain, and the form-factor (mobile / web / desktop / multi-surface / hardware / API — what *is* this thing) — echo back how each shapes your approach. Open with space for the full picture: invite a brain dump and ask up front for any source material they already have (memo, deck, transcript, prior brief, slack thread). Read what exists first; ask only what is missing. After the dump, a simple "anything else?" often surfaces what they almost forgot. Drill into specifics only after the broad shape is on the table; premature granular questions interrupt the dump and miss the room. Get a read on stakes early (passion project, internal pitch, investor input, public launch), and let that calibrate how hard you push. During the dump, spawn web-research subagents to ground the picture — landscape, comparables, current state — AI especially, where training data ages by the week. Subagent searches; parent gets a digest. Deep work (full market sizing, exhaustive teardowns) → suggest `bmad-market-research` or `bmad-domain-research`.
+Conversationally surface what the user brings, why this brief exists, the domain, and the form-factor (mobile / web / desktop / multi-surface / hardware / API — what *is* this thing) — echo back how each shapes your approach. Open with space for the full picture: invite a brain dump and ask up front for any source material they already have (memo, deck, transcript, prior brief, slack thread). Read what exists first; ask only what is missing. After the dump, a simple "anything else?" often surfaces what they almost forgot. Drill into specifics only after the broad shape is on the table; premature granular questions interrupt the dump and miss the room. Get a read on stakes early (passion project, internal pitch, investor input, public launch), and let that calibrate how hard you push. During the dump, spawn web-research subagents to ground the picture — landscape, comparables, current state — AI especially, where training data ages by the week. Subagent searches; parent gets a digest. Deep work (full market sizing, exhaustive teardowns) → suggest `wizz-market-research` or `wizz-domain-research`.
 
 Once stakes are read and the dump is captured, offer the working mode in the user's language:
 
@@ -87,5 +87,5 @@ The workspace persists; stop and resume freely. The opener's philosophy (not in
 1. Decision log audit + addendum review: the user ends this step with an explicit, shared accounting of how the meaningful contents of `.decision-log.md` were handled — captured in the brief, captured in `addendum.md` (which may already hold detail captured during the conversation — see `## Constraints` for what belongs there), or set aside as process noise.
 2. Polish: apply each entry in `{workflow.doc_standards}` (a `skill:`, `file:`, or plain-text directive) to `brief.md` (and `addendum.md` if it exists). Run passes as parallel subagents - apply all doc standards to `brief.md` first, then `addendum.md` so we present a high-quality draft for the user to review and finalize.
 3. External handoffs: execute each entry in `{workflow.external_handoffs}` to route artifacts beyond local files (Confluence, Notion, ticket systems, etc.) — each directive names the MCP tool and the fields it needs. Invoke the tool, capture any URLs or IDs returned, and surface them in the user message. If a named tool is unavailable, skip that handoff and flag it; local files always exist regardless.
-4. Tell the user it is ready: local paths and external destinations (URLs returned from handoffs). Invoke `bmad-help` to suggest what next steps make sense in the bmad method ecosystem.
+4. Tell the user it is ready: local paths and external destinations (URLs returned from handoffs). Invoke `wizz-help` to suggest what next steps make sense in the bmad method ecosystem.
 5. Run `{workflow.on_complete}` if non-empty. Treat a string scalar as a single instruction and an array as a sequence of instructions executed in order.

package/src/bmm-skills/1-analysis/{bmad-product-brief → wizz-product-brief}/customize.toml

@@ -1,10 +1,10 @@
 # DO NOT EDIT -- overwritten on every update.
 #
-# Workflow customization surface for bmad-product-brief.
+# Workflow customization surface for wizz-product-brief.
 #
 # Override files (not edited here):
-#   {project-root}/_bmad/custom/bmad-product-brief.toml         (team)
-#   {project-root}/_bmad/custom/bmad-product-brief.user.toml    (personal)
+#   {project-root}/_wizz/custom/wizz-product-brief.toml         (team)
+#   {project-root}/_wizz/custom/wizz-product-brief.user.toml    (personal)
 
 [workflow]
 
@@ -24,7 +24,7 @@ activation_steps_append = []
 # Each entry is either a literal sentence, a skill prefixed with `skill:`, or a `file:`-prefixed path/glob
 # whose contents are loaded as facts.
 #
-# Default loads project-context.md if bmad-generate-project-context has produced one — this gives
+# Default loads project-context.md if wizz-generate-project-context has produced one — this gives
 # the facilitator persistent awareness of the project's tech, domain, and constraints without
 # re-asking. Common opt-ins (set in team/user override TOML):
 #   "skill:acme-co:terms-and-conditions"                                      # a skill that contains some relevant info
@@ -53,8 +53,8 @@ run_folder_pattern = "brief-{project_name}-{date}"
 # findings before the user sees the draft. Encodes standards, not options.
 #
 # Examples:
-#   "skill:bmad-editorial-review-prose"
-#   "file:{project-root}/_bmad/style-guides/company-voice.md"
+#   "skill:wizz-editorial-review-prose"
+#   "file:{project-root}/_wizz/style-guides/company-voice.md"
 #   "Convert all dates to ISO 8601 format."
 #
 # Suggested order (broader passes first, narrower last):
@@ -65,8 +65,8 @@ run_folder_pattern = "brief-{project_name}-{date}"
 # Override the array in team/user TOML to add additional standards. Append-only:
 # base entries cannot be removed or replaced (resolver has no removal mechanism).
 doc_standards = [
-  "skill:bmad-editorial-review-structure",
-  "skill:bmad-editorial-review-prose",
+  "skill:wizz-editorial-review-structure",
+  "skill:wizz-editorial-review-prose",
 ]
 
 # External-source registry. Natural-language directives describing knowledge

package/src/bmm-skills/1-analysis/wizz-set-feature/SKILL.md

@@ -0,0 +1,74 @@
+---
+name: wizz-set-feature
+description: 'Set or switch the active feature context so planning and implementation artifacts are organized into a named subfolder. Use when the user says "set feature", "switch feature", "new feature", or asks "what feature is active".'
+---
+
+# Set Feature
+
+**Goal:** Set or switch the `active_feature` context so all subsequent planning and implementation artifacts are saved into a named subfolder.
+
+## Conventions
+
+- `{project-root}`-prefixed paths resolve from the project working directory.
+
+## On Activation
+
+### Step 1: Load Config
+
+Load config from `{project-root}/_wizz/bmm/config.yaml` and resolve:
+
+- `project_name`, `user_name`, `communication_language`
+- `planning_artifacts`, `implementation_artifacts`
+- `active_feature` (current value, may be empty or absent)
+
+Always speak in `{communication_language}`.
+
+### Step 2: Show Current State
+
+- If `active_feature` is set: "Active feature: **{active_feature}**".
+- If empty or absent: "No active feature set. Artifacts are saving to the roots."
+
+If the user only asked which feature is active, stop here.
+
+### Step 3: Ask for the Feature Slug
+
+Ask: "What is the feature name? Use a short kebab-case slug (e.g. `admin-panel`, `auth-refactor`, `dashboard-financeiro`). It becomes the subfolder name inside `planning-artifacts/` and `implementation-artifacts/`."
+
+Wait for the user's answer.
+
+### Step 4: Validate and Confirm
+
+- Reject empty input.
+- Normalize: lowercase and replace spaces with hyphens.
+- Show the normalized slug and confirm it with the user before proceeding.
+
+### Step 5: Update Config
+
+Edit `{project-root}/_wizz/bmm/config.yaml`:
+
+- If an `active_feature:` key exists, set its value to the confirmed slug.
+- If it does not exist, add the line `active_feature: "{slug}"`.
+- Save the file.
+
+### Step 6: Create Subfolders
+
+Create these directories if they do not already exist:
+
+- `{planning_artifacts}/{active_feature}/`
+- `{implementation_artifacts}/{active_feature}/`
+
+### Step 7: Confirm
+
+Tell the user:
+
+"Feature set to **{active_feature}**. New planning and implementation artifacts will be saved under:
+- `{planning_artifacts}/{active_feature}/`
+- `{implementation_artifacts}/{active_feature}/`
+
+Run this skill again anytime to switch features, or clear the slug to go back to the roots."
+
+## Success Criteria
+
+- ✅ `active_feature` updated in `_wizz/bmm/config.yaml`.
+- ✅ Subfolders created in planning-artifacts and implementation-artifacts.
+- ✅ User clearly informed of the new artifact paths.

package/src/bmm-skills/2-plan-workflows/{bmad-agent-pm → wizz-agent-pm}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: bmad-agent-pm
+name: wizz-agent-pm
 description: Product manager for PRD creation and requirements discovery. Use when the user asks to talk to John or requests the product manager.
 ---
 
@@ -20,13 +20,13 @@ You are John, the Product Manager. You drive PRD creation through user interview
 
 ### Step 1: Resolve the Agent Block
 
-Run: `python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key agent`
+Run: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key agent`
 
 **If the script fails**, resolve the `agent` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
 
 1. `{skill-root}/customize.toml` — defaults
-2. `{project-root}/_bmad/custom/{skill-name}.toml` — team overrides
-3. `{project-root}/_bmad/custom/{skill-name}.user.toml` — personal overrides
+2. `{project-root}/_wizz/custom/{skill-name}.toml` — team overrides
+3. `{project-root}/_wizz/custom/{skill-name}.user.toml` — personal overrides
 
 Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
 
@@ -46,7 +46,7 @@ Treat every entry in `{agent.persistent_facts}` as foundational context you carr
 
 ### Step 5: Load Config
 
-Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+Load config from `{project-root}/_wizz/bmm/config.yaml` and resolve:
 - Use `{user_name}` for greeting
 - Use `{communication_language}` for all communications
 - Use `{document_output_language}` for output documents
@@ -55,7 +55,7 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 
 ### Step 6: Greet the User
 
-Greet `{user_name}` warmly by name as John, speaking in `{communication_language}`. Lead the greeting with `{agent.icon}` so the user can see at a glance which agent is speaking. Remind the user they can invoke the `bmad-help` skill at any time for advice.
+Greet `{user_name}` warmly by name as John, speaking in `{communication_language}`. Lead the greeting with `{agent.icon}` so the user can see at a glance which agent is speaking. Remind the user they can invoke the `wizz-help` skill at any time for advice.
 
 Continue to prefix your messages with `{agent.icon}` throughout the session so the active persona stays visually identifiable.
 
@@ -71,6 +71,6 @@ If the user's initial message already names an intent that clearly maps to a men
 
 Otherwise render `{agent.menu}` as a numbered table: `Code`, `Description`, `Action` (the item's `skill` name, or a short label derived from its `prompt` text). **Stop and wait for input.** Accept a number, menu `code`, or fuzzy description match.
 
-Dispatch on a clear match by invoking the item's `skill` or executing its `prompt`. Only pause to clarify when two or more items are genuinely close — one short question, not a confirmation ritual. When nothing on the menu fits, just continue the conversation; chat, clarifying questions, and `bmad-help` are always fair game.
+Dispatch on a clear match by invoking the item's `skill` or executing its `prompt`. Only pause to clarify when two or more items are genuinely close — one short question, not a confirmation ritual. When nothing on the menu fits, just continue the conversation; chat, clarifying questions, and `wizz-help` are always fair game.
 
 From here, John stays active — persona, persistent facts, `{agent.icon}` prefix, and `{communication_language}` carry into every turn until the user dismisses him.

package/src/bmm-skills/2-plan-workflows/{bmad-agent-pm → wizz-agent-pm}/customize.toml

@@ -37,6 +37,7 @@ activation_steps_append = []
 
 persistent_facts = [
   "file:{project-root}/**/project-context.md",
+  "If active_feature is set in {project-root}/_wizz/bmm/config.yaml, save every planning and implementation artifact under a subfolder named after it (e.g. {planning_artifacts}/{active_feature}/, {implementation_artifacts}/{active_feature}/). If it is empty or unset, write to the artifact roots as usual.",
 ]
 
 role = "Translate product vision into a validated PRD, epics, and stories that development can execute during the BMad Method planning phase."
@@ -57,19 +58,19 @@ principles = [
 [[agent.menu]]
 code = "PRD"
 description = "Create, update, or validate a PRD — state your intent or the skill will ask"
-skill = "bmad-prd"
+skill = "wizz-prd"
 
 [[agent.menu]]
 code = "CE"
 description = "Create the Epics and Stories Listing that will drive development"
-skill = "bmad-create-epics-and-stories"
+skill = "wizz-create-epics-and-stories"
 
 [[agent.menu]]
 code = "IR"
 description = "Ensure the PRD, UX, Architecture and Epics and Stories List are all aligned"
-skill = "bmad-check-implementation-readiness"
+skill = "wizz-check-implementation-readiness"
 
 [[agent.menu]]
 code = "CC"
 description = "Determine how to proceed if major need for change is discovered mid implementation"
-skill = "bmad-correct-course"
+skill = "wizz-correct-course"

package/src/bmm-skills/2-plan-workflows/{bmad-agent-ux-designer → wizz-agent-ux-designer}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: bmad-agent-ux-designer
+name: wizz-agent-ux-designer
 description: UX designer and UI specialist. Use when the user asks to talk to Sally or requests the UX designer.
 ---
 
@@ -20,13 +20,13 @@ You are Sally, the UX Designer. You translate user needs into interaction design
 
 ### Step 1: Resolve the Agent Block
 
-Run: `python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key agent`
+Run: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key agent`
 
 **If the script fails**, resolve the `agent` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
 
 1. `{skill-root}/customize.toml` — defaults
-2. `{project-root}/_bmad/custom/{skill-name}.toml` — team overrides
-3. `{project-root}/_bmad/custom/{skill-name}.user.toml` — personal overrides
+2. `{project-root}/_wizz/custom/{skill-name}.toml` — team overrides
+3. `{project-root}/_wizz/custom/{skill-name}.user.toml` — personal overrides
 
 Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
 
@@ -46,7 +46,7 @@ Treat every entry in `{agent.persistent_facts}` as foundational context you carr
 
 ### Step 5: Load Config
 
-Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+Load config from `{project-root}/_wizz/bmm/config.yaml` and resolve:
 - Use `{user_name}` for greeting
 - Use `{communication_language}` for all communications
 - Use `{document_output_language}` for output documents
@@ -55,7 +55,7 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 
 ### Step 6: Greet the User
 
-Greet `{user_name}` warmly by name as Sally, speaking in `{communication_language}`. Lead the greeting with `{agent.icon}` so the user can see at a glance which agent is speaking. Remind the user they can invoke the `bmad-help` skill at any time for advice.
+Greet `{user_name}` warmly by name as Sally, speaking in `{communication_language}`. Lead the greeting with `{agent.icon}` so the user can see at a glance which agent is speaking. Remind the user they can invoke the `wizz-help` skill at any time for advice.
 
 Continue to prefix your messages with `{agent.icon}` throughout the session so the active persona stays visually identifiable.
 
@@ -71,6 +71,6 @@ If the user's initial message already names an intent that clearly maps to a men
 
 Otherwise render `{agent.menu}` as a numbered table: `Code`, `Description`, `Action` (the item's `skill` name, or a short label derived from its `prompt` text). **Stop and wait for input.** Accept a number, menu `code`, or fuzzy description match.
 
-Dispatch on a clear match by invoking the item's `skill` or executing its `prompt`. Only pause to clarify when two or more items are genuinely close — one short question, not a confirmation ritual. When nothing on the menu fits, just continue the conversation; chat, clarifying questions, and `bmad-help` are always fair game.
+Dispatch on a clear match by invoking the item's `skill` or executing its `prompt`. Only pause to clarify when two or more items are genuinely close — one short question, not a confirmation ritual. When nothing on the menu fits, just continue the conversation; chat, clarifying questions, and `wizz-help` are always fair game.
 
 From here, Sally stays active — persona, persistent facts, `{agent.icon}` prefix, and `{communication_language}` carry into every turn until the user dismisses her.

package/src/bmm-skills/2-plan-workflows/{bmad-agent-ux-designer → wizz-agent-ux-designer}/customize.toml

@@ -37,6 +37,7 @@ activation_steps_append = []
 
 persistent_facts = [
   "file:{project-root}/**/project-context.md",
+  "If active_feature is set in {project-root}/_wizz/bmm/config.yaml, save every planning and implementation artifact under a subfolder named after it (e.g. {planning_artifacts}/{active_feature}/, {implementation_artifacts}/{active_feature}/). If it is empty or unset, write to the artifact roots as usual.",
 ]
 
 role = "Turn user needs and the PRD into UX design specifications that inform architecture and implementation during the BMad Method planning phase."
@@ -57,4 +58,4 @@ principles = [
 [[agent.menu]]
 code = "CU"
 description = "Guidance through realizing the plan for your UX to inform architecture and implementation"
-skill = "bmad-ux"
+skill = "wizz-ux"

package/src/bmm-skills/2-plan-workflows/{bmad-create-prd → wizz-create-prd}/SKILL.md

@@ -1,30 +1,30 @@
 ---
-name: bmad-create-prd
-description: 'DEPRECATED — consolidated into bmad-prd create intent - this skill will be removed in v7 in favor of `bmad-prd`.'
+name: wizz-create-prd
+description: 'DEPRECATED — consolidated into wizz-prd create intent - this skill will be removed in v7 in favor of `wizz-prd`.'
 ---
 
-# DEPRECATED — forwards to bmad-prd (create intent)
+# DEPRECATED — forwards to wizz-prd (create intent)
 
-This skill was consolidated into `bmad-prd`. It is retained as a thin compatibility shim so existing invocations by name and `_bmad/custom/bmad-create-prd.toml` override files keep working. New work should invoke `bmad-prd` directly — it detects create / update / validate intent from the conversation.
+This skill was consolidated into `wizz-prd`. It is retained as a thin compatibility shim so existing invocations by name and `_wizz/custom/wizz-create-prd.toml` override files keep working. New work should invoke `wizz-prd` directly — it detects create / update / validate intent from the conversation.
 
 ## On Activation
 
-1. Resolve customization: `python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. This picks up any `{project-root}/_bmad/custom/bmad-create-prd.toml` and `bmad-create-prd.user.toml` overrides for the legacy fields (`activation_steps_prepend`, `activation_steps_append`, `persistent_facts`, `on_complete`).
+1. Resolve customization: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow`. This picks up any `{project-root}/_wizz/custom/wizz-create-prd.toml` and `wizz-create-prd.user.toml` overrides for the legacy fields (`activation_steps_prepend`, `activation_steps_append`, `persistent_facts`, `on_complete`).
 
-2. Load `{project-root}/_bmad/bmm/config.yaml` (and `config.user.yaml` if present) to resolve `{user_name}` and `{communication_language}`.
+2. Load `{project-root}/_wizz/bmm/config.yaml` (and `config.user.yaml` if present) to resolve `{user_name}` and `{communication_language}`.
 
 3. Emit a deprecation notice to the user in `{communication_language}`:
 
-   > Notice: `bmad-create-prd` is deprecated and will be removed in a future release. It now forwards to `bmad-prd` with create intent. To silence this notice and access the full new customization surface (`prd_template`, `validation_checklist`, `doc_standards`, `external_sources`, `external_handoffs`, `output_dir`, `output_folder_name`), migrate `_bmad/custom/bmad-create-prd.toml` to `_bmad/custom/bmad-prd.toml` and invoke `bmad-prd` directly next time. Customization fields that were in this version still remain in the new version and will be respected if present in `_bmad/custom/bmad-prd.toml`, but the new version also supports additional fields that you can take advantage of by migrating.
+   > Notice: `wizz-create-prd` is deprecated and will be removed in a future release. It now forwards to `wizz-prd` with create intent. To silence this notice and access the full new customization surface (`prd_template`, `validation_checklist`, `doc_standards`, `external_sources`, `external_handoffs`, `output_dir`, `output_folder_name`), migrate `_wizz/custom/wizz-create-prd.toml` to `_wizz/custom/wizz-prd.toml` and invoke `wizz-prd` directly next time. Customization fields that were in this version still remain in the new version and will be respected if present in `_wizz/custom/wizz-prd.toml`, but the new version also supports additional fields that you can take advantage of by migrating.
 
-4. Invoke `bmad-prd` with the following context. Pass these as the activating context so `bmad-prd` honors them instead of resolving its own customization from scratch:
+4. Invoke `wizz-prd` with the following context. Pass these as the activating context so `wizz-prd` honors them instead of resolving its own customization from scratch:
 
-   - **Intent:** `create` — skip `bmad-prd`'s usual intent detection step.
-   - **Pre-resolved legacy customization** — use these in place of resolving from `bmad-prd`'s own `customize.toml` for the four legacy fields. For everything else (`prd_template`, `validation_checklist`, `validation_report_template`, `doc_standards`, `output_dir`, `output_folder_name`, `external_sources`, `external_handoffs`), use `bmad-prd`'s own defaults and overrides as normal:
+   - **Intent:** `create` — skip `wizz-prd`'s usual intent detection step.
+   - **Pre-resolved legacy customization** — use these in place of resolving from `wizz-prd`'s own `customize.toml` for the four legacy fields. For everything else (`prd_template`, `validation_checklist`, `validation_report_template`, `doc_standards`, `output_dir`, `output_folder_name`, `external_sources`, `external_handoffs`), use `wizz-prd`'s own defaults and overrides as normal:
      - `activation_steps_prepend` = the resolved value from step 1
      - `activation_steps_append` = the resolved value from step 1
      - `persistent_facts` = the resolved value from step 1
      - `on_complete` = the resolved value from step 1
    - **Original user input:** forward whatever the user said when invoking this skill verbatim.
 
-   `bmad-prd` takes the workflow from here. Do not execute any further steps in this shim.
+   `wizz-prd` takes the workflow from here. Do not execute any further steps in this shim.

package/src/bmm-skills/2-plan-workflows/{bmad-create-prd → wizz-create-prd}/customize.toml

@@ -1,6 +1,6 @@
 # DO NOT EDIT -- overwritten on every update.
 #
-# Workflow customization surface for bmad-create-prd. Mirrors the
+# Workflow customization surface for wizz-create-prd. Mirrors the
 # agent customization shape under the [workflow] namespace.
 
 [workflow]

package/src/bmm-skills/2-plan-workflows/wizz-edit-prd/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: wizz-edit-prd
+description: 'DEPRECATED — consolidated into wizz-prd update intent - this skill will be removed in v7 in favor of `wizz-prd`.'
+---
+
+# DEPRECATED — forwards to wizz-prd (update intent)
+
+This skill was consolidated into `wizz-prd`. It is retained as a thin compatibility shim so existing invocations by name and `_wizz/custom/wizz-edit-prd.toml` override files keep working. New work should invoke `wizz-prd` directly — it detects create / update / validate intent from the conversation.
+
+## On Activation
+
+1. Resolve customization: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow`. This picks up any `{project-root}/_wizz/custom/wizz-edit-prd.toml` and `wizz-edit-prd.user.toml` overrides for the legacy fields (`activation_steps_prepend`, `activation_steps_append`, `persistent_facts`, `on_complete`).
+
+2. Load `{project-root}/_wizz/bmm/config.yaml` (and `config.user.yaml` if present) to resolve `{user_name}` and `{communication_language}`.
+
+3. Emit a deprecation notice to the user in `{communication_language}`:
+
+   > Notice: `wizz-edit-prd` is deprecated and will be removed in a future release. It now forwards to `wizz-prd` with update intent. To silence this notice and access the full new customization surface (`prd_template`, `validation_checklist`, `doc_standards`, `external_sources`, `external_handoffs`, `output_dir`, `output_folder_name`), migrate `_wizz/custom/wizz-edit-prd.toml` to `_wizz/custom/wizz-prd.toml` and invoke `wizz-prd` directly next time. Customization fields that were in this version still remain in the new version and will be respected if present in `_wizz/custom/wizz-prd.toml`, but the new version also supports additional fields that you can take advantage of by migrating.
+
+4. Invoke `wizz-prd` with the following context. Pass these as the activating context so `wizz-prd` honors them instead of resolving its own customization from scratch:
+
+   - **Intent:** `update` — skip `wizz-prd`'s usual intent detection step.
+   - **Pre-resolved legacy customization** — use these in place of resolving from `wizz-prd`'s own `customize.toml` for the four legacy fields. For everything else (`prd_template`, `validation_checklist`, `validation_report_template`, `doc_standards`, `output_dir`, `output_folder_name`, `external_sources`, `external_handoffs`), use `wizz-prd`'s own defaults and overrides as normal:
+     - `activation_steps_prepend` = the resolved value from step 1
+     - `activation_steps_append` = the resolved value from step 1
+     - `persistent_facts` = the resolved value from step 1
+     - `on_complete` = the resolved value from step 1
+   - **Original user input:** forward whatever the user said when invoking this skill verbatim (the target PRD path, the change signal, etc.).
+
+   `wizz-prd` takes the workflow from here. Do not execute any further steps in this shim.

package/src/bmm-skills/2-plan-workflows/{bmad-edit-prd → wizz-edit-prd}/customize.toml

@@ -1,6 +1,6 @@
 # DO NOT EDIT -- overwritten on every update.
 #
-# Workflow customization surface for bmad-edit-prd. Mirrors the
+# Workflow customization surface for wizz-edit-prd. Mirrors the
 # agent customization shape under the [workflow] namespace.
 
 [workflow]
@@ -36,7 +36,7 @@ persistent_facts = [
 
 # Scalar: executed when the workflow reaches Step E-4 (Complete & Validate) and the
 # user exits via [S] Summary or [X] Exit — not on [V] Validate (which chains to
-# bmad-validate-prd) or [E] Edit More (which loops back). Override wins.
+# wizz-validate-prd) or [E] Edit More (which loops back). Override wins.
 # Leave empty for no custom post-completion behavior.
 
 on_complete = ""

package/src/bmm-skills/2-plan-workflows/{bmad-prd → wizz-prd}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: bmad-prd
+name: wizz-prd
 description: Create, update, or validate a PRD. Use when the user wants help producing, editing, or validating a PRD.
 ---
 # BMad PRD
@@ -15,10 +15,10 @@ You are a master facilitator and coach helping the user create, edit, or validat
 
 ## On Activation
 
-1. Resolve customization: `python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}/customize.toml` directly and use defaults.
+1. Resolve customization: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}/customize.toml` directly and use defaults.
 2. Run `{workflow.activation_steps_prepend}`. Treat `{workflow.persistent_facts}` as foundational context (entries prefixed `file:` are loaded). `{workflow.external_sources}` is an org-configured registry of internal tools (knowledge bases, MCP tools); consult them alongside generic web research on the same triggers, org tools preferred when their directive matches. Research itself fires during Discovery — see **Research subagents**.
-3. Load `{project-root}/_bmad/bmm/config.yaml` (+ `config.user.yaml` if present). Resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{planning_artifacts}`, `{project_name}`, `{date}`. Missing keys → neutral defaults; never block.
-4. If headless, follow `references/headless.md` for the whole run. Otherwise greet the user **by name** using `{user_name}` and **in their language** using `{communication_language}` — and stay in `{communication_language}` for every turn for the entire run, not just the greeting. In the greeting, let the user know that at any point they can invoke `bmad-party-mode` for multi-agent perspectives or `bmad-advanced-elicitation` for deeper exploration on a specific section. Then scan for misroute on the first message: if the signal points elsewhere (game → BMad GDS; express build → `bmad-quick-dev`; one-pager → `bmad-product-brief`; vet product idea → `bmad-prfaq`; agent skill or custom agent → `bmad-workflow-builder`), suggest they might want the other options before continuing.
+3. Load `{project-root}/_wizz/bmm/config.yaml` (+ `config.user.yaml` if present). Resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{planning_artifacts}`, `{project_name}`, `{date}`. Missing keys → neutral defaults; never block.
+4. If headless, follow `references/headless.md` for the whole run. Otherwise greet the user **by name** using `{user_name}` and **in their language** using `{communication_language}` — and stay in `{communication_language}` for every turn for the entire run, not just the greeting. In the greeting, let the user know that at any point they can invoke `wizz-party-mode` for multi-agent perspectives or `wizz-advanced-elicitation` for deeper exploration on a specific section. Then scan for misroute on the first message: if the signal points elsewhere (game → BMad GDS; express build → `wizz-quick-dev`; one-pager → `wizz-product-brief`; vet product idea → `wizz-prfaq`; agent skill or custom agent → `bmad-workflow-builder`), suggest they might want the other options before continuing.
 5. Detect intent: **Create** (no PRD), **Update** (existing PRD), **Validate** (critique only). If ambiguous, ask. For Create intent, before binding a fresh workspace, scan `{workflow.prd_output_path}` for prior in-progress runs (folders matching `{workflow.run_folder_pattern}` whose `prd.md` frontmatter `status` is not `final`); if any exist, offer to resume rather than starting over.
 
 Run `{workflow.activation_steps_append}`.
@@ -88,5 +88,5 @@ Tell the user the sequence in one sentence, then walk it. Polish goes last so it
 4. **Triage open items.** All Open Questions, `[ASSUMPTION]` tags, `[NOTE FOR PM]` callouts. Phase-blockers (would make the PRD unsafe for UX/architecture/epics) surfaced one at a time and resolved; non-blockers deferred with owner + revisit condition logged to `.decision-log.md`. If phase-blocker count is high, flag it.
 5. **Polish.** Apply `{workflow.doc_standards}` to `prd.md` and `addendum.md` in declared order (structural passes before prose — prose should not polish soon-to-be-cut text). Parallelize across documents, sequential within.
 6. **External handoffs.** Execute `{workflow.external_handoffs}`; surface returned URLs/IDs. Skip and flag unavailable tools.
-7. **Close.** Set `prd.md` frontmatter `status: final` and `updated` to `{date}` so future invocations distinguish this PRD from in-progress drafts. Record finalization to `.decision-log.md`. Share artifact paths. Common next: `bmad-ux`, `bmad-architecture`, `bmad-create-epics-and-stories`; invoke `bmad-help` for authoritative routing.
+7. **Close.** Set `prd.md` frontmatter `status: final` and `updated` to `{date}` so future invocations distinguish this PRD from in-progress drafts. Record finalization to `.decision-log.md`. Share artifact paths. Common next: `wizz-ux`, `wizz-architecture`, `wizz-create-epics-and-stories`; invoke `wizz-help` for authoritative routing.
 8. Run `{workflow.on_complete}` if non-empty.

package/src/bmm-skills/2-plan-workflows/{bmad-prd → wizz-prd}/assets/prd-template.md

@@ -161,5 +161,5 @@ updated: {YYYY-MM-DD}
 - **Environmental and Reliability Requirements**.
 
 ### Small-scope all-inclusive *(use when scope is 1-2 stories' worth and the user wants a single captured artifact — chosen during the Right-skill check in Discovery)*
-- **Stories** — story-level specs listed inline at the end of the doc. Each story: *"As a [persona], I can [action] [under conditions]. Acceptance: [testable criteria]."* Numbered Story-1, Story-2, ... for reference. Pair with very lean §1 Vision, §2 Target User (often just JTBD + one UJ), §3 Glossary (handful of terms), §4 Features (often a single feature), §6 MVP Scope (in/out very tight). The whole doc fits on a page or two and captures intent + implementable stories in one place. If the user doesn't want the captured artifact at all, `bmad-quick-dev` is the better path — this cluster is only for "I want a doc *and* the stories."
+- **Stories** — story-level specs listed inline at the end of the doc. Each story: *"As a [persona], I can [action] [under conditions]. Acceptance: [testable criteria]."* Numbered Story-1, Story-2, ... for reference. Pair with very lean §1 Vision, §2 Target User (often just JTBD + one UJ), §3 Glossary (handful of terms), §4 Features (often a single feature), §6 MVP Scope (in/out very tight). The whole doc fits on a page or two and captures intent + implementable stories in one place. If the user doesn't want the captured artifact at all, `wizz-quick-dev` is the better path — this cluster is only for "I want a doc *and* the stories."
 

package/src/bmm-skills/2-plan-workflows/{bmad-prd → wizz-prd}/customize.toml

@@ -1,10 +1,10 @@
 # DO NOT EDIT -- overwritten on every update.
 #
-# Workflow customization surface for bmad-prd.
+# Workflow customization surface for wizz-prd.
 #
 # Override files (not edited here):
-#   {project-root}/_bmad/custom/bmad-prd.toml         (team)
-#   {project-root}/_bmad/custom/bmad-prd.user.toml    (personal)
+#   {project-root}/_wizz/custom/wizz-prd.toml         (team)
+#   {project-root}/_wizz/custom/wizz-prd.user.toml    (personal)
 
 [workflow]
 
@@ -24,7 +24,7 @@ activation_steps_append = []
 # Each entry is either a literal sentence, a skill prefixed with `skill:`, or a `file:`-prefixed path/glob
 # whose contents are loaded as facts.
 #
-# Default loads project-context.md if bmad-generate-project-context has produced one — this gives
+# Default loads project-context.md if wizz-generate-project-context has produced one — this gives
 # the facilitator persistent awareness of the project's tech, domain, and constraints without
 # re-asking. Common opt-ins (set in team/user override TOML):
 #   "skill:acme-co:terms-and-conditions"                                      # a skill that contains some relevant info
@@ -71,8 +71,8 @@ run_folder_pattern = "prd-{project_name}-{date}"
 # findings before the user sees the draft. Encodes standards, not options.
 #
 # Examples:
-#   "skill:bmad-editorial-review-prose"
-#   "file:{project-root}/_bmad/style-guides/company-voice.md"
+#   "skill:wizz-editorial-review-prose"
+#   "file:{project-root}/_wizz/style-guides/company-voice.md"
 #   "Convert all dates to ISO 8601 format."
 #
 # Suggested order (broader passes first, narrower last):
@@ -83,8 +83,8 @@ run_folder_pattern = "prd-{project_name}-{date}"
 # Override the array in team/user TOML to add additional standards. Append-only:
 # base entries cannot be removed or replaced (resolver has no removal mechanism).
 doc_standards = [
-  "skill:bmad-editorial-review-structure",
-  "skill:bmad-editorial-review-prose",
+  "skill:wizz-editorial-review-structure",
+  "skill:wizz-editorial-review-prose",
 ]
 
 # External-source registry. Natural-language directives describing knowledge

package/src/bmm-skills/2-plan-workflows/{bmad-prd → wizz-prd}/references/headless.md

@@ -1,6 +1,6 @@
 # Headless Mode
 
-Load this file when bmad-prd is invoked headless (no interactive user). Follow it for the whole run.
+Load this file when wizz-prd is invoked headless (no interactive user). Follow it for the whole run.
 
 ## Detection
 

package/src/bmm-skills/2-plan-workflows/{bmad-ux → wizz-ux}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: bmad-ux
+name: wizz-ux
 description: Plan UX patterns and design specifications. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"
 ---
 # BMad UX
@@ -30,10 +30,10 @@ UX may lead, follow, or stand alone. Inherit `sources:` by reference; the spines
 
 ## On Activation
 
-1. Resolve customization: `python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}/customize.toml` directly and use defaults.
+1. Resolve customization: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}/customize.toml` directly and use defaults.
 2. Run `{workflow.activation_steps_prepend}`. Treat `{workflow.persistent_facts}` as foundational context (entries prefixed `file:` are loaded). `{workflow.external_sources}` is an org-configured registry of internal tools; consult them alongside generic web research on the same triggers, org tools preferred when their directive matches.
-3. Load `{project-root}/_bmad/bmm/config.yaml` (+ `config.user.yaml` if present). Resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{planning_artifacts}`, `{project_name}`, `{date}`. Missing keys → neutral defaults; never block.
-4. If headless, follow `references/headless.md` for the whole run. Otherwise greet the user **by name** using `{user_name}` and **in their language** using `{communication_language}` — and stay in `{communication_language}` for every turn. In the greeting, let the user know `bmad-party-mode` and `bmad-advanced-elicitation` are always available. Then scan for misroute on the first message: PRD → `bmad-prd`; architecture → `bmad-architecture`; game UX → BMad GDS; agent/skill → `bmad-workflow-builder`; brief → `bmad-product-brief`.
+3. Load `{project-root}/_wizz/bmm/config.yaml` (+ `config.user.yaml` if present). Resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{planning_artifacts}`, `{project_name}`, `{date}`. Missing keys → neutral defaults; never block.
+4. If headless, follow `references/headless.md` for the whole run. Otherwise greet the user **by name** using `{user_name}` and **in their language** using `{communication_language}` — and stay in `{communication_language}` for every turn. In the greeting, let the user know `wizz-party-mode` and `wizz-advanced-elicitation` are always available. Then scan for misroute on the first message: PRD → `wizz-prd`; architecture → `wizz-architecture`; game UX → BMad GDS; agent/skill → `bmad-workflow-builder`; brief → `wizz-product-brief`.
 5. Detect intent: **Create**, **Update**, **Validate**. For Create, before binding a fresh workspace, scan `{workflow.ux_output_path}` for prior in-progress runs (folders matching `{workflow.run_folder_pattern}` whose `DESIGN.md` frontmatter `status` is not `final`) and offer to resume rather than starting over.
 
 Run `{workflow.activation_steps_append}`.
@@ -87,4 +87,4 @@ Outcomes, in order:
 - **Key-screen mocks rendered.** Key-screens tool → `.working/` for surfaces where layout drives behavior or anchors visual language.
 - **Mock coverage confirmed.** Walk every IA surface; classify *mocked* vs *spine-only*. Ask: *"These will be built from spine tables alone — any need a visual reference?"* Render more if named; log spine-only choices.
 - **Layout extracted, artifacts promoted.** Distill subagent re-reads each `.working/` and `imports/` artifact; lifts visual decisions into DESIGN.md and behavioral decisions into EXPERIENCE.md. Promote `.working/` keepers to `mockups/` (HTML) or `wireframes/` (Excalidraw); imports stay. Inline relative links at relevant spine sections; state spines-win-on-conflict once.
-- **Polished, handed off, closed.** Apply `{workflow.doc_standards}` in order. Execute `{workflow.external_handoffs}`; surface URLs. Set both files' `status: final`, `updated: {date}`. Log finalization. Share paths. Common next: `bmad-architecture`, `bmad-create-epics-and-stories`, `bmad-dev-story`. Run `{workflow.on_complete}`.
+- **Polished, handed off, closed.** Apply `{workflow.doc_standards}` in order. Execute `{workflow.external_handoffs}`; surface URLs. Set both files' `status: final`, `updated: {date}`. Log finalization. Share paths. Common next: `wizz-architecture`, `wizz-create-epics-and-stories`, `wizz-dev-story`. Run `{workflow.on_complete}`.