wizz-method 1.0.0

package/evals/bmm-skills/bmad-product-brief/files/mossridge-brief/brief.md

@@ -0,0 +1,57 @@
+---
+title: Mossridge Public Library — Tool Lending Library Proposal
+status: final
+created: 2026-04-30
+updated: 2026-04-30
+---
+
+# Tool Lending Library at Mossridge Public Library
+
+## What we're proposing
+
+A free tool-lending service operated out of the Mossridge Public Library, modeled on similar programs in Berkeley, Oakland, and Toronto. Cardholders borrow hand and power tools (drills, saws, ladders, sanders, plumbing snakes, gardening tools) for up to seven days, free of charge.
+
+## Why now
+
+Mossridge residents face rising costs of home maintenance and DIY supplies. Anecdotally, demand for community-shared resources is high — staff have fielded "do you lend tools?" requests for years. A tool library extends the library's mission of equitable access to information and skill-building into the practical-skills domain.
+
+## Who it serves
+
+Mossridge residents with active library cards. Primary audience: single-family homeowners doing their own home repairs, renters making minor improvements with landlord permission, hobbyist woodworkers and gardeners. Estimated 8,000 households in the library's service area.
+
+## Service design
+
+- **Catalog:** Approximately 200 tools to start, prioritizing the most-requested categories (drilling, cutting, sanding, ladders, garden).
+- **Loan period:** Seven days, one renewal allowed if no holds.
+- **Borrower requirements:** Active library card, signed liability waiver, completed safety briefing for power tools.
+- **Location:** Library basement, currently underutilized storage. Accessible by elevator.
+- **Hours:** Tuesday–Saturday during library hours; tools returned via after-hours drop slot when closed.
+
+## Funding
+
+- ARPA infrastructure grant: $42,000 (anticipated, application pending)
+- Friends of the Mossridge Library matching funds: $10,000 (committed)
+- In-kind tool donations from Mossridge Hardware (committed in principle)
+
+Year-one operating cost is estimated at $48,000, primarily tool purchase, maintenance supplies, and shelving/storage retrofit. Ongoing cost (year two and beyond) projected at $12,000 annually for replacement tools and consumables.
+
+## Operations
+
+The service will be run by trained library volunteers, supervised by the Adult Services Librarian. Volunteer training program to be developed in partnership with Mossridge Vocational Center. Estimated 4–6 active volunteers needed at any given time, with a roster of 12–15 trained volunteers to provide coverage.
+
+## Risks
+
+- **Theft and loss.** Tools are valuable and portable. Mitigation: deposit on power tools (refundable), card-required checkout, photo documentation at loan and return.
+- **Liability.** Borrower waivers will be required; the library's existing insurance policy is being reviewed for coverage.
+- **Demand uncertainty.** We do not yet know the actual borrowing volume the service will see.
+
+## Success criteria
+
+- Launch by Q3 2027 with a catalog of 200 tools.
+- 300 unique borrowers in the first year of operation.
+- Zero serious injury incidents.
+- Tool loss rate under 5% per year.
+
+## What we're asking
+
+Board approval to proceed with the ARPA grant application and finalize the service design for fall 2027 launch.

package/evals/bmm-skills/bmad-product-brief/files/mossridge-brief/decision-log.md

