npm - wizz-method - Versions diffs - 1.0.0 → 1.0.2 - Mend

wizz-method 1.0.0 → 1.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (709) hide show

package/build/site/workflow-map-diagram.html CHANGED Viewed

@@ -3,7 +3,7 @@
 <head>
     <meta charset="UTF-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <title>BMad Method Workflow Map</title>
+    <title>Wizz Method Workflow Map</title>
     <style>
         :root {
             --analysis: #0ea5e9;
@@ -131,7 +131,7 @@
 <body>
     <div class="header">
         <div class="header-badge">⚡ Workflow Map V6</div>
-        <h1>BMad Method</h1>
+        <h1>Wizz Method</h1>
         <p class="subtitle">Context engineering for AI-powered development</p>
     </div>

package/evals/bmm-skills/{bmad-product-brief → wizz-product-brief}/evals.json RENAMED Viewed

@@ -1,5 +1,5 @@
 {
-  "skill_name": "bmad-product-brief",
+  "skill_name": "wizz-product-brief",
   "_design_notes": "Single-shot evals across two patterns. Pattern A (A1-A8) tests artifact correctness given complete inputs in headless mode. Pattern B tests process discipline (decision log fidelity, polish execution, intent boundaries) by inspecting transcript and side-artifacts. Facilitation/conversation-quality evals are deferred to a future multi-turn simulator.",
   "evals": [
     {
@@ -38,9 +38,9 @@
     {
       "id": "A3",
       "_pattern": "artifact-correctness",
-      "prompt": "Run headless. Create a brief for our neighborhood compost coordinator app idea — we are moving forward with it. Q2 brainstorming session notes are at evals/bmm-skills/bmad-product-brief/files/q2-brainstorm.md; pull only what is relevant to the compost concept.",
+      "prompt": "Run headless. Create a brief for our neighborhood compost coordinator app idea — we are moving forward with it. Q2 brainstorming session notes are at evals/bmm-skills/wizz-product-brief/files/q2-brainstorm.md; pull only what is relevant to the compost concept.",
       "expected_output": "Brief focuses tightly on the compost coordinator concept. Source brainstorm is filtered, not ingested wholesale. Decision-log records that filtering occurred.",
-      "files": ["evals/bmm-skills/bmad-product-brief/files/q2-brainstorm.md"],
+      "files": ["evals/bmm-skills/wizz-product-brief/files/q2-brainstorm.md"],
       "expectations": [
         "brief.md addresses the neighborhood compost coordinator concept",
         "brief.md does not introduce content from unrelated brainstorm topics (weather + mood, meditation chime, podcasting tool, craft beer subscription, AI sommelier, office plants, ride coordinator, cookbook app, AR home staging)",
@@ -52,12 +52,12 @@
     {
       "id": "A4",
       "_pattern": "artifact-correctness",
-      "prompt": "Run headless. Validate the brief at evals/bmm-skills/bmad-product-brief/files/mossridge-brief/brief.md — the Mossridge Public Library board meets Monday and we need this to land. Read the addendum and decision-log in the same folder first. Cite specific sections, identify weaknesses, caveat what cannot be evaluated. Return inline only — no separate validation file.",
+      "prompt": "Run headless. Validate the brief at evals/bmm-skills/wizz-product-brief/files/mossridge-brief/brief.md — the Mossridge Public Library board meets Monday and we need this to land. Read the addendum and decision-log in the same folder first. Cite specific sections, identify weaknesses, caveat what cannot be evaluated. Return inline only — no separate validation file.",
       "expected_output": "Inline critique citing specific sections from the input brief. No new files. Caveats at least one claim that cannot be evaluated from the brief alone. Offers to roll findings into an Update.",
       "files": [
-        "evals/bmm-skills/bmad-product-brief/files/mossridge-brief/brief.md",
-        "evals/bmm-skills/bmad-product-brief/files/mossridge-brief/addendum.md",
-        "evals/bmm-skills/bmad-product-brief/files/mossridge-brief/decision-log.md"
+        "evals/bmm-skills/wizz-product-brief/files/mossridge-brief/brief.md",
+        "evals/bmm-skills/wizz-product-brief/files/mossridge-brief/addendum.md",
+        "evals/bmm-skills/wizz-product-brief/files/mossridge-brief/decision-log.md"
       ],
       "expectations": [
         "The final output cites specific section names or line content from the input brief (not generic feedback)",
@@ -85,9 +85,9 @@
     {
       "id": "A6",
       "_pattern": "artifact-correctness",
-      "prompt": "Run headless. Create a brief from this memo. It is from our last working group on a new microcredential program at Branfield Community College. Memo is at evals/bmm-skills/bmad-product-brief/files/branfield-memo.md. Use what is there; do not re-elicit facts already present.",
+      "prompt": "Run headless. Create a brief from this memo. It is from our last working group on a new microcredential program at Branfield Community College. Memo is at evals/bmm-skills/wizz-product-brief/files/branfield-memo.md. Use what is there; do not re-elicit facts already present.",
       "expected_output": "Brief reflects content from the memo. No re-asking for facts already present. Decision-log notes ingestion of the memo.",
-      "files": ["evals/bmm-skills/bmad-product-brief/files/branfield-memo.md"],
+      "files": ["evals/bmm-skills/wizz-product-brief/files/branfield-memo.md"],
       "expectations": [
         "brief.md incorporates at least 3 distinct facts or decisions present in the input memo",
         "decision-log.md references having used the memo as source material",
@@ -98,9 +98,9 @@
     {
       "id": "A7",
       "_pattern": "artifact-correctness",
-      "prompt": "Run headless. Create a brief for Brightway — our smart bike helmet with crash detection, turn signals, and braking lights. Meridian Insights produced a market research report on e-mobility at evals/bmm-skills/bmad-product-brief/files/meridian-mobility-report.md. Use only what is relevant to the safety helmet category — do not let the e-scooter, charging-infrastructure, or bike-share segments bleed into the brief.",
+      "prompt": "Run headless. Create a brief for Brightway — our smart bike helmet with crash detection, turn signals, and braking lights. Meridian Insights produced a market research report on e-mobility at evals/bmm-skills/wizz-product-brief/files/meridian-mobility-report.md. Use only what is relevant to the safety helmet category — do not let the e-scooter, charging-infrastructure, or bike-share segments bleed into the brief.",
       "expected_output": "Brief focuses on the smart bike helmet concept. Pulls relevant findings from the helmet section. Other mobility segments do not appear.",
-      "files": ["evals/bmm-skills/bmad-product-brief/files/meridian-mobility-report.md"],
+      "files": ["evals/bmm-skills/wizz-product-brief/files/meridian-mobility-report.md"],
       "expectations": [
         "brief.md addresses the Brightway smart bike helmet concept",
         "brief.md does not introduce content from unrelated mobility segments (e-scooters, charging infrastructure, bike-share, vehicle-to-grid)",
@@ -112,9 +112,9 @@
     {
       "id": "A8",
       "_pattern": "artifact-correctness",
-      "prompt": "Run headless. Create a brief for Pantry Bridge — a meal-kit subscription targeted at adults 65+ who live alone and want fresh meals without grocery shopping. Customer research transcripts are at evals/bmm-skills/bmad-product-brief/files/pantry-bridge-interviews.md. Pull what is relevant from the older-adult interviews; do not conflate insights from the working-parent, student, or corporate-buyer personas.",
+      "prompt": "Run headless. Create a brief for Pantry Bridge — a meal-kit subscription targeted at adults 65+ who live alone and want fresh meals without grocery shopping. Customer research transcripts are at evals/bmm-skills/wizz-product-brief/files/pantry-bridge-interviews.md. Pull what is relevant from the older-adult interviews; do not conflate insights from the working-parent, student, or corporate-buyer personas.",
       "expected_output": "Brief focuses on the older-adult target persona. Eleanor's interview drives the insights. Other personas do not pollute the brief.",
-      "files": ["evals/bmm-skills/bmad-product-brief/files/pantry-bridge-interviews.md"],
+      "files": ["evals/bmm-skills/wizz-product-brief/files/pantry-bridge-interviews.md"],
       "expectations": [
         "brief.md addresses the Pantry Bridge older-adult meal-kit concept",
         "brief.md does not conflate insights from non-target personas (working parent Susan, college student Marcus, corporate cafeteria buyer Dimitri)",
@@ -157,11 +157,11 @@
       "id": "B3",
       "_pattern": "process-discipline",
       "prompt": "Run headless. Create a product brief for InsuLens.\n\nContext (use exactly this — do not invent):\n- Product: a smartphone app that pairs with off-the-shelf $200 thermal imaging accessories (FLIR ONE Pro and Seek Compact Pro). The app guides homeowners through a structured walkthrough and produces a professional-grade insulation audit in under 20 minutes.\n- Target: suburban homeowners aged 35-65 with houses built before 2000.\n- Validation: 50 user interviews completed in Q4 2025; 78% willingness to pay $49 for a one-time audit.\n- Stakes: Series A pitch input.\n- Hardware: requires a thermal accessory (we do not manufacture hardware).\n\nProduce brief.md and decision-log.md. Run the polish phase before presenting.",
-      "expected_output": "The transcript shows the polish phase executing — the skill invokes bmad-editorial-review-structure and bmad-editorial-review-prose, either via the Skill tool directly or via Agent tool calls whose description or prompt targets those editorial skills. Both passes must occur after the initial draft is written and before the final JSON status block.",
+      "expected_output": "The transcript shows the polish phase executing — the skill invokes wizz-editorial-review-structure and wizz-editorial-review-prose, either via the Skill tool directly or via Agent tool calls whose description or prompt targets those editorial skills. Both passes must occur after the initial draft is written and before the final JSON status block.",
       "files": [],
       "expectations": [
-        "The transcript contains either a Skill tool call invoking bmad-editorial-review-structure, OR an Agent tool call whose description or prompt references structural review or bmad-editorial-review-structure",
-        "The transcript contains either a Skill tool call invoking bmad-editorial-review-prose, OR an Agent tool call whose description or prompt references prose review or bmad-editorial-review-prose",
+        "The transcript contains either a Skill tool call invoking wizz-editorial-review-structure, OR an Agent tool call whose description or prompt references structural review or wizz-editorial-review-structure",
+        "The transcript contains either a Skill tool call invoking wizz-editorial-review-prose, OR an Agent tool call whose description or prompt references prose review or wizz-editorial-review-prose",
         "Both editorial-pass dispatches (Skill or Agent) occur after the first Write tool call that creates brief.md",
         "Both editorial-pass dispatches (Skill or Agent) occur before the final assistant message containing the JSON status block"
       ]
@@ -169,12 +169,12 @@
     {
       "id": "B5",
       "_pattern": "process-discipline",
-      "prompt": "Run headless. Update the brief at evals/bmm-skills/bmad-product-brief/files/forkbird-brief/brief.md — we have decided to add B2B catering services for corporate events, in addition to the direct-to-consumer delivery model. Read the existing decision-log.md and addendum.md in the same folder first.",
+      "prompt": "Run headless. Update the brief at evals/bmm-skills/wizz-product-brief/files/forkbird-brief/brief.md — we have decided to add B2B catering services for corporate events, in addition to the direct-to-consumer delivery model. Read the existing decision-log.md and addendum.md in the same folder first.",
       "expected_output": "The skill MUST detect the contradiction with the prior 'rejected B2B catering for MVP' decision (in decision-log.md) before applying the change. Acceptable resolutions: (a) halt with blocked status surfacing the conflict, or (b) apply the change with addendum.md capturing the override and rationale. Brief must not silently flip without acknowledging the prior decision.",
       "files": [
-        "evals/bmm-skills/bmad-product-brief/files/forkbird-brief/brief.md",
-        "evals/bmm-skills/bmad-product-brief/files/forkbird-brief/addendum.md",
-        "evals/bmm-skills/bmad-product-brief/files/forkbird-brief/decision-log.md"
+        "evals/bmm-skills/wizz-product-brief/files/forkbird-brief/brief.md",
+        "evals/bmm-skills/wizz-product-brief/files/forkbird-brief/addendum.md",
+        "evals/bmm-skills/wizz-product-brief/files/forkbird-brief/decision-log.md"
       ],
       "expectations": [
         "The transcript or output explicitly references the prior 'rejected B2B catering for MVP' decision from decision-log.md",
@@ -187,12 +187,12 @@
     {
       "id": "B6",
       "_pattern": "process-discipline",
-      "prompt": "Run headless. Update the brief at evals/bmm-skills/bmad-product-brief/files/forkbird-brief/brief.md — we have signed our fifth chef partner (Chicago metro). Add this to the existing operating-model and what's-known sections. Read the existing decision-log.md first.",
+      "prompt": "Run headless. Update the brief at evals/bmm-skills/wizz-product-brief/files/forkbird-brief/brief.md — we have signed our fifth chef partner (Chicago metro). Add this to the existing operating-model and what's-known sections. Read the existing decision-log.md first.",
       "expected_output": "Clean update — does not contradict any prior decision. Brief gets updated, decision-log gains a new entry, YAML 'updated' bumps but 'created' stays the same. No spurious addendum since this is a status update, not an override.",
       "files": [
-        "evals/bmm-skills/bmad-product-brief/files/forkbird-brief/brief.md",
-        "evals/bmm-skills/bmad-product-brief/files/forkbird-brief/addendum.md",
-        "evals/bmm-skills/bmad-product-brief/files/forkbird-brief/decision-log.md"
+        "evals/bmm-skills/wizz-product-brief/files/forkbird-brief/brief.md",
+        "evals/bmm-skills/wizz-product-brief/files/forkbird-brief/addendum.md",
+        "evals/bmm-skills/wizz-product-brief/files/forkbird-brief/decision-log.md"
       ],
       "expectations": [
         "brief.md is updated to reflect the signed fifth chef partner in Chicago",
@@ -204,12 +204,12 @@
     {
       "id": "B7",
       "_pattern": "process-discipline",
-      "prompt": "Run headless. Validate the brief at evals/bmm-skills/bmad-product-brief/files/mossridge-brief/brief.md — we are presenting to the library board Monday. Read the addendum and decision-log in the same folder. Cite specific sections. Return inline only.",
+      "prompt": "Run headless. Validate the brief at evals/bmm-skills/wizz-product-brief/files/mossridge-brief/brief.md — we are presenting to the library board Monday. Read the addendum and decision-log in the same folder. Cite specific sections. Return inline only.",
       "expected_output": "Validate is read-only. No new files created. No existing files modified. Critique returned inline in the assistant output.",
       "files": [
-        "evals/bmm-skills/bmad-product-brief/files/mossridge-brief/brief.md",
-        "evals/bmm-skills/bmad-product-brief/files/mossridge-brief/addendum.md",
-        "evals/bmm-skills/bmad-product-brief/files/mossridge-brief/decision-log.md"
+        "evals/bmm-skills/wizz-product-brief/files/mossridge-brief/brief.md",
+        "evals/bmm-skills/wizz-product-brief/files/mossridge-brief/addendum.md",
+        "evals/bmm-skills/wizz-product-brief/files/mossridge-brief/decision-log.md"
       ],
       "expectations": [
         "No new files appear in the mossridge-brief artifacts directory after the run (only the three input files)",
@@ -222,11 +222,11 @@
       "id": "C1",
       "_pattern": "config-compliance",
       "prompt": "Run headless. Create a product brief for TaskFlow — a lightweight daily planning app for freelancers who juggle multiple clients. Core idea: a single daily view that pulls together tasks, time blocks, and client context so the freelancer always knows what to work on next. Target is independent freelancers, 1-3 clients at a time, who currently manage their day across sticky notes, calendar apps, and spreadsheets. MVP is mobile-first. No investors — the founder is bootstrapping.",
-      "expected_output": "Brief written in Spanish (document_output_language=Spanish). Assistant's conversational output reflects the configured British-accent communication style. Brief lands at the custom output path (test-output/artifacts/briefs/...) rather than the default _bmad-output path. Brief is right-sized for a bootstrapped solo project.",
+      "expected_output": "Brief written in Spanish (document_output_language=Spanish). Assistant's conversational output reflects the configured British-accent communication style. Brief lands at the custom output path (test-output/artifacts/briefs/...) rather than the default _wizz-output path. Brief is right-sized for a bootstrapped solo project.",
       "files": [],
       "expectations": [
-        "brief.md exists under test-output/artifacts/briefs/ (the custom planning_artifacts path), not under _bmad-output/",
-        "The final JSON status block artifact paths reference test-output/ rather than _bmad-output/",
+        "brief.md exists under test-output/artifacts/briefs/ (the custom planning_artifacts path), not under _wizz-output/",
+        "The final JSON status block artifact paths reference test-output/ rather than _wizz-output/",
         "brief.md body is written in Spanish — the majority of prose content (headings, section bodies) is in Spanish, not English",
         "brief.md covers the TaskFlow concept: freelancer daily planning, multi-client context, the sticky-notes-plus-calendar-plus-spreadsheet problem",
         "brief.md is right-sized for a bootstrapped side project — appropriate depth and scope for a solo-founder app with no investor audience, no TAM/SAM/SOM framing, no Series A language, and no sections that pad for enterprise credibility",

package/package.json CHANGED Viewed

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "wizz-method",
-  "version": "1.0.0",
+  "version": "1.0.2",
   "description": "Wizz Method — método de agência orientado por IA em PT-BR (fork independente do BMad Method)",
   "keywords": [
     "agile",

package/src/bmm-skills/1-analysis/research/{bmad-domain-research → wizz-domain-research}/SKILL.md RENAMED Viewed

@@ -1,5 +1,5 @@
 ---
-name: bmad-domain-research
+name: wizz-domain-research
 description: 'Conduct domain and industry research. Use when the user says wants to do domain research for a topic or industry'
 ---
@@ -24,13 +24,13 @@ description: 'Conduct domain and industry research. Use when the user says wants
 ### 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.
@@ -44,7 +44,7 @@ Treat every entry in `{workflow.persistent_facts}` as foundational context you c
 ### Step 4: Load Config
-Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+Load config from `{project-root}/_wizz/bmm/config.yaml` and resolve:
 - Use `{user_name}` for greeting
 - Use `{communication_language}` for all communications
 - Use `{document_output_language}` for output documents

package/src/bmm-skills/1-analysis/research/{bmad-domain-research → wizz-domain-research}/customize.toml RENAMED Viewed

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

package/src/bmm-skills/1-analysis/research/{bmad-domain-research → wizz-domain-research}/domain-steps/step-06-research-synthesis.md RENAMED Viewed

@@ -443,7 +443,7 @@ Complete authoritative research document on {{research_topic}} that:
 ## 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/1-analysis/research/{bmad-market-research → wizz-market-research}/SKILL.md RENAMED Viewed

@@ -1,5 +1,5 @@
 ---
-name: bmad-market-research
+name: wizz-market-research
 description: 'Conduct market research on competition and customers. Use when the user says they need market research'
 ---
@@ -24,13 +24,13 @@ description: 'Conduct market research on competition and customers. Use when the
 ### Step 1: Resolve the Workflow Block
-Run: `python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`
+Run: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow`
 **If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
 1. `{skill-root}/customize.toml` — defaults
-2. `{project-root}/_bmad/custom/{skill-name}.toml` — team overrides
-3. `{project-root}/_bmad/custom/{skill-name}.user.toml` — personal overrides
+2. `{project-root}/_wizz/custom/{skill-name}.toml` — team overrides
+3. `{project-root}/_wizz/custom/{skill-name}.user.toml` — personal overrides
 Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
@@ -44,7 +44,7 @@ Treat every entry in `{workflow.persistent_facts}` as foundational context you c
 ### Step 4: Load Config
-Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+Load config from `{project-root}/_wizz/bmm/config.yaml` and resolve:
 - Use `{user_name}` for greeting
 - Use `{communication_language}` for all communications
 - Use `{document_output_language}` for output documents

package/src/bmm-skills/1-analysis/research/{bmad-market-research → wizz-market-research}/customize.toml RENAMED Viewed

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

package/src/bmm-skills/1-analysis/research/{bmad-market-research → wizz-market-research}/steps/step-06-research-completion.md RENAMED Viewed

@@ -477,7 +477,7 @@ Comprehensive market research workflow complete. User may:
 ## 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/1-analysis/research/{bmad-technical-research → wizz-technical-research}/SKILL.md RENAMED Viewed

@@ -1,5 +1,5 @@
 ---
-name: bmad-technical-research
+name: wizz-technical-research
 description: 'Conduct technical research on technologies and architecture. Use when the user says they would like to do or produce a technical research report'
 ---
@@ -24,13 +24,13 @@ description: 'Conduct technical research on technologies and architecture. Use w
 ### 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.
@@ -44,7 +44,7 @@ Treat every entry in `{workflow.persistent_facts}` as foundational context you c
 ### Step 4: Load Config
-Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+Load config from `{project-root}/_wizz/bmm/config.yaml` and resolve:
 - Use `{user_name}` for greeting
 - Use `{communication_language}` for all communications
 - Use `{document_output_language}` for output documents

package/src/bmm-skills/1-analysis/research/{bmad-technical-research → wizz-technical-research}/customize.toml RENAMED Viewed

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

package/src/bmm-skills/1-analysis/research/{bmad-technical-research → wizz-technical-research}/technical-steps/step-06-research-synthesis.md RENAMED Viewed

@@ -486,7 +486,7 @@ Complete authoritative technical research document on {{research_topic}} that:
 ## 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/1-analysis/{bmad-agent-analyst → wizz-agent-analyst}/SKILL.md RENAMED Viewed

@@ -1,5 +1,5 @@
 ---
-name: bmad-agent-analyst
+name: wizz-agent-analyst
 description: Strategic business analyst and requirements expert. Use when the user asks to talk to Mary or requests the business analyst.
 ---
@@ -20,13 +20,13 @@ You are Mary, the Business Analyst. You bring deep expertise in market research,
 ### 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 Mary, 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 Mary, 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, Mary stays active — persona, persistent facts, `{agent.icon}` prefix, and `{communication_language}` carry into every turn until the user dismisses her.

package/src/bmm-skills/1-analysis/{bmad-agent-analyst → wizz-agent-analyst}/customize.toml RENAMED Viewed

@@ -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 = "Help the user ideate research and analyze before committing to a project in the BMad Method analysis phase."
@@ -57,34 +58,39 @@ principles = [
 [[agent.menu]]
 code = "BP"
 description = "Expert guided brainstorming facilitation"
-skill = "bmad-brainstorming"
+skill = "wizz-brainstorming"
 [[agent.menu]]
 code = "MR"
 description = "Market analysis, competitive landscape, customer needs and trends"
-skill = "bmad-market-research"
+skill = "wizz-market-research"
 [[agent.menu]]
 code = "DR"
 description = "Industry domain deep dive, subject matter expertise and terminology"
-skill = "bmad-domain-research"
+skill = "wizz-domain-research"
 [[agent.menu]]
 code = "TR"
 description = "Technical feasibility, architecture options and implementation approaches"
-skill = "bmad-technical-research"
+skill = "wizz-technical-research"
 [[agent.menu]]
 code = "CB"
 description = "Create or update product briefs through guided or autonomous discovery"
-skill = "bmad-product-brief"
+skill = "wizz-product-brief"
 [[agent.menu]]
 code = "WB"
 description = "Working Backwards PRFAQ challenge — forge and stress-test product concepts"
-skill = "bmad-prfaq"
+skill = "wizz-prfaq"
 [[agent.menu]]
 code = "DP"
 description = "Analyze an existing project to produce documentation for human and LLM consumption"
-skill = "bmad-document-project"
+skill = "wizz-document-project"
+[[agent.menu]]
+code = "SF"
+description = "Set or switch the active feature context for artifact subfolder organization"
+skill = "wizz-set-feature"

package/src/bmm-skills/1-analysis/{bmad-agent-tech-writer → wizz-agent-tech-writer}/SKILL.md RENAMED Viewed

@@ -1,5 +1,5 @@
 ---
-name: bmad-agent-tech-writer
+name: wizz-agent-tech-writer
 description: Technical documentation specialist and knowledge curator. Use when the user asks to talk to Paige or requests the tech writer.
 ---
@@ -20,13 +20,13 @@ You are Paige, the Technical Writer. You transform complex concepts into accessi
 ### 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 Paige, 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 Paige, 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, Paige stays active — persona, persistent facts, `{agent.icon}` prefix, and `{communication_language}` carry into every turn until the user dismisses her.

package/src/bmm-skills/1-analysis/{bmad-agent-tech-writer → wizz-agent-tech-writer}/customize.toml RENAMED Viewed

@@ -58,7 +58,7 @@ principles = [
 [[agent.menu]]
 code = "DP"
 description = "Generate comprehensive project documentation (brownfield analysis, architecture scanning)"
-skill = "bmad-document-project"
+skill = "wizz-document-project"
 [[agent.menu]]
 code = "WD"

package/src/bmm-skills/1-analysis/{bmad-document-project → wizz-document-project}/SKILL.md RENAMED Viewed

@@ -1,5 +1,5 @@
 ---
-name: bmad-document-project
+name: wizz-document-project
 description: 'Document brownfield projects for AI context. Use when the user says "document this project" or "generate project docs"'
 ---
@@ -20,13 +20,13 @@ description: 'Document brownfield projects for AI context. Use when the user say
 ### 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:
 - Use `{user_name}` for greeting
 - Use `{communication_language}` for all communications
 - Use `{document_output_language}` for output documents

package/src/bmm-skills/1-analysis/{bmad-document-project → wizz-document-project}/customize.toml RENAMED Viewed

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

package/src/bmm-skills/1-analysis/{bmad-document-project → wizz-document-project}/workflows/deep-dive-instructions.md RENAMED Viewed

@@ -291,7 +291,7 @@ These comprehensive docs are now ready for:
 Thank you for using the document-project workflow!
 </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>
 <action>Exit workflow</action>
 </action>
 </step>

package/src/bmm-skills/1-analysis/{bmad-document-project → wizz-document-project}/workflows/deep-dive-workflow.md RENAMED Viewed

@@ -11,7 +11,7 @@
 ### Configuration Loading
-Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+Load config from `{project-root}/_wizz/bmm/config.yaml` and resolve:
 - `project_knowledge`
 - `user_name`

package/src/bmm-skills/1-analysis/{bmad-document-project → wizz-document-project}/workflows/full-scan-instructions.md RENAMED Viewed

@@ -1103,6 +1103,6 @@ When ready to plan new features, run the PRD workflow and provide this index as
   </action>
 <action>Display: "State file saved: {{project_knowledge}}/project-scan-report.json"</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>
 </workflow>

package/src/bmm-skills/1-analysis/{bmad-document-project → wizz-document-project}/workflows/full-scan-workflow.md RENAMED Viewed

@@ -10,7 +10,7 @@
 ### Configuration Loading
-Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+Load config from `{project-root}/_wizz/bmm/config.yaml` and resolve:
 - `project_knowledge`
 - `user_name`