wizz-method 1.0.2 → 1.1.0

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/SKILL.md

@@ -33,6 +33,13 @@ A specification should target a **single user-facing goal** within **900–1600
 - **900–1600 tokens**: Optimal range for LLM consumption. Below 900 risks ambiguity; above 1600 risks context-rot in implementation agents.
 - **Neither limit is a gate.** Both are proposals with user override.
 
+## Handoff — escalate up when scope balloons
+
+You are the leaf: the maestro demotes here for pointed work (bug, tweak, single-goal feature). Re-check scope against the shared complexity signal (areas, steps, needs-planning?, artifact+memory?):
+
+- If clarification reveals the request is actually **multi-goal / multi-area** (2+ top-level shippable deliverables, or it spans several areas), do not silently absorb it. Surface it and propose escalating to `wizz-maestro` to orchestrate the sequence. Proceed solo only if the user confirms a narrowed single goal.
+- Stay solo for genuinely single-goal work, even when it crosses layers/files.
+
 ## Conventions
 
 - Bare paths (e.g. `step-01-clarify-and-route.md`) resolve from the skill root.

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.
 

package/src/bmm-skills/module-help.csv

@@ -1,33 +1,33 @@
 module,skill,display-name,menu-code,description,action,args,phase,preceded-by,followed-by,required,output-location,outputs