@@ -0,0 +1,29 @@
+# Decision Log — Mossridge Tool Lending Library
+
+## 2026-03-04
+- **Pursuing the project.** Adult Services Librarian + Library Director agreed there's enough informal demand signal (years of "do you lend tools?" inquiries) to investigate seriously. Acknowledged that informal inquiries are not the same as validated demand.
+
+## 2026-03-11
+- **Reference programs to study: Berkeley, Oakland, Toronto.** Selected based on size, longevity, and accessibility of operational data.
+
+## 2026-03-25
+- **Initial scope: hand and power tools only.** Rejected including specialty categories (sewing, electronics test gear, automotive) for MVP. Reason: staff expertise and storage. Revisit year 2.
+- **Free model.** Confirmed — paid model rejected as inconsistent with library mission. Donation jar approved as soft revenue.
+
+## 2026-04-01
+- **Volunteer-run model.** Selected to keep ongoing operating costs low. Acknowledged risk: Berkeley correspondence flagged staff-hours as the biggest sustainability concern in similar programs. Plan to revisit at year-one review.
+
+## 2026-04-08
+- **Funding architecture: ARPA grant + Friends matching + in-kind donations.** Considered municipal budget request; rejected as too slow (next budget cycle is 18 months out). Grant is faster but requires fall 2027 launch deadline.
+
+## 2026-04-15
+- **Launch timing: Q3 2027.** Driven by ARPA grant deadline, not by service-readiness analysis. Acknowledged this is grant-driven, not user-driven, timing.
+- **Year-one target: 300 unique borrowers.** Set by analogy to comparable programs scaled to Mossridge population. No local validation underlying this number.
+
+## 2026-04-22
+- **Hardware store satellite deferred to year 2.** Operational complexity exceeds our launch capacity.
+- **Liability: pending formal opinion from town legal.** Borrower waiver in draft.
+
+## 2026-04-30
+- **Brief finalized for board meeting.** Status moved to final.
+- **Open items acknowledged for board discussion:** demand validation method, volunteer sustainability, written legal opinion on off-premises tool use coverage.

package/evals/bmm-skills/bmad-product-brief/files/pantry-bridge-interviews.md

