wizz-method 1.0.1 → 1.0.3

package/src/bmm-skills/1-analysis/wizz-agent-analyst/customize.toml

@@ -9,7 +9,7 @@
 name="Mary"
 title="Business Analyst"
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays (persistent_facts, principles, activation_steps_*): append
 #   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
 
@@ -40,7 +40,7 @@ persistent_facts = [
   "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 = "Help the user ideate research and analyze before committing to a project in the BMad Method analysis phase."
+role = "Help the user ideate research and analyze before committing to a project in the Wizz Method analysis phase."
 identity = "Channels Michael Porter's strategic rigor and Barbara Minto's Pyramid Principle discipline."
 communication_style = "Treasure hunter's excitement for patterns, McKinsey memo's structure for findings."
 

package/src/bmm-skills/1-analysis/wizz-agent-tech-writer/customize.toml

@@ -9,7 +9,7 @@
 name = "Paige"
 title = "Technical Writer"
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 
 #   scalars: override wins • arrays (persistent_facts, principles, activation_steps_*): append
 #   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
@@ -40,7 +40,7 @@ persistent_facts = [
   "file:{project-root}/**/project-context.md",
 ]
 
-role = "Capture and curate project knowledge so humans and future LLM agents stay in sync during the BMad Method analysis phase."
+role = "Capture and curate project knowledge so humans and future LLM agents stay in sync during the Wizz Method analysis phase."
 identity = "Writes with Julia Evans's accessibility and Edward Tufte's visual precision."
 communication_style = "Patient educator — explains like teaching a friend. Every analogy earns its place."
 

package/src/bmm-skills/1-analysis/wizz-document-project/customize.toml

@@ -5,7 +5,7 @@
 
 [workflow]
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
 #   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
 

package/src/bmm-skills/1-analysis/wizz-document-project/templates/index-template.md

@@ -166,4 +166,4 @@ This documentation was generated specifically to enable AI agents to understand
 
 ---
 
-_Documentation generated by BMAD Method `document-project` workflow_
+_Documentation generated by WIZZ Method `document-project` workflow_

package/src/bmm-skills/1-analysis/wizz-document-project/templates/project-overview-template.md

@@ -100,4 +100,4 @@ For detailed information, see:
 
 ---
 
-_Generated using BMAD Method `document-project` workflow_
+_Generated using WIZZ Method `document-project` workflow_

package/src/bmm-skills/1-analysis/wizz-document-project/templates/source-tree-template.md

@@ -132,4 +132,4 @@ This project is organized into {{parts_count}} distinct parts:
 
 ---
 
-_Generated using BMAD Method `document-project` workflow_
+_Generated using WIZZ Method `document-project` workflow_

package/src/bmm-skills/1-analysis/wizz-prfaq/customize.toml

@@ -5,7 +5,7 @@
 
 [workflow]
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
 #   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
 

package/src/bmm-skills/1-analysis/wizz-product-brief/SKILL.md

@@ -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 `wizz-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 wizz 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/wizz-product-brief/customize.toml

@@ -8,7 +8,7 @@
 
 [workflow]
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays: append
 
 # Steps to run before the standard activation (config load, greet).

package/src/bmm-skills/2-plan-workflows/wizz-agent-pm/customize.toml

@@ -9,7 +9,7 @@
 name = "John"
 title = "Product Manager"
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays (persistent_facts, principles, activation_steps_*): append
 #   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
 
@@ -40,7 +40,7 @@ persistent_facts = [
   "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."
+role = "Translate product vision into a validated PRD, epics, and stories that development can execute during the Wizz Method planning phase."
 identity = "Thinks like Marty Cagan and Teresa Torres. Writes with Bezos's six-pager discipline."
 communication_style = "Detective's 'why?' relentless. Direct, data-sharp, cuts through fluff to what matters."
 

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

@@ -9,7 +9,7 @@
 name = "Sally"
 title = "UX Designer"
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays (persistent_facts, principles, activation_steps_*): append
 #   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
 
@@ -40,7 +40,7 @@ persistent_facts = [
   "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."
+role = "Turn user needs and the PRD into UX design specifications that inform architecture and implementation during the Wizz Method planning phase."
 identity = "Grounded in Don Norman's human-centered design and Alan Cooper's persona discipline."
 communication_style = "Paints pictures with words. User stories that make you feel the problem. Empathetic advocate."
 

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

@@ -1,6 +1,6 @@
 ---
 name: wizz-create-prd
-description: 'DEPRECATED — consolidated into wizz-prd create intent - this skill will be removed in v7 in favor of `wizz-prd`.'
+description: 'DEPRECATED — consolidated into wizz-prd create intent - this skill will be removed in v7 in favor of `wizz-prd`. Use when needed for backwards compatibility.'
 ---
 
 # DEPRECATED — forwards to wizz-prd (create intent)

package/src/bmm-skills/2-plan-workflows/wizz-create-prd/customize.toml

@@ -5,7 +5,7 @@
 
 [workflow]
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
 #   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
 

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

@@ -1,6 +1,6 @@
 ---
 name: wizz-edit-prd
-description: 'DEPRECATED — consolidated into wizz-prd update intent - this skill will be removed in v7 in favor of `wizz-prd`.'
+description: 'DEPRECATED — consolidated into wizz-prd update intent - this skill will be removed in v7 in favor of `wizz-prd`. Use when needed for backwards compatibility.'
 ---
 
 # DEPRECATED — forwards to wizz-prd (update intent)

package/src/bmm-skills/2-plan-workflows/wizz-edit-prd/customize.toml

@@ -5,7 +5,7 @@
 
 [workflow]
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
 #   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
 

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

@@ -2,14 +2,14 @@
 name: wizz-prd
 description: Create, update, or validate a PRD. Use when the user wants help producing, editing, or validating a PRD.
 ---
-# BMad PRD
+# Wizz PRD
 
 You are a master facilitator and coach helping the user create, edit, or validate a high quality PRD scoped to the level and rigor appropriate to their stated needs. Fight the urge to do the thinking for them unless they put you into Fast path.
 
 ## Conventions
 
 - Bare paths resolve from skill root; `{skill-root}` is this skill's install dir; `{project-root}` is the project working dir.
-- `{workflow.<name>}` resolves to fields in `customize.toml`'s `[workflow]` table (overrides win per BMad merge rules).
+- `{workflow.<name>}` resolves to fields in `customize.toml`'s `[workflow]` table (overrides win per Wizz merge rules).
 - `{doc_workspace}` is the bound run folder.
 - **File roles.** `.decision-log.md` is canonical memory and audit trail — every decision, change, and override (including headless overrides) is recorded there as the conversation unfolds. `addendum.md` preserves user-contributed depth that belongs in a downstream document (architecture, solution design, UX spec) or earned a place but does not fit the PRD itself — rejected-alternative rationale, options-considered matrices, mechanism/transport decisions, technical-how, in-depth personas, sizing data. Capture to the addendum *during* the conversation when the user volunteers such content — do not wait for finalize. Audit and override information never goes in the addendum.
 
@@ -18,7 +18,7 @@ You are a master facilitator and coach helping the user create, edit, or validat
 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}/_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.
+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 → Wizz GDS; express build → `wizz-quick-dev`; one-pager → `wizz-product-brief`; vet product idea → `wizz-prfaq`; agent skill or custom agent → `wizz-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}`.

package/src/bmm-skills/2-plan-workflows/wizz-prd/customize.toml

@@ -8,7 +8,7 @@
 
 [workflow]
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays: append
 
 # Steps to run before the standard activation (config load, greet).
@@ -140,7 +140,7 @@ external_handoffs = []
 #                  subagent applying that prompt to prd.md
 #   plain text     use the text directly as the subagent's review prompt
 #
-# Override TOML may append additional reviewers. Arrays append per BMad rules.
+# Override TOML may append additional reviewers. Arrays append per Wizz rules.
 #
 # Resolved on-demand by the authoring skill (not pulled at activation): only
 # when entering the Validate intent or assembling the gate at Finalize step 3.

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

@@ -2,7 +2,7 @@
 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
+# Wizz UX
 
 ## Overview
 
@@ -33,7 +33,7 @@ UX may lead, follow, or stand alone. Inherit `sources:` by reference; the spines
 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}/_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`.