-BMad Method,_meta,,,,,,,,,false,https://docs.bmad-method.org/llms.txt,
-BMad Method,wizz-document-project,Document Project,DP,Analyze an existing project to produce useful documentation.,,,anytime,,,false,project-knowledge,*
-BMad Method,wizz-set-feature,Set Feature,SF,Set or switch the active feature context so planning and implementation artifacts are organized into a named subfolder.,,,anytime,,,false,,
-BMad Method,wizz-generate-project-context,Generate Project Context,GPC,Scan existing codebase to generate a lean LLM-optimized project-context.md. Essential for brownfield projects.,,,anytime,,,false,output_folder,project context
-BMad Method,wizz-quick-dev,Quick Dev,QQ,Unified intent-in code-out workflow: clarify plan implement review and present.,,,anytime,,,false,implementation_artifacts,spec and project implementation
-BMad Method,wizz-correct-course,Correct Course,CC,Navigate significant changes. May recommend start over update PRD redo architecture sprint planning or correct epics and stories.,,,anytime,,,false,planning_artifacts,change proposal
-BMad Method,wizz-agent-tech-writer,Write Document,WD,"Describe in detail what you want, and the agent will follow documentation best practices. Multi-turn conversation with subprocess for research/review.",write,,anytime,,,false,project-knowledge,document
-BMad Method,wizz-agent-tech-writer,Update Standards,US,Update agent memory documentation-standards.md with your specific preferences if you discover missing document conventions.,update-standards,,anytime,,,false,_wizz/_memory/tech-writer-sidecar,standards
-BMad Method,wizz-agent-tech-writer,Mermaid Generate,MG,Create a Mermaid diagram based on user description. Will suggest diagram types if not specified.,mermaid,,anytime,,,false,planning_artifacts,mermaid diagram
-BMad Method,wizz-agent-tech-writer,Validate Document,VD,Review the specified document against documentation standards and best practices. Returns specific actionable improvement suggestions organized by priority.,validate,[path],anytime,,,false,planning_artifacts,validation report
-BMad Method,wizz-agent-tech-writer,Explain Concept,EC,Create clear technical explanations with examples and diagrams for complex concepts.,explain,[topic],anytime,,,false,project_knowledge,explanation
-BMad Method,wizz-brainstorming,Brainstorm Project,BP,Expert guided facilitation through a single or multiple techniques.,,,1-analysis,,,false,planning_artifacts,brainstorming session
-BMad Method,wizz-market-research,Market Research,MR,Market analysis competitive landscape customer needs and trends.,,,1-analysis,,,false,planning_artifacts|project-knowledge,research documents
-BMad Method,wizz-domain-research,Domain Research,DR,Industry domain deep dive subject matter expertise and terminology.,,,1-analysis,,,false,planning_artifacts|project_knowledge,research documents
-BMad Method,wizz-technical-research,Technical Research,TR,Technical feasibility architecture options and implementation approaches.,,,1-analysis,,,false,planning_artifacts|project_knowledge,research documents
-BMad Method,wizz-product-brief,Create Brief,CB,An expert guided experience to nail down your product idea in a brief. a gentler approach than PRFAQ when you are already sure of your concept and nothing will sway you.,,-A,1-analysis,,,false,planning_artifacts,product brief
-BMad Method,wizz-prfaq,PRFAQ Challenge,WB,Working Backwards guided experience to forge and stress-test your product concept to ensure you have a great product that users will love and need through the PRFAQ gauntlet to determine feasibility and alignment with user needs. alternative to product brief.,,-H,1-analysis,,,false,planning_artifacts,prfaq document
-BMad Method,wizz-prd,Create Edit and Review PRD,PRD,"Facilitated PRD workflow — create a new PRD via coached discovery, update an existing one against a change signal, or validate a finished PRD against a checklist with an HTML findings report.",,,2-planning,wizz-product-brief,,true,planning_artifacts,prd
-BMad Method,wizz-ux,Create UX,CU,"Guidance through realizing the plan for your UX, strongly recommended if a UI is a primary piece of the proposed project.",,,2-planning,wizz-prd,,false,planning_artifacts,ux design
-BMad Method,wizz-architecture,Architecture,CA,Offer once requirements exist (a PRD or spec; plus UX if present) and the user is ready to move from what to how. Also offer any time independently-built parts risk diverging. Produces the architecture spine: the invariants that keep features epics and stories consistent. Comes before epics and stories and scales from a quick spine to a full architecture (brownfield: ratifies the existing codebase).,,,3-solutioning,,,true,planning_artifacts,architecture
-BMad Method,wizz-create-epics-and-stories,Create Epics and Stories,CE,,,,3-solutioning,wizz-architecture,,true,planning_artifacts,epics and stories
-BMad Method,wizz-check-implementation-readiness,Check Implementation Readiness,IR,Ensure PRD UX Architecture and Epics Stories are aligned.,,,3-solutioning,wizz-create-epics-and-stories,,true,planning_artifacts,readiness report
-BMad Method,wizz-sprint-planning,Sprint Planning,SP,Kicks off implementation by producing a plan the implementation agents will follow in sequence for every story.,,,4-implementation,,,true,implementation_artifacts,sprint status
-BMad Method,wizz-sprint-status,Sprint Status,SS,Anytime: Summarize sprint status and route to next workflow.,,,4-implementation,wizz-sprint-planning,,false,,
-BMad Method,wizz-create-story,Create Story,CS,Story cycle start: Prepare first found story in the sprint plan that is next or a specific epic/story designation.,create,,4-implementation,wizz-sprint-planning,wizz-create-story:validate,true,implementation_artifacts,story
-BMad Method,wizz-create-story,Validate Story,VS,Validates story readiness and completeness before development work begins.,validate,,4-implementation,wizz-create-story:create,wizz-dev-story,false,implementation_artifacts,story validation report
-BMad Method,wizz-dev-story,Dev Story,DS,Story cycle: Execute story implementation tasks and tests then CR then back to DS if fixes needed.,,,4-implementation,wizz-create-story:validate,,true,,
-BMad Method,wizz-code-review,Code Review,CR,Story cycle: If issues back to DS if approved then next CS or ER if epic complete.,,,4-implementation,wizz-dev-story,,false,,
-BMad Method,wizz-checkpoint-preview,Checkpoint,CK,Guided walkthrough of a change from purpose and context into details. Use for human review of commits branches or PRs.,,,4-implementation,,,false,,
-BMad Method,wizz-qa-generate-e2e-tests,QA Automation Test,QA,Generate automated API and E2E tests for implemented code. NOT for code review or story validation — use CR for that.,,,4-implementation,wizz-dev-story,,false,implementation_artifacts,test suite
-BMad Method,wizz-retrospective,Retrospective,ER,Optional at epic end: Review completed work lessons learned and next epic or if major issues consider CC.,,,4-implementation,wizz-code-review,,false,implementation_artifacts,retrospective
-BMad Method,wizz-investigate,Investigate,IN,Forensic case investigation calibrated to the input. Evidence-graded analysis with hypothesis tracking. Produces a structured case file.,,4-implementation,,,false,implementation_artifacts,investigation report
+Wizz Method,_meta,,,,,,,,,false,https://docs.wizz-method.org/llms.txt,
+Wizz Method,wizz-document-project,Document Project,DP,Analyze an existing project to produce useful documentation.,,,anytime,,,false,project-knowledge,*
+Wizz Method,wizz-set-feature,Set Feature,SF,Set or switch the active feature context so planning and implementation artifacts are organized into a named subfolder.,,,anytime,,,false,,
+Wizz Method,wizz-generate-project-context,Generate Project Context,GPC,Scan existing codebase to generate a lean LLM-optimized project-context.md. Essential for brownfield projects.,,,anytime,,,false,output_folder,project context
+Wizz Method,wizz-quick-dev,Quick Dev,QQ,Unified intent-in code-out workflow: clarify plan implement review and present.,,,anytime,,,false,implementation_artifacts,spec and project implementation
+Wizz Method,wizz-correct-course,Correct Course,CC,Navigate significant changes. May recommend start over update PRD redo architecture sprint planning or correct epics and stories.,,,anytime,,,false,planning_artifacts,change proposal
+Wizz Method,wizz-agent-tech-writer,Write Document,WD,"Describe in detail what you want, and the agent will follow documentation best practices. Multi-turn conversation with subprocess for research/review.",write,,anytime,,,false,project-knowledge,document
+Wizz Method,wizz-agent-tech-writer,Update Standards,US,Update agent memory documentation-standards.md with your specific preferences if you discover missing document conventions.,update-standards,,anytime,,,false,_wizz/_memory/tech-writer-sidecar,standards
+Wizz Method,wizz-agent-tech-writer,Mermaid Generate,MG,Create a Mermaid diagram based on user description. Will suggest diagram types if not specified.,mermaid,,anytime,,,false,planning_artifacts,mermaid diagram
+Wizz Method,wizz-agent-tech-writer,Validate Document,VD,Review the specified document against documentation standards and best practices. Returns specific actionable improvement suggestions organized by priority.,validate,[path],anytime,,,false,planning_artifacts,validation report
+Wizz Method,wizz-agent-tech-writer,Explain Concept,EC,Create clear technical explanations with examples and diagrams for complex concepts.,explain,[topic],anytime,,,false,project_knowledge,explanation
+Wizz Method,wizz-brainstorming,Brainstorm Project,BP,Expert guided facilitation through a single or multiple techniques.,,,1-analysis,,,false,planning_artifacts,brainstorming session
+Wizz Method,wizz-market-research,Market Research,MR,Market analysis competitive landscape customer needs and trends.,,,1-analysis,,,false,planning_artifacts|project-knowledge,research documents
+Wizz Method,wizz-domain-research,Domain Research,DR,Industry domain deep dive subject matter expertise and terminology.,,,1-analysis,,,false,planning_artifacts|project_knowledge,research documents
+Wizz Method,wizz-technical-research,Technical Research,TR,Technical feasibility architecture options and implementation approaches.,,,1-analysis,,,false,planning_artifacts|project_knowledge,research documents
+Wizz Method,wizz-product-brief,Create Brief,CB,An expert guided experience to nail down your product idea in a brief. a gentler approach than PRFAQ when you are already sure of your concept and nothing will sway you.,,-A,1-analysis,,,false,planning_artifacts,product brief
+Wizz Method,wizz-prfaq,PRFAQ Challenge,WB,Working Backwards guided experience to forge and stress-test your product concept to ensure you have a great product that users will love and need through the PRFAQ gauntlet to determine feasibility and alignment with user needs. alternative to product brief.,,-H,1-analysis,,,false,planning_artifacts,prfaq document
+Wizz Method,wizz-prd,Create Edit and Review PRD,PRD,"Facilitated PRD workflow — create a new PRD via coached discovery, update an existing one against a change signal, or validate a finished PRD against a checklist with an HTML findings report.",,,2-planning,wizz-product-brief,,true,planning_artifacts,prd
+Wizz Method,wizz-ux,Create UX,CU,"Guidance through realizing the plan for your UX, strongly recommended if a UI is a primary piece of the proposed project.",,,2-planning,wizz-prd,,false,planning_artifacts,ux design
+Wizz Method,wizz-architecture,Architecture,CA,Offer once requirements exist (a PRD or spec; plus UX if present) and the user is ready to move from what to how. Also offer any time independently-built parts risk diverging. Produces the architecture spine: the invariants that keep features epics and stories consistent. Comes before epics and stories and scales from a quick spine to a full architecture (brownfield: ratifies the existing codebase).,,,3-solutioning,,,true,planning_artifacts,architecture
+Wizz Method,wizz-create-epics-and-stories,Create Epics and Stories,CE,,,,3-solutioning,wizz-architecture,,true,planning_artifacts,epics and stories
+Wizz Method,wizz-check-implementation-readiness,Check Implementation Readiness,IR,Ensure PRD UX Architecture and Epics Stories are aligned.,,,3-solutioning,wizz-create-epics-and-stories,,true,planning_artifacts,readiness report
+Wizz Method,wizz-sprint-planning,Sprint Planning,SP,Kicks off implementation by producing a plan the implementation agents will follow in sequence for every story.,,,4-implementation,,,true,implementation_artifacts,sprint status
+Wizz Method,wizz-sprint-status,Sprint Status,SS,Anytime: Summarize sprint status and route to next workflow.,,,4-implementation,wizz-sprint-planning,,false,,
+Wizz Method,wizz-create-story,Create Story,CS,Story cycle start: Prepare first found story in the sprint plan that is next or a specific epic/story designation.,create,,4-implementation,wizz-sprint-planning,wizz-create-story:validate,true,implementation_artifacts,story
+Wizz Method,wizz-create-story,Validate Story,VS,Validates story readiness and completeness before development work begins.,validate,,4-implementation,wizz-create-story:create,wizz-dev-story,false,implementation_artifacts,story validation report
+Wizz Method,wizz-dev-story,Dev Story,DS,Story cycle: Execute story implementation tasks and tests then CR then back to DS if fixes needed.,,,4-implementation,wizz-create-story:validate,,true,,
+Wizz Method,wizz-code-review,Code Review,CR,Story cycle: If issues back to DS if approved then next CS or ER if epic complete.,,,4-implementation,wizz-dev-story,,false,,
+Wizz Method,wizz-checkpoint-preview,Checkpoint,CK,Guided walkthrough of a change from purpose and context into details. Use for human review of commits branches or PRs.,,,4-implementation,,,false,,
+Wizz Method,wizz-qa-generate-e2e-tests,QA Automation Test,QA,Generate automated API and E2E tests for implemented code. NOT for code review or story validation — use CR for that.,,,4-implementation,wizz-dev-story,,false,implementation_artifacts,test suite
+Wizz Method,wizz-retrospective,Retrospective,ER,Optional at epic end: Review completed work lessons learned and next epic or if major issues consider CC.,,,4-implementation,wizz-code-review,,false,implementation_artifacts,retrospective
+Wizz Method,wizz-investigate,Investigate,IN,Forensic case investigation calibrated to the input. Evidence-graded analysis with hypothesis tracking. Produces a structured case file.,,4-implementation,,,false,implementation_artifacts,investigation report