@@ -0,0 +1,90 @@
+# Pantry Bridge — Customer Research Transcripts
+
+**Project:** Pantry Bridge meal-kit concept exploration
+**Research firm:** In-house
+**Round:** Discovery interviews, March 2026
+**Format:** 45-minute semi-structured interviews, video; excerpts below are lightly edited for length and clarity
+
+The four interviews below cover four distinct potential customer segments. We are sharing all four for context, though the team's current product hypothesis targets one specific segment.
+
+---
+
+## Interview 1 — Susan, 38, working parent
+
+**Household:** Two kids (ages 6 and 9), spouse works full-time, both parents work demanding office jobs. Suburban Chicago.
+
+**Susan:** "Honestly, the question is just — can I get dinner on the table by 6:30 without it being chicken nuggets again? My kids don't eat anything green unless we play games about it. My husband and I both have late meetings sometimes. We've tried HelloFresh, we've tried Blue Apron, we tried Home Chef. They all kind of work, and they all kind of don't.
+
+The thing that breaks them for us is the prep time. The boxes say 30 minutes but you need to add 10-15 to actually get it done. By Wednesday night I don't have 45 minutes. So we end up using the boxes on weekends and ordering takeout three nights a week, which is the opposite of what the boxes are supposed to do.
+
+If you really wanted to crack it for families like ours: pre-chopped vegetables, sauces that are actually finished and not 'whisk these eight things together.' I'll pay more for less prep. And the recipe books need to read like the kid is going to eat it — not like 'spicy harissa-rubbed cauliflower steaks.'
+
+Portion sizing — most kits send way too much for our family. We're a family of four but the kids each eat about 60% of a meal. We end up with leftovers that go bad. Better sizing would help."
+
+**Interviewer:** What about price?
+
+**Susan:** "We spend $250-350 a week on groceries currently and probably another $200 on takeout. So a meal kit that replaces three nights of takeout could be $200 a month and we'd still come out ahead. Most kits are priced fine; it's the time that breaks them."
+
+---
+
+## Interview 2 — Marcus, 21, college student
+
+**Household:** Junior at state university, off-campus apartment shared with two roommates, kitchen has a microwave, a stovetop, and a half-broken oven. Limited budget.
+
+**Marcus:** "I'm probably the wrong person for this conversation, no offense. I'm not really a meal-kit person. My food situation is, like, dining hall meal plan when I can use it, and the rest is whatever's cheap and fast. Trader Joe's frozen stuff. Eggs. Pasta. Costco runs with my roommates once a month.
+
+I tried a meal kit when my mom signed me up as a 'starting college' gift. It was nice, but it was $80 a week for two people, which is way out of budget. And honestly, the thing they don't get is that I don't have time at 7 PM to cook. I have time at 11 PM. I want to grab something on my way back from the library and not think.
+
+If you're trying to do meal kits for college students — and I don't really think you should — but if you were, the price has to be like $5 a meal. And it has to be food that survives in a fridge for two weeks because we don't shop on a weekly schedule. We shop when we run out.
+
+Snacks matter more to us than meals, actually. Like, the moment when I'm desperate is 10 PM in the library, not 7 PM. Solve that and I might pay attention."
+
+**Interviewer:** Do you have any dietary restrictions?
+
+**Marcus:** "I'm vegetarian, sort of. I eat fish. So pescatarian I guess. But mostly because meat is expensive."
+
+---
+
+## Interview 3 — Eleanor, 71, retired, lives alone
+
+**Household:** Widow, lives alone in the same single-family home she's been in for 36 years. Suburban Cleveland. Two adult children live out of state. Drives during the day but no longer at night.
+
+**Eleanor:** "I'll tell you what I miss. I miss cooking for someone. My husband Walter passed five years ago this June, and the hardest thing — well, not the hardest, but one of them — is that I don't really cook anymore. I cook eggs. I cook a piece of fish. I open a can of soup more often than I'd like to admit. I used to make Sunday dinners that would feed eight people. Now I eat standing up at the counter half the time.
+
+The grocery store is genuinely difficult. I drive there, I park in the back of the lot because I can usually find a spot, and then it's a long walk in. I get tired by the time I'm in the dairy aisle. Carrying the bags from the car to the kitchen — that's a project. My daughter wants me to use grocery delivery and I've tried, but the apps are all designed for someone twenty years younger than me. Tiny buttons, asking me to click through six screens to add a single tomato. I get frustrated and give up.
+
+What I would actually want — and I've thought about this — is meals for one person. Real portions. Not a frozen TV dinner. Not 'serves four, freeze the rest.' I have a freezer full of leftovers I'll never eat. Just one good meal that I can heat up or finish cooking, that tastes like food I would have made.
+
+I'm watching my sodium because of my blood pressure. Watching sugar too — borderline diabetic, my doctor calls it. So I read labels carefully. The frozen meals you can buy in stores are loaded with both. I'd pay more for less of both, if I trusted that the labels were accurate.
+
+The other thing — and please put this in your notes — is that I'm careful about who I let into my house and what I sign up for. There are scams. My friend Marian got taken for $4,000 last year. So if some company asks for my information, I want to know who they are. I want a real customer service number with a real person. I want it to feel like a real business, not a flashy app.
+
+I don't want it to feel like 'old-people food.' That's an important thing. The Meals on Wheels program in our township is wonderful but it's clearly designed for people who are sicker than I am. I'm not sick. I just live alone and grocery shopping is a lot."
+
+**Interviewer:** What would the ideal experience look like?
+
+**Eleanor:** "Someone delivers good food, in real portions, made with the kind of ingredients I would have used. I can heat it up or finish it. It doesn't taste like a hospital. The packaging is something I can actually open without a knife. I get a phone call once in a while from a person, not a robot. The price is reasonable — I'm on a fixed income but I can spend on things that matter. Eating well matters."
+
+---
+
+## Interview 4 — Dimitri, 44, Director of Food Services, mid-size hospital
+
+**Organization:** 340-bed hospital, food service operates patient meals, staff cafeteria, and a small retail café. Reports to the COO.
+
+**Dimitri:** "I'm probably also not who you should be talking to, but happy to share. We don't buy meal kits. We buy ingredients in institutional volumes from Sysco and US Foods primarily, with some specialty buys for dietary restrictions. We feed about 1,800 people a day across patients, staff, and visitors.
+
+What I deal with that you might find interesting is the patient diet matrix. We have to produce meals that meet specific medical requirements — renal diets, cardiac diets, diabetic diets, dysphagia textures, allergen-free, religious restrictions. Each patient gets a tray that meets their specific orders. It's complex.
+
+If a meal kit company wanted to play in our world, they'd be selling to me at the institutional level — bulk pricing, multi-year contracts, ability to deliver consistent specs across thousands of meals. That's not really a 'meal kit' anymore; that's wholesale food service.
+
+Now, where I might be a buyer in a different sense: my staff cafeteria. We're trying to compete with grab-and-go culture. If you produced ready-to-heat meals targeting our staff demographic — nurses, doctors, techs, who are working 12-hour shifts and want real food, not a sandwich — I might pay attention. But the price point would have to make sense for institutional buying, and you'd need to integrate with our existing food safety protocols.
+
+For consumer meal kits, I'm probably not your customer. We did try one when my wife and I were both working through COVID, and we let the subscription lapse after about three months. Fine product, just didn't fit our patterns."
+
+---
+
+## Note from the research lead
+
+These four interviews were selected to represent the range of segments we've considered. The team's working hypothesis after this round is that the older-adult-living-alone segment is the strongest fit for the Pantry Bridge concept — distinctive needs, acknowledged friction with current options, willingness to pay for quality, and a meaningful unmet need around portion sizing and trust. Working parent segment is well-served by existing competitors. College student segment is too price-sensitive. Institutional segment is a different business entirely.
+
+The brief should target the older-adult segment based on the Eleanor interview specifically.

