bmad-method 6.8.1-next.2 → 6.8.1-next.20

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

@@ -1,57 +0,0 @@
----
-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

@@ -1,29 +0,0 @@
-# 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

@@ -1,90 +0,0 @@
-# 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

@@ -1,101 +0,0 @@
-# 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

@@ -1,18 +0,0 @@
-[
-  { "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/src/bmm-skills/3-solutioning/bmad-create-architecture/architecture-decision-template.md

@@ -1,12 +0,0 @@
----
-stepsCompleted: []
-inputDocuments: []
-workflowType: 'architecture'
-project_name: '{{project_name}}'
-user_name: '{{user_name}}'
-date: '{{date}}'
----
-
-# Architecture Decision Document
-
-_This document builds collaboratively through step-by-step discovery. Sections are appended as we work through each architectural decision together._

package/src/bmm-skills/3-solutioning/bmad-create-architecture/data/domain-complexity.csv

@@ -1,13 +0,0 @@
-domain,signals,complexity_level,suggested_workflow,web_searches
-e_commerce,"shopping,cart,checkout,payment,products,store",medium,standard,"ecommerce architecture patterns, payment processing, inventory management"
-fintech,"banking,payment,trading,finance,money,investment",high,enhanced,"financial security, PCI compliance, trading algorithms, fraud detection"
-healthcare,"medical,diagnostic,clinical,patient,hospital,health",high,enhanced,"HIPAA compliance, medical data security, FDA regulations, health tech"
-social,"social network,community,users,friends,posts,sharing",high,advanced,"social graph algorithms, feed ranking, notification systems, privacy"
-education,"learning,course,student,teacher,training,academic",medium,standard,"LMS architecture, progress tracking, assessment systems, video streaming"
-productivity,"productivity,workflow,tasks,management,business,tools",medium,standard,"collaboration patterns, real-time editing, notification systems, integration"
-media,"content,media,video,audio,streaming,broadcast",high,advanced,"CDN architecture, video encoding, streaming protocols, content delivery"
-iot,"IoT,sensors,devices,embedded,smart,connected",high,advanced,"device communication, real-time data processing, edge computing, security"
-government,"government,civic,public,admin,policy,regulation",high,enhanced,"accessibility standards, security clearance, data privacy, audit trails"
-process_control,"industrial automation,process control,PLC,SCADA,DCS,HMI,operational technology,control system,cyberphysical,MES,instrumentation,I&C,P&ID",high,advanced,"industrial process control architecture, SCADA system design, OT cybersecurity architecture, real-time control systems"
-building_automation,"building automation,BAS,BMS,HVAC,smart building,fire alarm,fire protection,fire suppression,life safety,elevator,DDC,access control,sequence of operations,commissioning",high,advanced,"building automation architecture, BACnet integration patterns, smart building design, building management system security"
-gaming,"game,gaming,multiplayer,real-time,interactive,entertainment",high,advanced,"real-time multiplayer, game engine architecture, matchmaking, leaderboards"

package/src/bmm-skills/3-solutioning/bmad-create-architecture/data/project-types.csv

@@ -1,7 +0,0 @@
-project_type,detection_signals,description,typical_starters
-web_app,"website,web application,browser,frontend,UI,interface",Web-based applications running in browsers,Next.js, Vite, Remix
-mobile_app,"mobile,iOS,Android,app,smartphone,tablet",Native mobile applications,React Native, Expo, Flutter
-api_backend,"API,REST,GraphQL,backend,service,microservice",Backend services and APIs,NestJS, Express, Fastify
-full_stack,"full-stack,complete,web+mobile,frontend+backend",Applications with both frontend and backend,T3 App, RedwoodJS, Blitz
-cli_tool,"CLI,command line,terminal,console,tool",Command-line interface tools,oclif, Commander, Caporal
-desktop_app,"desktop,Electron,Tauri,native app,macOS,Windows",Desktop applications,Electron, Tauri, Flutter Desktop

package/src/bmm-skills/3-solutioning/bmad-create-architecture/steps/step-01-init.md

@@ -1,153 +0,0 @@
-# Step 1: Architecture Workflow Initialization
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
-- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
-- ✅ ALWAYS treat this as collaborative discovery between architectural peers
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- 💬 FOCUS on initialization and setup only - don't look ahead to future steps
-- 🚪 DETECT existing workflow state and handle continuation properly
-- ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Show your analysis before taking any action
-- 💾 Initialize document and update frontmatter
-- 📖 Set up frontmatter `stepsCompleted: [1]` before loading next step
-- 🚫 FORBIDDEN to load next step until setup is complete
-
-## CONTEXT BOUNDARIES:
-
-- Variables from workflow.md are available in memory
-- Previous context = what's in output document + frontmatter
-- Don't assume knowledge from other steps
-- Input document discovery happens in this step
-
-## YOUR TASK:
-
-Initialize the Architecture workflow by detecting continuation state, discovering input documents, and setting up the document for collaborative architectural decision making.
-
-## INITIALIZATION SEQUENCE:
-
-### 1. Check for Existing Workflow
-
-First, check if the output document already exists:
-
-- Look for existing {planning_artifacts}/`*architecture*.md`
-- If exists, read the complete file(s) including frontmatter
-- If not exists, this is a fresh workflow
-
-### 2. Handle Continuation (If Document Exists)
-
-If the document exists and has frontmatter with `stepsCompleted`:
-
-- **STOP here** and load `./step-01b-continue.md` immediately
-- Do not proceed with any initialization tasks
-- Let step-01b handle the continuation logic
-
-### 3. Fresh Workflow Setup (If No Document)
-
-If no document exists or no `stepsCompleted` in frontmatter:
-
-#### A. Input Document Discovery
-
-Discover and load context documents using smart discovery. Documents can be in the following locations:
-- {planning_artifacts}/**
-- {output_folder}/**
-- {project_knowledge}/**
-- {project-root}/docs/**
-
-Also - when searching - documents can be a single markdown file, or a folder with an index and multiple files. For Example, if searching for `*foo*.md` and not found, also search for a folder called *foo*/index.md (which indicates sharded content)
-
-Try to discover the following:
-- Product Brief (`*brief*.md`)
-- Product Requirements Document (`*prd*.md`)
-- UX Design (`*ux-design*.md`) and other
-- Research Documents (`*research*.md`)
-- Project Documentation (generally multiple documents might be found for this in the `{project_knowledge}` or `{project-root}/docs` folder.)
-- Project Context (`**/project-context.md`)
-
-<critical>Confirm what you have found with the user, along with asking if the user wants to provide anything else. Only after this confirmation will you proceed to follow the loading rules</critical>
-
-**Loading Rules:**
-
-- Load ALL discovered files completely that the user confirmed or provided (no offset/limit)
-- If there is a project context, whatever is relevant should try to be biased in the remainder of this whole workflow process
-- For sharded folders, load ALL files to get complete picture, using the index first to potentially know the potential of each document
-- index.md is a guide to what's relevant whenever available
-- Track all successfully loaded files in frontmatter `inputDocuments` array
-
-#### B. Validate Required Inputs
-
-Before proceeding, verify we have the essential inputs:
-
-**PRD Validation:**
-
-- If no PRD found: "Architecture requires a PRD to work from. Please run the PRD workflow first or provide the PRD file path."
-- Do NOT proceed without PRD
-
-**Other Input that might exist:**
-
-- UX Spec: "Provides UI/UX architectural requirements"
-
-#### C. Create Initial Document
-
-Copy the template from `../architecture-decision-template.md` to `{planning_artifacts}/architecture.md`
-
-#### D. Complete Initialization and Report
-
-Complete setup and report to user:
-
-**Document Setup:**
-
-- Created: `{planning_artifacts}/architecture.md` from template
-- Initialized frontmatter with workflow state
-
-**Input Documents Discovered:**
-Report what was found:
-"Welcome {{user_name}}! I've set up your Architecture workspace for {{project_name}}.
-
-**Documents Found:**
-
-- PRD: {number of PRD files loaded or "None found - REQUIRED"}
-- UX Design: {number of UX files loaded or "None found"}
-- Research: {number of research files loaded or "None found"}
-- Project docs: {number of project files loaded or "None found"}
-- Project context: {project_context_rules count of rules for AI agents found}
-
-**Files loaded:** {list of specific file names or "No additional documents found"}
-
-Ready to begin architectural decision making. Do you have any other documents you'd like me to include?
-
-[C] Continue to project context analysis
-
-## SUCCESS METRICS:
-
-✅ Existing workflow detected and handed off to step-01b correctly
-✅ Fresh workflow initialized with template and frontmatter
-✅ Input documents discovered and loaded using sharded-first logic
-✅ All discovered files tracked in frontmatter `inputDocuments`
-✅ PRD requirement validated and communicated
-✅ User confirmed document setup and can proceed
-
-## FAILURE MODES:
-
-❌ Proceeding with fresh initialization when existing workflow exists
-❌ Not updating frontmatter with discovered input documents
-❌ Creating document without proper template
-❌ Not checking sharded folders first before whole files
-❌ Not reporting what documents were found to user
-❌ Proceeding without validating PRD requirement
-
-❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
-❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
-❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
-
-## NEXT STEP:
-
-After user selects [C] to continue, only after ensuring all the template output has been created, then load `./step-02-context.md` to analyze the project context and begin architectural decision making.
-
-Remember: Do NOT proceed to step-02 until user explicitly selects [C] from the menu and setup is confirmed!