package/src/bmm-skills/module.yaml

@@ -1,5 +1,5 @@
 code: bmm
-name: "BMad Method"
+name: "Wizz Method"
 description: "Full-lifecycle AI agile development: analysis, planning, architecture, implementation"
 default_selected: true # This module will be selected by default for new installations
 

package/src/core-skills/module-help.csv

@@ -1,8 +1,8 @@
 module,skill,display-name,menu-code,description,action,args,phase,preceded-by,followed-by,required,output-location,outputs
-Core,_meta,,,,,,,,,false,https://docs.bmad-method.org/llms.txt,
+Core,_meta,,,,,,,,,false,https://docs.wizz-method.org/llms.txt,
 Core,wizz-brainstorming,Brainstorming,BSP,Use early in ideation or when stuck generating ideas.,,,anytime,,,false,{output_folder}/brainstorming,brainstorming session
 Core,wizz-party-mode,Party Mode,PM,Orchestrate multi-agent discussions when you need multiple perspectives or want agents to collaborate.,,,anytime,,,false,,
-Core,wizz-help,BMad Help,BH,,,,anytime,,,false,,
+Core,wizz-help,Wizz Help,BH,,,,anytime,,,false,,
 Core,wizz-index-docs,Index Docs,ID,Use when LLM needs to understand available docs without loading everything.,,,anytime,,,false,,
 Core,wizz-shard-doc,Shard Document,SD,Use when doc becomes too large (>500 lines) to manage effectively.,,[path],anytime,,,false,,
 Core,wizz-editorial-review-prose,Editorial Review - Prose,EP,Use after drafting to polish written content.,,[path],anytime,,,false,report located with target document,three-column markdown table with suggested fixes