package/evals/bmm-skills/bmad-product-brief/files/q2-brainstorm.md

@@ -0,0 +1,101 @@
+# Q2 Brainstorm — Hatchet & Loop Studio
+
+**Date:** 2026-04-15
+**Present:** Mira, Devon, Sofia, Theo
+
+Annual Q2 ideation. We're hunting for our next side-project-that-could-become-a-product. Format: 10 minutes wild ideas, 3 minutes per idea on quick takes, then we vote on one to dig into.
+
+## Round 1: Everything goes
+
+(10 minutes, no filtering. We just throw stuff out.)
+
+- A weather app that tracks your mood alongside the forecast (Devon)
+- Meditation chime that learns your sleep cycle and chimes only at the right wake-window (Theo)
+- A podcasting tool for non-podcasters — like, you record voice notes and it auto-edits and posts (Sofia)
+- Craft beer subscription with detailed brewer notes you can read while drinking (Mira)
+- AI sommelier app that tells you what wine to buy at Trader Joe's based on a photo (Theo)
+- Office-plant-care subscription with auto-replacement when one dies (Devon)
+- Neighborhood ride coordinator — like a private Uber pool for one neighborhood (Mira)
+- Neighborhood compost coordinator — connect people with food scraps to people with active compost piles (Sofia)
+- Cookbook app where you click "I'll cook this Tuesday" and it auto-generates the shopping list and sends it to your delivery service (Devon)
+- AR home staging — point your phone at a room and it shows you what it would look like with different furniture (Theo)
+
+## Round 2: Quick takes
+
+### Weather + mood
+
+Devon: "I'd use it." Sofia thinks the data correlation isn't strong enough to be useful — interesting concept but the science doesn't support a product. Park.
+
+### Sleep-cycle meditation chime
+
+Theo's pitch — exists already (Sleep Cycle, etc.). Differentiation would be the chime, which is hardware. Out of scope for a software-first studio.
+
+### Podcasting for non-podcasters
+
+Sofia: "There are like fifty of these." She's right. Skip.
+
+### Craft beer subscription
+
+Mira admits this is mostly her wanting it for herself. We're not in the logistics business. Skip.
+
+### AI sommelier
+
+Theo: "The model would have to be incredibly good at label recognition." Sofia: "And there's already Vivino." Skip.
+
+### Office-plant-care subscription
+
+Devon: "I worked at a place that had this. They were always sad plants." Operational nightmare, low margin. Skip.
+
+### Neighborhood ride coordinator
+
+Mira: "Saturated. Lyft and Uber both have pool features. Uber Neighborhood was a thing and they killed it." Skip.
+
+### Neighborhood compost coordinator
+
+Sofia: "Hear me out. Cities are mandating organic waste separation but most apartments don't have a composting option. People in single-family homes often have active compost piles and would love more material. There's a missing match-making layer." General agreement this is more interesting than the others. Theo: "How do we make money?" Sofia: "Eventually a small fee on the compost-pile-host side, but for MVP just free and prove the demand." Group lights up. We agree to dig into this in Round 3.
+
+### Cookbook → shopping list
+
+Devon's pitch. Already exists (Mealime, Plan to Eat). Skip.
+
+### AR home staging
+
+Theo: "IKEA already has this." Skip.
+
+## Round 3: Compost coordinator deep dive
+
+We spent 45 minutes on this. Notes:
+
+**Who is the user?**
+Two-sided market. Side A: apartment dwellers and renters who generate food scraps and want them composted (motivated by environmental values, sometimes by city mandates). Side B: people with active backyard compost piles who want more "browns and greens" — single-family homeowners, urban farmers, school gardens, community gardens.
+
+Sofia thinks Side A is the harder side to acquire (weak intent — recycling-adjacent behavior). Side B is easier but smaller. The product has to be designed around Side A's friction points.
+
+**Geographic scope.**
+Hyperlocal — neighborhood-level, not city-wide. The whole point is short-distance handoff: Side A doesn't want to drive their food scraps across town. We're talking 5-block radius matches.
+
+**Business model (later).**
+Free at launch. Eventually: subscription for Side B (compost-pile hosts) — they pay to access more matches. Side A always free. Possibly partner with cities that have green-waste mandates (B2G channel).
+
+**Technical approach.**
+Web app first, mobile second. Map-based discovery. Identity verification light-touch (apartment dwellers are skittish about strangers; need trust signals). Match-and-message pattern, not real-time logistics.
+
+**Competition.**
+ShareWaste exists but is global and not focused on hyperlocal density. Some city-specific apps (NYC's GrowNYC). No one has cracked the neighborhood-density model.
+
+**MVP scope.**
+One pilot neighborhood. Sofia knows people in a Portland neighborhood (Sunnyside / Hawthorne area) where compost culture is strong. Start there.
+
+**Open questions.**
+- How do we acquire Side A (apartment dwellers)? They have low intent and lots of competing options (just throwing scraps in trash, paying a service, signing up for city pickup if available).
+- What does the trust layer look like? Reviews? Vouching? Real-name only?
+- Does Side B saturation become a problem fast (one compost pile can only take so much)? How do we route demand?
+
+## Action items
+
+- Sofia: write up the compost coordinator concept as a brief by next Wednesday. Take it to Mira and Devon for first read.
+- Devon: research ShareWaste's user numbers and any teardowns of why they haven't dominated.
+- Theo: sketch the trust-layer UX concepts.
+- Mira: talk to Sofia's Portland contacts about doing user interviews.
+
+Next meeting: 2026-04-29 — review brief draft, decide on go/no-go.

package/evals/bmm-skills/bmad-product-brief/triggers.json

@@ -0,0 +1,18 @@
+[
+  { "query": "Help me write a product brief for my new app idea", "should_trigger": true },
+  { "query": "I need to draft a brief for a feature we're scoping", "should_trigger": true },
+  { "query": "Update this product brief — we changed the target audience", "should_trigger": true },
+  { "query": "Review my brief and tell me if it's investor-ready", "should_trigger": true },
+  { "query": "Validate this brief before our board meeting Monday", "should_trigger": true },
+  { "query": "Pressure-test my product brief for weak assumptions", "should_trigger": true },
+  { "query": "Help me put together a one-page summary of my product idea for stakeholders", "should_trigger": true },
+
+  { "query": "Help me brainstorm ideas for a new feature", "should_trigger": false },
+  { "query": "Write me a PRD for our checkout flow redesign", "should_trigger": false },
+  { "query": "Run a working backwards exercise for my product idea", "should_trigger": false },
+  { "query": "Document this existing codebase for AI agents", "should_trigger": false },
+  { "query": "Help me write user stories for the next sprint", "should_trigger": false },
+  { "query": "Generate a system architecture for my app", "should_trigger": false },
+  { "query": "Write code to parse JSON in Python", "should_trigger": false },
+  { "query": "Create a marketing landing page for my product", "should_trigger": false }
+]

package/package.json

@@ -0,0 +1,114 @@
+{
+  "$schema": "https://json.schemastore.org/package.json",
+  "name": "wizz-method",
+  "version": "1.0.0",
+  "description": "Wizz Method — método de agência orientado por IA em PT-BR (fork independente do BMad Method)",
+  "keywords": [
+    "agile",
+    "ai",
+    "orchestrator",
+    "development",
+    "methodology",
+    "agents",
+    "wizz",
+    "wizzcomms"
+  ],
+  "homepage": "https://method.wizzcomms.com",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/wizzcomms/wizz-method.git"
+  },
+  "license": "MIT",
+  "author": "Wizz! comms. (wizzcomms)",
+  "main": "tools/installer/bmad-cli.js",
+  "bin": {
+    "wizz": "tools/installer/bmad-cli.js",
+    "wizz-method": "tools/installer/bmad-cli.js"
+  },
+  "scripts": {
+    "bmad:install": "node tools/installer/bmad-cli.js install",
+    "bmad:uninstall": "node tools/installer/bmad-cli.js uninstall",
+    "docs:build": "node tools/build-docs.mjs",
+    "docs:dev": "astro dev --root website",
+    "docs:fix-links": "node tools/fix-doc-links.js",
+    "docs:preview": "astro preview --root website",
+    "docs:validate-links": "node tools/validate-doc-links.js",
+    "docs:validate-sidebar": "node tools/validate-sidebar-order.js",
+    "format:check": "prettier --check \"**/*.{js,cjs,mjs,json,yaml}\"",
+    "format:fix": "prettier --write \"**/*.{js,cjs,mjs,json,yaml}\"",
+    "format:fix:staged": "prettier --write",
+    "install:bmad": "node tools/installer/bmad-cli.js install",
+    "lint": "eslint . --ext .js,.cjs,.mjs,.yaml --max-warnings=0",
+    "lint:fix": "eslint . --ext .js,.cjs,.mjs,.yaml --fix",
+    "lint:md": "markdownlint-cli2 \"**/*.md\"",
+    "prepare": "command -v husky >/dev/null 2>&1 && husky || exit 0",
+    "quality": "npm run format:check && npm run lint && npm run lint:md && npm run docs:build && npm run test:install && npm run test:urls && npm run validate:refs && npm run validate:skills && npm run docs:validate-sidebar",
+    "rebundle": "node tools/installer/bundlers/bundle-web.js rebundle",
+    "test": "npm run test:refs && npm run test:install && npm run test:urls && npm run test:channels && npm run lint && npm run lint:md && npm run format:check",
+    "test:channels": "node test/test-installer-channels.js",
+    "test:install": "node test/test-installation-components.js",
+    "test:refs": "node test/test-file-refs-csv.js",
+    "test:urls": "node test/test-parse-source-urls.js",
+    "validate:refs": "node tools/validate-file-refs.js --strict",
+    "validate:skills": "node tools/validate-skills.js --strict"
+  },
+  "lint-staged": {
+    "*.{js,cjs,mjs}": [
+      "npm run lint:fix",
+      "npm run format:fix:staged"
+    ],
+    "*.yaml": [
+      "eslint --fix",
+      "npm run format:fix:staged"
+    ],
+    "*.json": [
+      "npm run format:fix:staged"
+    ],
+    "*.md": [
+      "markdownlint-cli2"
+    ]
+  },
+  "dependencies": {
+    "@clack/core": "^1.3.1",
+    "@clack/prompts": "^1.4.0",
+    "@kayvan/markdown-tree-parser": "^1.6.1",
+    "chalk": "^4.1.2",
+    "commander": "^14.0.0",
+    "csv-parse": "^6.1.0",
+    "glob": "^11.0.3",
+    "ignore": "^7.0.5",
+    "js-yaml": "^4.1.0",
+    "picocolors": "^1.1.1",
+    "semver": "^7.6.3",
+    "xml2js": "^0.6.2",
+    "yaml": "^2.7.0"
+  },
+  "devDependencies": {
+    "@astrojs/sitemap": "^3.6.0",
+    "@astrojs/starlight": "^0.37.5",
+    "@eslint/js": "^9.33.0",
+    "astro": "^5.16.0",
+    "c8": "^10.1.3",
+    "eslint": "^9.33.0",
+    "eslint-config-prettier": "^10.1.8",
+    "eslint-plugin-n": "^17.21.3",
+    "eslint-plugin-unicorn": "^60.0.0",
+    "eslint-plugin-yml": "^1.18.0",
+    "husky": "^9.1.7",
+    "jest": "^30.2.0",
+    "lint-staged": "^16.1.1",
+    "markdownlint-cli2": "^0.19.1",
+    "prettier": "^3.7.4",
+    "prettier-plugin-packagejson": "^2.5.19",
+    "sharp": "^0.33.5",
+    "unist-util-visit": "^5.1.0",
+    "yaml-eslint-parser": "^1.2.3",
+    "yaml-lint": "^1.7.0"
+  },
+  "engines": {
+    "node": ">=20.12.0"
+  },
+  "publishConfig": {
+    "access": "public"
+  }
+}

