wizz-method 1.0.0 → 1.0.1

package/src/bmm-skills/4-implementation/{bmad-agent-dev → wizz-agent-dev}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: bmad-agent-dev
+name: wizz-agent-dev
 description: Senior software engineer for story execution and code implementation. Use when the user asks to talk to Amelia or requests the developer agent.
 ---
 
@@ -20,13 +20,13 @@ You are Amelia, the Senior Software Engineer. You execute approved stories with
 
 ### 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 Amelia, 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 Amelia, 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, Amelia stays active — persona, persistent facts, `{agent.icon}` prefix, and `{communication_language}` carry into every turn until the user dismisses her.

package/src/bmm-skills/4-implementation/{bmad-agent-dev → wizz-agent-dev}/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 = "Implement approved stories with test-first discipline and ship working, verified code during the BMad Method implementation phase."
@@ -57,39 +58,39 @@ principles = [
 [[agent.menu]]
 code = "DS"
 description = "Write the next or specified story's tests and code"
-skill = "bmad-dev-story"
+skill = "wizz-dev-story"
 
 [[agent.menu]]
 code = "QD"
 description = "Unified quick flow — clarify intent, plan, implement, review, present"
-skill = "bmad-quick-dev"
+skill = "wizz-quick-dev"
 
 [[agent.menu]]
 code = "QA"
 description = "Generate API and E2E tests for existing features"
-skill = "bmad-qa-generate-e2e-tests"
+skill = "wizz-qa-generate-e2e-tests"
 
 [[agent.menu]]
 code = "CR"
 description = "Initiate a comprehensive code review across multiple quality facets"
-skill = "bmad-code-review"
+skill = "wizz-code-review"
 
 [[agent.menu]]
 code = "SP"
 description = "Generate or update the sprint plan that sequences tasks for implementation"
-skill = "bmad-sprint-planning"
+skill = "wizz-sprint-planning"
 
 [[agent.menu]]
 code = "CS"
 description = "Prepare a story with all required context for implementation"
-skill = "bmad-create-story"
+skill = "wizz-create-story"
 
 [[agent.menu]]
 code = "ER"
 description = "Party mode review of all work completed across an epic"
-skill = "bmad-retrospective"
+skill = "wizz-retrospective"
 
 [[agent.menu]]
 code = "IN"
 description = "Forensic case investigation with evidence-graded findings, calibrated to the input"
-skill = "bmad-investigate"
+skill = "wizz-investigate"

package/src/bmm-skills/4-implementation/{bmad-checkpoint-preview → wizz-checkpoint-preview}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: bmad-checkpoint-preview
+name: wizz-checkpoint-preview
 description: 'LLM-assisted human-in-the-loop review. Make sense of a change, focus attention where it matters, test. Use when the user says "checkpoint", "human review", or "walk me through this change".'
 ---
 
@@ -20,13 +20,13 @@ description: 'LLM-assisted human-in-the-loop review. Make sense of a change, foc
 
 ### 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.
 
@@ -40,7 +40,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:
 
 - `implementation_artifacts`
 - `planning_artifacts`

package/src/bmm-skills/4-implementation/{bmad-checkpoint-preview → wizz-checkpoint-preview}/customize.toml

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

package/src/bmm-skills/4-implementation/{bmad-checkpoint-preview → wizz-checkpoint-preview}/step-05-wrapup.md

@@ -25,6 +25,6 @@ HALT — do not proceed until the user makes their choice.
 
 ## On Complete
 
-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/4-implementation/{bmad-code-review → wizz-code-review}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: bmad-code-review
+name: wizz-code-review
 description: 'Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code"'
 ---
 
@@ -23,13 +23,13 @@ If you need an explicit user instruction to run them, ask once now for the whole
 
 ### 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.
 
@@ -43,7 +43,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:
 
 - `project_name`, `planning_artifacts`, `implementation_artifacts`, `user_name`
 - `communication_language`, `document_output_language`, `user_skill_level`

package/src/bmm-skills/4-implementation/{bmad-code-review → wizz-code-review}/customize.toml

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

package/src/bmm-skills/4-implementation/{bmad-code-review → wizz-code-review}/steps/step-02-review.md

@@ -18,9 +18,9 @@ failed_layers: '' # set at runtime: comma-separated list of layers that failed o
 
 2. Launch parallel subagents without conversation context. If subagents are not available, generate prompt files in `{implementation_artifacts}` — one per reviewer role below — and HALT. Ask the user to run each in a separate session (ideally a different LLM) and paste back the findings. When findings are pasted, resume from this point and proceed to step 3.
 
-   - **Blind Hunter** — receives inline `{diff_output}` only. No spec, no context docs, no project access. Invoke via the `bmad-review-adversarial-general` skill.
+   - **Blind Hunter** — receives inline `{diff_output}` only. No spec, no context docs, no project access. Invoke via the `wizz-review-adversarial-general` skill.
 
-   - **Edge Case Hunter** — receives `{diff_output}` and read access to the project. Invoke via the `bmad-review-edge-case-hunter` skill.
+   - **Edge Case Hunter** — receives `{diff_output}` and read access to the project. Invoke via the `wizz-review-edge-case-hunter` skill.
 
    - **Acceptance Auditor** (only if `{review_mode}` = `"full"`) — receives `{diff_output}`, the content of the file at `{spec_file}`, and any loaded context docs. Its prompt:
      > You are an Acceptance Auditor. Review this diff against the spec and context docs. Check for: violations of acceptance criteria, deviations from spec intent, missing implementation of specified behavior, contradictions between spec constraints and actual code. Output findings as a Markdown list. Each finding: one-line title, which AC/constraint it violates, and evidence from the diff.

package/src/bmm-skills/4-implementation/{bmad-code-review → wizz-code-review}/steps/step-04-present.md

@@ -127,6 +127,6 @@ Present the user with follow-up options:
 
 ## On Complete
 
-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/4-implementation/{bmad-correct-course → wizz-correct-course}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: bmad-correct-course
+name: wizz-correct-course
 description: 'Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change"'
 ---
 
@@ -20,13 +20,13 @@ description: 'Manage significant changes during sprint execution. Use when the u
 
 ### 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.
 
@@ -40,7 +40,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:
 
 - `project_name`, `user_name`
 - `communication_language`, `document_output_language`
@@ -295,7 +295,7 @@ Activation is complete. If `activation_steps_prepend` or `activation_steps_appen
 
 <action>Report workflow completion to user with personalized message: "Correct Course workflow complete, {user_name}!"</action>
 <action>Remind user of success criteria and next steps for Developer agent</action>
-<action>Run: `python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete` — if the resolved value is non-empty, follow it as the final terminal instruction before exiting.</action>
+<action>Run: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete` — if the resolved value is non-empty, follow it as the final terminal instruction before exiting.</action>
 </step>
 
 </workflow>

package/src/bmm-skills/4-implementation/{bmad-correct-course → wizz-correct-course}/customize.toml

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

package/src/bmm-skills/4-implementation/{bmad-create-story → wizz-create-story}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: bmad-create-story
+name: wizz-create-story
 description: 'Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]"'
 ---
 
@@ -30,13 +30,13 @@ If you need an explicit user instruction to run them, ask once now for the whole
 
 ### 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:
 
 - `project_name`, `user_name`
 - `communication_language`, `document_output_language`
@@ -426,7 +426,7 @@ Activation is complete. If `activation_steps_prepend` or `activation_steps_appen
 
     **The developer now has everything needed for flawless implementation!**
   </output>
-  <action>Run: `python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete` — if the resolved value is non-empty, follow it as the final terminal instruction before exiting.</action>
+  <action>Run: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete` — if the resolved value is non-empty, follow it as the final terminal instruction before exiting.</action>
 </step>
 
 </workflow>

package/src/bmm-skills/4-implementation/{bmad-create-story → wizz-create-story}/customize.toml

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

package/src/bmm-skills/4-implementation/{bmad-dev-story → wizz-dev-story}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: bmad-dev-story
+name: wizz-dev-story
 description: 'Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"'
 ---
 
@@ -15,6 +15,7 @@ description: 'Execute story implementation following a context filled story spec
 - Absolutely DO NOT stop because of "milestones", "significant progress", or "session boundaries". Continue in a single execution until the story is COMPLETE (all ACs satisfied and all tasks/subtasks checked) UNLESS a HALT condition is triggered or the USER gives other instruction.
 - Do NOT schedule a "next session" or request review pauses unless a HALT condition applies. Only Step 9 decides completion.
 - User skill level ({user_skill_level}) affects conversation style ONLY, not code updates.
+- **BE CONCISE.** Minimize prose. Use one-line status updates (e.g. "✅ Task 1 done"). No preambles, no re-stating intent, no summaries between tasks. Show code, not explanations. Only elaborate when a HALT or a user question requires it.
 
 ## Conventions
 
@@ -27,13 +28,13 @@ description: 'Execute story implementation following a context filled story spec
 
 ### 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.
 
@@ -47,7 +48,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:
 
 - `project_name`, `user_name`
 - `communication_language`, `document_output_language`
@@ -494,7 +495,7 @@ Activation is complete. If `activation_steps_prepend` or `activation_steps_appen
       <action>Suggest checking {sprint_status} to see project progress</action>
     </check>
     <action>Remain flexible - allow user to choose their own path or ask for other assistance</action>
-  <action>Run: `python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete` — if the resolved value is non-empty, follow it as the final terminal instruction before exiting.</action>
+  <action>Run: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete` — if the resolved value is non-empty, follow it as the final terminal instruction before exiting.</action>
   </step>
 
 </workflow>

package/src/bmm-skills/4-implementation/{bmad-dev-story → wizz-dev-story}/customize.toml

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

package/src/bmm-skills/4-implementation/{bmad-investigate → wizz-investigate}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: bmad-investigate
+name: wizz-investigate
 description: Forensic case investigation with evidence-graded findings, calibrated to the input. Use when the user asks to investigate a bug, trace what caused an incident, walk through unfamiliar code, or build a mental model of a code area before working on it.
 ---
 
@@ -52,7 +52,7 @@ After every outcome, present what was learned and pause for the user before cont
 
 ### 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, stop and surface the error.
 
@@ -67,7 +67,7 @@ Treat each entry in `{workflow.persistent_facts}` as foundational context. `file
 
 ### Step 4: Load config
 
-Load `{project-root}/_bmad/bmm/config.yaml` and resolve `{user_name}`, `{communication_language}`,
+Load `{project-root}/_wizz/bmm/config.yaml` and resolve `{user_name}`, `{communication_language}`,
 `{document_output_language}`, `{implementation_artifacts}`, `{project_knowledge}`. If `{implementation_artifacts}` is
 unresolved, fall back to `./investigations/` and surface the fallback before initializing.
 
@@ -179,8 +179,8 @@ Update `{case_file}`:
 - **Reproduction Plan** when applicable, or a verification plan for exploration cases.
 - **Status:** Active / Concluded / Blocked on evidence.
 
-Present the conclusion, then a concrete next-steps menu: trivial fix → `bmad-quick-dev`; scope/plan adjustment →
-`bmad-correct-course`; tracked story → `bmad-create-story`; fresh review → `bmad-code-review`. Recommend the
+Present the conclusion, then a concrete next-steps menu: trivial fix → `wizz-quick-dev`; scope/plan adjustment →
+`wizz-correct-course`; tracked story → `wizz-create-story`; fresh review → `wizz-code-review`. Recommend the
 highest-value action. Mitigations and workarounds are generated only on explicit request — investigation stops at the
 diagnosis. Execute `{workflow.on_complete}` if non-empty. Pause for user with the recap above; wait for direction.
 

package/src/bmm-skills/4-implementation/{bmad-investigate → wizz-investigate}/customize.toml

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

package/src/bmm-skills/4-implementation/{bmad-qa-generate-e2e-tests → wizz-qa-generate-e2e-tests}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: bmad-qa-generate-e2e-tests
+name: wizz-qa-generate-e2e-tests
 description: 'Generate end to end automated tests for existing features. Use when the user says "create qa automated tests for [feature]"'
 ---
 
@@ -7,7 +7,7 @@ description: 'Generate end to end automated tests for existing features. Use whe
 
 **Goal:** Generate automated API and E2E tests for implemented code.
 
-**Your Role:** You are a QA automation engineer. You generate tests ONLY — no code review or story validation (use the `bmad-code-review` skill for that).
+**Your Role:** You are a QA automation engineer. You generate tests ONLY — no code review or story validation (use the `wizz-code-review` skill for that).
 
 ## Conventions
 
@@ -20,13 +20,13 @@ description: 'Generate end to end automated tests for existing features. Use whe
 
 ### 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.
 
@@ -40,7 +40,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:
 
 - `project_name`, `user_name`
 - `communication_language`, `document_output_language`
@@ -171,6 +171,6 @@ Save summary to: `{default_output_file}`
 
 ## On Complete
 
-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/4-implementation/{bmad-qa-generate-e2e-tests → wizz-qa-generate-e2e-tests}/customize.toml

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

package/src/bmm-skills/4-implementation/{bmad-quick-dev → wizz-quick-dev}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: bmad-quick-dev
+name: wizz-quick-dev
 description: 'Implements any user intent, requirement, story, bug fix or change request by producing clean working code artifacts that follow the project''s existing architecture, patterns and conventions. Use when the user wants to build, fix, tweak, refactor, add or modify any code, component or feature.'
 ---
 
@@ -7,6 +7,8 @@ description: 'Implements any user intent, requirement, story, bug fix or change
 
 **Goal:** Turn user intent into a hardened, reviewable artifact.
 
+**Communication style:** BE CONCISE. Minimal prose. One-line status updates (e.g. "✅ done", "🔨 implementing X"). No preambles, no re-stating what you are about to do, no summaries between tasks. Show code, not explanations. Only elaborate on HALTs or explicit user questions.
+
 **CRITICAL:** If a step says "read fully and follow step-XX", you read and follow step-XX. No exceptions.
 
 Subagents, when the capability is available, are an important part of this workflow. Use them as directed by the workflow steps.
@@ -42,13 +44,13 @@ A specification should target a **single user-facing goal** within **900–1600
 
 ### 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.
 
@@ -62,7 +64,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:
 
 - `project_name`, `planning_artifacts`, `implementation_artifacts`, `user_name`
 - `communication_language`, `document_output_language`, `user_skill_level`

package/src/bmm-skills/4-implementation/{bmad-quick-dev → wizz-quick-dev}/customize.toml

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

package/src/bmm-skills/4-implementation/{bmad-quick-dev → wizz-quick-dev}/step-02-plan.md

@@ -30,7 +30,7 @@ After presenting the summary, display this note:
 
 ---
 
-Before approving, you can open the spec file in an editor or ask me questions and tell me what to change. You can also use `bmad-advanced-elicitation`, `bmad-party-mode`, or `bmad-code-review` skills, ideally in another session to avoid context bloat.
+Before approving, you can open the spec file in an editor or ask me questions and tell me what to change. You can also use `wizz-advanced-elicitation`, `wizz-party-mode`, or `wizz-code-review` skills, ideally in another session to avoid context bloat.
 
 ---
 

package/src/bmm-skills/4-implementation/{bmad-quick-dev → wizz-quick-dev}/step-04-review.md

@@ -25,8 +25,8 @@ Do NOT `git add` anything — this is read-only inspection.
 
 Launch three subagents without conversation context. If no sub-agents are available, generate three review prompt files in `{implementation_artifacts}` — one per reviewer role below — and HALT. Ask the human to run each in a separate session (ideally a different LLM) and paste back the findings.
 
-- **Blind hunter** — receives inline `{diff_output}` only. No spec, no context docs, no project access. Invoke via the `bmad-review-adversarial-general` skill.
-- **Edge case hunter** — receives `{diff_output}` and read access to the project. Invoke via the `bmad-review-edge-case-hunter` skill.
+- **Blind hunter** — receives inline `{diff_output}` only. No spec, no context docs, no project access. Invoke via the `wizz-review-adversarial-general` skill.
+- **Edge case hunter** — receives `{diff_output}` and read access to the project. Invoke via the `wizz-review-edge-case-hunter` skill.
 - **Acceptance auditor** — receives `{diff_output}`, `{spec_file}`, and read access to the project. Must also read the docs listed in `{spec_file}` frontmatter `context`. Checks for violations of acceptance criteria, rules, and principles from the spec and context docs.
 
 ### Classify

package/src/bmm-skills/4-implementation/{bmad-quick-dev → wizz-quick-dev}/step-05-present.md

@@ -73,6 +73,6 @@ Workflow complete.
 
 ## On Complete
 
-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/4-implementation/{bmad-quick-dev → wizz-quick-dev}/step-oneshot.md

@@ -19,7 +19,7 @@ Implement the clarified intent directly.
 
 ### Review
 
-Invoke the `bmad-review-adversarial-general` skill in a subagent with the changed files. The subagent gets NO conversation context — to avoid anchoring bias. Launch at the same model capability as the current session. If no sub-agents are available, write the changed files to a review prompt file in `{implementation_artifacts}` and HALT. Ask the human to run the review in a separate session and paste back the findings.
+Invoke the `wizz-review-adversarial-general` skill in a subagent with the changed files. The subagent gets NO conversation context — to avoid anchoring bias. Launch at the same model capability as the current session. If no sub-agents are available, write the changed files to a review prompt file in `{implementation_artifacts}` and HALT. Ask the human to run the review in a separate session and paste back the findings.
 
 ### Classify
 
@@ -66,6 +66,6 @@ Workflow complete.
 
 ## On Complete
 
-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.