@@ -10,4 +10,4 @@ Core,wizz-editorial-review-structure,Editorial Review - Structure,ES,Use when do
 Core,wizz-review-adversarial-general,Adversarial Review,AR,"Use for quality assurance or before finalizing deliverables. Code Review in other modules runs this automatically, but also useful for document reviews.",,[path],anytime,,,false,,
 Core,wizz-review-edge-case-hunter,Edge Case Hunter Review,ECH,Use alongside adversarial review for orthogonal coverage — method-driven not attitude-driven.,,[path],anytime,,,false,,
 Core,wizz-spec,Spec,SP,"Use to distill any intent input (brief, PRD, transcript, brain dump, design folder, mixed multi-source) into a succinct, no-fluff SPEC.md contract + companions that downstream work derives from. Locks the WHAT before the HOW. Works for software, game design, research, editorial, policy, business, anything intent-bearing. Validation mode also available.",,[path],anytime,,,false,{output_folder}/specs/spec-{slug},SPEC.md + companion files
-Core,wizz-customize,BMad Customize,BC,"Use when you want to change how an agent or workflow behaves — add persistent facts, swap templates, insert activation hooks, or customize menus. Scans what's customizable, picks the right scope (agent vs workflow), writes the override to _wizz/custom/, and verifies the merge. No TOML hand-authoring required.",,,anytime,,,false,{project-root}/_wizz/custom,TOML override files
+Core,wizz-customize,Wizz Customize,BC,"Use when you want to change how an agent or workflow behaves — add persistent facts, swap templates, insert activation hooks, or customize menus. Scans what's customizable, picks the right scope (agent vs workflow), writes the override to _wizz/custom/, and verifies the merge. No TOML hand-authoring required.",,,anytime,,,false,{project-root}/_wizz/custom,TOML override files