package/removals.txt

@@ -0,0 +1,62 @@
+# BMad Method - Skill Removal List
+# Entries listed here will be removed from IDE skill directories during install/update.
+# One entry per line. Lines starting with # are comments.
+# Each entry is a skill directory name (canonicalId) that was removed or renamed.
+
+# Removed agents (v6.2.0 - v6.2.2)
+bmad-agent-sm
+bmad-agent-qa
+bmad-agent-quick-flow-solo-dev
+
+# Removed skills (v6.2.0 - v6.2.2)
+bmad-create-product-brief
+bmad-product-brief-preview
+bmad-quick-spec
+bmad-quick-flow
+bmad-quick-dev-new-preview
+bmad-init
+
+# Pre-v6.2.0 wrapper skills (module-prefixed naming, dropped in v6.2.0).
+# Users upgrading from v6.0.x / v6.1.x had these installed and the cleanup
+# never knew to remove them; they remained alongside the new self-contained
+# skills causing duplicates and broken-file errors. See issue #2309.
+bmad-agent-bmm-analyst
+bmad-agent-bmm-architect
+bmad-agent-bmm-dev
+bmad-agent-bmm-pm
+bmad-agent-bmm-qa
+bmad-agent-bmm-quick-flow-solo-dev
+bmad-agent-bmm-sm
+bmad-agent-bmm-tech-writer
+bmad-agent-bmm-ux-designer
+bmad-bmm-check-implementation-readiness
+bmad-bmm-code-review
+bmad-bmm-correct-course
+bmad-bmm-create-architecture
+bmad-bmm-create-epics-and-stories
+bmad-bmm-create-prd
+bmad-bmm-create-product-brief
+bmad-bmm-create-story
+bmad-bmm-create-ux-design
+bmad-bmm-dev-story
+bmad-bmm-document-project
+bmad-bmm-domain-research
+bmad-bmm-edit-prd
+bmad-bmm-generate-project-context
+bmad-bmm-market-research
+bmad-bmm-qa-generate-e2e-tests
+bmad-bmm-quick-dev
+bmad-bmm-quick-spec
+bmad-bmm-retrospective
+bmad-bmm-sprint-planning
+bmad-bmm-sprint-status
+bmad-bmm-technical-research
+bmad-bmm-validate-prd
+
+# Removed skills (post-v6.7.x)
+# bmad-distillator: superseded by bmad-spec (universal intent distiller with
+# preservation-validated contract for downstream skills).
+bmad-distillator
+# bmad-create-ux-design: renamed to bmad-ux (spine-based skill with separate
+# DESIGN.md and EXPERIENCE.md outputs).
+bmad-create-ux-design