+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 → Wizz GDS; agent/skill → `wizz-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}`.

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

@@ -1,6 +1,6 @@
 ---
 name: wizz-validate-prd
-description: 'DEPRECATED — consolidated into wizz-prd validate intent - this skill will be removed in v7 in favor of `wizz-prd`.'
+description: 'DEPRECATED — consolidated into wizz-prd validate intent - this skill will be removed in v7 in favor of `wizz-prd`. Use when needed for backwards compatibility.'
 ---
 
 # DEPRECATED — forwards to wizz-prd (validate intent)

package/src/bmm-skills/2-plan-workflows/wizz-validate-prd/customize.toml

@@ -5,7 +5,7 @@
 
 [workflow]
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
 #   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
 

package/src/bmm-skills/3-solutioning/wizz-agent-architect/customize.toml

@@ -9,7 +9,7 @@
 name = "Winston"
 title = "System Architect"
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays (persistent_facts, principles, activation_steps_*): append
 #   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
 
@@ -40,7 +40,7 @@ persistent_facts = [
   "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 = "Convert the PRD and UX into technical architecture decisions that keep implementation on track during the BMad Method solutioning phase."
+role = "Convert the PRD and UX into technical architecture decisions that keep implementation on track during the Wizz Method solutioning phase."
 identity = "Channels Martin Fowler's pragmatism and Werner Vogels's cloud-scale realism."
 communication_style = "Calm and pragmatic. Balances 'what could be' with 'what should be.' Answers with trade-offs, not verdicts."
 

package/src/bmm-skills/3-solutioning/wizz-architecture/SKILL.md

@@ -2,7 +2,7 @@
 name: wizz-architecture
 description: 'Produce the architecture: a lean spine of invariants that keeps everything built from it consistent, projected into whatever format the work needs. Use when the user says "create the architecture", "create technical architecture", "architecture spine", or "create a solution design".'
 ---
-# BMad Architecture
+# Wizz Architecture
 
 ## Overview
 
@@ -52,7 +52,7 @@ Writes go through the shared script (don't read the file back except on resume):
 
 1. Resolve customization: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow` (on failure read `{skill-root}/customize.toml`, use defaults). Run `{workflow.activation_steps_prepend}`, then `{workflow.activation_steps_append}`. Hold `{workflow.persistent_facts}` as standing context — the default loads `project-context.md`, load-bearing for brownfield — and consult `{workflow.external_sources}` on demand.
 2. Load `{project-root}/_wizz/bmm/config.yaml` (+ `config.user.yaml`) for `{user_name}`, `{communication_language}`, `{document_output_language}`, `{planning_artifacts}`, `{project_name}`, `{date}`; missing keys take neutral defaults, never block.
-3. Headless (no interactive user) → follow `references/headless.md` for the whole run. Otherwise greet `{user_name}` in `{communication_language}`. Detect the intent from the conversation and input — **create** (the default), **update** an existing spine, or **validate** one (see those sections). If the real ask is requirements / UX / a capability contract / epic breakdown / an agent, invoke the `wizz-prd`, `wizz-ux`, `wizz-spec`, `wizz-create-epics-and-stories`, or `bmad-workflow-builder` (if the BMad Builder module is installed) skill instead.
+3. Headless (no interactive user) → follow `references/headless.md` for the whole run. Otherwise greet `{user_name}` in `{communication_language}`. Detect the intent from the conversation and input — **create** (the default), **update** an existing spine, or **validate** one (see those sections). If the real ask is requirements / UX / a capability contract / epic breakdown / an agent, invoke the `wizz-prd`, `wizz-ux`, `wizz-spec`, `wizz-create-epics-and-stories`, or `wizz-workflow-builder` (if the Wizz Builder module is installed) skill instead.
 4. If a run folder for this target already exists under `{workflow.spine_output_path}`, offer to resume from its memlog rather than restart.
 5. Interactive create: offer the working mode in `{communication_language}` — **Coaching path** (default) or **Fast path** (see *How you work*) — before any drafting; default to Coaching unless the user asks for speed.
 6. **Mandatory, both paths, before drafting:** ask whether the spine is the only deliverable — and if not, draw out the *purpose and audience* rather than a document type. "An architecture doc" balloons into bloat; what they actually need might be a one-detail explainer for a single team or a non-technical vision piece for a board. Purpose right-sizes the artifact and may call for extra elicitation up front, not just a finale add-on.

package/src/bmm-skills/3-solutioning/wizz-architecture/customize.toml

@@ -8,7 +8,7 @@
 
 [workflow]
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays: append
 
 # Steps to run before the standard activation (config load, greet).
@@ -73,7 +73,9 @@ doc_standards = [
 # Examples (set in team/user override TOML):
 #   "When choosing a datastore, consult corp:platform_catalog before recommending one."
 #   "For current library versions, query corp:artifact_registry before web search."
-external_sources = []
+external_sources = [
+  "For current library/framework docs, APIs, and versions, consult Context7 before web search: call resolve-library-id with the library name, then query-docs with the returned /org/project id and a specific question. If Context7 is unavailable, tell the user once that they can enable it with `npx ctx7 setup`, then fall back to web research and note the gap.",
+]
 
 # External-handoff routing applied at Finalize to push outputs beyond local files (Confluence,
 # Notion, ticket systems). Each entry names the MCP tool, the destination, and required fields.

package/src/bmm-skills/3-solutioning/wizz-check-implementation-readiness/customize.toml

@@ -5,7 +5,7 @@
 
 [workflow]
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
 #   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
 

package/src/bmm-skills/3-solutioning/wizz-create-architecture/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wizz-create-architecture
-description: 'DEPRECATED — consolidated into wizz-architecture create intent - this skill will be removed in v7 in favor of `wizz-architecture`.'
+description: 'DEPRECATED — consolidated into wizz-architecture create intent - this skill will be removed in v7 in favor of `wizz-architecture`. Use when needed for backwards compatibility.'
 ---
 
 # DEPRECATED — forwards to wizz-architecture (create intent)

package/src/bmm-skills/3-solutioning/wizz-create-architecture/customize.toml

@@ -5,7 +5,7 @@
 
 [workflow]
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
 #   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
 

package/src/bmm-skills/3-solutioning/wizz-create-epics-and-stories/customize.toml

@@ -5,7 +5,7 @@
 
 [workflow]
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
 #   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
 

package/src/bmm-skills/3-solutioning/wizz-generate-project-context/customize.toml

@@ -5,7 +5,7 @@
 
 [workflow]
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
 #   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
 

package/src/bmm-skills/4-implementation/wizz-agent-dev/customize.toml

@@ -9,7 +9,7 @@
 name = "Amelia"
 title = "Senior Software Engineer"
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays (persistent_facts, principles, activation_steps_*): append
 #   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
 
@@ -38,9 +38,10 @@ 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.",
+  "When implementing against a library or framework, consult Context7 for current docs, APIs, and version-specific syntax before relying on training data or web search: call resolve-library-id with the library name, then query-docs with the returned /org/project id and a specific question. If Context7 is unavailable, tell the user once that they can enable it with `npx ctx7 setup`, then fall back to web research.",
 ]
 
-role = "Implement approved stories with test-first discipline and ship working, verified code during the BMad Method implementation phase."
+role = "Implement approved stories with test-first discipline and ship working, verified code during the Wizz Method implementation phase."
 identity = "Disciplined in Kent Beck's TDD and the Pragmatic Programmer's precision."
 communication_style = "Ultra-succinct. Speaks in file paths and AC IDs — every statement citable. No fluff, all precision."
 

package/src/bmm-skills/4-implementation/wizz-checkpoint-preview/customize.toml

@@ -5,7 +5,7 @@
 
 [workflow]
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
 #   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
 

package/src/bmm-skills/4-implementation/wizz-code-review/customize.toml

@@ -5,7 +5,7 @@
 
 [workflow]
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
 #   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
 

package/src/bmm-skills/4-implementation/wizz-correct-course/customize.toml

@@ -5,7 +5,7 @@
 
 [workflow]
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
 #   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
 

package/src/bmm-skills/4-implementation/wizz-create-story/SKILL.md

@@ -410,7 +410,7 @@ Activation is complete. If `activation_steps_prepend` or `activation_steps_appen
   </check>
 
   <action>Report completion</action>
-  <output>**🎯 ULTIMATE BMad Method STORY CONTEXT CREATED, {user_name}!**
+  <output>**🎯 ULTIMATE Wizz Method STORY CONTEXT CREATED, {user_name}!**
 
     **Story Details:**
     - Story ID: {{story_id}}
@@ -422,7 +422,7 @@ Activation is complete. If `activation_steps_prepend` or `activation_steps_appen
     1. Review the comprehensive story in {{story_file}}
     2. Run dev agents `dev-story` for optimized implementation
     3. Run `code-review` when complete (auto-marks done)
-    4. Optional: If Test Architect module installed, run `/bmad:tea:automate` after `dev-story` to generate guardrail tests
+    4. Optional: If Test Architect module installed, run `/wizz:tea:automate` after `dev-story` to generate guardrail tests
 
     **The developer now has everything needed for flawless implementation!**
   </output>

package/src/bmm-skills/4-implementation/wizz-create-story/customize.toml

@@ -5,7 +5,7 @@
 
 [workflow]
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
 #   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
 

package/src/bmm-skills/4-implementation/wizz-dev-story/SKILL.md

@@ -487,7 +487,7 @@ Activation is complete. If `activation_steps_prepend` or `activation_steps_appen
       - Verify all acceptance criteria are met
       - Ensure deployment readiness if applicable
       - Run `code-review` workflow for peer review
-      - Optional: If Test Architect module installed, run `/bmad:tea:automate` to expand guardrail tests
+      - Optional: If Test Architect module installed, run `/wizz:tea:automate` to expand guardrail tests
     </action>
 
     <output>💡 **Tip:** For best results, run `code-review` using a **different** LLM than the one that implemented this story.</output>

package/src/bmm-skills/4-implementation/wizz-dev-story/customize.toml

@@ -5,7 +5,7 @@
 
 [workflow]
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
 #   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
 

package/src/bmm-skills/4-implementation/wizz-investigate/customize.toml

@@ -5,7 +5,7 @@
 
 [workflow]
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
 #   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
 

package/src/bmm-skills/4-implementation/wizz-qa-generate-e2e-tests/customize.toml

@@ -5,7 +5,7 @@
 
 [workflow]
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
 #   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
 

package/src/bmm-skills/4-implementation/wizz-quick-dev/customize.toml

@@ -5,7 +5,7 @@
 
 [workflow]
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
 #   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
 

package/src/bmm-skills/4-implementation/wizz-quick-dev/step-01-clarify-and-route.md

@@ -69,7 +69,7 @@ If the spec is an epic story and `{sprint_status}` exists: find the `development
      6. **Resolve `{story_key}`.** If not already set by an earlier early-exit path, run **Story-key resolution** (above) now.
 
      **B) Freeform path** — if the intent is not an epic story:
-     - Planning artifacts are the output of BMAD phases 1-3. Typical files include:
+     - Planning artifacts are the output of WIZZ phases 1-3. Typical files include:
        - **PRD** (`*prd*`) — product requirements and success criteria
        - **Architecture** (`*architecture*`) — technical design decisions and constraints
        - **UX/Design** (`*ux*`) — user experience and interaction design

package/src/bmm-skills/4-implementation/wizz-retrospective/customize.toml

@@ -5,7 +5,7 @@
 
 [workflow]
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
 #   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
 

package/src/bmm-skills/4-implementation/wizz-sprint-planning/customize.toml

@@ -5,7 +5,7 @@
 
 [workflow]
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
 #   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
 

package/src/bmm-skills/4-implementation/wizz-sprint-status/SKILL.md

@@ -94,7 +94,7 @@ Activation is complete. If `activation_steps_prepend` or `activation_steps_appen
   <action>Try {sprint_status_file}</action>
   <check if="file not found">
     <output>sprint-status.yaml not found.
-Run `/bmad:bmm:workflows:sprint-planning` to generate it, then rerun sprint-status.</output>
+Run `/wizz:bmm:workflows:sprint-planning` to generate it, then rerun sprint-status.</output>
     <action>Exit workflow</action>
   </check>
   <action>Continue to Step 2</action>
@@ -150,9 +150,9 @@ Enter corrections (e.g., "1=in-progress, 2=backlog") or "skip" to continue witho
 
 <action>Detect risks:</action>
 
-- IF any story has status "review": suggest `/bmad:bmm:workflows:code-review`
+- IF any story has status "review": suggest `/wizz:bmm:workflows:code-review`
 - IF any story has status "in-progress" AND no stories have status "ready-for-dev": recommend staying focused on active story
-- IF all epics have status "backlog" AND no stories have status "ready-for-dev": prompt `/bmad:bmm:workflows:create-story`
+- IF all epics have status "backlog" AND no stories have status "ready-for-dev": prompt `/wizz:bmm:workflows:create-story`
 - IF `last_updated` timestamp is more than 7 days old (or `last_updated` is missing, fall back to `generated`): warn "sprint-status.yaml may be stale"
 - IF any story key doesn't match an epic pattern (e.g., story "5-1-..." but no "epic-5"): warn "orphaned story detected"
 - IF any epic has status in-progress but has no associated stories: warn "in-progress epic has no stories"
@@ -182,7 +182,7 @@ Enter corrections (e.g., "1=in-progress, 2=backlog") or "skip" to continue witho
 
 **Epics:** backlog {{epic_backlog}}, in-progress {{epic_in_progress}}, done {{epic_done}}
 
-**Next Recommendation:** /bmad:bmm:workflows:{{next_workflow_id}} ({{next_story_id}})
+**Next Recommendation:** /wizz:bmm:workflows:{{next_workflow_id}} ({{next_story_id}})
 
 {{#if open_action_items}}
 **Open Action Items:**
@@ -212,7 +212,7 @@ Enter corrections (e.g., "1=in-progress, 2=backlog") or "skip" to continue witho
 Choice:</ask>
 
   <check if="choice == 1">
-    <output>Run `/bmad:bmm:workflows:{{next_workflow_id}}`.
+    <output>Run `/wizz:bmm:workflows:{{next_workflow_id}}`.
 If the command targets a story, set `story_key={{next_story_id}}` when prompted.</output>
   </check>
 

package/src/bmm-skills/4-implementation/wizz-sprint-status/customize.toml

@@ -5,7 +5,7 @@
 
 [workflow]
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
 #   arrays-of-tables with `code`/`id`: replace matching items, append new ones.