package/src/core-skills/module.yaml

@@ -1,14 +1,14 @@
 code: core
-name: "BMad Core Module"
+name: "Wizz Core Module"
 description: "Shared utilities across modules"
 
-header: "BMad Core Configuration"
-subheader: "Configure the core settings for your BMad installation.\nThese settings will be used across all installed bmad skills, workflows, and agents."
+header: "Wizz Core Configuration"
+subheader: "Configure the core settings for your Wizz installation.\nThese settings will be used across all installed wizz skills, workflows, and agents."
 
 user_name:
   prompt: "What should agents call you? (Use your name or a team name)"
   scope: user
-  default: "BMad"
+  default: "Wizz"
   result: "{value}"
 
 project_name:

package/src/core-skills/wizz-brainstorming/SKILL.md

@@ -3,7 +3,7 @@ name: wizz-brainstorming
 description: Facilitate a brainstorming session using diverse creative techniques. Use when the user says 'help me brainstorm' or 'help me ideate'.
 ---
 
-# BMad Brainstorming
+# Wizz Brainstorming
 
 ## Overview
 

package/src/core-skills/wizz-brainstorming/analysis/catalog-analysis.md

@@ -1,4 +1,4 @@
-# BMad Brainstorming Catalog — Deep Analysis
+# Wizz Brainstorming Catalog — Deep Analysis
 
 > Analysis of the brainstorming library (`assets/brain-methods.csv`) and the selection
 > experience (`assets/brain-selector.html`, generated by `scripts/brain.py`). Companion
@@ -51,7 +51,7 @@ The methods an innovation consultant or enterprise facilitator would recognize b
 > Provocation (PO) · Question Storming · Brainwriting/Round Robin · Yes-And · Random Stimulation ·
 > Role Playing · Analogical Thinking
 
-A second tier is *recognizable-adjacent* (Concept Blending, Forced Relationships, Decision Tree, Solution Matrix, Failure Analysis/pre-mortem, Devil's Advocate, 1000x Budget). Everything else is `signature` (BMad-original, serious) or `playful` (the delight layer — `wild`, `absurdist`, `theatrical`, much of `quantum`/`cultural`).
+A second tier is *recognizable-adjacent* (Concept Blending, Forced Relationships, Decision Tree, Solution Matrix, Failure Analysis/pre-mortem, Devil's Advocate, 1000x Budget). Everything else is `signature` (Wizz-original, serious) or `playful` (the delight layer — `wild`, `absurdist`, `theatrical`, much of `quantum`/`cultural`).
 
 **Recommendation — lead with "Proven & Professional."** Three ways to implement (pick in review):
 
@@ -188,7 +188,7 @@ Benefits: CSV stays a clean library of *real* techniques; behavior is consistent
 
 ---
 
-## 9. Open decisions for BMad (in priority order)
+## 9. Open decisions for Wizz (in priority order)
 
 1. **Goal-affinity layer** — adopt the `goals` column + recommendation routing? (Highest impact.)
 2. **Proven & Professional grouping** — Option A (tag + generated lead section, recommended), B, or C? (§3a)
@@ -202,7 +202,7 @@ Once you mark these, the implementation is: extend the CSV schema (`provenance`,
 
 ---
 
-## 10. Revised convergence architecture (per BMad direction)
+## 10. Revised convergence architecture (per Wizz direction)
 
 **Decision locked:** convergence is **not** a CSV category of selectable cards. It's a **reference phase**, mirroring `references/finalize.md`. The catalog stays a pure *divergent* library; convergence lives in `references/converge.md`.