package/src/bmm-skills/1-analysis/bmad-agent-analyst/SKILL.md

@@ -0,0 +1,76 @@
+---
+name: bmad-agent-analyst
+description: Strategic business analyst and requirements expert. Use when the user asks to talk to Mary or requests the business analyst.
+---
+
+# Mary — Business Analyst
+
+## Overview
+
+You are Mary, the Business Analyst. You bring deep expertise in market research, competitive analysis, requirements elicitation, and domain knowledge — translating vague needs into actionable specs while staying grounded in evidence-based analysis.
+
+## Conventions
+
+- Bare paths (e.g. `references/guide.md`) resolve from the skill root.
+- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
+- `{project-root}`-prefixed paths resolve from the project working directory.
+- `{skill-name}` resolves to the skill directory's basename.
+
+## On Activation
+
+### Step 1: Resolve the Agent Block
+
+Run: `python3 {project-root}/_bmad/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
+
+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.
+
+### Step 2: Execute Prepend Steps
+
+Execute each entry in `{agent.activation_steps_prepend}` in order before proceeding.
+
+### Step 3: Adopt Persona
+
+Adopt the Mary / Business Analyst identity established in the Overview. Layer the customized persona on top: fill the additional role of `{agent.role}`, embody `{agent.identity}`, speak in the style of `{agent.communication_style}`, and follow `{agent.principles}`.
+
+Fully embody this persona so the user gets the best experience. Do not break character until the user dismisses the persona. When the user calls a skill, this persona carries through and remains active.
+
+### Step 4: Load Persistent Facts
+
+Treat every entry in `{agent.persistent_facts}` as foundational context you carry for the rest of the session. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.
+
+### Step 5: Load Config
+
+Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+- Use `{user_name}` for greeting
+- Use `{communication_language}` for all communications
+- Use `{document_output_language}` for output documents
+- Use `{planning_artifacts}` for output location and artifact scanning
+- Use `{project_knowledge}` for additional context scanning
+
+### 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.
+
+Continue to prefix your messages with `{agent.icon}` throughout the session so the active persona stays visually identifiable.
+
+### Step 7: Execute Append Steps
+
+Execute each entry in `{agent.activation_steps_append}` in order.
+
+Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.
+
+### Step 8: Dispatch or Present the Menu
+
+If the user's initial message already names an intent that clearly maps to a menu item (e.g. "hey Mary, let's brainstorm"), skip the menu and dispatch that item directly after greeting.
+
+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.
+
+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/customize.toml

@@ -0,0 +1,90 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Mary, the Business Analyst, is the hardcoded identity of this agent.
+# Customize the persona and menu below to shape behavior without
+# changing who the agent is.
+
+[agent]
+# non-configurable skill frontmatter, create a custom agent if you need a new name/title
+name="Mary"
+title="Business Analyst"
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays (persistent_facts, principles, activation_steps_*): append
+#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
+
+icon = "📊"
+
+# Steps to run before the standard activation (persona, config, greet).
+# Overrides append. Use for pre-flight loads, compliance checks, etc.
+
+activation_steps_prepend = []
+
+# Steps to run after greet but before presenting the menu.
+# Overrides append. Use for context-heavy setup that should happen
+# once the user has been acknowledged.
+
+activation_steps_append = []
+
+# Persistent facts the agent keeps in mind for the whole session (org rules,
+# domain constants, user preferences). Distinct from the runtime memory
+# sidecar — these are static context loaded on activation. Overrides append.
+#
+# Each entry is either:
+#   - a literal sentence, e.g. "Our org is AWS-only -- do not propose GCP or Azure."
+#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
+#     (glob patterns are supported; the file's contents are loaded and treated as facts).
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+role = "Help the user ideate research and analyze before committing to a project in the BMad 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."
+
+# The agent's value system. Overrides append to defaults.
+principles = [
+  "Every finding grounded in verifiable evidence.",
+  "Requirements stated with absolute precision.",
+  "Every stakeholder voice represented.",
+]
+
+# Capabilities menu. Overrides merge by `code`: matching codes replace the item
+# in place, new codes append. Each item has exactly one of `skill` (invokes a
+# registered skill by name) or `prompt` (executes the prompt text directly).
+
+[[agent.menu]]
+code = "BP"
+description = "Expert guided brainstorming facilitation"
+skill = "bmad-brainstorming"
+
+[[agent.menu]]
+code = "MR"
+description = "Market analysis, competitive landscape, customer needs and trends"
+skill = "bmad-market-research"
+
+[[agent.menu]]
+code = "DR"
+description = "Industry domain deep dive, subject matter expertise and terminology"
+skill = "bmad-domain-research"
+
+[[agent.menu]]
+code = "TR"
+description = "Technical feasibility, architecture options and implementation approaches"
+skill = "bmad-technical-research"
+
+[[agent.menu]]
+code = "CB"
+description = "Create or update product briefs through guided or autonomous discovery"
+skill = "bmad-product-brief"
+
+[[agent.menu]]
+code = "WB"
+description = "Working Backwards PRFAQ challenge — forge and stress-test product concepts"
+skill = "bmad-prfaq"
+
+[[agent.menu]]
+code = "DP"
+description = "Analyze an existing project to produce documentation for human and LLM consumption"
+skill = "bmad-document-project"