From 734966b7fddf61dd21d36d224af79212ad518d03 Mon Sep 17 00:00:00 2001
From: k9ert <117085+k9ert@users.noreply.github.com>
Date: Tue, 9 Dec 2025 20:40:19 +0100
Subject: [PATCH 1/2] bmad: initial
---
.../commands/bmad/agents/bmb-bmad-builder.md | 14 +
.augment/commands/bmad/agents/bmm-analyst.md | 14 +
.../commands/bmad/agents/bmm-architect.md | 14 +
.augment/commands/bmad/agents/bmm-dev.md | 14 +
.augment/commands/bmad/agents/bmm-pm.md | 14 +
.../bmad/agents/bmm-quick-flow-solo-dev.md | 14 +
.augment/commands/bmad/agents/bmm-sm.md | 14 +
.augment/commands/bmad/agents/bmm-tea.md | 14 +
.../commands/bmad/agents/bmm-tech-writer.md | 14 +
.../commands/bmad/agents/bmm-ux-designer.md | 14 +
.../commands/bmad/agents/core-bmad-master.md | 14 +
.../bmad/tasks/core-advanced-elicitation.md | 125 +
.../commands/bmad/tasks/core-index-docs.md | 74 +
.../commands/bmad/tools/core-shard-doc.md | 119 +
.../bmb-Meal Prep & Nutrition Plan.md | 5 +
.../bmad/workflows/bmb-create-agent.md | 5 +
.../bmad/workflows/bmb-create-module.md | 5 +
.../bmad/workflows/bmb-create-workflow.md | 5 +
.../commands/bmad/workflows/bmb-edit-agent.md | 5 +
.../bmad/workflows/bmb-edit-workflow.md | 5 +
.../bmb-workflow-compliance-check.md | 5 +
.../bmm-check-implementation-readiness.md | 5 +
.../bmad/workflows/bmm-code-review.md | 13 +
.../bmad/workflows/bmm-correct-course.md | 13 +
.../bmad/workflows/bmm-create-architecture.md | 5 +
.../workflows/bmm-create-epics-stories.md | 5 +
.../bmm-create-excalidraw-dataflow.md | 13 +
.../bmm-create-excalidraw-diagram.md | 13 +
.../bmm-create-excalidraw-flowchart.md | 13 +
.../bmm-create-excalidraw-wireframe.md | 13 +
.../commands/bmad/workflows/bmm-create-prd.md | 5 +
.../workflows/bmm-create-product-brief.md | 5 +
.../bmad/workflows/bmm-create-story.md | 13 +
.../bmad/workflows/bmm-create-tech-spec.md | 13 +
.../bmad/workflows/bmm-create-ux-design.md | 5 +
.../commands/bmad/workflows/bmm-dev-story.md | 13 +
.../bmad/workflows/bmm-document-project.md | 13 +
.../workflows/bmm-generate-project-context.md | 5 +
.../commands/bmad/workflows/bmm-quick-dev.md | 13 +
.../commands/bmad/workflows/bmm-research.md | 5 +
.../bmad/workflows/bmm-retrospective.md | 13 +
.../bmad/workflows/bmm-sprint-planning.md | 13 +
.../bmad/workflows/bmm-sprint-status.md | 13 +
.../bmad/workflows/bmm-testarch-atdd.md | 13 +
.../bmad/workflows/bmm-testarch-automate.md | 13 +
.../bmad/workflows/bmm-testarch-ci.md | 13 +
.../bmad/workflows/bmm-testarch-framework.md | 13 +
.../bmad/workflows/bmm-testarch-nfr.md | 13 +
.../workflows/bmm-testarch-test-design.md | 13 +
.../workflows/bmm-testarch-test-review.md | 13 +
.../bmad/workflows/bmm-testarch-trace.md | 13 +
.../bmad/workflows/bmm-workflow-init.md | 13 +
.../bmad/workflows/bmm-workflow-status.md | 13 +
.../workflows/core-brainstorming-session.md | 5 +
.../bmad/workflows/core-party-mode.md | 5 +
.bmad/_cfg/agent-manifest.csv | 12 +
.../agents/bmb-bmad-builder.customize.yaml | 42 +
.bmad/_cfg/agents/bmm-analyst.customize.yaml | 42 +
.../_cfg/agents/bmm-architect.customize.yaml | 42 +
.bmad/_cfg/agents/bmm-dev.customize.yaml | 42 +
.bmad/_cfg/agents/bmm-pm.customize.yaml | 42 +
.../bmm-quick-flow-solo-dev.customize.yaml | 42 +
.bmad/_cfg/agents/bmm-sm.customize.yaml | 42 +
.bmad/_cfg/agents/bmm-tea.customize.yaml | 42 +
.../agents/bmm-tech-writer.customize.yaml | 42 +
.../agents/bmm-ux-designer.customize.yaml | 42 +
.../agents/core-bmad-master.customize.yaml | 42 +
.bmad/_cfg/files-manifest.csv | 439 ++
.bmad/_cfg/ides/claude-code.yaml | 6 +
.bmad/_cfg/manifest.yaml | 12 +
.bmad/_cfg/task-manifest.csv | 6 +
.bmad/_cfg/tool-manifest.csv | 2 +
.bmad/_cfg/workflow-manifest.csv | 42 +
.bmad/bmb/README.md | 261 +
.bmad/bmb/agents/bmad-builder.md | 59 +
.bmad/bmb/config.yaml | 16 +
.bmad/bmb/docs/agents/agent-compilation.md | 340 ++
.bmad/bmb/docs/agents/agent-menu-patterns.md | 524 ++
.../docs/agents/expert-agent-architecture.md | 364 ++
.bmad/bmb/docs/agents/index.md | 55 +
.bmad/bmb/docs/agents/kb.csv | 0
.../docs/agents/module-agent-architecture.md | 367 ++
.../docs/agents/simple-agent-architecture.md | 292 +
.../docs/agents/understanding-agent-types.md | 184 +
.bmad/bmb/docs/workflows/architecture.md | 220 +
.../docs/workflows/common-workflow-tools.csv | 19 +
.../docs/workflows/csv-data-file-standards.md | 206 +
.bmad/bmb/docs/workflows/index.md | 45 +
.../intent-vs-prescriptive-spectrum.md | 220 +
.bmad/bmb/docs/workflows/kb.csv | 0
.../step-01-init-continuable-template.md | 241 +
.../workflows/templates/step-1b-template.md | 223 +
.../bmb/docs/workflows/templates/step-file.md | 139 +
.../docs/workflows/templates/step-template.md | 290 +
.../workflows/templates/workflow-template.md | 104 +
.../bmb/docs/workflows/templates/workflow.md | 58 +
.bmad/bmb/docs/workflows/terms.md | 97 +
.bmad/bmb/reference/README.md | 3 +
.../expert-examples/journal-keeper/README.md | 242 +
.../agents/module-examples/README.md | 50 +
.../agents/simple-examples/README.md | 223 +
.../data/dietary-restrictions.csv | 18 +
.../data/macro-calculator.csv | 16 +
.../data/recipe-database.csv | 28 +
.../meal-prep-nutrition/steps/step-01-init.md | 176 +
.../steps/step-01b-continue.md | 120 +
.../steps/step-02-profile.md | 164 +
.../steps/step-03-assessment.md | 153 +
.../steps/step-04-strategy.md | 182 +
.../steps/step-05-shopping.md | 167 +
.../steps/step-06-prep-schedule.md | 194 +
.../templates/assessment-section.md | 25 +
.../templates/nutrition-plan.md | 68 +
.../templates/prep-schedule-section.md | 29 +
.../templates/profile-section.md | 47 +
.../templates/shopping-section.md | 37 +
.../templates/strategy-section.md | 18 +
.../workflows/meal-prep-nutrition/workflow.md | 58 +
.../workflows-legacy/edit-module/README.md | 187 +
.../workflows-legacy/edit-module/checklist.md | 164 +
.../edit-module/instructions.md | 341 ++
.../edit-module/workflow.yaml | 33 +
.../workflows-legacy/module-brief/README.md | 264 +
.../module-brief/checklist.md | 116 +
.../module-brief/instructions.md | 268 +
.../workflows-legacy/module-brief/template.md | 275 +
.../module-brief/workflow.yaml | 35 +
.../data/agent-validation-checklist.md | 174 +
.../create-agent/data/brainstorm-context.md | 153 +
.../data/communication-presets.csv | 61 +
.../data/info-and-installation-guide.md | 29 +
.../create-agent/data/reference/README.md | 3 +
.../expert-examples/journal-keeper/README.md | 242 +
.../agents/module-examples/README.md | 50 +
.../agents/simple-examples/README.md | 223 +
.../data/dietary-restrictions.csv | 18 +
.../data/macro-calculator.csv | 16 +
.../data/recipe-database.csv | 28 +
.../meal-prep-nutrition/steps/step-01-init.md | 177 +
.../steps/step-01b-continue.md | 150 +
.../steps/step-02-profile.md | 164 +
.../steps/step-03-assessment.md | 152 +
.../steps/step-04-strategy.md | 182 +
.../steps/step-05-shopping.md | 167 +
.../steps/step-06-prep-schedule.md | 194 +
.../templates/assessment-section.md | 25 +
.../templates/nutrition-plan.md | 68 +
.../templates/prep-schedule-section.md | 29 +
.../templates/profile-section.md | 47 +
.../templates/shopping-section.md | 37 +
.../templates/strategy-section.md | 18 +
.../workflows/meal-prep-nutrition/workflow.md | 58 +
.../create-agent/data/validation-complete.md | 305 +
.../create-agent/steps/step-01-brainstorm.md | 145 +
.../create-agent/steps/step-02-discover.md | 210 +
.../create-agent/steps/step-03-persona.md | 260 +
.../create-agent/steps/step-04-commands.md | 237 +
.../create-agent/steps/step-05-name.md | 231 +
.../create-agent/steps/step-06-build.md | 224 +
.../create-agent/steps/step-07-validate.md | 234 +
.../create-agent/steps/step-08-setup.md | 179 +
.../create-agent/steps/step-09-customize.md | 197 +
.../create-agent/steps/step-10-build-tools.md | 180 +
.../create-agent/steps/step-11-celebrate.md | 222 +
.../create-agent/templates/agent_commands.md | 21 +
.../create-agent/templates/agent_persona.md | 25 +
.../templates/agent_purpose_and_type.md | 23 +
.bmad/bmb/workflows/create-agent/workflow.md | 91 +
.../create-module/steps/step-01-init.md | 155 +
.../create-module/steps/step-01b-continue.md | 169 +
.../create-module/steps/step-02-concept.md | 217 +
.../create-module/steps/step-03-components.md | 267 +
.../create-module/steps/step-04-structure.md | 228 +
.../create-module/steps/step-05-config.md | 233 +
.../create-module/steps/step-06-agents.md | 296 +
.../create-module/steps/step-07-workflows.md | 228 +
.../create-module/steps/step-08-installer.md | 186 +
.../steps/step-09-documentation.md | 309 +
.../create-module/steps/step-10-roadmap.md | 337 ++
.../create-module/steps/step-11-validate.md | 335 ++
.../create-module/templates/agent.template.md | 317 ++
.../templates/installer.template.js | 47 +
.../templates/module-plan.template.md | 5 +
.../templates/module.template.yaml | 53 +
.../templates/workflow-plan-template.md | 23 +
.../bmb/workflows/create-module/validation.md | 126 +
.bmad/bmb/workflows/create-module/workflow.md | 55 +
.../create-workflow/steps/step-01-init.md | 157 +
.../create-workflow/steps/step-02-gather.md | 211 +
.../steps/step-03-tools-configuration.md | 250 +
.../steps/step-04-plan-review.md | 216 +
.../steps/step-05-output-format-design.md | 289 +
.../create-workflow/steps/step-06-design.md | 271 +
.../create-workflow/steps/step-07-build.md | 308 +
.../create-workflow/steps/step-08-review.md | 284 +
.../create-workflow/steps/step-09-complete.md | 187 +
.../bmb/workflows/create-workflow/workflow.md | 58 +
.../steps/step-01-discover-intent.md | 134 +
.../edit-agent/steps/step-02-analyze-agent.md | 202 +
.../steps/step-03-propose-changes.md | 157 +
.../edit-agent/steps/step-04-apply-changes.md | 150 +
.../edit-agent/steps/step-05-validate.md | 150 +
.bmad/bmb/workflows/edit-agent/workflow.md | 58 +
.../edit-workflow/steps/step-01-analyze.md | 217 +
.../edit-workflow/steps/step-02-discover.md | 253 +
.../edit-workflow/steps/step-03-improve.md | 217 +
.../edit-workflow/steps/step-04-validate.md | 193 +
.../steps/step-05-compliance-check.md | 245 +
.../templates/completion-summary.md | 75 +
.../templates/improvement-goals.md | 68 +
.../templates/improvement-log.md | 40 +
.../templates/validation-results.md | 51 +
.../templates/workflow-analysis.md | 56 +
.bmad/bmb/workflows/edit-workflow/workflow.md | 58 +
.../steps/step-01-validate-goal.md | 152 +
.../steps/step-02-workflow-validation.md | 243 +
.../steps/step-03-step-validation.md | 274 +
.../steps/step-04-file-validation.md | 295 +
.../step-05-intent-spectrum-validation.md | 264 +
.../step-06-web-subprocess-validation.md | 360 ++
.../steps/step-07-holistic-analysis.md | 258 +
.../steps/step-08-generate-report.md | 301 +
.../templates/compliance-report.md | 140 +
.../workflow-compliance-check/workflow.md | 58 +
.bmad/bmm/README.md | 128 +
.bmad/bmm/agents/analyst.md | 73 +
.bmad/bmm/agents/architect.md | 67 +
.bmad/bmm/agents/dev.md | 69 +
.bmad/bmm/agents/pm.md | 67 +
.bmad/bmm/agents/quick-flow-solo-dev.md | 64 +
.bmad/bmm/agents/sm.md | 82 +
.bmad/bmm/agents/tea.md | 74 +
.bmad/bmm/agents/tech-writer.md | 77 +
.bmad/bmm/agents/ux-designer.md | 75 +
.bmad/bmm/config.yaml | 19 +
.bmad/bmm/data/README.md | 29 +
.bmad/bmm/data/documentation-standards.md | 262 +
.bmad/bmm/data/project-context-template.md | 40 +
.bmad/bmm/docs/README.md | 274 +
.bmad/bmm/docs/agents-guide.md | 1085 ++++
.bmad/bmm/docs/bmad-quick-flow.md | 528 ++
.bmad/bmm/docs/brownfield-guide.md | 748 +++
.../docs/enterprise-agentic-development.md | 686 +++
.bmad/bmm/docs/faq.md | 555 ++
.bmad/bmm/docs/glossary.md | 307 +
.bmad/bmm/docs/images/README.md | 37 +
.../workflow-method-greenfield.excalidraw | 5034 +++++++++++++++++
.../images/workflow-method-greenfield.svg | 4 +
.bmad/bmm/docs/party-mode.md | 224 +
.bmad/bmm/docs/quick-flow-solo-dev.md | 337 ++
.bmad/bmm/docs/quick-spec-flow.md | 652 +++
.bmad/bmm/docs/quick-start.md | 366 ++
.bmad/bmm/docs/scale-adaptive-system.md | 618 ++
.bmad/bmm/docs/test-architecture.md | 462 ++
.bmad/bmm/docs/troubleshooting.md | 680 +++
.../docs/workflow-architecture-reference.md | 366 ++
.../workflow-document-project-reference.md | 489 ++
.bmad/bmm/docs/workflows-analysis.md | 266 +
.bmad/bmm/docs/workflows-implementation.md | 311 +
.bmad/bmm/docs/workflows-planning.md | 451 ++
.bmad/bmm/docs/workflows-solutioning.md | 509 ++
.bmad/bmm/tasks/daily-standup.xml | 85 +
.bmad/bmm/teams/default-party.csv | 21 +
.bmad/bmm/teams/team-fullstack.yaml | 12 +
.bmad/bmm/testarch/knowledge/api-request.md | 303 +
.bmad/bmm/testarch/knowledge/auth-session.md | 356 ++
.bmad/bmm/testarch/knowledge/burn-in.md | 273 +
.bmad/bmm/testarch/knowledge/ci-burn-in.md | 675 +++
.bmad/bmm/testarch/knowledge/component-tdd.md | 486 ++
.../testarch/knowledge/contract-testing.md | 957 ++++
.../bmm/testarch/knowledge/data-factories.md | 500 ++
.bmad/bmm/testarch/knowledge/email-auth.md | 721 +++
.../bmm/testarch/knowledge/error-handling.md | 725 +++
.bmad/bmm/testarch/knowledge/feature-flags.md | 750 +++
.bmad/bmm/testarch/knowledge/file-utils.md | 260 +
.../knowledge/fixture-architecture.md | 401 ++
.../knowledge/fixtures-composition.md | 382 ++
.../knowledge/intercept-network-call.md | 280 +
.bmad/bmm/testarch/knowledge/log.md | 294 +
.../knowledge/network-error-monitor.md | 272 +
.bmad/bmm/testarch/knowledge/network-first.md | 486 ++
.../testarch/knowledge/network-recorder.md | 265 +
.bmad/bmm/testarch/knowledge/nfr-criteria.md | 670 +++
.bmad/bmm/testarch/knowledge/overview.md | 284 +
.../testarch/knowledge/playwright-config.md | 730 +++
.../testarch/knowledge/probability-impact.md | 601 ++
.bmad/bmm/testarch/knowledge/recurse.md | 296 +
.../bmm/testarch/knowledge/risk-governance.md | 615 ++
.../testarch/knowledge/selective-testing.md | 732 +++
.../testarch/knowledge/selector-resilience.md | 527 ++
.../knowledge/test-healing-patterns.md | 644 +++
.../knowledge/test-levels-framework.md | 473 ++
.../knowledge/test-priorities-matrix.md | 373 ++
.bmad/bmm/testarch/knowledge/test-quality.md | 664 +++
.../testarch/knowledge/timing-debugging.md | 372 ++
.../testarch/knowledge/visual-debugging.md | 524 ++
.bmad/bmm/testarch/tea-index.csv | 33 +
.../product-brief/product-brief.template.md | 8 +
.../product-brief/steps/step-01-init.md | 192 +
.../product-brief/steps/step-01b-continue.md | 167 +
.../product-brief/steps/step-02-vision.md | 203 +
.../product-brief/steps/step-03-users.md | 206 +
.../product-brief/steps/step-04-metrics.md | 209 +
.../product-brief/steps/step-05-scope.md | 223 +
.../product-brief/steps/step-06-complete.md | 199 +
.../1-analysis/product-brief/workflow.md | 58 +
.../research/domain-steps/step-01-init.md | 136 +
.../domain-steps/step-02-domain-analysis.md | 228 +
.../step-03-competitive-landscape.md | 237 +
.../domain-steps/step-04-regulatory-focus.md | 205 +
.../domain-steps/step-05-technical-trends.md | 233 +
.../step-06-research-synthesis.md | 442 ++
.../research/market-steps/step-01-init.md | 181 +
.../market-steps/step-02-customer-behavior.md | 236 +
.../market-steps/step-02-customer-insights.md | 199 +
.../step-03-customer-pain-points.md | 248 +
.../step-04-customer-decisions.md | 258 +
.../step-05-competitive-analysis.md | 176 +
.../step-06-research-completion.md | 474 ++
.../1-analysis/research/research.template.md | 15 +
.../research/technical-steps/step-01-init.md | 136 +
.../step-02-technical-overview.md | 238 +
.../step-03-integration-patterns.md | 247 +
.../step-04-architectural-patterns.md | 201 +
.../step-05-implementation-research.md | 238 +
.../step-06-research-synthesis.md | 485 ++
.../workflows/1-analysis/research/workflow.md | 204 +
.../create-ux-design/steps/step-01-init.md | 159 +
.../steps/step-01b-continue.md | 126 +
.../steps/step-02-discovery.md | 209 +
.../steps/step-03-core-experience.md | 215 +
.../steps/step-04-emotional-response.md | 218 +
.../steps/step-05-inspiration.md | 233 +
.../steps/step-06-design-system.md | 251 +
.../steps/step-07-defining-experience.md | 253 +
.../steps/step-08-visual-foundation.md | 223 +
.../steps/step-09-design-directions.md | 223 +
.../steps/step-10-user-journeys.md | 240 +
.../steps/step-11-component-strategy.md | 247 +
.../steps/step-12-ux-patterns.md | 236 +
.../steps/step-13-responsive-accessibility.md | 263 +
.../steps/step-14-complete.md | 226 +
.../create-ux-design/ux-design-template.md | 13 +
.../create-ux-design/workflow.md | 59 +
.../prd/domain-complexity.csv | 13 +
.../2-plan-workflows/prd/prd-template.md | 16 +
.../2-plan-workflows/prd/project-types.csv | 11 +
.../prd/steps/step-01-init.md | 243 +
.../prd/steps/step-01b-continue.md | 165 +
.../prd/steps/step-02-discovery.md | 420 ++
.../prd/steps/step-03-success.md | 289 +
.../prd/steps/step-04-journeys.md | 290 +
.../prd/steps/step-05-domain.md | 270 +
.../prd/steps/step-06-innovation.md | 261 +
.../prd/steps/step-07-project-type.md | 257 +
.../prd/steps/step-08-scoping.md | 298 +
.../prd/steps/step-09-functional.md | 269 +
.../prd/steps/step-10-nonfunctional.md | 293 +
.../prd/steps/step-11-complete.md | 223 +
.../2-plan-workflows/prd/workflow.md | 61 +
.../architecture-decision-template.md | 13 +
.../architecture/data/domain-complexity.csv | 11 +
.../architecture/data/project-types.csv | 7 +
.../architecture/steps/step-01-init.md | 194 +
.../architecture/steps/step-01b-continue.md | 163 +
.../architecture/steps/step-02-context.md | 223 +
.../architecture/steps/step-03-starter.md | 330 ++
.../architecture/steps/step-04-decisions.md | 317 ++
.../architecture/steps/step-05-patterns.md | 358 ++
.../architecture/steps/step-06-structure.md | 378 ++
.../architecture/steps/step-07-validation.md | 358 ++
.../architecture/steps/step-08-complete.md | 351 ++
.../3-solutioning/architecture/workflow.md | 49 +
.../steps/step-01-validate-prerequisites.md | 258 +
.../steps/step-02-design-epics.md | 232 +
.../steps/step-03-create-stories.md | 271 +
.../steps/step-04-final-validation.md | 144 +
.../templates/epics-template.md | 57 +
.../create-epics-and-stories/workflow.md | 58 +
.../steps/step-01-document-discovery.md | 189 +
.../steps/step-02-prd-analysis.md | 177 +
.../steps/step-03-epic-coverage-validation.md | 178 +
.../steps/step-04-ux-alignment.md | 138 +
.../steps/step-05-epic-quality-review.md | 251 +
.../steps/step-06-final-assessment.md | 132 +
.../templates/readiness-report-template.md | 4 +
.../implementation-readiness/workflow.md | 54 +
.../4-implementation/code-review/checklist.md | 23 +
.../code-review/instructions.xml | 224 +
.../code-review/workflow.yaml | 53 +
.../correct-course/checklist.md | 279 +
.../correct-course/instructions.md | 206 +
.../correct-course/workflow.yaml | 56 +
.../create-story/checklist.md | 358 ++
.../create-story/instructions.xml | 354 ++
.../4-implementation/create-story/template.md | 51 +
.../create-story/workflow.yaml | 58 +
.../4-implementation/dev-story/checklist.md | 80 +
.../dev-story/instructions.xml | 406 ++
.../4-implementation/dev-story/workflow.yaml | 25 +
.../retrospective/instructions.md | 1443 +++++
.../retrospective/workflow.yaml | 56 +
.../sprint-planning/checklist.md | 33 +
.../sprint-planning/instructions.md | 232 +
.../sprint-status-template.yaml | 56 +
.../sprint-planning/workflow.yaml | 51 +
.../sprint-status/instructions.md | 174 +
.../sprint-status/workflow.yaml | 34 +
.../create-tech-spec/instructions.md | 115 +
.../create-tech-spec/workflow.yaml | 25 +
.../bmad-quick-flow/quick-dev/checklist.md | 25 +
.../bmad-quick-flow/quick-dev/instructions.md | 202 +
.../bmad-quick-flow/quick-dev/workflow.yaml | 32 +
.../diagrams/_shared/excalidraw-library.json | 90 +
.../_shared/excalidraw-templates.yaml | 127 +
.../diagrams/create-dataflow/checklist.md | 39 +
.../diagrams/create-dataflow/instructions.md | 130 +
.../diagrams/create-dataflow/workflow.yaml | 26 +
.../diagrams/create-diagram/checklist.md | 43 +
.../diagrams/create-diagram/instructions.md | 141 +
.../diagrams/create-diagram/workflow.yaml | 26 +
.../diagrams/create-flowchart/checklist.md | 49 +
.../diagrams/create-flowchart/instructions.md | 241 +
.../diagrams/create-flowchart/workflow.yaml | 26 +
.../diagrams/create-wireframe/checklist.md | 38 +
.../diagrams/create-wireframe/instructions.md | 133 +
.../diagrams/create-wireframe/workflow.yaml | 26 +
.../workflows/document-project/checklist.md | 245 +
.../documentation-requirements.csv | 12 +
.../document-project/instructions.md | 222 +
.../templates/deep-dive-template.md | 345 ++
.../templates/index-template.md | 169 +
.../templates/project-overview-template.md | 103 +
.../templates/project-scan-report-schema.json | 160 +
.../templates/source-tree-template.md | 135 +
.../workflows/document-project/workflow.yaml | 29 +
.../workflows/deep-dive-instructions.md | 298 +
.../document-project/workflows/deep-dive.yaml | 31 +
.../workflows/full-scan-instructions.md | 1106 ++++
.../document-project/workflows/full-scan.yaml | 31 +
.../project-context-template.md | 20 +
.../steps/step-01-discover.md | 193 +
.../steps/step-02-generate.md | 317 ++
.../steps/step-03-complete.md | 277 +
.../generate-project-context/workflow.md | 48 +
.../testarch/atdd/atdd-checklist-template.md | 363 ++
.../bmm/workflows/testarch/atdd/checklist.md | 373 ++
.../workflows/testarch/atdd/instructions.md | 805 +++
.../bmm/workflows/testarch/atdd/workflow.yaml | 45 +
.../workflows/testarch/automate/checklist.md | 580 ++
.../testarch/automate/instructions.md | 1324 +++++
.../workflows/testarch/automate/workflow.yaml | 52 +
.bmad/bmm/workflows/testarch/ci/checklist.md | 246 +
.../testarch/ci/github-actions-template.yaml | 198 +
.../testarch/ci/gitlab-ci-template.yaml | 149 +
.../bmm/workflows/testarch/ci/instructions.md | 534 ++
.bmad/bmm/workflows/testarch/ci/workflow.yaml | 45 +
.../workflows/testarch/framework/checklist.md | 321 ++
.../testarch/framework/instructions.md | 481 ++
.../testarch/framework/workflow.yaml | 47 +
.../testarch/nfr-assess/checklist.md | 405 ++
.../testarch/nfr-assess/instructions.md | 722 +++
.../nfr-assess/nfr-report-template.md | 443 ++
.../testarch/nfr-assess/workflow.yaml | 47 +
.../testarch/test-design/checklist.md | 234 +
.../testarch/test-design/instructions.md | 788 +++
.../test-design/test-design-template.md | 285 +
.../testarch/test-design/workflow.yaml | 48 +
.../testarch/test-review/checklist.md | 470 ++
.../testarch/test-review/instructions.md | 628 ++
.../test-review/test-review-template.md | 388 ++
.../testarch/test-review/workflow.yaml | 46 +
.../bmm/workflows/testarch/trace/checklist.md | 654 +++
.../workflows/testarch/trace/instructions.md | 1045 ++++
.../testarch/trace/trace-template.md | 673 +++
.../workflows/testarch/trace/workflow.yaml | 55 +
.../workflow-status/init/instructions.md | 346 ++
.../workflow-status/init/workflow.yaml | 28 +
.../workflows/workflow-status/instructions.md | 395 ++
.../paths/enterprise-brownfield.yaml | 122 +
.../paths/enterprise-greenfield.yaml | 110 +
.../paths/method-brownfield.yaml | 106 +
.../paths/method-greenfield.yaml | 96 +
.../workflow-status/project-levels.yaml | 59 +
.../workflow-status-template.yaml | 24 +
.../workflows/workflow-status/workflow.yaml | 28 +
.bmad/core/agents/bmad-master.md | 67 +
.../agents/bmad-web-orchestrator.agent.xml | 113 +
.bmad/core/config.yaml | 12 +
.bmad/core/module.yaml | 39 +
.bmad/core/resources/excalidraw/README.md | 160 +
.../excalidraw/excalidraw-helpers.md | 127 +
.../resources/excalidraw/library-loader.md | 50 +
.../excalidraw/validate-json-instructions.md | 79 +
.../tasks/advanced-elicitation-methods.csv | 51 +
.bmad/core/tasks/advanced-elicitation.xml | 116 +
.bmad/core/tasks/index-docs.xml | 65 +
.bmad/core/tasks/validate-workflow.xml | 89 +
.bmad/core/tasks/workflow.xml | 235 +
.bmad/core/tools/shard-doc.xml | 109 +
.../workflows/brainstorming/brain-methods.csv | 62 +
.../steps/step-01-session-setup.md | 196 +
.../brainstorming/steps/step-01b-continue.md | 121 +
.../steps/step-02a-user-selected.md | 224 +
.../steps/step-02b-ai-recommended.md | 236 +
.../steps/step-02c-random-selection.md | 208 +
.../steps/step-02d-progressive-flow.md | 263 +
.../steps/step-03-technique-execution.md | 339 ++
.../steps/step-04-idea-organization.md | 302 +
.../core/workflows/brainstorming/template.md | 15 +
.../core/workflows/brainstorming/workflow.md | 51 +
.../party-mode/steps/step-01-agent-loading.md | 138 +
.../steps/step-02-discussion-orchestration.md | 203 +
.../party-mode/steps/step-03-graceful-exit.md | 158 +
.bmad/core/workflows/party-mode/workflow.md | 206 +
.bmad/docs/auggie-instructions.md | 31 +
.bmad/docs/claude-code-instructions.md | 25 +
.../commands/bmad/bmb/agents/bmad-builder.md | 14 +
.../workflows/Meal Prep & Nutrition Plan.md | 5 +
.../bmad/bmb/workflows/create-agent.md | 5 +
.../bmad/bmb/workflows/create-module.md | 5 +
.../bmad/bmb/workflows/create-workflow.md | 5 +
.../commands/bmad/bmb/workflows/edit-agent.md | 5 +
.../bmad/bmb/workflows/edit-workflow.md | 5 +
.../workflows/workflow-compliance-check.md | 5 +
.claude/commands/bmad/bmm/agents/analyst.md | 14 +
.claude/commands/bmad/bmm/agents/architect.md | 14 +
.claude/commands/bmad/bmm/agents/dev.md | 14 +
.claude/commands/bmad/bmm/agents/pm.md | 14 +
.../bmad/bmm/agents/quick-flow-solo-dev.md | 14 +
.claude/commands/bmad/bmm/agents/sm.md | 14 +
.claude/commands/bmad/bmm/agents/tea.md | 14 +
.../commands/bmad/bmm/agents/tech-writer.md | 14 +
.../commands/bmad/bmm/agents/ux-designer.md | 14 +
.../check-implementation-readiness.md | 5 +
.../bmad/bmm/workflows/code-review.md | 13 +
.../bmad/bmm/workflows/correct-course.md | 13 +
.../bmad/bmm/workflows/create-architecture.md | 5 +
.../bmm/workflows/create-epics-stories.md | 5 +
.../workflows/create-excalidraw-dataflow.md | 13 +
.../workflows/create-excalidraw-diagram.md | 13 +
.../workflows/create-excalidraw-flowchart.md | 13 +
.../workflows/create-excalidraw-wireframe.md | 13 +
.../commands/bmad/bmm/workflows/create-prd.md | 5 +
.../bmm/workflows/create-product-brief.md | 5 +
.../bmad/bmm/workflows/create-story.md | 13 +
.../bmad/bmm/workflows/create-tech-spec.md | 13 +
.../bmad/bmm/workflows/create-ux-design.md | 5 +
.../commands/bmad/bmm/workflows/dev-story.md | 13 +
.../bmad/bmm/workflows/document-project.md | 13 +
.../bmm/workflows/generate-project-context.md | 5 +
.../commands/bmad/bmm/workflows/quick-dev.md | 13 +
.../commands/bmad/bmm/workflows/research.md | 5 +
.../bmad/bmm/workflows/retrospective.md | 13 +
.../bmad/bmm/workflows/sprint-planning.md | 13 +
.../bmad/bmm/workflows/sprint-status.md | 13 +
.../bmad/bmm/workflows/testarch-atdd.md | 13 +
.../bmad/bmm/workflows/testarch-automate.md | 13 +
.../bmad/bmm/workflows/testarch-ci.md | 13 +
.../bmad/bmm/workflows/testarch-framework.md | 13 +
.../bmad/bmm/workflows/testarch-nfr.md | 13 +
.../bmm/workflows/testarch-test-design.md | 13 +
.../bmm/workflows/testarch-test-review.md | 13 +
.../bmad/bmm/workflows/testarch-trace.md | 13 +
.../bmad/bmm/workflows/workflow-init.md | 13 +
.../bmad/bmm/workflows/workflow-status.md | 13 +
.../commands/bmad/core/agents/bmad-master.md | 14 +
.../bmad/core/tasks/advanced-elicitation.md | 9 +
.../commands/bmad/core/tasks/index-docs.md | 9 +
.claude/commands/bmad/core/tools/shard-doc.md | 9 +
.../core/workflows/brainstorming-session.md | 5 +
.../bmad/core/workflows/party-mode.md | 5 +
bmad-custom-src/custom.yaml | 3 +
573 files changed, 103923 insertions(+)
create mode 100644 .augment/commands/bmad/agents/bmb-bmad-builder.md
create mode 100644 .augment/commands/bmad/agents/bmm-analyst.md
create mode 100644 .augment/commands/bmad/agents/bmm-architect.md
create mode 100644 .augment/commands/bmad/agents/bmm-dev.md
create mode 100644 .augment/commands/bmad/agents/bmm-pm.md
create mode 100644 .augment/commands/bmad/agents/bmm-quick-flow-solo-dev.md
create mode 100644 .augment/commands/bmad/agents/bmm-sm.md
create mode 100644 .augment/commands/bmad/agents/bmm-tea.md
create mode 100644 .augment/commands/bmad/agents/bmm-tech-writer.md
create mode 100644 .augment/commands/bmad/agents/bmm-ux-designer.md
create mode 100644 .augment/commands/bmad/agents/core-bmad-master.md
create mode 100644 .augment/commands/bmad/tasks/core-advanced-elicitation.md
create mode 100644 .augment/commands/bmad/tasks/core-index-docs.md
create mode 100644 .augment/commands/bmad/tools/core-shard-doc.md
create mode 100644 .augment/commands/bmad/workflows/bmb-Meal Prep & Nutrition Plan.md
create mode 100644 .augment/commands/bmad/workflows/bmb-create-agent.md
create mode 100644 .augment/commands/bmad/workflows/bmb-create-module.md
create mode 100644 .augment/commands/bmad/workflows/bmb-create-workflow.md
create mode 100644 .augment/commands/bmad/workflows/bmb-edit-agent.md
create mode 100644 .augment/commands/bmad/workflows/bmb-edit-workflow.md
create mode 100644 .augment/commands/bmad/workflows/bmb-workflow-compliance-check.md
create mode 100644 .augment/commands/bmad/workflows/bmm-check-implementation-readiness.md
create mode 100644 .augment/commands/bmad/workflows/bmm-code-review.md
create mode 100644 .augment/commands/bmad/workflows/bmm-correct-course.md
create mode 100644 .augment/commands/bmad/workflows/bmm-create-architecture.md
create mode 100644 .augment/commands/bmad/workflows/bmm-create-epics-stories.md
create mode 100644 .augment/commands/bmad/workflows/bmm-create-excalidraw-dataflow.md
create mode 100644 .augment/commands/bmad/workflows/bmm-create-excalidraw-diagram.md
create mode 100644 .augment/commands/bmad/workflows/bmm-create-excalidraw-flowchart.md
create mode 100644 .augment/commands/bmad/workflows/bmm-create-excalidraw-wireframe.md
create mode 100644 .augment/commands/bmad/workflows/bmm-create-prd.md
create mode 100644 .augment/commands/bmad/workflows/bmm-create-product-brief.md
create mode 100644 .augment/commands/bmad/workflows/bmm-create-story.md
create mode 100644 .augment/commands/bmad/workflows/bmm-create-tech-spec.md
create mode 100644 .augment/commands/bmad/workflows/bmm-create-ux-design.md
create mode 100644 .augment/commands/bmad/workflows/bmm-dev-story.md
create mode 100644 .augment/commands/bmad/workflows/bmm-document-project.md
create mode 100644 .augment/commands/bmad/workflows/bmm-generate-project-context.md
create mode 100644 .augment/commands/bmad/workflows/bmm-quick-dev.md
create mode 100644 .augment/commands/bmad/workflows/bmm-research.md
create mode 100644 .augment/commands/bmad/workflows/bmm-retrospective.md
create mode 100644 .augment/commands/bmad/workflows/bmm-sprint-planning.md
create mode 100644 .augment/commands/bmad/workflows/bmm-sprint-status.md
create mode 100644 .augment/commands/bmad/workflows/bmm-testarch-atdd.md
create mode 100644 .augment/commands/bmad/workflows/bmm-testarch-automate.md
create mode 100644 .augment/commands/bmad/workflows/bmm-testarch-ci.md
create mode 100644 .augment/commands/bmad/workflows/bmm-testarch-framework.md
create mode 100644 .augment/commands/bmad/workflows/bmm-testarch-nfr.md
create mode 100644 .augment/commands/bmad/workflows/bmm-testarch-test-design.md
create mode 100644 .augment/commands/bmad/workflows/bmm-testarch-test-review.md
create mode 100644 .augment/commands/bmad/workflows/bmm-testarch-trace.md
create mode 100644 .augment/commands/bmad/workflows/bmm-workflow-init.md
create mode 100644 .augment/commands/bmad/workflows/bmm-workflow-status.md
create mode 100644 .augment/commands/bmad/workflows/core-brainstorming-session.md
create mode 100644 .augment/commands/bmad/workflows/core-party-mode.md
create mode 100644 .bmad/_cfg/agent-manifest.csv
create mode 100644 .bmad/_cfg/agents/bmb-bmad-builder.customize.yaml
create mode 100644 .bmad/_cfg/agents/bmm-analyst.customize.yaml
create mode 100644 .bmad/_cfg/agents/bmm-architect.customize.yaml
create mode 100644 .bmad/_cfg/agents/bmm-dev.customize.yaml
create mode 100644 .bmad/_cfg/agents/bmm-pm.customize.yaml
create mode 100644 .bmad/_cfg/agents/bmm-quick-flow-solo-dev.customize.yaml
create mode 100644 .bmad/_cfg/agents/bmm-sm.customize.yaml
create mode 100644 .bmad/_cfg/agents/bmm-tea.customize.yaml
create mode 100644 .bmad/_cfg/agents/bmm-tech-writer.customize.yaml
create mode 100644 .bmad/_cfg/agents/bmm-ux-designer.customize.yaml
create mode 100644 .bmad/_cfg/agents/core-bmad-master.customize.yaml
create mode 100644 .bmad/_cfg/files-manifest.csv
create mode 100644 .bmad/_cfg/ides/claude-code.yaml
create mode 100644 .bmad/_cfg/manifest.yaml
create mode 100644 .bmad/_cfg/task-manifest.csv
create mode 100644 .bmad/_cfg/tool-manifest.csv
create mode 100644 .bmad/_cfg/workflow-manifest.csv
create mode 100644 .bmad/bmb/README.md
create mode 100644 .bmad/bmb/agents/bmad-builder.md
create mode 100644 .bmad/bmb/config.yaml
create mode 100644 .bmad/bmb/docs/agents/agent-compilation.md
create mode 100644 .bmad/bmb/docs/agents/agent-menu-patterns.md
create mode 100644 .bmad/bmb/docs/agents/expert-agent-architecture.md
create mode 100644 .bmad/bmb/docs/agents/index.md
create mode 100644 .bmad/bmb/docs/agents/kb.csv
create mode 100644 .bmad/bmb/docs/agents/module-agent-architecture.md
create mode 100644 .bmad/bmb/docs/agents/simple-agent-architecture.md
create mode 100644 .bmad/bmb/docs/agents/understanding-agent-types.md
create mode 100644 .bmad/bmb/docs/workflows/architecture.md
create mode 100644 .bmad/bmb/docs/workflows/common-workflow-tools.csv
create mode 100644 .bmad/bmb/docs/workflows/csv-data-file-standards.md
create mode 100644 .bmad/bmb/docs/workflows/index.md
create mode 100644 .bmad/bmb/docs/workflows/intent-vs-prescriptive-spectrum.md
create mode 100644 .bmad/bmb/docs/workflows/kb.csv
create mode 100644 .bmad/bmb/docs/workflows/templates/step-01-init-continuable-template.md
create mode 100644 .bmad/bmb/docs/workflows/templates/step-1b-template.md
create mode 100644 .bmad/bmb/docs/workflows/templates/step-file.md
create mode 100644 .bmad/bmb/docs/workflows/templates/step-template.md
create mode 100644 .bmad/bmb/docs/workflows/templates/workflow-template.md
create mode 100644 .bmad/bmb/docs/workflows/templates/workflow.md
create mode 100644 .bmad/bmb/docs/workflows/terms.md
create mode 100644 .bmad/bmb/reference/README.md
create mode 100644 .bmad/bmb/reference/agents/expert-examples/journal-keeper/README.md
create mode 100644 .bmad/bmb/reference/agents/module-examples/README.md
create mode 100644 .bmad/bmb/reference/agents/simple-examples/README.md
create mode 100644 .bmad/bmb/reference/workflows/meal-prep-nutrition/data/dietary-restrictions.csv
create mode 100644 .bmad/bmb/reference/workflows/meal-prep-nutrition/data/macro-calculator.csv
create mode 100644 .bmad/bmb/reference/workflows/meal-prep-nutrition/data/recipe-database.csv
create mode 100644 .bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md
create mode 100644 .bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-01b-continue.md
create mode 100644 .bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-02-profile.md
create mode 100644 .bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-03-assessment.md
create mode 100644 .bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-04-strategy.md
create mode 100644 .bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-05-shopping.md
create mode 100644 .bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-06-prep-schedule.md
create mode 100644 .bmad/bmb/reference/workflows/meal-prep-nutrition/templates/assessment-section.md
create mode 100644 .bmad/bmb/reference/workflows/meal-prep-nutrition/templates/nutrition-plan.md
create mode 100644 .bmad/bmb/reference/workflows/meal-prep-nutrition/templates/prep-schedule-section.md
create mode 100644 .bmad/bmb/reference/workflows/meal-prep-nutrition/templates/profile-section.md
create mode 100644 .bmad/bmb/reference/workflows/meal-prep-nutrition/templates/shopping-section.md
create mode 100644 .bmad/bmb/reference/workflows/meal-prep-nutrition/templates/strategy-section.md
create mode 100644 .bmad/bmb/reference/workflows/meal-prep-nutrition/workflow.md
create mode 100644 .bmad/bmb/workflows-legacy/edit-module/README.md
create mode 100644 .bmad/bmb/workflows-legacy/edit-module/checklist.md
create mode 100644 .bmad/bmb/workflows-legacy/edit-module/instructions.md
create mode 100644 .bmad/bmb/workflows-legacy/edit-module/workflow.yaml
create mode 100644 .bmad/bmb/workflows-legacy/module-brief/README.md
create mode 100644 .bmad/bmb/workflows-legacy/module-brief/checklist.md
create mode 100644 .bmad/bmb/workflows-legacy/module-brief/instructions.md
create mode 100644 .bmad/bmb/workflows-legacy/module-brief/template.md
create mode 100644 .bmad/bmb/workflows-legacy/module-brief/workflow.yaml
create mode 100644 .bmad/bmb/workflows/create-agent/data/agent-validation-checklist.md
create mode 100644 .bmad/bmb/workflows/create-agent/data/brainstorm-context.md
create mode 100644 .bmad/bmb/workflows/create-agent/data/communication-presets.csv
create mode 100644 .bmad/bmb/workflows/create-agent/data/info-and-installation-guide.md
create mode 100644 .bmad/bmb/workflows/create-agent/data/reference/README.md
create mode 100644 .bmad/bmb/workflows/create-agent/data/reference/agents/expert-examples/journal-keeper/README.md
create mode 100644 .bmad/bmb/workflows/create-agent/data/reference/agents/module-examples/README.md
create mode 100644 .bmad/bmb/workflows/create-agent/data/reference/agents/simple-examples/README.md
create mode 100644 .bmad/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/data/dietary-restrictions.csv
create mode 100644 .bmad/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/data/macro-calculator.csv
create mode 100644 .bmad/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/data/recipe-database.csv
create mode 100644 .bmad/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-01-init.md
create mode 100644 .bmad/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-01b-continue.md
create mode 100644 .bmad/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-02-profile.md
create mode 100644 .bmad/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-03-assessment.md
create mode 100644 .bmad/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-04-strategy.md
create mode 100644 .bmad/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-05-shopping.md
create mode 100644 .bmad/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-06-prep-schedule.md
create mode 100644 .bmad/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/templates/assessment-section.md
create mode 100644 .bmad/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/templates/nutrition-plan.md
create mode 100644 .bmad/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/templates/prep-schedule-section.md
create mode 100644 .bmad/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/templates/profile-section.md
create mode 100644 .bmad/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/templates/shopping-section.md
create mode 100644 .bmad/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/templates/strategy-section.md
create mode 100644 .bmad/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/workflow.md
create mode 100644 .bmad/bmb/workflows/create-agent/data/validation-complete.md
create mode 100644 .bmad/bmb/workflows/create-agent/steps/step-01-brainstorm.md
create mode 100644 .bmad/bmb/workflows/create-agent/steps/step-02-discover.md
create mode 100644 .bmad/bmb/workflows/create-agent/steps/step-03-persona.md
create mode 100644 .bmad/bmb/workflows/create-agent/steps/step-04-commands.md
create mode 100644 .bmad/bmb/workflows/create-agent/steps/step-05-name.md
create mode 100644 .bmad/bmb/workflows/create-agent/steps/step-06-build.md
create mode 100644 .bmad/bmb/workflows/create-agent/steps/step-07-validate.md
create mode 100644 .bmad/bmb/workflows/create-agent/steps/step-08-setup.md
create mode 100644 .bmad/bmb/workflows/create-agent/steps/step-09-customize.md
create mode 100644 .bmad/bmb/workflows/create-agent/steps/step-10-build-tools.md
create mode 100644 .bmad/bmb/workflows/create-agent/steps/step-11-celebrate.md
create mode 100644 .bmad/bmb/workflows/create-agent/templates/agent_commands.md
create mode 100644 .bmad/bmb/workflows/create-agent/templates/agent_persona.md
create mode 100644 .bmad/bmb/workflows/create-agent/templates/agent_purpose_and_type.md
create mode 100644 .bmad/bmb/workflows/create-agent/workflow.md
create mode 100644 .bmad/bmb/workflows/create-module/steps/step-01-init.md
create mode 100644 .bmad/bmb/workflows/create-module/steps/step-01b-continue.md
create mode 100644 .bmad/bmb/workflows/create-module/steps/step-02-concept.md
create mode 100644 .bmad/bmb/workflows/create-module/steps/step-03-components.md
create mode 100644 .bmad/bmb/workflows/create-module/steps/step-04-structure.md
create mode 100644 .bmad/bmb/workflows/create-module/steps/step-05-config.md
create mode 100644 .bmad/bmb/workflows/create-module/steps/step-06-agents.md
create mode 100644 .bmad/bmb/workflows/create-module/steps/step-07-workflows.md
create mode 100644 .bmad/bmb/workflows/create-module/steps/step-08-installer.md
create mode 100644 .bmad/bmb/workflows/create-module/steps/step-09-documentation.md
create mode 100644 .bmad/bmb/workflows/create-module/steps/step-10-roadmap.md
create mode 100644 .bmad/bmb/workflows/create-module/steps/step-11-validate.md
create mode 100644 .bmad/bmb/workflows/create-module/templates/agent.template.md
create mode 100644 .bmad/bmb/workflows/create-module/templates/installer.template.js
create mode 100644 .bmad/bmb/workflows/create-module/templates/module-plan.template.md
create mode 100644 .bmad/bmb/workflows/create-module/templates/module.template.yaml
create mode 100644 .bmad/bmb/workflows/create-module/templates/workflow-plan-template.md
create mode 100644 .bmad/bmb/workflows/create-module/validation.md
create mode 100644 .bmad/bmb/workflows/create-module/workflow.md
create mode 100644 .bmad/bmb/workflows/create-workflow/steps/step-01-init.md
create mode 100644 .bmad/bmb/workflows/create-workflow/steps/step-02-gather.md
create mode 100644 .bmad/bmb/workflows/create-workflow/steps/step-03-tools-configuration.md
create mode 100644 .bmad/bmb/workflows/create-workflow/steps/step-04-plan-review.md
create mode 100644 .bmad/bmb/workflows/create-workflow/steps/step-05-output-format-design.md
create mode 100644 .bmad/bmb/workflows/create-workflow/steps/step-06-design.md
create mode 100644 .bmad/bmb/workflows/create-workflow/steps/step-07-build.md
create mode 100644 .bmad/bmb/workflows/create-workflow/steps/step-08-review.md
create mode 100644 .bmad/bmb/workflows/create-workflow/steps/step-09-complete.md
create mode 100644 .bmad/bmb/workflows/create-workflow/workflow.md
create mode 100644 .bmad/bmb/workflows/edit-agent/steps/step-01-discover-intent.md
create mode 100644 .bmad/bmb/workflows/edit-agent/steps/step-02-analyze-agent.md
create mode 100644 .bmad/bmb/workflows/edit-agent/steps/step-03-propose-changes.md
create mode 100644 .bmad/bmb/workflows/edit-agent/steps/step-04-apply-changes.md
create mode 100644 .bmad/bmb/workflows/edit-agent/steps/step-05-validate.md
create mode 100644 .bmad/bmb/workflows/edit-agent/workflow.md
create mode 100644 .bmad/bmb/workflows/edit-workflow/steps/step-01-analyze.md
create mode 100644 .bmad/bmb/workflows/edit-workflow/steps/step-02-discover.md
create mode 100644 .bmad/bmb/workflows/edit-workflow/steps/step-03-improve.md
create mode 100644 .bmad/bmb/workflows/edit-workflow/steps/step-04-validate.md
create mode 100644 .bmad/bmb/workflows/edit-workflow/steps/step-05-compliance-check.md
create mode 100644 .bmad/bmb/workflows/edit-workflow/templates/completion-summary.md
create mode 100644 .bmad/bmb/workflows/edit-workflow/templates/improvement-goals.md
create mode 100644 .bmad/bmb/workflows/edit-workflow/templates/improvement-log.md
create mode 100644 .bmad/bmb/workflows/edit-workflow/templates/validation-results.md
create mode 100644 .bmad/bmb/workflows/edit-workflow/templates/workflow-analysis.md
create mode 100644 .bmad/bmb/workflows/edit-workflow/workflow.md
create mode 100644 .bmad/bmb/workflows/workflow-compliance-check/steps/step-01-validate-goal.md
create mode 100644 .bmad/bmb/workflows/workflow-compliance-check/steps/step-02-workflow-validation.md
create mode 100644 .bmad/bmb/workflows/workflow-compliance-check/steps/step-03-step-validation.md
create mode 100644 .bmad/bmb/workflows/workflow-compliance-check/steps/step-04-file-validation.md
create mode 100644 .bmad/bmb/workflows/workflow-compliance-check/steps/step-05-intent-spectrum-validation.md
create mode 100644 .bmad/bmb/workflows/workflow-compliance-check/steps/step-06-web-subprocess-validation.md
create mode 100644 .bmad/bmb/workflows/workflow-compliance-check/steps/step-07-holistic-analysis.md
create mode 100644 .bmad/bmb/workflows/workflow-compliance-check/steps/step-08-generate-report.md
create mode 100644 .bmad/bmb/workflows/workflow-compliance-check/templates/compliance-report.md
create mode 100644 .bmad/bmb/workflows/workflow-compliance-check/workflow.md
create mode 100644 .bmad/bmm/README.md
create mode 100644 .bmad/bmm/agents/analyst.md
create mode 100644 .bmad/bmm/agents/architect.md
create mode 100644 .bmad/bmm/agents/dev.md
create mode 100644 .bmad/bmm/agents/pm.md
create mode 100644 .bmad/bmm/agents/quick-flow-solo-dev.md
create mode 100644 .bmad/bmm/agents/sm.md
create mode 100644 .bmad/bmm/agents/tea.md
create mode 100644 .bmad/bmm/agents/tech-writer.md
create mode 100644 .bmad/bmm/agents/ux-designer.md
create mode 100644 .bmad/bmm/config.yaml
create mode 100644 .bmad/bmm/data/README.md
create mode 100644 .bmad/bmm/data/documentation-standards.md
create mode 100644 .bmad/bmm/data/project-context-template.md
create mode 100644 .bmad/bmm/docs/README.md
create mode 100644 .bmad/bmm/docs/agents-guide.md
create mode 100644 .bmad/bmm/docs/bmad-quick-flow.md
create mode 100644 .bmad/bmm/docs/brownfield-guide.md
create mode 100644 .bmad/bmm/docs/enterprise-agentic-development.md
create mode 100644 .bmad/bmm/docs/faq.md
create mode 100644 .bmad/bmm/docs/glossary.md
create mode 100644 .bmad/bmm/docs/images/README.md
create mode 100644 .bmad/bmm/docs/images/workflow-method-greenfield.excalidraw
create mode 100644 .bmad/bmm/docs/images/workflow-method-greenfield.svg
create mode 100644 .bmad/bmm/docs/party-mode.md
create mode 100644 .bmad/bmm/docs/quick-flow-solo-dev.md
create mode 100644 .bmad/bmm/docs/quick-spec-flow.md
create mode 100644 .bmad/bmm/docs/quick-start.md
create mode 100644 .bmad/bmm/docs/scale-adaptive-system.md
create mode 100644 .bmad/bmm/docs/test-architecture.md
create mode 100644 .bmad/bmm/docs/troubleshooting.md
create mode 100644 .bmad/bmm/docs/workflow-architecture-reference.md
create mode 100644 .bmad/bmm/docs/workflow-document-project-reference.md
create mode 100644 .bmad/bmm/docs/workflows-analysis.md
create mode 100644 .bmad/bmm/docs/workflows-implementation.md
create mode 100644 .bmad/bmm/docs/workflows-planning.md
create mode 100644 .bmad/bmm/docs/workflows-solutioning.md
create mode 100644 .bmad/bmm/tasks/daily-standup.xml
create mode 100644 .bmad/bmm/teams/default-party.csv
create mode 100644 .bmad/bmm/teams/team-fullstack.yaml
create mode 100644 .bmad/bmm/testarch/knowledge/api-request.md
create mode 100644 .bmad/bmm/testarch/knowledge/auth-session.md
create mode 100644 .bmad/bmm/testarch/knowledge/burn-in.md
create mode 100644 .bmad/bmm/testarch/knowledge/ci-burn-in.md
create mode 100644 .bmad/bmm/testarch/knowledge/component-tdd.md
create mode 100644 .bmad/bmm/testarch/knowledge/contract-testing.md
create mode 100644 .bmad/bmm/testarch/knowledge/data-factories.md
create mode 100644 .bmad/bmm/testarch/knowledge/email-auth.md
create mode 100644 .bmad/bmm/testarch/knowledge/error-handling.md
create mode 100644 .bmad/bmm/testarch/knowledge/feature-flags.md
create mode 100644 .bmad/bmm/testarch/knowledge/file-utils.md
create mode 100644 .bmad/bmm/testarch/knowledge/fixture-architecture.md
create mode 100644 .bmad/bmm/testarch/knowledge/fixtures-composition.md
create mode 100644 .bmad/bmm/testarch/knowledge/intercept-network-call.md
create mode 100644 .bmad/bmm/testarch/knowledge/log.md
create mode 100644 .bmad/bmm/testarch/knowledge/network-error-monitor.md
create mode 100644 .bmad/bmm/testarch/knowledge/network-first.md
create mode 100644 .bmad/bmm/testarch/knowledge/network-recorder.md
create mode 100644 .bmad/bmm/testarch/knowledge/nfr-criteria.md
create mode 100644 .bmad/bmm/testarch/knowledge/overview.md
create mode 100644 .bmad/bmm/testarch/knowledge/playwright-config.md
create mode 100644 .bmad/bmm/testarch/knowledge/probability-impact.md
create mode 100644 .bmad/bmm/testarch/knowledge/recurse.md
create mode 100644 .bmad/bmm/testarch/knowledge/risk-governance.md
create mode 100644 .bmad/bmm/testarch/knowledge/selective-testing.md
create mode 100644 .bmad/bmm/testarch/knowledge/selector-resilience.md
create mode 100644 .bmad/bmm/testarch/knowledge/test-healing-patterns.md
create mode 100644 .bmad/bmm/testarch/knowledge/test-levels-framework.md
create mode 100644 .bmad/bmm/testarch/knowledge/test-priorities-matrix.md
create mode 100644 .bmad/bmm/testarch/knowledge/test-quality.md
create mode 100644 .bmad/bmm/testarch/knowledge/timing-debugging.md
create mode 100644 .bmad/bmm/testarch/knowledge/visual-debugging.md
create mode 100644 .bmad/bmm/testarch/tea-index.csv
create mode 100644 .bmad/bmm/workflows/1-analysis/product-brief/product-brief.template.md
create mode 100644 .bmad/bmm/workflows/1-analysis/product-brief/steps/step-01-init.md
create mode 100644 .bmad/bmm/workflows/1-analysis/product-brief/steps/step-01b-continue.md
create mode 100644 .bmad/bmm/workflows/1-analysis/product-brief/steps/step-02-vision.md
create mode 100644 .bmad/bmm/workflows/1-analysis/product-brief/steps/step-03-users.md
create mode 100644 .bmad/bmm/workflows/1-analysis/product-brief/steps/step-04-metrics.md
create mode 100644 .bmad/bmm/workflows/1-analysis/product-brief/steps/step-05-scope.md
create mode 100644 .bmad/bmm/workflows/1-analysis/product-brief/steps/step-06-complete.md
create mode 100644 .bmad/bmm/workflows/1-analysis/product-brief/workflow.md
create mode 100644 .bmad/bmm/workflows/1-analysis/research/domain-steps/step-01-init.md
create mode 100644 .bmad/bmm/workflows/1-analysis/research/domain-steps/step-02-domain-analysis.md
create mode 100644 .bmad/bmm/workflows/1-analysis/research/domain-steps/step-03-competitive-landscape.md
create mode 100644 .bmad/bmm/workflows/1-analysis/research/domain-steps/step-04-regulatory-focus.md
create mode 100644 .bmad/bmm/workflows/1-analysis/research/domain-steps/step-05-technical-trends.md
create mode 100644 .bmad/bmm/workflows/1-analysis/research/domain-steps/step-06-research-synthesis.md
create mode 100644 .bmad/bmm/workflows/1-analysis/research/market-steps/step-01-init.md
create mode 100644 .bmad/bmm/workflows/1-analysis/research/market-steps/step-02-customer-behavior.md
create mode 100644 .bmad/bmm/workflows/1-analysis/research/market-steps/step-02-customer-insights.md
create mode 100644 .bmad/bmm/workflows/1-analysis/research/market-steps/step-03-customer-pain-points.md
create mode 100644 .bmad/bmm/workflows/1-analysis/research/market-steps/step-04-customer-decisions.md
create mode 100644 .bmad/bmm/workflows/1-analysis/research/market-steps/step-05-competitive-analysis.md
create mode 100644 .bmad/bmm/workflows/1-analysis/research/market-steps/step-06-research-completion.md
create mode 100644 .bmad/bmm/workflows/1-analysis/research/research.template.md
create mode 100644 .bmad/bmm/workflows/1-analysis/research/technical-steps/step-01-init.md
create mode 100644 .bmad/bmm/workflows/1-analysis/research/technical-steps/step-02-technical-overview.md
create mode 100644 .bmad/bmm/workflows/1-analysis/research/technical-steps/step-03-integration-patterns.md
create mode 100644 .bmad/bmm/workflows/1-analysis/research/technical-steps/step-04-architectural-patterns.md
create mode 100644 .bmad/bmm/workflows/1-analysis/research/technical-steps/step-05-implementation-research.md
create mode 100644 .bmad/bmm/workflows/1-analysis/research/technical-steps/step-06-research-synthesis.md
create mode 100644 .bmad/bmm/workflows/1-analysis/research/workflow.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01-init.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01b-continue.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-02-discovery.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-05-inspiration.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-06-design-system.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-07-defining-experience.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-08-visual-foundation.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-09-design-directions.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-10-user-journeys.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-11-component-strategy.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-12-ux-patterns.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-13-responsive-accessibility.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/create-ux-design/ux-design-template.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/prd/domain-complexity.csv
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/prd/prd-template.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/prd/project-types.csv
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/prd/steps/step-01-init.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/prd/steps/step-01b-continue.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/prd/steps/step-02-discovery.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/prd/steps/step-03-success.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/prd/steps/step-04-journeys.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/prd/steps/step-05-domain.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/prd/steps/step-09-functional.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/prd/steps/step-11-complete.md
create mode 100644 .bmad/bmm/workflows/2-plan-workflows/prd/workflow.md
create mode 100644 .bmad/bmm/workflows/3-solutioning/architecture/architecture-decision-template.md
create mode 100644 .bmad/bmm/workflows/3-solutioning/architecture/data/domain-complexity.csv
create mode 100644 .bmad/bmm/workflows/3-solutioning/architecture/data/project-types.csv
create mode 100644 .bmad/bmm/workflows/3-solutioning/architecture/steps/step-01-init.md
create mode 100644 .bmad/bmm/workflows/3-solutioning/architecture/steps/step-01b-continue.md
create mode 100644 .bmad/bmm/workflows/3-solutioning/architecture/steps/step-02-context.md
create mode 100644 .bmad/bmm/workflows/3-solutioning/architecture/steps/step-03-starter.md
create mode 100644 .bmad/bmm/workflows/3-solutioning/architecture/steps/step-04-decisions.md
create mode 100644 .bmad/bmm/workflows/3-solutioning/architecture/steps/step-05-patterns.md
create mode 100644 .bmad/bmm/workflows/3-solutioning/architecture/steps/step-06-structure.md
create mode 100644 .bmad/bmm/workflows/3-solutioning/architecture/steps/step-07-validation.md
create mode 100644 .bmad/bmm/workflows/3-solutioning/architecture/steps/step-08-complete.md
create mode 100644 .bmad/bmm/workflows/3-solutioning/architecture/workflow.md
create mode 100644 .bmad/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md
create mode 100644 .bmad/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-02-design-epics.md
create mode 100644 .bmad/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-03-create-stories.md
create mode 100644 .bmad/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md
create mode 100644 .bmad/bmm/workflows/3-solutioning/create-epics-and-stories/templates/epics-template.md
create mode 100644 .bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md
create mode 100644 .bmad/bmm/workflows/3-solutioning/implementation-readiness/steps/step-01-document-discovery.md
create mode 100644 .bmad/bmm/workflows/3-solutioning/implementation-readiness/steps/step-02-prd-analysis.md
create mode 100644 .bmad/bmm/workflows/3-solutioning/implementation-readiness/steps/step-03-epic-coverage-validation.md
create mode 100644 .bmad/bmm/workflows/3-solutioning/implementation-readiness/steps/step-04-ux-alignment.md
create mode 100644 .bmad/bmm/workflows/3-solutioning/implementation-readiness/steps/step-05-epic-quality-review.md
create mode 100644 .bmad/bmm/workflows/3-solutioning/implementation-readiness/steps/step-06-final-assessment.md
create mode 100644 .bmad/bmm/workflows/3-solutioning/implementation-readiness/templates/readiness-report-template.md
create mode 100644 .bmad/bmm/workflows/3-solutioning/implementation-readiness/workflow.md
create mode 100644 .bmad/bmm/workflows/4-implementation/code-review/checklist.md
create mode 100644 .bmad/bmm/workflows/4-implementation/code-review/instructions.xml
create mode 100644 .bmad/bmm/workflows/4-implementation/code-review/workflow.yaml
create mode 100644 .bmad/bmm/workflows/4-implementation/correct-course/checklist.md
create mode 100644 .bmad/bmm/workflows/4-implementation/correct-course/instructions.md
create mode 100644 .bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml
create mode 100644 .bmad/bmm/workflows/4-implementation/create-story/checklist.md
create mode 100644 .bmad/bmm/workflows/4-implementation/create-story/instructions.xml
create mode 100644 .bmad/bmm/workflows/4-implementation/create-story/template.md
create mode 100644 .bmad/bmm/workflows/4-implementation/create-story/workflow.yaml
create mode 100644 .bmad/bmm/workflows/4-implementation/dev-story/checklist.md
create mode 100644 .bmad/bmm/workflows/4-implementation/dev-story/instructions.xml
create mode 100644 .bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml
create mode 100644 .bmad/bmm/workflows/4-implementation/retrospective/instructions.md
create mode 100644 .bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml
create mode 100644 .bmad/bmm/workflows/4-implementation/sprint-planning/checklist.md
create mode 100644 .bmad/bmm/workflows/4-implementation/sprint-planning/instructions.md
create mode 100644 .bmad/bmm/workflows/4-implementation/sprint-planning/sprint-status-template.yaml
create mode 100644 .bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml
create mode 100644 .bmad/bmm/workflows/4-implementation/sprint-status/instructions.md
create mode 100644 .bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml
create mode 100644 .bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/instructions.md
create mode 100644 .bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml
create mode 100644 .bmad/bmm/workflows/bmad-quick-flow/quick-dev/checklist.md
create mode 100644 .bmad/bmm/workflows/bmad-quick-flow/quick-dev/instructions.md
create mode 100644 .bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml
create mode 100644 .bmad/bmm/workflows/diagrams/_shared/excalidraw-library.json
create mode 100644 .bmad/bmm/workflows/diagrams/_shared/excalidraw-templates.yaml
create mode 100644 .bmad/bmm/workflows/diagrams/create-dataflow/checklist.md
create mode 100644 .bmad/bmm/workflows/diagrams/create-dataflow/instructions.md
create mode 100644 .bmad/bmm/workflows/diagrams/create-dataflow/workflow.yaml
create mode 100644 .bmad/bmm/workflows/diagrams/create-diagram/checklist.md
create mode 100644 .bmad/bmm/workflows/diagrams/create-diagram/instructions.md
create mode 100644 .bmad/bmm/workflows/diagrams/create-diagram/workflow.yaml
create mode 100644 .bmad/bmm/workflows/diagrams/create-flowchart/checklist.md
create mode 100644 .bmad/bmm/workflows/diagrams/create-flowchart/instructions.md
create mode 100644 .bmad/bmm/workflows/diagrams/create-flowchart/workflow.yaml
create mode 100644 .bmad/bmm/workflows/diagrams/create-wireframe/checklist.md
create mode 100644 .bmad/bmm/workflows/diagrams/create-wireframe/instructions.md
create mode 100644 .bmad/bmm/workflows/diagrams/create-wireframe/workflow.yaml
create mode 100644 .bmad/bmm/workflows/document-project/checklist.md
create mode 100644 .bmad/bmm/workflows/document-project/documentation-requirements.csv
create mode 100644 .bmad/bmm/workflows/document-project/instructions.md
create mode 100644 .bmad/bmm/workflows/document-project/templates/deep-dive-template.md
create mode 100644 .bmad/bmm/workflows/document-project/templates/index-template.md
create mode 100644 .bmad/bmm/workflows/document-project/templates/project-overview-template.md
create mode 100644 .bmad/bmm/workflows/document-project/templates/project-scan-report-schema.json
create mode 100644 .bmad/bmm/workflows/document-project/templates/source-tree-template.md
create mode 100644 .bmad/bmm/workflows/document-project/workflow.yaml
create mode 100644 .bmad/bmm/workflows/document-project/workflows/deep-dive-instructions.md
create mode 100644 .bmad/bmm/workflows/document-project/workflows/deep-dive.yaml
create mode 100644 .bmad/bmm/workflows/document-project/workflows/full-scan-instructions.md
create mode 100644 .bmad/bmm/workflows/document-project/workflows/full-scan.yaml
create mode 100644 .bmad/bmm/workflows/generate-project-context/project-context-template.md
create mode 100644 .bmad/bmm/workflows/generate-project-context/steps/step-01-discover.md
create mode 100644 .bmad/bmm/workflows/generate-project-context/steps/step-02-generate.md
create mode 100644 .bmad/bmm/workflows/generate-project-context/steps/step-03-complete.md
create mode 100644 .bmad/bmm/workflows/generate-project-context/workflow.md
create mode 100644 .bmad/bmm/workflows/testarch/atdd/atdd-checklist-template.md
create mode 100644 .bmad/bmm/workflows/testarch/atdd/checklist.md
create mode 100644 .bmad/bmm/workflows/testarch/atdd/instructions.md
create mode 100644 .bmad/bmm/workflows/testarch/atdd/workflow.yaml
create mode 100644 .bmad/bmm/workflows/testarch/automate/checklist.md
create mode 100644 .bmad/bmm/workflows/testarch/automate/instructions.md
create mode 100644 .bmad/bmm/workflows/testarch/automate/workflow.yaml
create mode 100644 .bmad/bmm/workflows/testarch/ci/checklist.md
create mode 100644 .bmad/bmm/workflows/testarch/ci/github-actions-template.yaml
create mode 100644 .bmad/bmm/workflows/testarch/ci/gitlab-ci-template.yaml
create mode 100644 .bmad/bmm/workflows/testarch/ci/instructions.md
create mode 100644 .bmad/bmm/workflows/testarch/ci/workflow.yaml
create mode 100644 .bmad/bmm/workflows/testarch/framework/checklist.md
create mode 100644 .bmad/bmm/workflows/testarch/framework/instructions.md
create mode 100644 .bmad/bmm/workflows/testarch/framework/workflow.yaml
create mode 100644 .bmad/bmm/workflows/testarch/nfr-assess/checklist.md
create mode 100644 .bmad/bmm/workflows/testarch/nfr-assess/instructions.md
create mode 100644 .bmad/bmm/workflows/testarch/nfr-assess/nfr-report-template.md
create mode 100644 .bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml
create mode 100644 .bmad/bmm/workflows/testarch/test-design/checklist.md
create mode 100644 .bmad/bmm/workflows/testarch/test-design/instructions.md
create mode 100644 .bmad/bmm/workflows/testarch/test-design/test-design-template.md
create mode 100644 .bmad/bmm/workflows/testarch/test-design/workflow.yaml
create mode 100644 .bmad/bmm/workflows/testarch/test-review/checklist.md
create mode 100644 .bmad/bmm/workflows/testarch/test-review/instructions.md
create mode 100644 .bmad/bmm/workflows/testarch/test-review/test-review-template.md
create mode 100644 .bmad/bmm/workflows/testarch/test-review/workflow.yaml
create mode 100644 .bmad/bmm/workflows/testarch/trace/checklist.md
create mode 100644 .bmad/bmm/workflows/testarch/trace/instructions.md
create mode 100644 .bmad/bmm/workflows/testarch/trace/trace-template.md
create mode 100644 .bmad/bmm/workflows/testarch/trace/workflow.yaml
create mode 100644 .bmad/bmm/workflows/workflow-status/init/instructions.md
create mode 100644 .bmad/bmm/workflows/workflow-status/init/workflow.yaml
create mode 100644 .bmad/bmm/workflows/workflow-status/instructions.md
create mode 100644 .bmad/bmm/workflows/workflow-status/paths/enterprise-brownfield.yaml
create mode 100644 .bmad/bmm/workflows/workflow-status/paths/enterprise-greenfield.yaml
create mode 100644 .bmad/bmm/workflows/workflow-status/paths/method-brownfield.yaml
create mode 100644 .bmad/bmm/workflows/workflow-status/paths/method-greenfield.yaml
create mode 100644 .bmad/bmm/workflows/workflow-status/project-levels.yaml
create mode 100644 .bmad/bmm/workflows/workflow-status/workflow-status-template.yaml
create mode 100644 .bmad/bmm/workflows/workflow-status/workflow.yaml
create mode 100644 .bmad/core/agents/bmad-master.md
create mode 100644 .bmad/core/agents/bmad-web-orchestrator.agent.xml
create mode 100644 .bmad/core/config.yaml
create mode 100644 .bmad/core/module.yaml
create mode 100644 .bmad/core/resources/excalidraw/README.md
create mode 100644 .bmad/core/resources/excalidraw/excalidraw-helpers.md
create mode 100644 .bmad/core/resources/excalidraw/library-loader.md
create mode 100644 .bmad/core/resources/excalidraw/validate-json-instructions.md
create mode 100644 .bmad/core/tasks/advanced-elicitation-methods.csv
create mode 100644 .bmad/core/tasks/advanced-elicitation.xml
create mode 100644 .bmad/core/tasks/index-docs.xml
create mode 100644 .bmad/core/tasks/validate-workflow.xml
create mode 100644 .bmad/core/tasks/workflow.xml
create mode 100644 .bmad/core/tools/shard-doc.xml
create mode 100644 .bmad/core/workflows/brainstorming/brain-methods.csv
create mode 100644 .bmad/core/workflows/brainstorming/steps/step-01-session-setup.md
create mode 100644 .bmad/core/workflows/brainstorming/steps/step-01b-continue.md
create mode 100644 .bmad/core/workflows/brainstorming/steps/step-02a-user-selected.md
create mode 100644 .bmad/core/workflows/brainstorming/steps/step-02b-ai-recommended.md
create mode 100644 .bmad/core/workflows/brainstorming/steps/step-02c-random-selection.md
create mode 100644 .bmad/core/workflows/brainstorming/steps/step-02d-progressive-flow.md
create mode 100644 .bmad/core/workflows/brainstorming/steps/step-03-technique-execution.md
create mode 100644 .bmad/core/workflows/brainstorming/steps/step-04-idea-organization.md
create mode 100644 .bmad/core/workflows/brainstorming/template.md
create mode 100644 .bmad/core/workflows/brainstorming/workflow.md
create mode 100644 .bmad/core/workflows/party-mode/steps/step-01-agent-loading.md
create mode 100644 .bmad/core/workflows/party-mode/steps/step-02-discussion-orchestration.md
create mode 100644 .bmad/core/workflows/party-mode/steps/step-03-graceful-exit.md
create mode 100644 .bmad/core/workflows/party-mode/workflow.md
create mode 100644 .bmad/docs/auggie-instructions.md
create mode 100644 .bmad/docs/claude-code-instructions.md
create mode 100644 .claude/commands/bmad/bmb/agents/bmad-builder.md
create mode 100644 .claude/commands/bmad/bmb/workflows/Meal Prep & Nutrition Plan.md
create mode 100644 .claude/commands/bmad/bmb/workflows/create-agent.md
create mode 100644 .claude/commands/bmad/bmb/workflows/create-module.md
create mode 100644 .claude/commands/bmad/bmb/workflows/create-workflow.md
create mode 100644 .claude/commands/bmad/bmb/workflows/edit-agent.md
create mode 100644 .claude/commands/bmad/bmb/workflows/edit-workflow.md
create mode 100644 .claude/commands/bmad/bmb/workflows/workflow-compliance-check.md
create mode 100644 .claude/commands/bmad/bmm/agents/analyst.md
create mode 100644 .claude/commands/bmad/bmm/agents/architect.md
create mode 100644 .claude/commands/bmad/bmm/agents/dev.md
create mode 100644 .claude/commands/bmad/bmm/agents/pm.md
create mode 100644 .claude/commands/bmad/bmm/agents/quick-flow-solo-dev.md
create mode 100644 .claude/commands/bmad/bmm/agents/sm.md
create mode 100644 .claude/commands/bmad/bmm/agents/tea.md
create mode 100644 .claude/commands/bmad/bmm/agents/tech-writer.md
create mode 100644 .claude/commands/bmad/bmm/agents/ux-designer.md
create mode 100644 .claude/commands/bmad/bmm/workflows/check-implementation-readiness.md
create mode 100644 .claude/commands/bmad/bmm/workflows/code-review.md
create mode 100644 .claude/commands/bmad/bmm/workflows/correct-course.md
create mode 100644 .claude/commands/bmad/bmm/workflows/create-architecture.md
create mode 100644 .claude/commands/bmad/bmm/workflows/create-epics-stories.md
create mode 100644 .claude/commands/bmad/bmm/workflows/create-excalidraw-dataflow.md
create mode 100644 .claude/commands/bmad/bmm/workflows/create-excalidraw-diagram.md
create mode 100644 .claude/commands/bmad/bmm/workflows/create-excalidraw-flowchart.md
create mode 100644 .claude/commands/bmad/bmm/workflows/create-excalidraw-wireframe.md
create mode 100644 .claude/commands/bmad/bmm/workflows/create-prd.md
create mode 100644 .claude/commands/bmad/bmm/workflows/create-product-brief.md
create mode 100644 .claude/commands/bmad/bmm/workflows/create-story.md
create mode 100644 .claude/commands/bmad/bmm/workflows/create-tech-spec.md
create mode 100644 .claude/commands/bmad/bmm/workflows/create-ux-design.md
create mode 100644 .claude/commands/bmad/bmm/workflows/dev-story.md
create mode 100644 .claude/commands/bmad/bmm/workflows/document-project.md
create mode 100644 .claude/commands/bmad/bmm/workflows/generate-project-context.md
create mode 100644 .claude/commands/bmad/bmm/workflows/quick-dev.md
create mode 100644 .claude/commands/bmad/bmm/workflows/research.md
create mode 100644 .claude/commands/bmad/bmm/workflows/retrospective.md
create mode 100644 .claude/commands/bmad/bmm/workflows/sprint-planning.md
create mode 100644 .claude/commands/bmad/bmm/workflows/sprint-status.md
create mode 100644 .claude/commands/bmad/bmm/workflows/testarch-atdd.md
create mode 100644 .claude/commands/bmad/bmm/workflows/testarch-automate.md
create mode 100644 .claude/commands/bmad/bmm/workflows/testarch-ci.md
create mode 100644 .claude/commands/bmad/bmm/workflows/testarch-framework.md
create mode 100644 .claude/commands/bmad/bmm/workflows/testarch-nfr.md
create mode 100644 .claude/commands/bmad/bmm/workflows/testarch-test-design.md
create mode 100644 .claude/commands/bmad/bmm/workflows/testarch-test-review.md
create mode 100644 .claude/commands/bmad/bmm/workflows/testarch-trace.md
create mode 100644 .claude/commands/bmad/bmm/workflows/workflow-init.md
create mode 100644 .claude/commands/bmad/bmm/workflows/workflow-status.md
create mode 100644 .claude/commands/bmad/core/agents/bmad-master.md
create mode 100644 .claude/commands/bmad/core/tasks/advanced-elicitation.md
create mode 100644 .claude/commands/bmad/core/tasks/index-docs.md
create mode 100644 .claude/commands/bmad/core/tools/shard-doc.md
create mode 100644 .claude/commands/bmad/core/workflows/brainstorming-session.md
create mode 100644 .claude/commands/bmad/core/workflows/party-mode.md
create mode 100644 bmad-custom-src/custom.yaml
diff --git a/.augment/commands/bmad/agents/bmb-bmad-builder.md b/.augment/commands/bmad/agents/bmb-bmad-builder.md
new file mode 100644
index 0000000..427386b
--- /dev/null
+++ b/.augment/commands/bmad/agents/bmb-bmad-builder.md
@@ -0,0 +1,14 @@
+---
+name: 'bmad-builder'
+description: 'bmad-builder agent'
+---
+
+You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
+
+
+1. LOAD the FULL agent file from @.bmad/bmb/agents/bmad-builder.md
+2. READ its entire contents - this contains the complete agent persona, menu, and instructions
+3. Execute ALL activation steps exactly as written in the agent file
+4. Follow the agent's persona and menu system precisely
+5. Stay in character throughout the session
+
diff --git a/.augment/commands/bmad/agents/bmm-analyst.md b/.augment/commands/bmad/agents/bmm-analyst.md
new file mode 100644
index 0000000..c82142b
--- /dev/null
+++ b/.augment/commands/bmad/agents/bmm-analyst.md
@@ -0,0 +1,14 @@
+---
+name: 'analyst'
+description: 'analyst agent'
+---
+
+You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
+
+
+1. LOAD the FULL agent file from @.bmad/bmm/agents/analyst.md
+2. READ its entire contents - this contains the complete agent persona, menu, and instructions
+3. Execute ALL activation steps exactly as written in the agent file
+4. Follow the agent's persona and menu system precisely
+5. Stay in character throughout the session
+
diff --git a/.augment/commands/bmad/agents/bmm-architect.md b/.augment/commands/bmad/agents/bmm-architect.md
new file mode 100644
index 0000000..f74475e
--- /dev/null
+++ b/.augment/commands/bmad/agents/bmm-architect.md
@@ -0,0 +1,14 @@
+---
+name: 'architect'
+description: 'architect agent'
+---
+
+You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
+
+
+1. LOAD the FULL agent file from @.bmad/bmm/agents/architect.md
+2. READ its entire contents - this contains the complete agent persona, menu, and instructions
+3. Execute ALL activation steps exactly as written in the agent file
+4. Follow the agent's persona and menu system precisely
+5. Stay in character throughout the session
+
diff --git a/.augment/commands/bmad/agents/bmm-dev.md b/.augment/commands/bmad/agents/bmm-dev.md
new file mode 100644
index 0000000..c0d2371
--- /dev/null
+++ b/.augment/commands/bmad/agents/bmm-dev.md
@@ -0,0 +1,14 @@
+---
+name: 'dev'
+description: 'dev agent'
+---
+
+You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
+
+
+1. LOAD the FULL agent file from @.bmad/bmm/agents/dev.md
+2. READ its entire contents - this contains the complete agent persona, menu, and instructions
+3. Execute ALL activation steps exactly as written in the agent file
+4. Follow the agent's persona and menu system precisely
+5. Stay in character throughout the session
+
diff --git a/.augment/commands/bmad/agents/bmm-pm.md b/.augment/commands/bmad/agents/bmm-pm.md
new file mode 100644
index 0000000..6ca91db
--- /dev/null
+++ b/.augment/commands/bmad/agents/bmm-pm.md
@@ -0,0 +1,14 @@
+---
+name: 'pm'
+description: 'pm agent'
+---
+
+You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
+
+
+1. LOAD the FULL agent file from @.bmad/bmm/agents/pm.md
+2. READ its entire contents - this contains the complete agent persona, menu, and instructions
+3. Execute ALL activation steps exactly as written in the agent file
+4. Follow the agent's persona and menu system precisely
+5. Stay in character throughout the session
+
diff --git a/.augment/commands/bmad/agents/bmm-quick-flow-solo-dev.md b/.augment/commands/bmad/agents/bmm-quick-flow-solo-dev.md
new file mode 100644
index 0000000..1da69c0
--- /dev/null
+++ b/.augment/commands/bmad/agents/bmm-quick-flow-solo-dev.md
@@ -0,0 +1,14 @@
+---
+name: 'quick-flow-solo-dev'
+description: 'quick-flow-solo-dev agent'
+---
+
+You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
+
+
+1. LOAD the FULL agent file from @.bmad/bmm/agents/quick-flow-solo-dev.md
+2. READ its entire contents - this contains the complete agent persona, menu, and instructions
+3. Execute ALL activation steps exactly as written in the agent file
+4. Follow the agent's persona and menu system precisely
+5. Stay in character throughout the session
+
diff --git a/.augment/commands/bmad/agents/bmm-sm.md b/.augment/commands/bmad/agents/bmm-sm.md
new file mode 100644
index 0000000..56d0ea8
--- /dev/null
+++ b/.augment/commands/bmad/agents/bmm-sm.md
@@ -0,0 +1,14 @@
+---
+name: 'sm'
+description: 'sm agent'
+---
+
+You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
+
+
+1. LOAD the FULL agent file from @.bmad/bmm/agents/sm.md
+2. READ its entire contents - this contains the complete agent persona, menu, and instructions
+3. Execute ALL activation steps exactly as written in the agent file
+4. Follow the agent's persona and menu system precisely
+5. Stay in character throughout the session
+
diff --git a/.augment/commands/bmad/agents/bmm-tea.md b/.augment/commands/bmad/agents/bmm-tea.md
new file mode 100644
index 0000000..e747f30
--- /dev/null
+++ b/.augment/commands/bmad/agents/bmm-tea.md
@@ -0,0 +1,14 @@
+---
+name: 'tea'
+description: 'tea agent'
+---
+
+You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
+
+
+1. LOAD the FULL agent file from @.bmad/bmm/agents/tea.md
+2. READ its entire contents - this contains the complete agent persona, menu, and instructions
+3. Execute ALL activation steps exactly as written in the agent file
+4. Follow the agent's persona and menu system precisely
+5. Stay in character throughout the session
+
diff --git a/.augment/commands/bmad/agents/bmm-tech-writer.md b/.augment/commands/bmad/agents/bmm-tech-writer.md
new file mode 100644
index 0000000..d0e0e7b
--- /dev/null
+++ b/.augment/commands/bmad/agents/bmm-tech-writer.md
@@ -0,0 +1,14 @@
+---
+name: 'tech-writer'
+description: 'tech-writer agent'
+---
+
+You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
+
+
+1. LOAD the FULL agent file from @.bmad/bmm/agents/tech-writer.md
+2. READ its entire contents - this contains the complete agent persona, menu, and instructions
+3. Execute ALL activation steps exactly as written in the agent file
+4. Follow the agent's persona and menu system precisely
+5. Stay in character throughout the session
+
diff --git a/.augment/commands/bmad/agents/bmm-ux-designer.md b/.augment/commands/bmad/agents/bmm-ux-designer.md
new file mode 100644
index 0000000..3454e90
--- /dev/null
+++ b/.augment/commands/bmad/agents/bmm-ux-designer.md
@@ -0,0 +1,14 @@
+---
+name: 'ux-designer'
+description: 'ux-designer agent'
+---
+
+You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
+
+
+1. LOAD the FULL agent file from @.bmad/bmm/agents/ux-designer.md
+2. READ its entire contents - this contains the complete agent persona, menu, and instructions
+3. Execute ALL activation steps exactly as written in the agent file
+4. Follow the agent's persona and menu system precisely
+5. Stay in character throughout the session
+
diff --git a/.augment/commands/bmad/agents/core-bmad-master.md b/.augment/commands/bmad/agents/core-bmad-master.md
new file mode 100644
index 0000000..2ce492a
--- /dev/null
+++ b/.augment/commands/bmad/agents/core-bmad-master.md
@@ -0,0 +1,14 @@
+---
+name: 'bmad-master'
+description: 'bmad-master agent'
+---
+
+You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
+
+
+1. LOAD the FULL agent file from @.bmad/core/agents/bmad-master.md
+2. READ its entire contents - this contains the complete agent persona, menu, and instructions
+3. Execute ALL activation steps exactly as written in the agent file
+4. Follow the agent's persona and menu system precisely
+5. Stay in character throughout the session
+
diff --git a/.augment/commands/bmad/tasks/core-advanced-elicitation.md b/.augment/commands/bmad/tasks/core-advanced-elicitation.md
new file mode 100644
index 0000000..c5e0d54
--- /dev/null
+++ b/.augment/commands/bmad/tasks/core-advanced-elicitation.md
@@ -0,0 +1,125 @@
+---
+description: "Execute the Advanced Elicitation task"
+---
+
+# Advanced Elicitation Task
+
+
+
+ MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER
+ DO NOT skip steps or change the sequence
+ HALT immediately when halt-conditions are met
+ Each action xml tag within step xml tag is a REQUIRED action to complete that step
+ Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution
+
+
+
+ When called during template workflow processing:
+ 1. Receive or review the current section content that was just generated or
+ 2. Apply elicitation methods iteratively to enhance that specific content
+ 3. Return the enhanced version back when user selects 'x' to proceed and return back
+ 4. The enhanced content replaces the original section content in the output document
+
+
+
+
+ Load and read {{methods}} and {{agent-party}}
+
+
+ category: Method grouping (core, structural, risk, etc.)
+ method_name: Display name for the method
+ description: Rich explanation of what the method does, when to use it, and why it's valuable
+ output_pattern: Flexible flow guide using → arrows (e.g., "analysis → insights → action")
+
+
+
+ Use conversation history
+ Analyze: content type, complexity, stakeholder needs, risk level, and creative potential
+
+
+
+ 1. Analyze context: Content type, complexity, stakeholder needs, risk level, creative potential
+ 2. Parse descriptions: Understand each method's purpose from the rich descriptions in CSV
+ 3. Select 5 methods: Choose methods that best match the context based on their descriptions
+ 4. Balance approach: Include mix of foundational and specialized techniques as appropriate
+
+
+
+
+
+
+ **Advanced Elicitation Options (If you launched Party Mode, they will participate randomly)**
+ Choose a number (1-5), [r] to Reshuffle, [a] List All, or [x] to Proceed:
+
+ 1. [Method Name]
+ 2. [Method Name]
+ 3. [Method Name]
+ 4. [Method Name]
+ 5. [Method Name]
+ r. Reshuffle the list with 5 new options
+ a. List all methods with descriptions
+ x. Proceed / No Further Actions
+
+
+
+
+ Execute the selected method using its description from the CSV
+ Adapt the method's complexity and output format based on the current context
+ Apply the method creatively to the current section content being enhanced
+ Display the enhanced version showing what the method revealed or improved
+ CRITICAL: Ask the user if they would like to apply the changes to the doc (y/n/other) and HALT to await response.
+ CRITICAL: ONLY if Yes, apply the changes. IF No, discard your memory of the proposed changes. If any other reply, try best to
+ follow the instructions given by the user.
+ CRITICAL: Re-present the same 1-5,r,x prompt to allow additional elicitations
+
+
+ Select 5 random methods from advanced-elicitation-methods.csv, present new list with same prompt format
+ When selecting, try to think and pick a diverse set of methods covering different categories and approaches, with 1 and 2 being
+ potentially the most useful for the document or section being discovered
+
+
+ Complete elicitation and proceed
+ Return the fully enhanced content back to create-doc.md
+ The enhanced content becomes the final version for that section
+ Signal completion back to create-doc.md to continue with next section
+
+
+ List all methods with their descriptions from the CSV in a compact table
+ Allow user to select any method by name or number from the full list
+ After selection, execute the method as described in the n="1-5" case above
+
+
+ Apply changes to current section content and re-present choices
+
+
+ Execute methods in sequence on the content, then re-offer choices
+
+
+
+
+
+ Method execution: Use the description from CSV to understand and apply each method
+ Output pattern: Use the pattern as a flexible guide (e.g., "paths → evaluation → selection")
+ Dynamic adaptation: Adjust complexity based on content needs (simple to sophisticated)
+ Creative application: Interpret methods flexibly based on context while maintaining pattern consistency
+ Focus on actionable insights
+ Stay relevant: Tie elicitation to specific content being analyzed (the current section from the document being created unless user
+ indicates otherwise)
+ Identify personas: For single or multi-persona methods, clearly identify viewpoints, and use party members if available in memory
+ already
+ Critical loop behavior: Always re-offer the 1-5,r,a,x choices after each method execution
+ Continue until user selects 'x' to proceed with enhanced content, confirm or ask the user what should be accepted from the session
+ Each method application builds upon previous enhancements
+ Content preservation: Track all enhancements made during elicitation
+ Iterative enhancement: Each selected method (1-5) should:
+ 1. Apply to the current enhanced version of the content
+ 2. Show the improvements made
+ 3. Return to the prompt for additional elicitations or completion
+
+
+
+
+## Module
+BMAD CORE module
diff --git a/.augment/commands/bmad/tasks/core-index-docs.md b/.augment/commands/bmad/tasks/core-index-docs.md
new file mode 100644
index 0000000..fcff9bf
--- /dev/null
+++ b/.augment/commands/bmad/tasks/core-index-docs.md
@@ -0,0 +1,74 @@
+---
+description: "Execute the Index Docs task"
+---
+
+# Index Docs Task
+
+
+
+ MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER
+ DO NOT skip steps or change the sequence
+ HALT immediately when halt-conditions are met
+ Each action xml tag within step xml tag is a REQUIRED action to complete that step
+ Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution
+
+
+
+
+ List all files and subdirectories in the target location
+
+
+
+ Organize files by type, purpose, or subdirectory
+
+
+
+ Read each file to understand its actual purpose and create brief (3-10 word) descriptions based on the content, not just the
+ filename
+
+
+
+ Write or update index.md with organized file listings
+
+
+
+
+
+ # Directory Index
+
+ ## Files
+
+ - **[filename.ext](./filename.ext)** - Brief description
+ - **[another-file.ext](./another-file.ext)** - Brief description
+
+ ## Subdirectories
+
+ ### subfolder/
+
+ - **[file1.ext](./subfolder/file1.ext)** - Brief description
+ - **[file2.ext](./subfolder/file2.ext)** - Brief description
+
+ ### another-folder/
+
+ - **[file3.ext](./another-folder/file3.ext)** - Brief description
+
+
+
+
+ HALT if target directory does not exist or is inaccessible
+ HALT if user does not have write permissions to create index.md
+
+
+
+ Use relative paths starting with ./
+ Group similar files together
+ Read file contents to generate accurate descriptions - don't guess from filenames
+ Keep descriptions concise but informative (3-10 words)
+ Sort alphabetically within groups
+ Skip hidden files (starting with .) unless specified
+
+
+
+## Module
+BMAD CORE module
diff --git a/.augment/commands/bmad/tools/core-shard-doc.md b/.augment/commands/bmad/tools/core-shard-doc.md
new file mode 100644
index 0000000..e7e276c
--- /dev/null
+++ b/.augment/commands/bmad/tools/core-shard-doc.md
@@ -0,0 +1,119 @@
+---
+description: "Use the Shard Document tool"
+---
+
+# Shard Document Tool
+
+
+ Split large markdown documents into smaller, organized files based on level 2 sections using @kayvan/markdown-tree-parser tool
+
+
+ MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER
+ DO NOT skip steps or change the sequence
+ HALT immediately when halt-conditions are met
+ Each action xml tag within step xml tag is a REQUIRED action to complete that step
+ Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution
+
+
+
+ Uses `npx @kayvan/markdown-tree-parser` to automatically shard documents by level 2 headings and generate an index
+
+
+
+
+ Ask user for the source document path if not provided already
+ Verify file exists and is accessible
+ Verify file is markdown format (.md extension)
+ HALT with error message
+
+
+
+ Determine default destination: same location as source file, folder named after source file without .md extension
+ Example: /path/to/architecture.md → /path/to/architecture/
+ Ask user for the destination folder path ([y] to confirm use of default: [suggested-path], else enter a new path)
+ Use the suggested destination path
+ Use the custom destination path
+ Verify destination folder exists or can be created
+ Check write permissions for destination
+ HALT with error message
+
+
+
+ Inform user that sharding is beginning
+ Execute command: `npx @kayvan/markdown-tree-parser explode [source-document] [destination-folder]`
+ Capture command output and any errors
+ HALT and display error to user
+
+
+
+ Check that destination folder contains sharded files
+ Verify index.md was created in destination folder
+ Count the number of files created
+ HALT with error message
+
+
+
+ Display completion report to user including:
+ - Source document path and name
+ - Destination folder path
+ - Number of section files created
+ - Confirmation that index.md was created
+ - Any tool output or warnings
+ Inform user that sharding completed successfully
+
+
+
+ Keeping both the original and sharded versions defeats the purpose of sharding and can cause confusion
+ Present user with options for the original document:
+
+ What would you like to do with the original document `[source-document-name]`?
+
+Options:
+[d] Delete - Remove the original (recommended - shards can always be recombined)
+[m] Move to archive - Move original to a backup/archive location
+[k] Keep - Leave original in place (NOT recommended - defeats sharding purpose)
+
+Your choice (d/m/k):
+
+
+ Delete the original source document file
+ Confirm deletion to user: "✓ Original document deleted: [source-document-path]"
+ The document can be reconstructed from shards by concatenating all section files in order
+
+
+
+ Determine default archive location: same directory as source, in an "archive" subfolder
+ Example: /path/to/architecture.md → /path/to/archive/architecture.md
+ Archive location ([y] to use default: [default-archive-path], or provide custom path):
+ Use default archive path
+ Use custom archive path
+ Create archive directory if it doesn't exist
+ Move original document to archive location
+ Confirm move to user: "✓ Original document moved to: [archive-path]"
+
+
+
+ Display warning to user:
+
+ Confirm user choice: "Original document kept at: [source-document-path]"
+
+
+
+
+
+ HALT if npx command fails or produces no output files
+
+
+
+
+## Module
+BMAD CORE module
diff --git a/.augment/commands/bmad/workflows/bmb-Meal Prep & Nutrition Plan.md b/.augment/commands/bmad/workflows/bmb-Meal Prep & Nutrition Plan.md
new file mode 100644
index 0000000..4f4cbbd
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmb-Meal Prep & Nutrition Plan.md
@@ -0,0 +1,5 @@
+---
+description: 'Creates personalized meal plans through collaborative nutrition planning between an expert facilitator and individual seeking to improve their nutrition habits.'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/workflow.md, READ its entire contents and follow its directions exactly!
diff --git a/.augment/commands/bmad/workflows/bmb-create-agent.md b/.augment/commands/bmad/workflows/bmb-create-agent.md
new file mode 100644
index 0000000..250473c
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmb-create-agent.md
@@ -0,0 +1,5 @@
+---
+description: 'Interactive workflow to build BMAD Core compliant agents with optional brainstorming, persona development, and command structure'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/bmb/workflows/create-agent/workflow.md, READ its entire contents and follow its directions exactly!
diff --git a/.augment/commands/bmad/workflows/bmb-create-module.md b/.augment/commands/bmad/workflows/bmb-create-module.md
new file mode 100644
index 0000000..90cb0d5
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmb-create-module.md
@@ -0,0 +1,5 @@
+---
+description: 'Interactive workflow to build complete BMAD modules with agents, workflows, and installation infrastructure'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/bmb/workflows/create-module/workflow.md, READ its entire contents and follow its directions exactly!
diff --git a/.augment/commands/bmad/workflows/bmb-create-workflow.md b/.augment/commands/bmad/workflows/bmb-create-workflow.md
new file mode 100644
index 0000000..b86ff95
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmb-create-workflow.md
@@ -0,0 +1,5 @@
+---
+description: 'Create structured standalone workflows using markdown-based step architecture'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/bmb/workflows/create-workflow/workflow.md, READ its entire contents and follow its directions exactly!
diff --git a/.augment/commands/bmad/workflows/bmb-edit-agent.md b/.augment/commands/bmad/workflows/bmb-edit-agent.md
new file mode 100644
index 0000000..cf60a82
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmb-edit-agent.md
@@ -0,0 +1,5 @@
+---
+description: 'Edit existing BMAD agents while following all best practices and conventions'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/bmb/workflows/edit-agent/workflow.md, READ its entire contents and follow its directions exactly!
diff --git a/.augment/commands/bmad/workflows/bmb-edit-workflow.md b/.augment/commands/bmad/workflows/bmb-edit-workflow.md
new file mode 100644
index 0000000..2867f51
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmb-edit-workflow.md
@@ -0,0 +1,5 @@
+---
+description: 'Intelligent workflow editor that helps modify existing workflows while following best practices'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/bmb/workflows/edit-workflow/workflow.md, READ its entire contents and follow its directions exactly!
diff --git a/.augment/commands/bmad/workflows/bmb-workflow-compliance-check.md b/.augment/commands/bmad/workflows/bmb-workflow-compliance-check.md
new file mode 100644
index 0000000..61dedd0
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmb-workflow-compliance-check.md
@@ -0,0 +1,5 @@
+---
+description: 'Systematic validation of workflows against BMAD standards with adversarial analysis and detailed reporting'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/bmb/workflows/workflow-compliance-check/workflow.md, READ its entire contents and follow its directions exactly!
diff --git a/.augment/commands/bmad/workflows/bmm-check-implementation-readiness.md b/.augment/commands/bmad/workflows/bmm-check-implementation-readiness.md
new file mode 100644
index 0000000..0e7c7ec
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-check-implementation-readiness.md
@@ -0,0 +1,5 @@
+---
+description: 'Critical validation workflow that assesses PRD, Architecture, and Epics & Stories for completeness and alignment before implementation. Uses adversarial review approach to find gaps and issues.'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/bmm/workflows/3-solutioning/implementation-readiness/workflow.md, READ its entire contents and follow its directions exactly!
diff --git a/.augment/commands/bmad/workflows/bmm-code-review.md b/.augment/commands/bmad/workflows/bmm-code-review.md
new file mode 100644
index 0000000..5f053ac
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-code-review.md
@@ -0,0 +1,13 @@
+---
+description: 'Perform an ADVERSARIAL Senior Developer code review that finds 3-10 specific problems in every story. Challenges everything: code quality, test coverage, architecture compliance, security, performance. NEVER accepts `looks good` - must find minimum issues and can auto-fix with user approval.'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/4-implementation/code-review/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/4-implementation/code-review/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+
diff --git a/.augment/commands/bmad/workflows/bmm-correct-course.md b/.augment/commands/bmad/workflows/bmm-correct-course.md
new file mode 100644
index 0000000..60f5a2f
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-correct-course.md
@@ -0,0 +1,13 @@
+---
+description: 'Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+
diff --git a/.augment/commands/bmad/workflows/bmm-create-architecture.md b/.augment/commands/bmad/workflows/bmm-create-architecture.md
new file mode 100644
index 0000000..e2d3cab
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-create-architecture.md
@@ -0,0 +1,5 @@
+---
+description: 'Collaborative architectural decision facilitation for AI-agent consistency. Replaces template-driven architecture with intelligent, adaptive conversation that produces a decision-focused architecture document optimized for preventing agent conflicts.'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/bmm/workflows/3-solutioning/architecture/workflow.md, READ its entire contents and follow its directions exactly!
diff --git a/.augment/commands/bmad/workflows/bmm-create-epics-stories.md b/.augment/commands/bmad/workflows/bmm-create-epics-stories.md
new file mode 100644
index 0000000..b27f9cc
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-create-epics-stories.md
@@ -0,0 +1,5 @@
+---
+description: 'Transform PRD requirements and Architecture decisions into comprehensive stories organized by user value. This workflow requires completed PRD + Architecture documents (UX recommended if UI exists) and breaks down requirements into implementation-ready epics and user stories that incorporate all available technical and design context. Creates detailed, actionable stories with complete acceptance criteria for development teams.'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md, READ its entire contents and follow its directions exactly!
diff --git a/.augment/commands/bmad/workflows/bmm-create-excalidraw-dataflow.md b/.augment/commands/bmad/workflows/bmm-create-excalidraw-dataflow.md
new file mode 100644
index 0000000..3ec7b12
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-create-excalidraw-dataflow.md
@@ -0,0 +1,13 @@
+---
+description: 'Create data flow diagrams (DFD) in Excalidraw format'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/diagrams/create-dataflow/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/diagrams/create-dataflow/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+
diff --git a/.augment/commands/bmad/workflows/bmm-create-excalidraw-diagram.md b/.augment/commands/bmad/workflows/bmm-create-excalidraw-diagram.md
new file mode 100644
index 0000000..f359318
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-create-excalidraw-diagram.md
@@ -0,0 +1,13 @@
+---
+description: 'Create system architecture diagrams, ERDs, UML diagrams, or general technical diagrams in Excalidraw format'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/diagrams/create-diagram/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/diagrams/create-diagram/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+
diff --git a/.augment/commands/bmad/workflows/bmm-create-excalidraw-flowchart.md b/.augment/commands/bmad/workflows/bmm-create-excalidraw-flowchart.md
new file mode 100644
index 0000000..60f507a
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-create-excalidraw-flowchart.md
@@ -0,0 +1,13 @@
+---
+description: 'Create a flowchart visualization in Excalidraw format for processes, pipelines, or logic flows'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/diagrams/create-flowchart/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/diagrams/create-flowchart/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+
diff --git a/.augment/commands/bmad/workflows/bmm-create-excalidraw-wireframe.md b/.augment/commands/bmad/workflows/bmm-create-excalidraw-wireframe.md
new file mode 100644
index 0000000..5df40a7
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-create-excalidraw-wireframe.md
@@ -0,0 +1,13 @@
+---
+description: 'Create website or app wireframes in Excalidraw format'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/diagrams/create-wireframe/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/diagrams/create-wireframe/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+
diff --git a/.augment/commands/bmad/workflows/bmm-create-prd.md b/.augment/commands/bmad/workflows/bmm-create-prd.md
new file mode 100644
index 0000000..993b742
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-create-prd.md
@@ -0,0 +1,5 @@
+---
+description: 'Creates a comprehensive PRDs through collaborative step-by-step discovery between two product managers working as peers.'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/bmm/workflows/2-plan-workflows/prd/workflow.md, READ its entire contents and follow its directions exactly!
diff --git a/.augment/commands/bmad/workflows/bmm-create-product-brief.md b/.augment/commands/bmad/workflows/bmm-create-product-brief.md
new file mode 100644
index 0000000..fb93144
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-create-product-brief.md
@@ -0,0 +1,5 @@
+---
+description: 'Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/bmm/workflows/1-analysis/product-brief/workflow.md, READ its entire contents and follow its directions exactly!
diff --git a/.augment/commands/bmad/workflows/bmm-create-story.md b/.augment/commands/bmad/workflows/bmm-create-story.md
new file mode 100644
index 0000000..76495aa
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-create-story.md
@@ -0,0 +1,13 @@
+---
+description: 'Create the next user story from epics+stories with enhanced context analysis and direct ready-for-dev marking'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/4-implementation/create-story/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/4-implementation/create-story/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+
diff --git a/.augment/commands/bmad/workflows/bmm-create-tech-spec.md b/.augment/commands/bmad/workflows/bmm-create-tech-spec.md
new file mode 100644
index 0000000..cfb28be
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-create-tech-spec.md
@@ -0,0 +1,13 @@
+---
+description: 'Conversational spec engineering - ask questions, investigate code, produce implementation-ready tech-spec.'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+
diff --git a/.augment/commands/bmad/workflows/bmm-create-ux-design.md b/.augment/commands/bmad/workflows/bmm-create-ux-design.md
new file mode 100644
index 0000000..ceba853
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-create-ux-design.md
@@ -0,0 +1,5 @@
+---
+description: 'Work with a peer UX Design expert to plan your applications UX patterns, look and feel.'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md, READ its entire contents and follow its directions exactly!
diff --git a/.augment/commands/bmad/workflows/bmm-dev-story.md b/.augment/commands/bmad/workflows/bmm-dev-story.md
new file mode 100644
index 0000000..d81c2c4
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-dev-story.md
@@ -0,0 +1,13 @@
+---
+description: 'Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+
diff --git a/.augment/commands/bmad/workflows/bmm-document-project.md b/.augment/commands/bmad/workflows/bmm-document-project.md
new file mode 100644
index 0000000..8639199
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-document-project.md
@@ -0,0 +1,13 @@
+---
+description: 'Analyzes and documents brownfield projects by scanning codebase, architecture, and patterns to create comprehensive reference documentation for AI-assisted development'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/document-project/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/document-project/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+
diff --git a/.augment/commands/bmad/workflows/bmm-generate-project-context.md b/.augment/commands/bmad/workflows/bmm-generate-project-context.md
new file mode 100644
index 0000000..349ab8d
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-generate-project-context.md
@@ -0,0 +1,5 @@
+---
+description: 'Creates a concise project_context.md file with critical rules and patterns that AI agents must follow when implementing code. Optimized for LLM context efficiency.'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/bmm/workflows/generate-project-context/workflow.md, READ its entire contents and follow its directions exactly!
diff --git a/.augment/commands/bmad/workflows/bmm-quick-dev.md b/.augment/commands/bmad/workflows/bmm-quick-dev.md
new file mode 100644
index 0000000..792b6ff
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-quick-dev.md
@@ -0,0 +1,13 @@
+---
+description: 'Flexible development - execute tech-specs OR direct instructions with optional planning.'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+
diff --git a/.augment/commands/bmad/workflows/bmm-research.md b/.augment/commands/bmad/workflows/bmm-research.md
new file mode 100644
index 0000000..6e9ba2f
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-research.md
@@ -0,0 +1,5 @@
+---
+description: 'Conduct comprehensive research across multiple domains using current web data and verified sources - Market, Technical, Domain and other research types.'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/bmm/workflows/1-analysis/research/workflow.md, READ its entire contents and follow its directions exactly!
diff --git a/.augment/commands/bmad/workflows/bmm-retrospective.md b/.augment/commands/bmad/workflows/bmm-retrospective.md
new file mode 100644
index 0000000..b86df3a
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-retrospective.md
@@ -0,0 +1,13 @@
+---
+description: 'Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+
diff --git a/.augment/commands/bmad/workflows/bmm-sprint-planning.md b/.augment/commands/bmad/workflows/bmm-sprint-planning.md
new file mode 100644
index 0000000..ac1d203
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-sprint-planning.md
@@ -0,0 +1,13 @@
+---
+description: 'Generate and manage the sprint status tracking file for Phase 4 implementation, extracting all epics and stories from epic files and tracking their status through the development lifecycle'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+
diff --git a/.augment/commands/bmad/workflows/bmm-sprint-status.md b/.augment/commands/bmad/workflows/bmm-sprint-status.md
new file mode 100644
index 0000000..e157497
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-sprint-status.md
@@ -0,0 +1,13 @@
+---
+description: 'Summarize sprint-status.yaml, surface risks, and route to the right implementation workflow.'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+
diff --git a/.augment/commands/bmad/workflows/bmm-testarch-atdd.md b/.augment/commands/bmad/workflows/bmm-testarch-atdd.md
new file mode 100644
index 0000000..50959c1
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-testarch-atdd.md
@@ -0,0 +1,13 @@
+---
+description: 'Generate failing acceptance tests before implementation using TDD red-green-refactor cycle'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/testarch/atdd/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/testarch/atdd/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+
diff --git a/.augment/commands/bmad/workflows/bmm-testarch-automate.md b/.augment/commands/bmad/workflows/bmm-testarch-automate.md
new file mode 100644
index 0000000..42d2ace
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-testarch-automate.md
@@ -0,0 +1,13 @@
+---
+description: 'Expand test automation coverage after implementation or analyze existing codebase to generate comprehensive test suite'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/testarch/automate/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/testarch/automate/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+
diff --git a/.augment/commands/bmad/workflows/bmm-testarch-ci.md b/.augment/commands/bmad/workflows/bmm-testarch-ci.md
new file mode 100644
index 0000000..e923897
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-testarch-ci.md
@@ -0,0 +1,13 @@
+---
+description: 'Scaffold CI/CD quality pipeline with test execution, burn-in loops, and artifact collection'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/testarch/ci/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/testarch/ci/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+
diff --git a/.augment/commands/bmad/workflows/bmm-testarch-framework.md b/.augment/commands/bmad/workflows/bmm-testarch-framework.md
new file mode 100644
index 0000000..09a81b5
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-testarch-framework.md
@@ -0,0 +1,13 @@
+---
+description: 'Initialize production-ready test framework architecture (Playwright or Cypress) with fixtures, helpers, and configuration'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/testarch/framework/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/testarch/framework/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+
diff --git a/.augment/commands/bmad/workflows/bmm-testarch-nfr.md b/.augment/commands/bmad/workflows/bmm-testarch-nfr.md
new file mode 100644
index 0000000..c080ad9
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-testarch-nfr.md
@@ -0,0 +1,13 @@
+---
+description: 'Assess non-functional requirements (performance, security, reliability, maintainability) before release with evidence-based validation'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+
diff --git a/.augment/commands/bmad/workflows/bmm-testarch-test-design.md b/.augment/commands/bmad/workflows/bmm-testarch-test-design.md
new file mode 100644
index 0000000..763911f
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-testarch-test-design.md
@@ -0,0 +1,13 @@
+---
+description: 'Dual-mode workflow: (1) System-level testability review in Solutioning phase, or (2) Epic-level test planning in Implementation phase. Auto-detects mode based on project phase.'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/testarch/test-design/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/testarch/test-design/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+
diff --git a/.augment/commands/bmad/workflows/bmm-testarch-test-review.md b/.augment/commands/bmad/workflows/bmm-testarch-test-review.md
new file mode 100644
index 0000000..646f46e
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-testarch-test-review.md
@@ -0,0 +1,13 @@
+---
+description: 'Review test quality using comprehensive knowledge base and best practices validation'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/testarch/test-review/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/testarch/test-review/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+
diff --git a/.augment/commands/bmad/workflows/bmm-testarch-trace.md b/.augment/commands/bmad/workflows/bmm-testarch-trace.md
new file mode 100644
index 0000000..9d6e076
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-testarch-trace.md
@@ -0,0 +1,13 @@
+---
+description: 'Generate requirements-to-tests traceability matrix, analyze coverage, and make quality gate decision (PASS/CONCERNS/FAIL/WAIVED)'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/testarch/trace/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/testarch/trace/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+
diff --git a/.augment/commands/bmad/workflows/bmm-workflow-init.md b/.augment/commands/bmad/workflows/bmm-workflow-init.md
new file mode 100644
index 0000000..cba8e3a
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-workflow-init.md
@@ -0,0 +1,13 @@
+---
+description: 'Initialize a new BMM project by determining level, type, and creating workflow path'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/workflow-status/init/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/workflow-status/init/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+
diff --git a/.augment/commands/bmad/workflows/bmm-workflow-status.md b/.augment/commands/bmad/workflows/bmm-workflow-status.md
new file mode 100644
index 0000000..b5d35af
--- /dev/null
+++ b/.augment/commands/bmad/workflows/bmm-workflow-status.md
@@ -0,0 +1,13 @@
+---
+description: 'Lightweight status checker - answers "what should I do now?" for any agent. Reads YAML status file for workflow tracking. Use workflow-init for new projects.'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+
+1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/workflow-status/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/workflow-status/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+
diff --git a/.augment/commands/bmad/workflows/core-brainstorming-session.md b/.augment/commands/bmad/workflows/core-brainstorming-session.md
new file mode 100644
index 0000000..4ff323c
--- /dev/null
+++ b/.augment/commands/bmad/workflows/core-brainstorming-session.md
@@ -0,0 +1,5 @@
+---
+description: 'Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/core/workflows/brainstorming/workflow.md, READ its entire contents and follow its directions exactly!
diff --git a/.augment/commands/bmad/workflows/core-party-mode.md b/.augment/commands/bmad/workflows/core-party-mode.md
new file mode 100644
index 0000000..8af2a44
--- /dev/null
+++ b/.augment/commands/bmad/workflows/core-party-mode.md
@@ -0,0 +1,5 @@
+---
+description: 'Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/core/workflows/party-mode/workflow.md, READ its entire contents and follow its directions exactly!
diff --git a/.bmad/_cfg/agent-manifest.csv b/.bmad/_cfg/agent-manifest.csv
new file mode 100644
index 0000000..61b7183
--- /dev/null
+++ b/.bmad/_cfg/agent-manifest.csv
@@ -0,0 +1,12 @@
+name,displayName,title,icon,role,identity,communicationStyle,principles,module,path
+"bmad-master","BMad Master","BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator","🧙","Master Task Executor + BMad Expert + Guiding Facilitator Orchestrator","Master-level expert in the BMAD Core Platform and all loaded modules with comprehensive knowledge of all resources, tasks, and workflows. Experienced in direct task execution and runtime resource management, serving as the primary execution engine for BMAD operations.","Direct and comprehensive, refers to himself in the 3rd person. Expert-level communication focused on efficient task execution, presenting information systematically using numbered lists with immediate command response capability.","Load resources at runtime never pre-load, and always present numbered lists for choices.","core",".bmad/core/agents/bmad-master.md"
+"bmad-builder","BMad Builder","BMad Builder","🧙","Generalist Builder and BMAD System Maintainer","A hands-on builder who gets things done efficiently and maintains the entire BMAD ecosystem","Direct, action-oriented, and encouraging with a can-do attitude","Execute resources directly without hesitation Load resources at runtime never pre-load Always present numbered lists for clear choices Focus on practical implementation and results Maintain system-wide coherence and standards Balance speed with quality and compliance","bmb",".bmad/bmb/agents/bmad-builder.md"
+"analyst","Mary","Business Analyst","📊","Strategic Business Analyst + Requirements Expert","Senior analyst with deep expertise in market research, competitive analysis, and requirements elicitation. Specializes in translating vague needs into actionable specs.","Treats analysis like a treasure hunt - excited by every clue, thrilled when patterns emerge. Asks questions that spark 'aha!' moments while structuring insights with precision.","- Every business challenge has root causes waiting to be discovered. Ground findings in verifiable evidence. - Articulate requirements with absolute precision. Ensure all stakeholder voices heard. - Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`","bmm",".bmad/bmm/agents/analyst.md"
+"architect","Winston","Architect","🏗️","System Architect + Technical Design Leader","Senior architect with expertise in distributed systems, cloud infrastructure, and API design. Specializes in scalable patterns and technology selection.","Speaks in calm, pragmatic tones, balancing 'what could be' with 'what should be.' Champions boring technology that actually works.","- User journeys drive technical decisions. Embrace boring technology for stability. - Design simple solutions that scale when needed. Developer productivity is architecture. Connect every decision to business value and user impact. - Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`","bmm",".bmad/bmm/agents/architect.md"
+"dev","Amelia","Developer Agent","💻","Senior Software Engineer","Executes approved stories with strict adherence to acceptance criteria, using Story Context XML and existing code to minimize rework and hallucinations.","Ultra-succinct. Speaks in file paths and AC IDs - every statement citable. No fluff, all precision.","- The Story File is the single source of truth - tasks/subtasks sequence is authoritative over any model priors - Follow red-green-refactor cycle: write failing test, make it pass, improve code while keeping tests green - Never implement anything not mapped to a specific task/subtask in the story file - All existing tests must pass 100% before story is ready for review - Every task/subtask must be covered by comprehensive unit tests before marking complete - Project context provides coding standards but never overrides story requirements - Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`","bmm",".bmad/bmm/agents/dev.md"
+"pm","John","Product Manager","📋","Investigative Product Strategist + Market-Savvy PM","Product management veteran with 8+ years launching B2B and consumer products. Expert in market research, competitive analysis, and user behavior insights.","Asks 'WHY?' relentlessly like a detective on a case. Direct and data-sharp, cuts through fluff to what actually matters.","- Uncover the deeper WHY behind every requirement. Ruthless prioritization to achieve MVP goals. Proactively identify risks. - Align efforts with measurable business impact. Back all claims with data and user insights. - Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`","bmm",".bmad/bmm/agents/pm.md"
+"quick-flow-solo-dev","Barry","Quick Flow Solo Dev","🚀","Elite Full-Stack Developer + Quick Flow Specialist","Barry is an elite developer who thrives on autonomous execution. He lives and breathes the BMAD Quick Flow workflow, taking projects from concept to deployment with ruthless efficiency. No handoffs, no delays - just pure, focused development. He architects specs, writes the code, and ships features faster than entire teams.","Direct, confident, and implementation-focused. Uses tech slang and gets straight to the point. No fluff, just results. Every response moves the project forward.","- Planning and execution are two sides of the same coin. Quick Flow is my religion. - Specs are for building, not bureaucracy. Code that ships is better than perfect code that doesn't. - Documentation happens alongside development, not after. Ship early, ship often. - Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md ``","bmm",".bmad/bmm/agents/quick-flow-solo-dev.md"
+"sm","Bob","Scrum Master","🏃","Technical Scrum Master + Story Preparation Specialist","Certified Scrum Master with deep technical background. Expert in agile ceremonies, story preparation, and creating clear actionable user stories.","Crisp and checklist-driven. Every word has a purpose, every requirement crystal clear. Zero tolerance for ambiguity.","- Strict boundaries between story prep and implementation - Stories are single source of truth - Perfect alignment between PRD and dev execution - Enable efficient sprints - Deliver developer-ready specs with precise handoffs","bmm",".bmad/bmm/agents/sm.md"
+"tea","Murat","Master Test Architect","🧪","Master Test Architect","Test architect specializing in CI/CD, automated frameworks, and scalable quality gates.","Blends data with gut instinct. 'Strong opinions, weakly held' is their mantra. Speaks in risk calculations and impact assessments.","- Risk-based testing - depth scales with impact - Quality gates backed by data - Tests mirror usage patterns - Flakiness is critical technical debt - Tests first AI implements suite validates - Calculate risk vs value for every testing decision","bmm",".bmad/bmm/agents/tea.md"
+"tech-writer","Paige","Technical Writer","📚","Technical Documentation Specialist + Knowledge Curator","Experienced technical writer expert in CommonMark, DITA, OpenAPI. Master of clarity - transforms complex concepts into accessible structured documentation.","Patient educator who explains like teaching a friend. Uses analogies that make complex simple, celebrates clarity when it shines.","- Documentation is teaching. Every doc helps someone accomplish a task. Clarity above all. - Docs are living artifacts that evolve with code. Know when to simplify vs when to be detailed.","bmm",".bmad/bmm/agents/tech-writer.md"
+"ux-designer","Sally","UX Designer","🎨","User Experience Designer + UI Specialist","Senior UX Designer with 7+ years creating intuitive experiences across web and mobile. Expert in user research, interaction design, AI-assisted tools.","Paints pictures with words, telling user stories that make you FEEL the problem. Empathetic advocate with creative storytelling flair.","- Every decision serves genuine user needs - Start simple, evolve through feedback - Balance empathy with edge case attention - AI tools accelerate human-centered design - Data-informed but always creative","bmm",".bmad/bmm/agents/ux-designer.md"
diff --git a/.bmad/_cfg/agents/bmb-bmad-builder.customize.yaml b/.bmad/_cfg/agents/bmb-bmad-builder.customize.yaml
new file mode 100644
index 0000000..3fb4785
--- /dev/null
+++ b/.bmad/_cfg/agents/bmb-bmad-builder.customize.yaml
@@ -0,0 +1,42 @@
+# Agent Customization
+# Customize any section below - all are optional
+# After editing: npx bmad-method build
+
+# Override agent name
+agent:
+ metadata:
+ name: ""
+
+# Replace entire persona (not merged)
+persona:
+ role: ""
+ identity: ""
+ communication_style: ""
+ principles: []
+
+# Add custom critical actions (appended after standard config loading)
+critical_actions: []
+
+# Add persistent memories for the agent
+memories: []
+# Example:
+# memories:
+# - "User prefers detailed technical explanations"
+# - "Current project uses React and TypeScript"
+
+# Add custom menu items (appended to base menu)
+# Don't include * prefix or help/exit - auto-injected
+menu: []
+# Example:
+# menu:
+# - trigger: my-workflow
+# workflow: "{project-root}/custom/my.yaml"
+# description: My custom workflow
+
+# Add custom prompts (for action="#id" handlers)
+prompts: []
+# Example:
+# prompts:
+# - id: my-prompt
+# content: |
+# Prompt instructions here
diff --git a/.bmad/_cfg/agents/bmm-analyst.customize.yaml b/.bmad/_cfg/agents/bmm-analyst.customize.yaml
new file mode 100644
index 0000000..3fb4785
--- /dev/null
+++ b/.bmad/_cfg/agents/bmm-analyst.customize.yaml
@@ -0,0 +1,42 @@
+# Agent Customization
+# Customize any section below - all are optional
+# After editing: npx bmad-method build
+
+# Override agent name
+agent:
+ metadata:
+ name: ""
+
+# Replace entire persona (not merged)
+persona:
+ role: ""
+ identity: ""
+ communication_style: ""
+ principles: []
+
+# Add custom critical actions (appended after standard config loading)
+critical_actions: []
+
+# Add persistent memories for the agent
+memories: []
+# Example:
+# memories:
+# - "User prefers detailed technical explanations"
+# - "Current project uses React and TypeScript"
+
+# Add custom menu items (appended to base menu)
+# Don't include * prefix or help/exit - auto-injected
+menu: []
+# Example:
+# menu:
+# - trigger: my-workflow
+# workflow: "{project-root}/custom/my.yaml"
+# description: My custom workflow
+
+# Add custom prompts (for action="#id" handlers)
+prompts: []
+# Example:
+# prompts:
+# - id: my-prompt
+# content: |
+# Prompt instructions here
diff --git a/.bmad/_cfg/agents/bmm-architect.customize.yaml b/.bmad/_cfg/agents/bmm-architect.customize.yaml
new file mode 100644
index 0000000..3fb4785
--- /dev/null
+++ b/.bmad/_cfg/agents/bmm-architect.customize.yaml
@@ -0,0 +1,42 @@
+# Agent Customization
+# Customize any section below - all are optional
+# After editing: npx bmad-method build
+
+# Override agent name
+agent:
+ metadata:
+ name: ""
+
+# Replace entire persona (not merged)
+persona:
+ role: ""
+ identity: ""
+ communication_style: ""
+ principles: []
+
+# Add custom critical actions (appended after standard config loading)
+critical_actions: []
+
+# Add persistent memories for the agent
+memories: []
+# Example:
+# memories:
+# - "User prefers detailed technical explanations"
+# - "Current project uses React and TypeScript"
+
+# Add custom menu items (appended to base menu)
+# Don't include * prefix or help/exit - auto-injected
+menu: []
+# Example:
+# menu:
+# - trigger: my-workflow
+# workflow: "{project-root}/custom/my.yaml"
+# description: My custom workflow
+
+# Add custom prompts (for action="#id" handlers)
+prompts: []
+# Example:
+# prompts:
+# - id: my-prompt
+# content: |
+# Prompt instructions here
diff --git a/.bmad/_cfg/agents/bmm-dev.customize.yaml b/.bmad/_cfg/agents/bmm-dev.customize.yaml
new file mode 100644
index 0000000..3fb4785
--- /dev/null
+++ b/.bmad/_cfg/agents/bmm-dev.customize.yaml
@@ -0,0 +1,42 @@
+# Agent Customization
+# Customize any section below - all are optional
+# After editing: npx bmad-method build
+
+# Override agent name
+agent:
+ metadata:
+ name: ""
+
+# Replace entire persona (not merged)
+persona:
+ role: ""
+ identity: ""
+ communication_style: ""
+ principles: []
+
+# Add custom critical actions (appended after standard config loading)
+critical_actions: []
+
+# Add persistent memories for the agent
+memories: []
+# Example:
+# memories:
+# - "User prefers detailed technical explanations"
+# - "Current project uses React and TypeScript"
+
+# Add custom menu items (appended to base menu)
+# Don't include * prefix or help/exit - auto-injected
+menu: []
+# Example:
+# menu:
+# - trigger: my-workflow
+# workflow: "{project-root}/custom/my.yaml"
+# description: My custom workflow
+
+# Add custom prompts (for action="#id" handlers)
+prompts: []
+# Example:
+# prompts:
+# - id: my-prompt
+# content: |
+# Prompt instructions here
diff --git a/.bmad/_cfg/agents/bmm-pm.customize.yaml b/.bmad/_cfg/agents/bmm-pm.customize.yaml
new file mode 100644
index 0000000..3fb4785
--- /dev/null
+++ b/.bmad/_cfg/agents/bmm-pm.customize.yaml
@@ -0,0 +1,42 @@
+# Agent Customization
+# Customize any section below - all are optional
+# After editing: npx bmad-method build
+
+# Override agent name
+agent:
+ metadata:
+ name: ""
+
+# Replace entire persona (not merged)
+persona:
+ role: ""
+ identity: ""
+ communication_style: ""
+ principles: []
+
+# Add custom critical actions (appended after standard config loading)
+critical_actions: []
+
+# Add persistent memories for the agent
+memories: []
+# Example:
+# memories:
+# - "User prefers detailed technical explanations"
+# - "Current project uses React and TypeScript"
+
+# Add custom menu items (appended to base menu)
+# Don't include * prefix or help/exit - auto-injected
+menu: []
+# Example:
+# menu:
+# - trigger: my-workflow
+# workflow: "{project-root}/custom/my.yaml"
+# description: My custom workflow
+
+# Add custom prompts (for action="#id" handlers)
+prompts: []
+# Example:
+# prompts:
+# - id: my-prompt
+# content: |
+# Prompt instructions here
diff --git a/.bmad/_cfg/agents/bmm-quick-flow-solo-dev.customize.yaml b/.bmad/_cfg/agents/bmm-quick-flow-solo-dev.customize.yaml
new file mode 100644
index 0000000..3fb4785
--- /dev/null
+++ b/.bmad/_cfg/agents/bmm-quick-flow-solo-dev.customize.yaml
@@ -0,0 +1,42 @@
+# Agent Customization
+# Customize any section below - all are optional
+# After editing: npx bmad-method build
+
+# Override agent name
+agent:
+ metadata:
+ name: ""
+
+# Replace entire persona (not merged)
+persona:
+ role: ""
+ identity: ""
+ communication_style: ""
+ principles: []
+
+# Add custom critical actions (appended after standard config loading)
+critical_actions: []
+
+# Add persistent memories for the agent
+memories: []
+# Example:
+# memories:
+# - "User prefers detailed technical explanations"
+# - "Current project uses React and TypeScript"
+
+# Add custom menu items (appended to base menu)
+# Don't include * prefix or help/exit - auto-injected
+menu: []
+# Example:
+# menu:
+# - trigger: my-workflow
+# workflow: "{project-root}/custom/my.yaml"
+# description: My custom workflow
+
+# Add custom prompts (for action="#id" handlers)
+prompts: []
+# Example:
+# prompts:
+# - id: my-prompt
+# content: |
+# Prompt instructions here
diff --git a/.bmad/_cfg/agents/bmm-sm.customize.yaml b/.bmad/_cfg/agents/bmm-sm.customize.yaml
new file mode 100644
index 0000000..3fb4785
--- /dev/null
+++ b/.bmad/_cfg/agents/bmm-sm.customize.yaml
@@ -0,0 +1,42 @@
+# Agent Customization
+# Customize any section below - all are optional
+# After editing: npx bmad-method build
+
+# Override agent name
+agent:
+ metadata:
+ name: ""
+
+# Replace entire persona (not merged)
+persona:
+ role: ""
+ identity: ""
+ communication_style: ""
+ principles: []
+
+# Add custom critical actions (appended after standard config loading)
+critical_actions: []
+
+# Add persistent memories for the agent
+memories: []
+# Example:
+# memories:
+# - "User prefers detailed technical explanations"
+# - "Current project uses React and TypeScript"
+
+# Add custom menu items (appended to base menu)
+# Don't include * prefix or help/exit - auto-injected
+menu: []
+# Example:
+# menu:
+# - trigger: my-workflow
+# workflow: "{project-root}/custom/my.yaml"
+# description: My custom workflow
+
+# Add custom prompts (for action="#id" handlers)
+prompts: []
+# Example:
+# prompts:
+# - id: my-prompt
+# content: |
+# Prompt instructions here
diff --git a/.bmad/_cfg/agents/bmm-tea.customize.yaml b/.bmad/_cfg/agents/bmm-tea.customize.yaml
new file mode 100644
index 0000000..3fb4785
--- /dev/null
+++ b/.bmad/_cfg/agents/bmm-tea.customize.yaml
@@ -0,0 +1,42 @@
+# Agent Customization
+# Customize any section below - all are optional
+# After editing: npx bmad-method build
+
+# Override agent name
+agent:
+ metadata:
+ name: ""
+
+# Replace entire persona (not merged)
+persona:
+ role: ""
+ identity: ""
+ communication_style: ""
+ principles: []
+
+# Add custom critical actions (appended after standard config loading)
+critical_actions: []
+
+# Add persistent memories for the agent
+memories: []
+# Example:
+# memories:
+# - "User prefers detailed technical explanations"
+# - "Current project uses React and TypeScript"
+
+# Add custom menu items (appended to base menu)
+# Don't include * prefix or help/exit - auto-injected
+menu: []
+# Example:
+# menu:
+# - trigger: my-workflow
+# workflow: "{project-root}/custom/my.yaml"
+# description: My custom workflow
+
+# Add custom prompts (for action="#id" handlers)
+prompts: []
+# Example:
+# prompts:
+# - id: my-prompt
+# content: |
+# Prompt instructions here
diff --git a/.bmad/_cfg/agents/bmm-tech-writer.customize.yaml b/.bmad/_cfg/agents/bmm-tech-writer.customize.yaml
new file mode 100644
index 0000000..3fb4785
--- /dev/null
+++ b/.bmad/_cfg/agents/bmm-tech-writer.customize.yaml
@@ -0,0 +1,42 @@
+# Agent Customization
+# Customize any section below - all are optional
+# After editing: npx bmad-method build
+
+# Override agent name
+agent:
+ metadata:
+ name: ""
+
+# Replace entire persona (not merged)
+persona:
+ role: ""
+ identity: ""
+ communication_style: ""
+ principles: []
+
+# Add custom critical actions (appended after standard config loading)
+critical_actions: []
+
+# Add persistent memories for the agent
+memories: []
+# Example:
+# memories:
+# - "User prefers detailed technical explanations"
+# - "Current project uses React and TypeScript"
+
+# Add custom menu items (appended to base menu)
+# Don't include * prefix or help/exit - auto-injected
+menu: []
+# Example:
+# menu:
+# - trigger: my-workflow
+# workflow: "{project-root}/custom/my.yaml"
+# description: My custom workflow
+
+# Add custom prompts (for action="#id" handlers)
+prompts: []
+# Example:
+# prompts:
+# - id: my-prompt
+# content: |
+# Prompt instructions here
diff --git a/.bmad/_cfg/agents/bmm-ux-designer.customize.yaml b/.bmad/_cfg/agents/bmm-ux-designer.customize.yaml
new file mode 100644
index 0000000..3fb4785
--- /dev/null
+++ b/.bmad/_cfg/agents/bmm-ux-designer.customize.yaml
@@ -0,0 +1,42 @@
+# Agent Customization
+# Customize any section below - all are optional
+# After editing: npx bmad-method build
+
+# Override agent name
+agent:
+ metadata:
+ name: ""
+
+# Replace entire persona (not merged)
+persona:
+ role: ""
+ identity: ""
+ communication_style: ""
+ principles: []
+
+# Add custom critical actions (appended after standard config loading)
+critical_actions: []
+
+# Add persistent memories for the agent
+memories: []
+# Example:
+# memories:
+# - "User prefers detailed technical explanations"
+# - "Current project uses React and TypeScript"
+
+# Add custom menu items (appended to base menu)
+# Don't include * prefix or help/exit - auto-injected
+menu: []
+# Example:
+# menu:
+# - trigger: my-workflow
+# workflow: "{project-root}/custom/my.yaml"
+# description: My custom workflow
+
+# Add custom prompts (for action="#id" handlers)
+prompts: []
+# Example:
+# prompts:
+# - id: my-prompt
+# content: |
+# Prompt instructions here
diff --git a/.bmad/_cfg/agents/core-bmad-master.customize.yaml b/.bmad/_cfg/agents/core-bmad-master.customize.yaml
new file mode 100644
index 0000000..3fb4785
--- /dev/null
+++ b/.bmad/_cfg/agents/core-bmad-master.customize.yaml
@@ -0,0 +1,42 @@
+# Agent Customization
+# Customize any section below - all are optional
+# After editing: npx bmad-method build
+
+# Override agent name
+agent:
+ metadata:
+ name: ""
+
+# Replace entire persona (not merged)
+persona:
+ role: ""
+ identity: ""
+ communication_style: ""
+ principles: []
+
+# Add custom critical actions (appended after standard config loading)
+critical_actions: []
+
+# Add persistent memories for the agent
+memories: []
+# Example:
+# memories:
+# - "User prefers detailed technical explanations"
+# - "Current project uses React and TypeScript"
+
+# Add custom menu items (appended to base menu)
+# Don't include * prefix or help/exit - auto-injected
+menu: []
+# Example:
+# menu:
+# - trigger: my-workflow
+# workflow: "{project-root}/custom/my.yaml"
+# description: My custom workflow
+
+# Add custom prompts (for action="#id" handlers)
+prompts: []
+# Example:
+# prompts:
+# - id: my-prompt
+# content: |
+# Prompt instructions here
diff --git a/.bmad/_cfg/files-manifest.csv b/.bmad/_cfg/files-manifest.csv
new file mode 100644
index 0000000..2919902
--- /dev/null
+++ b/.bmad/_cfg/files-manifest.csv
@@ -0,0 +1,439 @@
+type,name,module,path,hash
+"csv","agent-manifest","_cfg","_cfg/agent-manifest.csv","feac0624114f1de2e28a9da11686d0947a5212a91079ebd1bde5a1c2ace9a2df"
+"csv","task-manifest","_cfg","_cfg/task-manifest.csv","368b7cced3cb58dd8da1757b368308f8c76dd238fbcf4e0435677a26b6773a23"
+"csv","workflow-manifest","_cfg","_cfg/workflow-manifest.csv","36638da34ecc06111322b5a5df8e5715374faf9a698d3e54fc8c6a9600ea8a78"
+"yaml","manifest","_cfg","_cfg/manifest.yaml","598f9a078b72bceea7daa2860d98f4dfc3c2b354c4f0b18f18b898d74fcb7184"
+"csv","common-workflow-tools","bmb","bmb/docs/workflows/common-workflow-tools.csv","7f5bd0fc9e8d92f12c1d304a72d1f3925efc7d36ab6da0b5eda2f43608546081"
+"csv","communication-presets","bmb","bmb/workflows/create-agent/data/communication-presets.csv","1d40b718418c672b19700516f03479dce199fb3646ff26250536e42113a91224"
+"csv","dietary-restrictions","bmb","bmb/reference/workflows/meal-prep-nutrition/data/dietary-restrictions.csv","ccde18712553d55ea63ca85d6d1f10e74086d4f47a03dec65141d4bb9942592b"
+"csv","dietary-restrictions","bmb","bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/data/dietary-restrictions.csv","ccde18712553d55ea63ca85d6d1f10e74086d4f47a03dec65141d4bb9942592b"
+"csv","kb","bmb","bmb/docs/agents/kb.csv","e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
+"csv","kb","bmb","bmb/docs/workflows/kb.csv","e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
+"csv","macro-calculator","bmb","bmb/reference/workflows/meal-prep-nutrition/data/macro-calculator.csv","6f218ae98911f5c2200a72c94cf85a45a4928a6d3208a23acf9c2e34b06e494c"
+"csv","macro-calculator","bmb","bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/data/macro-calculator.csv","6f218ae98911f5c2200a72c94cf85a45a4928a6d3208a23acf9c2e34b06e494c"
+"csv","recipe-database","bmb","bmb/reference/workflows/meal-prep-nutrition/data/recipe-database.csv","f97b38bc7405369cfd8a7d88b39708af8df2bcb9c9867313aef9e8b555291e88"
+"csv","recipe-database","bmb","bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/data/recipe-database.csv","f97b38bc7405369cfd8a7d88b39708af8df2bcb9c9867313aef9e8b555291e88"
+"js","installer.template","bmb","bmb/workflows/create-module/templates/installer.template.js","52e573290f20fbafa5030517bf5bd6c0d204f32cdac76fd1d3c4771fcc493695"
+"md","agent_commands","bmb","bmb/workflows/create-agent/templates/agent_commands.md","e65ed1674b8064467059adaf5432aabf937a5420e7a59801f2c1e166766f403a"
+"md","agent_persona","bmb","bmb/workflows/create-agent/templates/agent_persona.md","a4da0b314ac04a59e574f78948d9527591f1327ffc648f0e82b56c9c5f5e2273"
+"md","agent_purpose_and_type","bmb","bmb/workflows/create-agent/templates/agent_purpose_and_type.md","e7b69190e3ef74319ebc26be12405c0a4bcfb6fb079d65ec545392237e799711"
+"md","agent-compilation","bmb","bmb/docs/agents/agent-compilation.md","c9381fc09c183183016657fd6403ca0c96516aa89820296ba159d17d26a4d629"
+"md","agent-menu-patterns","bmb","bmb/docs/agents/agent-menu-patterns.md","e91765d1861b30339a5de87be5ea5eefb729aa50504a5c044a641db1fe91a2fa"
+"md","agent-validation-checklist","bmb","bmb/workflows/create-agent/data/agent-validation-checklist.md","7b1172ac27735a8adcd02448692b652bd6d089fdab3ea667b5bec7c724f240e9"
+"md","agent.template","bmb","bmb/workflows/create-module/templates/agent.template.md","52f7378b3f4a5a30a620808cf78dfceada748e2b6f21dd2d7e3fd8c69c54cfee"
+"md","architecture","bmb","bmb/docs/workflows/architecture.md","a76178d7610878e5a1b7a99effa7be568e54cf5fc471639544127161d17849a9"
+"md","assessment-section","bmb","bmb/reference/workflows/meal-prep-nutrition/templates/assessment-section.md","9fa8380217ce2ecb29e05d4023e0e5c17c84b5880e9af92df45a57a7dc2f2fb1"
+"md","assessment-section","bmb","bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/templates/assessment-section.md","9fa8380217ce2ecb29e05d4023e0e5c17c84b5880e9af92df45a57a7dc2f2fb1"
+"md","brainstorm-context","bmb","bmb/workflows/create-agent/data/brainstorm-context.md","576d7a02935ef4e34bdc6476527b658d954bb490b8d09b09ef7e0cf58712d96f"
+"md","checklist","bmb","bmb/workflows-legacy/edit-module/checklist.md","4e0f17d6c4a2e02a766cbba0dd8bf1971a824b2ea61a7310e8e945bd08338271"
+"md","checklist","bmb","bmb/workflows-legacy/module-brief/checklist.md","4710f9c7e48a1cb29b225d43955bf313271dc7f9bb471bfecb1a8edf5f57a10a"
+"md","completion-summary","bmb","bmb/workflows/edit-workflow/templates/completion-summary.md","5fb732313bbf466c106e59c2c5d16d92be6e4f2a749fbd4f3d99415bddbeea1c"
+"md","compliance-report","bmb","bmb/workflows/workflow-compliance-check/templates/compliance-report.md","01184bebdad49cc5b9a188f27b6998e7834de5c4dcdaa4f3d9f827a1b46d7037"
+"md","csv-data-file-standards","bmb","bmb/docs/workflows/csv-data-file-standards.md","96fcc0e54f5607044adf0f50b10a5a74c12331b71469d5574765e635988406eb"
+"md","expert-agent-architecture","bmb","bmb/docs/agents/expert-agent-architecture.md","161615a1d36222badba72e2743325e6036fc34bc61239a8425d230f1f1acff1a"
+"md","improvement-goals","bmb","bmb/workflows/edit-workflow/templates/improvement-goals.md","d4f0b61a4a7327388ee23fac02e0cb3bf5fb34780f63d439aa060bc65a43fef4"
+"md","improvement-log","bmb","bmb/workflows/edit-workflow/templates/improvement-log.md","3487cd5e19c56696e8c4bb92e45ee77a3f76bb70bb26509f751e39a7bdc79ca2"
+"md","index","bmb","bmb/docs/agents/index.md","899fd0c9bfcee050533e95e1b6fd9aee1f4a01de07b99796cd1328c8feb4282b"
+"md","index","bmb","bmb/docs/workflows/index.md","43f56996ccd0aa559bf54c7bdc490b2506ccff3f019b3dc6cd87669ae9e47a2c"
+"md","info-and-installation-guide","bmb","bmb/workflows/create-agent/data/info-and-installation-guide.md","4a6ed038899b23c0a659c0de8bfd44979f49793a536c84cd1ab26dad44ff0ede"
+"md","instructions","bmb","bmb/workflows-legacy/edit-module/instructions.md","1dfece3903ddfec71f8802cc17ecde4a66b5131dce223b898a769f05092eb39d"
+"md","instructions","bmb","bmb/workflows-legacy/module-brief/instructions.md","a1386d90d1d347c4bad17b628f3c201e1a61d162ffe8468bba89ef377996ce8c"
+"md","intent-vs-prescriptive-spectrum","bmb","bmb/docs/workflows/intent-vs-prescriptive-spectrum.md","def3cd9e350556da9c602db93b2db34b9aa96d965ef51ab85499c414d4ea1564"
+"md","module-agent-architecture","bmb","bmb/docs/agents/module-agent-architecture.md","cdf59be1eac3130f46d6a6dd44cf80cd129255e15b44880c87ee7f649d248cc9"
+"md","module-plan.template","bmb","bmb/workflows/create-module/templates/module-plan.template.md","2bbdf9fbdb548f055a564ca8e4ec78ab86c2b4f33ef69689f2cd07f6d52e791d"
+"md","nutrition-plan","bmb","bmb/reference/workflows/meal-prep-nutrition/templates/nutrition-plan.md","8622904f32a9de6e4a85059daa62f7a1277000df48d82b17eddfb39f25eb5a7d"
+"md","nutrition-plan","bmb","bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/templates/nutrition-plan.md","8622904f32a9de6e4a85059daa62f7a1277000df48d82b17eddfb39f25eb5a7d"
+"md","prep-schedule-section","bmb","bmb/reference/workflows/meal-prep-nutrition/templates/prep-schedule-section.md","1c770d8deb07863adee05fe91114ffe2f9b0d366d653f554c2cb39a847d3d3ed"
+"md","prep-schedule-section","bmb","bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/templates/prep-schedule-section.md","1c770d8deb07863adee05fe91114ffe2f9b0d366d653f554c2cb39a847d3d3ed"
+"md","profile-section","bmb","bmb/reference/workflows/meal-prep-nutrition/templates/profile-section.md","8f2df3ab5d41f229f401b153d54d67818e3205ef06b7ca5cfc6439f21112be74"
+"md","profile-section","bmb","bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/templates/profile-section.md","8f2df3ab5d41f229f401b153d54d67818e3205ef06b7ca5cfc6439f21112be74"
+"md","README","bmb","bmb/README.md","5c9d066088007960dc50dde6338f59523720b7986765a43e16fb21cd9f9716c6"
+"md","README","bmb","bmb/reference/README.md","fd0dcb1c9acd089b6855dcfc89a74c9c27e4b1637d3c2c2e8db4cde2fb1140eb"
+"md","README","bmb","bmb/reference/agents/expert-examples/journal-keeper/README.md","192965d472552081c2775100c08d0c508218c82da0d52e1bf5ed7f587b6aab18"
+"md","README","bmb","bmb/reference/agents/module-examples/README.md","40f4fd37eb3e0f11b5a1dd9b66c2c2add420e98f65a9a3e6092506b7c5ae5c4b"
+"md","README","bmb","bmb/reference/agents/simple-examples/README.md","645ad486a3cf20b6e57d60255571c890a57af59522b42e675a553ba8cdc38b2b"
+"md","README","bmb","bmb/workflows/create-agent/data/reference/README.md","fd0dcb1c9acd089b6855dcfc89a74c9c27e4b1637d3c2c2e8db4cde2fb1140eb"
+"md","README","bmb","bmb/workflows/create-agent/data/reference/agents/expert-examples/journal-keeper/README.md","192965d472552081c2775100c08d0c508218c82da0d52e1bf5ed7f587b6aab18"
+"md","README","bmb","bmb/workflows/create-agent/data/reference/agents/module-examples/README.md","40f4fd37eb3e0f11b5a1dd9b66c2c2add420e98f65a9a3e6092506b7c5ae5c4b"
+"md","README","bmb","bmb/workflows/create-agent/data/reference/agents/simple-examples/README.md","645ad486a3cf20b6e57d60255571c890a57af59522b42e675a553ba8cdc38b2b"
+"md","README","bmb","bmb/workflows-legacy/edit-module/README.md","f95914b31f5118eba63e737f1198b08bb7ab4f8dbb8dfdc06ac2e85d9acd4f90"
+"md","README","bmb","bmb/workflows-legacy/module-brief/README.md","3b6456ebaff447a2312d1274b50bad538da6a8e7c73c2e7e4d5b7f6092852219"
+"md","shopping-section","bmb","bmb/reference/workflows/meal-prep-nutrition/templates/shopping-section.md","8441562d59975a6126e27ef90cb20da97acacd4137b15bf47659c80838101b67"
+"md","shopping-section","bmb","bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/templates/shopping-section.md","8441562d59975a6126e27ef90cb20da97acacd4137b15bf47659c80838101b67"
+"md","simple-agent-architecture","bmb","bmb/docs/agents/simple-agent-architecture.md","48e366e7520ad4bcefbb35452cdad6be452b1a9d435bc4dfae45bd4d64aeb82d"
+"md","step-01-analyze","bmb","bmb/workflows/edit-workflow/steps/step-01-analyze.md","46bdc9175c6c3a16376f283f5b85968f07f05026209f6385a003e551eacaa89b"
+"md","step-01-brainstorm","bmb","bmb/workflows/create-agent/steps/step-01-brainstorm.md","affe72129e5d3c8738f05d6a7022b18a8583de4a5b024e517a9266337e480693"
+"md","step-01-discover-intent","bmb","bmb/workflows/edit-agent/steps/step-01-discover-intent.md","b140d8ad80f7445c9c9af7cea4e4ff2eef44ff1d855df2eff32edd5d92cd57af"
+"md","step-01-init","bmb","bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md","ef6a33270080111f3852ba8ccffa51bdd7bd47f336426b4834bbbbecfe571fa4"
+"md","step-01-init","bmb","bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-01-init.md","7b2ffadffea2d6a4d3a1b204ebfb5c617270d2a8a9ef634aeadf443cc7046302"
+"md","step-01-init","bmb","bmb/workflows/create-module/steps/step-01-init.md","5ab334cf35bf53e587a6d4cb38e1c7c0d344f0e74b5d4cfb933e1496aa463451"
+"md","step-01-init","bmb","bmb/workflows/create-workflow/steps/step-01-init.md","0693ec2c0190b19b2ec350e843299b1431f43d309ce4493343e6bfc4978ccc16"
+"md","step-01-init-continuable-template","bmb","bmb/docs/workflows/templates/step-01-init-continuable-template.md","9874f78647c5835a16fb4b6292029f77646b851afcd54007c60ae5b19306a105"
+"md","step-01-validate-goal","bmb","bmb/workflows/workflow-compliance-check/steps/step-01-validate-goal.md","58d018e73dfddbccd1e8e21c67d7053450fc83484e41395feb092f71cb86683c"
+"md","step-01b-continue","bmb","bmb/reference/workflows/meal-prep-nutrition/steps/step-01b-continue.md","865e0f964e78cd31067cc478c22bbc79e80f29d6637bf0ba27756f38ef4cf04f"
+"md","step-01b-continue","bmb","bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-01b-continue.md","ae3756669334f57cea74002a53365093ea08d2c70d747772baaa52452b66eb30"
+"md","step-01b-continue","bmb","bmb/workflows/create-module/steps/step-01b-continue.md","4a35d969c20be0bfc188a7650c239e00d291d554e61b638e2358726bb6e61681"
+"md","step-02-analyze-agent","bmb","bmb/workflows/edit-agent/steps/step-02-analyze-agent.md","16f550505c06a0ab735a8c1ff5be28e6996638b2f73b2444e60b8757dfd464e9"
+"md","step-02-concept","bmb","bmb/workflows/create-module/steps/step-02-concept.md","2e7bdabc81124b4854bbe90bf97f846506a3e7fa1d8aacfde13f4d312950a64b"
+"md","step-02-discover","bmb","bmb/workflows/create-agent/steps/step-02-discover.md","0aa20cf2bc32a4b630adaf8ee5c73d31479bc701d2910476405891845fd9040f"
+"md","step-02-discover","bmb","bmb/workflows/edit-workflow/steps/step-02-discover.md","6c054a7217b8c0c3fefefed083d15ff3c89bd0f41a86d5303e6d0a2e1fe15117"
+"md","step-02-gather","bmb","bmb/workflows/create-workflow/steps/step-02-gather.md","02a5c41a9bde5fc18e81d42dcf43445fd3a054015e100480a905b9f352f56078"
+"md","step-02-profile","bmb","bmb/reference/workflows/meal-prep-nutrition/steps/step-02-profile.md","d3179ea36f1600303e1cd53f674a06416822c8e2703b2fba51f57eb7ac7ad58e"
+"md","step-02-profile","bmb","bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-02-profile.md","22a3df31583ceb55abdaee61c42e34a5e38af9da10c168c49b4af319a6045cc9"
+"md","step-02-workflow-validation","bmb","bmb/workflows/workflow-compliance-check/steps/step-02-workflow-validation.md","50832b0a0591515aabd94f7b51e749bba42ce0eb0a00f9d93bb32606cae4cdd8"
+"md","step-03-assessment","bmb","bmb/reference/workflows/meal-prep-nutrition/steps/step-03-assessment.md","65f002686e530fffe3baa8b34755bb593f4f7d7ffb92d1f81f91c9a2d1da82f8"
+"md","step-03-assessment","bmb","bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-03-assessment.md","dc1fa58e07c17db0208e1dbea305cd18cae06b06a6a0a2d38c317afdcdb3456f"
+"md","step-03-components","bmb","bmb/workflows/create-module/steps/step-03-components.md","b2d62738b8183af652ead215ac302f0fb97a95d965d6c36458f17996ced30b65"
+"md","step-03-improve","bmb","bmb/workflows/edit-workflow/steps/step-03-improve.md","5eda7d8d4e6af85b41c548bdc430c8a8e1046c41b14c439f13c660db3d3e0e7a"
+"md","step-03-persona","bmb","bmb/workflows/create-agent/steps/step-03-persona.md","4f0292d3b46de5cefab505a9424dd299fd7de6d511a4f6aafd9f00a6015d925e"
+"md","step-03-propose-changes","bmb","bmb/workflows/edit-agent/steps/step-03-propose-changes.md","092f1e5bc79f205a6db475d19d5a61bc41e3862e7be56e9eac07bd92b1823f03"
+"md","step-03-step-validation","bmb","bmb/workflows/workflow-compliance-check/steps/step-03-step-validation.md","3e78b269e0e431d5b887d11fe4f1a66f78c5a5bbcdf25cb288b3aafb73715c6f"
+"md","step-03-tools-configuration","bmb","bmb/workflows/create-workflow/steps/step-03-tools-configuration.md","aac2aedc42406cf4c65c99e7c81ae7bc5b98d780d7bc0dce0d2f48d12e9f1f60"
+"md","step-04-apply-changes","bmb","bmb/workflows/edit-agent/steps/step-04-apply-changes.md","0d90b8e95453f732e1c9414070aebba76959bf207c0c37e471c4091780ab8a69"
+"md","step-04-commands","bmb","bmb/workflows/create-agent/steps/step-04-commands.md","932ab6242bfb85d49d411d623059bbd75cb550204b64a7d34bad2ca54ca9b1c0"
+"md","step-04-file-validation","bmb","bmb/workflows/workflow-compliance-check/steps/step-04-file-validation.md","fa01176653e813e93c6a54403432a453b83e5fe9beb2d8059d8dc3eb40272a66"
+"md","step-04-plan-review","bmb","bmb/workflows/create-workflow/steps/step-04-plan-review.md","c97eaa802f69371ee1927e95496a134d23951137b68e43a663f9733b174cd121"
+"md","step-04-strategy","bmb","bmb/reference/workflows/meal-prep-nutrition/steps/step-04-strategy.md","bd967e2ea8b99259572144c33bd0826e6f55079e8576d2f1e6ca39ebf2eb19d7"
+"md","step-04-strategy","bmb","bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-04-strategy.md","69c086f9088ea41fc28a2246a6c521b3ad2cb9fed3d933a0ce2e1703db37ebf2"
+"md","step-04-structure","bmb","bmb/workflows/create-module/steps/step-04-structure.md","d68b7a43986c20753128736c9e5735008f60b5e1a0d2980b104ce37cc14e031e"
+"md","step-04-validate","bmb","bmb/workflows/edit-workflow/steps/step-04-validate.md","0de575a433f7c36ee35b7b073e871e94e1540804daa4356f3ce03101230129ec"
+"md","step-05-compliance-check","bmb","bmb/workflows/edit-workflow/steps/step-05-compliance-check.md","107651afdfc3fad42270a4139c3f96fae2a334a7cbc7f09126f7899a4abed08b"
+"md","step-05-config","bmb","bmb/workflows/create-module/steps/step-05-config.md","c56f2541f0329dfaa843915ac59516496f6b6e618f41ecfff038a18e20b528f8"
+"md","step-05-intent-spectrum-validation","bmb","bmb/workflows/workflow-compliance-check/steps/step-05-intent-spectrum-validation.md","7cec2a90eeea4ec7f54253dbe6ec8d91d5523c2ca96e9d4060e30006ba8dc081"
+"md","step-05-name","bmb","bmb/workflows/create-agent/steps/step-05-name.md","8f32e922c7bdc703484f9b65794e0d4170aba1cc3aae45ad4693655c3b4102cb"
+"md","step-05-output-format-design","bmb","bmb/workflows/create-workflow/steps/step-05-output-format-design.md","dbe6343c248870e9e2a6c4c81602ee8e3fcfe4fe3323a97e2915ec91eb392596"
+"md","step-05-shopping","bmb","bmb/reference/workflows/meal-prep-nutrition/steps/step-05-shopping.md","e5d18d401ec99960ab7da50bd5e8413e4c6c512fe9fc3b97aa7cb4ac33aeee8d"
+"md","step-05-shopping","bmb","bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-05-shopping.md","be2cf3511c3b648453d9a4d82ef5108791661395168ac59d4280ceac7a5e55d1"
+"md","step-05-validate","bmb","bmb/workflows/edit-agent/steps/step-05-validate.md","724486806a7bba7a5adf68cb3eb1d1cd7d6920df2a9b2f31625cf1eaba81dd7d"
+"md","step-06-agents","bmb","bmb/workflows/create-module/steps/step-06-agents.md","7004c4fdf7d908b211363204a48b797e2b1619282efe48851dda3145f27f1dc0"
+"md","step-06-build","bmb","bmb/workflows/create-agent/steps/step-06-build.md","ad385580969f2f1528964862c0e67e8ad9fb6df5fae321fdd50f107b68595a81"
+"md","step-06-design","bmb","bmb/workflows/create-workflow/steps/step-06-design.md","9a79b1c1e65514133d057d098b49146fa747046fdd6a56f1be1217c454eefb94"
+"md","step-06-prep-schedule","bmb","bmb/reference/workflows/meal-prep-nutrition/steps/step-06-prep-schedule.md","5da1e1d9630d13a4cd91da5ae9e59761ff2393a03b62bab02f521a576442d3f2"
+"md","step-06-prep-schedule","bmb","bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-06-prep-schedule.md","e5c9558ae2c140aaa7f000fcb609337fb41d6cb6a7df5464830fcf4301d0a7d7"
+"md","step-06-web-subprocess-validation","bmb","bmb/workflows/workflow-compliance-check/steps/step-06-web-subprocess-validation.md","9e0c817b37954802ca22783becee647bce985979e48905602df46da6067f2477"
+"md","step-07-build","bmb","bmb/workflows/create-workflow/steps/step-07-build.md","8e2e00b40a9ca89f996ab674de0cb5445e3988d8ad8d8a80dc0054233cb458d2"
+"md","step-07-holistic-analysis","bmb","bmb/workflows/workflow-compliance-check/steps/step-07-holistic-analysis.md","e49d543ca355f8e6a24853c5d9dc6c352b4b733a56f4ac39a1ac3fef5d53ba53"
+"md","step-07-validate","bmb","bmb/workflows/create-agent/steps/step-07-validate.md","b96e794f351ff446dfa5b2911ffb02da2b5106f0e6db0304d19d24147aa87936"
+"md","step-07-workflows","bmb","bmb/workflows/create-module/steps/step-07-workflows.md","28395587dc7c6b7b401d048e68fc1b457522eea677e593adfcf2dd12ed2261ad"
+"md","step-08-generate-report","bmb","bmb/workflows/workflow-compliance-check/steps/step-08-generate-report.md","181989805a3ee0bac78b8d2890f06129dfc99a17c23b4379b6e91e25515e1ad3"
+"md","step-08-installer","bmb","bmb/workflows/create-module/steps/step-08-installer.md","c76cb0e41c3e756670fab44ba970506d0dc272050a688f95f64deab895607080"
+"md","step-08-review","bmb","bmb/workflows/create-workflow/steps/step-08-review.md","b0677bc8b183fe091f81d610e872f1f0657370bdf3e46dcdc986b198d0aba561"
+"md","step-08-setup","bmb","bmb/workflows/create-agent/steps/step-08-setup.md","16dd12f2771fa9f546fa8d5f82fbd389d5abad459fda6e02a65391794475787c"
+"md","step-09-complete","bmb","bmb/workflows/create-workflow/steps/step-09-complete.md","d28265cd1aa083c4c52a54a404dd23b54812fe2b7e140948b94474d3b54cdd72"
+"md","step-09-customize","bmb","bmb/workflows/create-agent/steps/step-09-customize.md","e3e8d2e7868098e245f7539708ebf867ca39b20dc73c5f33de1b43356b78ada7"
+"md","step-09-documentation","bmb","bmb/workflows/create-module/steps/step-09-documentation.md","88bd60b346024984ac928a047165fdac8ccb7a90d51bc41e9c47c8892157a4cf"
+"md","step-10-build-tools","bmb","bmb/workflows/create-agent/steps/step-10-build-tools.md","83982865d3c86c1bb3cd2bf92420ac1a359082f95f09290696441077f4ffe977"
+"md","step-10-roadmap","bmb","bmb/workflows/create-module/steps/step-10-roadmap.md","04405e5e6d2641aff9194ef28625e53ae2ad3ccc1776339a1a026a764d1f24bc"
+"md","step-11-celebrate","bmb","bmb/workflows/create-agent/steps/step-11-celebrate.md","0ed8a33745c825c82db33f2f6844e2d6c267b8e65df5416036032f99325d898a"
+"md","step-11-validate","bmb","bmb/workflows/create-module/steps/step-11-validate.md","7c66ccbf1ad9c9df2dcf60cb8db782b442166d8c3c30144d66081d1461980535"
+"md","step-1b-template","bmb","bmb/docs/workflows/templates/step-1b-template.md","128d4f3f770f6d84938818a0ecfc99ba19466fd5360ab43d1e4e1b635639949b"
+"md","step-file","bmb","bmb/docs/workflows/templates/step-file.md","e82371cbdd32b1e12a5fed6b0f00f5d3de097c3ae1511b7512cdf571e7fd214b"
+"md","step-template","bmb","bmb/docs/workflows/templates/step-template.md","fd6ae54260cd7dade0a331d091a91e63ccc532cb87e11f96901197aa9a9ec998"
+"md","strategy-section","bmb","bmb/reference/workflows/meal-prep-nutrition/templates/strategy-section.md","0d75fedb5bedc07bd0e17a63f370b011f770d3d696eb7835cc07fa4fe5a77337"
+"md","strategy-section","bmb","bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/templates/strategy-section.md","0d75fedb5bedc07bd0e17a63f370b011f770d3d696eb7835cc07fa4fe5a77337"
+"md","template","bmb","bmb/workflows-legacy/module-brief/template.md","7d1ad5ec40b06510fcbb0a3da8ea32aefa493e5b04c3a2bba90ce5685b894275"
+"md","terms","bmb","bmb/docs/workflows/terms.md","4335bbc77ca4ccb6ad8baf39a553325b92c047b3cfdfa1903079ea3ebe34b91c"
+"md","understanding-agent-types","bmb","bmb/docs/agents/understanding-agent-types.md","17cd17d09295dd9064d46ae9beebf4943976c146d4cbf93a903da14063153d08"
+"md","validation","bmb","bmb/workflows/create-module/validation.md","2e2330bc7cc3f1bad8387a22712816c965dc6050c747ed11e0bffd363477fab5"
+"md","validation-complete","bmb","bmb/workflows/create-agent/data/validation-complete.md","2dee12dfa3003f15b88328459c121a4d2bc35072169ba9f58ffcac7f043a0c27"
+"md","validation-results","bmb","bmb/workflows/edit-workflow/templates/validation-results.md","97ed6deaab6c60849fdce797ace3c7c9a2bbb63f0fb3601cbe8d47895c4b6731"
+"md","workflow","bmb","bmb/docs/workflows/templates/workflow.md","46933e9f9e0b4e9ffcf95b69f7a88ad8a57ab50e3d0d9a4e7fd70170ab855c12"
+"md","workflow","bmb","bmb/reference/workflows/meal-prep-nutrition/workflow.md","bb203a404fc6e7408acc84974295d411c86196ab0cc54b4b987d742655f6eb3e"
+"md","workflow","bmb","bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/workflow.md","bee70a6a9839554d41cef790ad1f478c186b3b514a8f9d369d6f3ec33562aa07"
+"md","workflow","bmb","bmb/workflows/create-agent/workflow.md","ed436dfc3c79a56cb30067316c1879c20cb1831c7191ff325e45a2044f9d6a88"
+"md","workflow","bmb","bmb/workflows/create-module/workflow.md","8f46c5d5dfd2647acd6db8d4c8c5f4eca5e74782f9ecc8b02394c545277c2990"
+"md","workflow","bmb","bmb/workflows/create-workflow/workflow.md","43f8ca56ae63b4e42f4768817e2c16a8514c41c9a318a87567849569456e3f7c"
+"md","workflow","bmb","bmb/workflows/edit-agent/workflow.md","4ebb3eb4a992dffa409bc69c53cfd440fea4aa80bc24eef6cf1ea0abf752a0be"
+"md","workflow","bmb","bmb/workflows/edit-workflow/workflow.md","27e59fa0180c5f115b40a579269e61eebf03888fa7269a9dae5839fc17c7f01c"
+"md","workflow","bmb","bmb/workflows/workflow-compliance-check/workflow.md","6780a16fda8c9d9d594b2f2113fe847f2f532b903f863e7e9077221dde2d63b3"
+"md","workflow-analysis","bmb","bmb/workflows/edit-workflow/templates/workflow-analysis.md","9e2196c12fcdfbde8a074ea97a0d883cbe629c465e2b6ff52bb1619d687d6b8a"
+"md","workflow-plan-template","bmb","bmb/workflows/create-module/templates/workflow-plan-template.md","2f9274926e662398103abb2393c61d1cac8db2be7b0096c0ab1ef13d93c12a3c"
+"md","workflow-template","bmb","bmb/docs/workflows/templates/workflow-template.md","5fc6880d2143b6b592e92032d4fee20ce188feed448e2ab9a5ee167e882e8600"
+"yaml","config","bmb","bmb/config.yaml","6b2cd948ae9e1f62500cec2af464e001230afa0fec02eae6c082ac2cc3375071"
+"yaml","module.template","bmb","bmb/workflows/create-module/templates/module.template.yaml","508387a0658304e43921c3fc4391d012ecb1bd0b6677c353adbbaa3cd4642838"
+"yaml","workflow","bmb","bmb/workflows-legacy/edit-module/workflow.yaml","25ee3994fad9845ae7d3f8979ab0e08548f4f5473a04bf2fd9704bf42793dc1f"
+"yaml","workflow","bmb","bmb/workflows-legacy/module-brief/workflow.yaml","1a178ab87b8f602a5a27262ee2276fe16ea0f132c888524d774dde0dd6ba4b9f"
+"csv","default-party","bmm","bmm/teams/default-party.csv","43209253a2e784e6b054a4ac427c9532a50d9310f6a85052d93ce975b9162156"
+"csv","documentation-requirements","bmm","bmm/workflows/document-project/documentation-requirements.csv","d1253b99e88250f2130516b56027ed706e643bfec3d99316727a4c6ec65c6c1d"
+"csv","domain-complexity","bmm","bmm/workflows/2-plan-workflows/prd/domain-complexity.csv","ed4d30e9fd87db2d628fb66cac7a302823ef6ebb3a8da53b9265326f10a54e11"
+"csv","domain-complexity","bmm","bmm/workflows/3-solutioning/architecture/data/domain-complexity.csv","cb9244ed2084143146f9f473244ad9cf63d33891742b9f6fbcb6e354fa4f3a93"
+"csv","project-types","bmm","bmm/workflows/2-plan-workflows/prd/project-types.csv","7a01d336e940fb7a59ff450064fd1194cdedda316370d939264a0a0adcc0aca3"
+"csv","project-types","bmm","bmm/workflows/3-solutioning/architecture/data/project-types.csv","12343635a2f11343edb1d46906981d6f5e12b9cad2f612e13b09460b5e5106e7"
+"csv","tea-index","bmm","bmm/testarch/tea-index.csv","374a8d53b5e127a9440751a02c5112c66f81bc00e2128d11d11f16d8f45292ea"
+"excalidraw","workflow-method-greenfield","bmm","bmm/docs/images/workflow-method-greenfield.excalidraw","cd623b99dcbd424f6f1d0c4b5c7cc8019d523a40682a12aaacd58a3a71181ba3"
+"json","excalidraw-library","bmm","bmm/workflows/diagrams/_shared/excalidraw-library.json","8e5079f4e79ff17f4781358423f2126a1f14ab48bbdee18fd28943865722030c"
+"json","project-scan-report-schema","bmm","bmm/workflows/document-project/templates/project-scan-report-schema.json","53255f15a10cab801a1d75b4318cdb0095eed08c51b3323b7e6c236ae6b399b7"
+"md","agents-guide","bmm","bmm/docs/agents-guide.md","0ed51e6eaf804e26841e91b776c1aaf7d96aee3d389895e9a6ebc1ac757c4900"
+"md","api-request","bmm","bmm/testarch/knowledge/api-request.md","93ac674f645cb389aafe08ce31e53280ebc0385c59e585a199b772bb0e0651fb"
+"md","architecture-decision-template","bmm","bmm/workflows/3-solutioning/architecture/architecture-decision-template.md","677abaa21e5ea5aa11ea84d596f3ff81506652b5929b6403d404d9c7623c3752"
+"md","atdd-checklist-template","bmm","bmm/workflows/testarch/atdd/atdd-checklist-template.md","4a663156ada567c617993fa334e51e4eb670d47098d9b04e2007c4d286c818dc"
+"md","auth-session","bmm","bmm/testarch/knowledge/auth-session.md","b2ee00c5650655311ff54d20dcd6013afb5b280a66faa8336f9fb810436f1aab"
+"md","bmad-quick-flow","bmm","bmm/docs/bmad-quick-flow.md","e437c81feedf8a981595a6f53119d5ffff37b3815d0b58901340b1908d470136"
+"md","brownfield-guide","bmm","bmm/docs/brownfield-guide.md","72107bb66d7d1f76d935d022b4913a831dba6ddd838833d1e3ac8b55d4e4033a"
+"md","burn-in","bmm","bmm/testarch/knowledge/burn-in.md","5ba3d2abe6b961e5bc3948ab165e801195bff3ee6e66569c00c219b484aa4b5d"
+"md","checklist","bmm","bmm/workflows/4-implementation/code-review/checklist.md","e30d2890ba5c50777bbe04071f754e975a1d7ec168501f321a79169c4201dd28"
+"md","checklist","bmm","bmm/workflows/4-implementation/correct-course/checklist.md","c02bdd4bf4b1f8ea8f7c7babaa485d95f7837818e74cef07486a20b31671f6f5"
+"md","checklist","bmm","bmm/workflows/4-implementation/create-story/checklist.md","da609c09af4a9dea4a0a3cb2bd691b5032e15120f539c9b43f7452cfbe68cafb"
+"md","checklist","bmm","bmm/workflows/4-implementation/dev-story/checklist.md","5e9fe3c5df30f2ab79eac375317d4d1ade1face371d2ac669cef52762afe0fc4"
+"md","checklist","bmm","bmm/workflows/4-implementation/sprint-planning/checklist.md","80b10aedcf88ab1641b8e5f99c9a400c8fd9014f13ca65befc5c83992e367dd7"
+"md","checklist","bmm","bmm/workflows/bmad-quick-flow/quick-dev/checklist.md","7a26f68fa535caa6b461c4e84846241db4669da29b19a7ab510eeeff434bae12"
+"md","checklist","bmm","bmm/workflows/diagrams/create-dataflow/checklist.md","f420aaf346833dfda5454ffec9f90a680e903453bcc4d3e277d089e6781fec55"
+"md","checklist","bmm","bmm/workflows/diagrams/create-diagram/checklist.md","6357350a6e2237c1b819edd8fc847e376192bf802000cb1a4337c9584fc91a18"
+"md","checklist","bmm","bmm/workflows/diagrams/create-flowchart/checklist.md","45aaf882b8e9a1042683406ae2cfc0b23d3d39bd1dac3ddb0778d5b7165f7047"
+"md","checklist","bmm","bmm/workflows/diagrams/create-wireframe/checklist.md","588f9354bf366c173aa261cf5a8b3a87c878ea72fd2c0f8088c4b3289e984641"
+"md","checklist","bmm","bmm/workflows/document-project/checklist.md","2f1edb9e5e0b003f518b333ae842f344ff94d4dda7df07ba7f30c5b066013a68"
+"md","checklist","bmm","bmm/workflows/testarch/atdd/checklist.md","c4fa594d949dd8f1f818c11054b28643b458ab05ed90cf65f118deb1f4818e9f"
+"md","checklist","bmm","bmm/workflows/testarch/automate/checklist.md","bf1ae220c15c9f263967d1606658b19adcd37d57aef2b0faa30d34f01e5b0d22"
+"md","checklist","bmm","bmm/workflows/testarch/ci/checklist.md","13f19e4224f8106acb018ce87169329ab1bc9384f06328d6d2164b3b8b1629ce"
+"md","checklist","bmm","bmm/workflows/testarch/framework/checklist.md","16cc3aee710abb60fb85d2e92f0010b280e66b38fac963c0955fb36e7417103a"
+"md","checklist","bmm","bmm/workflows/testarch/nfr-assess/checklist.md","044416df40402db39eb660509eedadafc292c16edc247cf93812f2a325ee032c"
+"md","checklist","bmm","bmm/workflows/testarch/test-design/checklist.md","1a7e5e975d5a2bd3afd81e743e5ee3a2aa72571fce250caac24a6643808394eb"
+"md","checklist","bmm","bmm/workflows/testarch/test-review/checklist.md","0626c675114c23019e20e4ae2330a64baba43ad11774ff268c027b3c584a0891"
+"md","checklist","bmm","bmm/workflows/testarch/trace/checklist.md","a4468ae2afa9cf676310ec1351bb34317d5390e4a02ded9684cc15a62f2fd4fd"
+"md","ci-burn-in","bmm","bmm/testarch/knowledge/ci-burn-in.md","4cdcf7b576dae8b5cb591a6fad69674f65044a0dc72ea57d561623dac93ec475"
+"md","component-tdd","bmm","bmm/testarch/knowledge/component-tdd.md","88bd1f9ca1d5bcd1552828845fe80b86ff3acdf071bac574eda744caf7120ef8"
+"md","contract-testing","bmm","bmm/testarch/knowledge/contract-testing.md","d8f662c286b2ea4772213541c43aebef006ab6b46e8737ebdc4a414621895599"
+"md","data-factories","bmm","bmm/testarch/knowledge/data-factories.md","d7428fe7675da02b6f5c4c03213fc5e542063f61ab033efb47c1c5669b835d88"
+"md","deep-dive-instructions","bmm","bmm/workflows/document-project/workflows/deep-dive-instructions.md","8cb3d32d7685e5deff4731c2003d30b4321ef6c29247b3ddbe672c185e022604"
+"md","deep-dive-template","bmm","bmm/workflows/document-project/templates/deep-dive-template.md","6198aa731d87d6a318b5b8d180fc29b9aa53ff0966e02391c17333818e94ffe9"
+"md","documentation-standards","bmm","bmm/data/documentation-standards.md","fc26d4daff6b5a73eb7964eacba6a4f5cf8f9810a8c41b6949c4023a4176d853"
+"md","email-auth","bmm","bmm/testarch/knowledge/email-auth.md","43f4cc3138a905a91f4a69f358be6664a790b192811b4dfc238188e826f6b41b"
+"md","enterprise-agentic-development","bmm","bmm/docs/enterprise-agentic-development.md","e6bd84922c69224331e8fd193f5486e261866047982d921e268152659f789f1a"
+"md","epics-template","bmm","bmm/workflows/3-solutioning/create-epics-and-stories/templates/epics-template.md","b8ec5562b2a77efd80c40eba0421bbaab931681552e5a0ff01cd93902c447ff7"
+"md","error-handling","bmm","bmm/testarch/knowledge/error-handling.md","8a314eafb31e78020e2709d88aaf4445160cbefb3aba788b62d1701557eb81c1"
+"md","faq","bmm","bmm/docs/faq.md","e1f6d88aa6381cd86bd52a06b944e5db34adcd87069b0d5d2048a6e4d6b278e8"
+"md","feature-flags","bmm","bmm/testarch/knowledge/feature-flags.md","f6db7e8de2b63ce40a1ceb120a4055fbc2c29454ad8fca5db4e8c065d98f6f49"
+"md","file-utils","bmm","bmm/testarch/knowledge/file-utils.md","e0d4e98ca6ec32035ae07a14880c65ab99298e9240404d27a05788c974659e8b"
+"md","fixture-architecture","bmm","bmm/testarch/knowledge/fixture-architecture.md","a3b6c1bcaf5e925068f3806a3d2179ac11dde7149e404bc4bb5602afb7392501"
+"md","fixtures-composition","bmm","bmm/testarch/knowledge/fixtures-composition.md","8e57a897663a272fd603026aeec76941543c1e09d129e377846726fd405f3a5a"
+"md","full-scan-instructions","bmm","bmm/workflows/document-project/workflows/full-scan-instructions.md","6c6e0d77b33f41757eed8ebf436d4def69cd6ce412395b047bf5909f66d876aa"
+"md","glossary","bmm","bmm/docs/glossary.md","c50812db5de4331113205abe905da8aa95420c59f27c82751cd4136586927d32"
+"md","index-template","bmm","bmm/workflows/document-project/templates/index-template.md","42c8a14f53088e4fda82f26a3fe41dc8a89d4bcb7a9659dd696136378b64ee90"
+"md","instructions","bmm","bmm/workflows/4-implementation/correct-course/instructions.md","36bdc26a75adcba6aba508f3384512502d6640f96926742666e026f1eb380666"
+"md","instructions","bmm","bmm/workflows/4-implementation/retrospective/instructions.md","5508761efc7f88a54dc8de697977b6eccdd11f588f8469c1beb49ba70b2532af"
+"md","instructions","bmm","bmm/workflows/4-implementation/sprint-planning/instructions.md","655ca6098c868ae5775a5cc547e97273f10814af1c59a61d6e38543e6d4ab1ac"
+"md","instructions","bmm","bmm/workflows/4-implementation/sprint-status/instructions.md","7f6a8498f4bfb3c47073d70283a3c53ef174961c984ed6f10430d372638cb092"
+"md","instructions","bmm","bmm/workflows/bmad-quick-flow/create-tech-spec/instructions.md","4fe696440982bdfb01d936a20c55aea658d934786ec9918b4080e36730c5ad4d"
+"md","instructions","bmm","bmm/workflows/bmad-quick-flow/quick-dev/instructions.md","3b5f3f5040289389f1aadbf61c9ca6ed18ed743dc0d50ec946d441848deabdf4"
+"md","instructions","bmm","bmm/workflows/diagrams/create-dataflow/instructions.md","d07ed411e68fce925af5e59800e718406a783f8b94dadaa42425f3a33f460637"
+"md","instructions","bmm","bmm/workflows/diagrams/create-diagram/instructions.md","231d3ce0f0fe0f8af9010acebf2720eb858a45ea34cd1e7ec8385878bcd5e27f"
+"md","instructions","bmm","bmm/workflows/diagrams/create-flowchart/instructions.md","36e8b3327dd6c97270f11de6f3bea346c17dd1b0e25fef65245fe166b00a2543"
+"md","instructions","bmm","bmm/workflows/diagrams/create-wireframe/instructions.md","60309b71a73d1bee9804aaf63228c917066b8da64b929b32813b1d0411a8b8b2"
+"md","instructions","bmm","bmm/workflows/document-project/instructions.md","da53bc02e056f83987e55a19939ecd3319b98a6de1a6eddde08c9a002636e249"
+"md","instructions","bmm","bmm/workflows/testarch/atdd/instructions.md","eef9fc4eb4b866bacfc3e5b85a492c0f45530640c648cbe1dbbc78885db9a21e"
+"md","instructions","bmm","bmm/workflows/testarch/automate/instructions.md","49b5979463bd683271df610128e174ec08725e351500dbc2aa05b8b19e99d56c"
+"md","instructions","bmm","bmm/workflows/testarch/ci/instructions.md","bd4b8ef35428a9c046a926c7467920ac9c0de90e1222bf5bf7671f4ac6d1f429"
+"md","instructions","bmm","bmm/workflows/testarch/framework/instructions.md","14009ff970a6dbce184439b466eac968abc26667271217981c314c1911a09db9"
+"md","instructions","bmm","bmm/workflows/testarch/nfr-assess/instructions.md","7de16907253721c8baae2612be35325c6fa543765377783763a09739fa71f072"
+"md","instructions","bmm","bmm/workflows/testarch/test-design/instructions.md","abe606f1b1daeb6da224ad8868515f7a3bdc1dcca95b74b3b53b891df8f6ecec"
+"md","instructions","bmm","bmm/workflows/testarch/test-review/instructions.md","615eed020131c681f77ec2405559e40c38f3b6789b81c2effb3cb759fd674d1a"
+"md","instructions","bmm","bmm/workflows/testarch/trace/instructions.md","fe499a09c4bebbff0a0bce763ced2c36bee5c36b268a4abb4e964a309ff2fa20"
+"md","instructions","bmm","bmm/workflows/workflow-status/init/instructions.md","4377ed6015f4e0a6b9c85b68343f3ebcefefe5f08c77386d280ed9d13adfd592"
+"md","instructions","bmm","bmm/workflows/workflow-status/instructions.md","ee1d418a8360906a505abc019e22fbd94a0bc7deaf7b8d5e4684240028b1b485"
+"md","intercept-network-call","bmm","bmm/testarch/knowledge/intercept-network-call.md","fb551cb0cefe3c062c28ae255a121aaae098638ec35a16fcdba98f670887ab6a"
+"md","log","bmm","bmm/testarch/knowledge/log.md","b6267716ccbe6f9e2cc1b2b184501faeb30277bc8546206a66f31500c52381d0"
+"md","network-error-monitor","bmm","bmm/testarch/knowledge/network-error-monitor.md","0380eb6df15af0a136334ad00cf44c92c779f311b07231f5aa6230e198786799"
+"md","network-first","bmm","bmm/testarch/knowledge/network-first.md","2920e58e145626f5505bcb75e263dbd0e6ac79a8c4c2ec138f5329e06a6ac014"
+"md","network-recorder","bmm","bmm/testarch/knowledge/network-recorder.md","9f120515cc377c4c500ec0b5fff0968666a9a4edee03a328d92514147d50f073"
+"md","nfr-criteria","bmm","bmm/testarch/knowledge/nfr-criteria.md","e63cee4a0193e4858c8f70ff33a497a1b97d13a69da66f60ed5c9a9853025aa1"
+"md","nfr-report-template","bmm","bmm/workflows/testarch/nfr-assess/nfr-report-template.md","b1d8fcbdfc9715a285a58cb161242dea7d311171c09a2caab118ad8ace62b80c"
+"md","overview","bmm","bmm/testarch/knowledge/overview.md","bae70e1489fc29692a40e83e605f63a8c82cfde7db1c58b15b565dc5cdee49d4"
+"md","party-mode","bmm","bmm/docs/party-mode.md","7acadc96c7235695a88cba42b5642e1ee3a7f96eb2264862f629e1d4280b9761"
+"md","playwright-config","bmm","bmm/testarch/knowledge/playwright-config.md","42516511104a7131775f4446196cf9e5dd3295ba3272d5a5030660b1dffaa69f"
+"md","prd-template","bmm","bmm/workflows/2-plan-workflows/prd/prd-template.md","77e54c1f7e16986be40c8ff411e954894492ef678fd21f310dd77e62d87b5315"
+"md","probability-impact","bmm","bmm/testarch/knowledge/probability-impact.md","446dba0caa1eb162734514f35366f8c38ed3666528b0b5e16c7f03fd3c537d0f"
+"md","product-brief.template","bmm","bmm/workflows/1-analysis/product-brief/product-brief.template.md","0993d8a5b0bb42d1aebd092e726d0829bdcab6ccfa227dc3816626366e8ccf8c"
+"md","project-context-template","bmm","bmm/data/project-context-template.md","34421aed3e0ad921dc0c0080297f3a2299735b00a25351de589ada99dae56559"
+"md","project-context-template","bmm","bmm/workflows/generate-project-context/project-context-template.md","df2e7d5a78f80e96e90891219c6770849a6a4a61670cd80561d1c47a6302b974"
+"md","project-overview-template","bmm","bmm/workflows/document-project/templates/project-overview-template.md","a7c7325b75a5a678dca391b9b69b1e3409cfbe6da95e70443ed3ace164e287b2"
+"md","quick-flow-solo-dev","bmm","bmm/docs/quick-flow-solo-dev.md","8ca0bb322aeebe7ceff2598920eae6f8e450759cf1a232ad55efba71d94d6edf"
+"md","quick-spec-flow","bmm","bmm/docs/quick-spec-flow.md","e732f1d06040a38393c2621cf89736bdb652dd57fc38f341d262c4aaacb77eb2"
+"md","quick-start","bmm","bmm/docs/quick-start.md","46307514eff57cc42d6580afedda259f44f64913576e51169df446b8a45884bf"
+"md","readiness-report-template","bmm","bmm/workflows/3-solutioning/implementation-readiness/templates/readiness-report-template.md","0da97ab1e38818e642f36dc0ef24d2dae69fc6e0be59924dc2dbf44329738ff6"
+"md","README","bmm","bmm/README.md","ad4e6d0c002e3a5fef1b695bda79e245fe5a43345375c699165b32d6fc511457"
+"md","README","bmm","bmm/data/README.md","352c44cff4dd0e5a90cdf6781168ceb57f5a78eaabddcd168433d8784854e4fb"
+"md","README","bmm","bmm/docs/README.md","778ecc53301f36398a86dc3e9b7a7476281601e9d835d60f288653062641e3ba"
+"md","README","bmm","bmm/docs/images/README.md","4f9c7bdfeef5599172046e8f3165e2c95d67d4749448e689ebfc507b39a65679"
+"md","recurse","bmm","bmm/testarch/knowledge/recurse.md","19056fb5b7e5e626aad81277b3e5eec333f2aed36a17aea6c7d8714a5460c8b2"
+"md","research.template","bmm","bmm/workflows/1-analysis/research/research.template.md","f556c1797899e279c453b654fad1830deb65da3726b6349b1ad8ddec0fa43543"
+"md","risk-governance","bmm","bmm/testarch/knowledge/risk-governance.md","2fa2bc3979c4f6d4e1dec09facb2d446f2a4fbc80107b11fc41cbef2b8d65d68"
+"md","scale-adaptive-system","bmm","bmm/docs/scale-adaptive-system.md","343e3772c2e24e9ddd6b9278f72e48dc7be961ee5ad23496003cc17cac57314c"
+"md","selective-testing","bmm","bmm/testarch/knowledge/selective-testing.md","c14c8e1bcc309dbb86a60f65bc921abf5a855c18a753e0c0654a108eb3eb1f1c"
+"md","selector-resilience","bmm","bmm/testarch/knowledge/selector-resilience.md","a55c25a340f1cd10811802665754a3f4eab0c82868fea61fea9cc61aa47ac179"
+"md","source-tree-template","bmm","bmm/workflows/document-project/templates/source-tree-template.md","109bc335ebb22f932b37c24cdc777a351264191825444a4d147c9b82a1e2ad7a"
+"md","step-01-discover","bmm","bmm/workflows/generate-project-context/steps/step-01-discover.md","150bbebcbfbe5f4b57ad0fc4a3b2b992d9dc537c3e3c018c47e267abf6f886a3"
+"md","step-01-document-discovery","bmm","bmm/workflows/3-solutioning/implementation-readiness/steps/step-01-document-discovery.md","ce231c3d88c9cb014a940b671f5dc25b69db8a297a3f226e1a9ffbc3aedd181d"
+"md","step-01-init","bmm","bmm/workflows/1-analysis/product-brief/steps/step-01-init.md","8fe8b488f6766456ba0dc9ac7d45e145c1266dcaca4633ae850c101381d4db54"
+"md","step-01-init","bmm","bmm/workflows/1-analysis/research/domain-steps/step-01-init.md","c880668be8190af4db0df42cf1609097c747478b048b6ba2554fc7044444a3b3"
+"md","step-01-init","bmm","bmm/workflows/1-analysis/research/market-steps/step-01-init.md","e47f961651ad449964cbbd16f39f0a34b2e7ffa0da7e9d06a8a361329e2d7ba1"
+"md","step-01-init","bmm","bmm/workflows/1-analysis/research/technical-steps/step-01-init.md","4d6ed6afc591c556dda2284265960cf74ea7e8c4d65108edb3278043fc915ef1"
+"md","step-01-init","bmm","bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01-init.md","8c0811939c75acc2400c4670ac0a3721d8d8df1564119e625ea6a70bb56e5ace"
+"md","step-01-init","bmm","bmm/workflows/2-plan-workflows/prd/steps/step-01-init.md","b2d8ce68633dbecc4cd32d4df8e6068731de8dc61faf1ddafbb651af3f87baee"
+"md","step-01-init","bmm","bmm/workflows/3-solutioning/architecture/steps/step-01-init.md","f464457c30fef1dcc5b5fd31d3feef8aa807f16f85f998d61e5fa9391aa02774"
+"md","step-01-validate-prerequisites","bmm","bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md","4f1c61d1379a07c28d058a48efb16c805b303e2ab19dbf2743ee68778dba2765"
+"md","step-01b-continue","bmm","bmm/workflows/1-analysis/product-brief/steps/step-01b-continue.md","029570dbfd0cede406fd6de79e9196d9a673007f2b3687c4ff9a6d1380c1a4cf"
+"md","step-01b-continue","bmm","bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01b-continue.md","e897baf661717873e781abfea7b0f30dc0fc5668e8dfb87511f8d848e4429e78"
+"md","step-01b-continue","bmm","bmm/workflows/2-plan-workflows/prd/steps/step-01b-continue.md","0401baf1faad67432912ae6e5a3755eca2764a09b7fafde21f7b40388c81a0ce"
+"md","step-01b-continue","bmm","bmm/workflows/3-solutioning/architecture/steps/step-01b-continue.md","4188f4abe9674b83108571317f8be8e35fc95d51d156397827dded6ef7429213"
+"md","step-02-context","bmm","bmm/workflows/3-solutioning/architecture/steps/step-02-context.md","2875692c74095e5f9eedf88bb461c56685373a938ee436bddbfa1e1304c60956"
+"md","step-02-customer-behavior","bmm","bmm/workflows/1-analysis/research/market-steps/step-02-customer-behavior.md","fb25681e5e731736df99f7a3cc3ecf3181d8faea0a872fb5b5d3bdc3d98c3266"
+"md","step-02-customer-insights","bmm","bmm/workflows/1-analysis/research/market-steps/step-02-customer-insights.md","3c516f4958f55f9732838238a45948987a7a88cab14c9c469f5d03a1f5b4a375"
+"md","step-02-design-epics","bmm","bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-02-design-epics.md","4a58e62aa46ec866b43ff04e842ca45219eddaa932cc8c4f9543ba1bad9fb491"
+"md","step-02-discovery","bmm","bmm/workflows/2-plan-workflows/create-ux-design/steps/step-02-discovery.md","a618c7b9c1cc8fa4ac859e36b979cbbfa66fee8d2e50015f902cc8fbe7c6ddcb"
+"md","step-02-discovery","bmm","bmm/workflows/2-plan-workflows/prd/steps/step-02-discovery.md","76323855c878faf2c2a2e03a881c5742a7d8915dc3aa4817fba5649433e4479a"
+"md","step-02-domain-analysis","bmm","bmm/workflows/1-analysis/research/domain-steps/step-02-domain-analysis.md","f0281c46b50151af72d28bf71fbf70e451b89b01dd1e0607d5c4c8d45a9fe9a3"
+"md","step-02-generate","bmm","bmm/workflows/generate-project-context/steps/step-02-generate.md","3ce90684fcbe072c568f53e0518dafbe2cddbf9b78195ace806f277374c2e7a1"
+"md","step-02-prd-analysis","bmm","bmm/workflows/3-solutioning/implementation-readiness/steps/step-02-prd-analysis.md","309a073dcaa2a4beaa7f75da4b6955582c1504d93ac860c2369b351a1d054e9f"
+"md","step-02-technical-overview","bmm","bmm/workflows/1-analysis/research/technical-steps/step-02-technical-overview.md","dfef6c9c0054dbf4a9faf43a7f577a0296a69ab1a1e2fe9aa64affdad3dee84b"
+"md","step-02-vision","bmm","bmm/workflows/1-analysis/product-brief/steps/step-02-vision.md","3c880759b86ff79b9bfa28bd55eb3a90d8bdaf79ed010467ba7fb0906f5b5bd7"
+"md","step-03-competitive-landscape","bmm","bmm/workflows/1-analysis/research/domain-steps/step-03-competitive-landscape.md","bdb6b7ad4157c50fe5cb7b87aaa332a32f2581468afda783dec77efb1761805d"
+"md","step-03-complete","bmm","bmm/workflows/generate-project-context/steps/step-03-complete.md","9158815e89b1ac9c959502a8dfcff0c019a736aabea7d7e6f319984f65ba5c73"
+"md","step-03-core-experience","bmm","bmm/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md","be36e09b94f46140b84af7bfecad7b0dc2513c057b9a72969f5e1a7c56673426"
+"md","step-03-create-stories","bmm","bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-03-create-stories.md","8ae4f79b022613766cd63bc9221b4854c23c99fb0c90671bcf77f02422c4644b"
+"md","step-03-customer-pain-points","bmm","bmm/workflows/1-analysis/research/market-steps/step-03-customer-pain-points.md","63f5e16bf31da6a377812744fcc03fc886e6e84f30685d383836c688466049ff"
+"md","step-03-epic-coverage-validation","bmm","bmm/workflows/3-solutioning/implementation-readiness/steps/step-03-epic-coverage-validation.md","b14e4ebde6bbb56ffbd337c3b895a9036f9b6d38eebf81b83b52e3f1d4f319bf"
+"md","step-03-integration-patterns","bmm","bmm/workflows/1-analysis/research/technical-steps/step-03-integration-patterns.md","516d5543ebe5f9004dc6ff7e09428704cbb85baf5aa33f2693d57515f43cc43e"
+"md","step-03-starter","bmm","bmm/workflows/3-solutioning/architecture/steps/step-03-starter.md","d6c517d59bd51bcd19f7bc2978b102ea14f1e7bd23de14b07acab3d8ec3d27fc"
+"md","step-03-success","bmm","bmm/workflows/2-plan-workflows/prd/steps/step-03-success.md","b1a9d4bce7ec0f4239968d4e763e6f6cf41865ea79c2cd26a002199bfa9b7ff2"
+"md","step-03-users","bmm","bmm/workflows/1-analysis/product-brief/steps/step-03-users.md","bcbc8a7d46c892fe235feec68e5d15864c934dcbe71bcefa590e156ed47b32e7"
+"md","step-04-architectural-patterns","bmm","bmm/workflows/1-analysis/research/technical-steps/step-04-architectural-patterns.md","9e7d6107622625fa95ad2de6cbfdeb6b52864e78a4dcf3707d1f6202c53c4851"
+"md","step-04-customer-decisions","bmm","bmm/workflows/1-analysis/research/market-steps/step-04-customer-decisions.md","79b952a9d41819dfd448a058525450e7894a8d6bf15dbbbcfd60d6698c24db94"
+"md","step-04-decisions","bmm","bmm/workflows/3-solutioning/architecture/steps/step-04-decisions.md","936ba06a19f3fff6858dfcd7c119065066ea0e3ca37a7076c08b4d0e9439e8c3"
+"md","step-04-emotional-response","bmm","bmm/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md","ecaf542e3e73423898a1d7ff12cc183e9ccf94110e934fbe731765627f684513"
+"md","step-04-final-validation","bmm","bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md","1761893b0eca2f0cc173a5be823de42dfe9b6980d9bbb98b16ae6cbd16e3b13f"
+"md","step-04-journeys","bmm","bmm/workflows/2-plan-workflows/prd/steps/step-04-journeys.md","f1342c23fbc3d6d607dd3764b4d4c4344d2c582631f0f20d50c4da65d1599e07"
+"md","step-04-metrics","bmm","bmm/workflows/1-analysis/product-brief/steps/step-04-metrics.md","6e4c8aaa2577e2608df8dc1ac6893c38b406c4e292ba4673221c685c65275380"
+"md","step-04-regulatory-focus","bmm","bmm/workflows/1-analysis/research/domain-steps/step-04-regulatory-focus.md","6fd786eb13f598569dca4e1b75f9d21b9be97721219c89743c08d7f7779c9c26"
+"md","step-04-ux-alignment","bmm","bmm/workflows/3-solutioning/implementation-readiness/steps/step-04-ux-alignment.md","52b0d64f014425a6f89ccd020c5f2773398c2bbdea7d3c239dfa2b90f53d87de"
+"md","step-05-competitive-analysis","bmm","bmm/workflows/1-analysis/research/market-steps/step-05-competitive-analysis.md","5e6053df3323fdb561871881989d33e696fd43270cfed98c0064e409031f42b4"
+"md","step-05-domain","bmm","bmm/workflows/2-plan-workflows/prd/steps/step-05-domain.md","5dfcd708499c211e9f91b360740ad8fe734f4bc9da55c49b0f8034ddb930cfe1"
+"md","step-05-epic-quality-review","bmm","bmm/workflows/3-solutioning/implementation-readiness/steps/step-05-epic-quality-review.md","e6a90281966eed2cfa06223f65848119ffa8e93d7e932ee92ccb701f0d5accff"
+"md","step-05-implementation-research","bmm","bmm/workflows/1-analysis/research/technical-steps/step-05-implementation-research.md","f8067535a667f5e367e85844599ef92848872bdb57bff1dfcdad3aefb1c6512a"
+"md","step-05-inspiration","bmm","bmm/workflows/2-plan-workflows/create-ux-design/steps/step-05-inspiration.md","cd3c0612dacb466d8c8c1cebba688852f32dd188e8bc7ae3405be18b779be1e6"
+"md","step-05-patterns","bmm","bmm/workflows/3-solutioning/architecture/steps/step-05-patterns.md","3fff9ec3b093a089b332fb905728dc5c9206cab9ce0ee8dcecf389a123b4d8ad"
+"md","step-05-scope","bmm","bmm/workflows/1-analysis/product-brief/steps/step-05-scope.md","fa80e32015904b2f88fe210c64842d10b996bbd074529b36b91ef23199c4dfaa"
+"md","step-05-technical-trends","bmm","bmm/workflows/1-analysis/research/domain-steps/step-05-technical-trends.md","4923fbc706e69ff2fdff372284e103ad1db5c9ed7486a77a00f9c494a90966a6"
+"md","step-06-complete","bmm","bmm/workflows/1-analysis/product-brief/steps/step-06-complete.md","4265c8e99832037f2a9e9cff8430a0775aec6c500765468b93abc316d136ad0d"
+"md","step-06-design-system","bmm","bmm/workflows/2-plan-workflows/create-ux-design/steps/step-06-design-system.md","21548ba370fcebd0ee14178e0beff84930523e166c8b570ac0a590ab66459970"
+"md","step-06-final-assessment","bmm","bmm/workflows/3-solutioning/implementation-readiness/steps/step-06-final-assessment.md","7a1630b701947ad6e3478ca53190e42d4ebf20818de952f8f7f3dab19d74aff0"
+"md","step-06-innovation","bmm","bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md","9083b908aaf5f196f4bb1391dd2334b857d43f7ed097e118a40213c000e4880d"
+"md","step-06-research-completion","bmm","bmm/workflows/1-analysis/research/market-steps/step-06-research-completion.md","72d52d60cb2eb00402b96f64f3d44f252326f6b7c713dfe73c6a055325919f18"
+"md","step-06-research-synthesis","bmm","bmm/workflows/1-analysis/research/domain-steps/step-06-research-synthesis.md","b8c29bb261f3cfe2ec06d69c4c2fbce4fb945f628168143d33667a5295648b49"
+"md","step-06-research-synthesis","bmm","bmm/workflows/1-analysis/research/technical-steps/step-06-research-synthesis.md","78d3cdb130563cf819baf397bdc8dd27159264be74d86d3ec83795aa78bffde3"
+"md","step-06-structure","bmm","bmm/workflows/3-solutioning/architecture/steps/step-06-structure.md","61e4b0c0fb330f13bea220f0c9c8e4f756e9ac19ae3e2b3dfafdbc4a8a4e01c7"
+"md","step-07-defining-experience","bmm","bmm/workflows/2-plan-workflows/create-ux-design/steps/step-07-defining-experience.md","739d82e834c5bc65a7ec0f4b356b5beb79c782fa4a93b1651beb1468f8f7a087"
+"md","step-07-project-type","bmm","bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md","7ff98e4411f8d46bb7a0c212f25b5e04a5035ee425f8af3011887707d18f7c85"
+"md","step-07-validation","bmm","bmm/workflows/3-solutioning/architecture/steps/step-07-validation.md","83ff68cce8340a603ee8dd028aaace6bf85f92c810422b89b94c57a8ef541df5"
+"md","step-08-complete","bmm","bmm/workflows/3-solutioning/architecture/steps/step-08-complete.md","87f452c0d8d023166f6805494ef10624e11b3793472411b922b02c006cf723b4"
+"md","step-08-scoping","bmm","bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md","1b3d08ebacb86dd5e3f4e5724ad0b68c87347e1bb0df2ef6cd0dc6618dd0c59a"
+"md","step-08-visual-foundation","bmm","bmm/workflows/2-plan-workflows/create-ux-design/steps/step-08-visual-foundation.md","fa7e5214293a97225a55be1aa0277e6d5bc545ef9cbec84f45f6d6e4a655a40c"
+"md","step-09-design-directions","bmm","bmm/workflows/2-plan-workflows/create-ux-design/steps/step-09-design-directions.md","352e5636a19798e7fa118bd10958e13dd1e2c4ac4e3c111cfc5a4a9c1dbe469e"
+"md","step-09-functional","bmm","bmm/workflows/2-plan-workflows/prd/steps/step-09-functional.md","9adbc4f021bdcf06cca3de1b4ac6bae5c1bb62eb146d0b741471eb5697b0a400"
+"md","step-10-nonfunctional","bmm","bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md","3f4bf931ce6b5aa57aebdb9bb9c0e1bae35ce83e3430bac58a9cb35ef571aae0"
+"md","step-10-user-journeys","bmm","bmm/workflows/2-plan-workflows/create-ux-design/steps/step-10-user-journeys.md","b258da09427d558f9f78a292146be9f2fc927cdedc20cf0ee2278b90e0f5435d"
+"md","step-11-complete","bmm","bmm/workflows/2-plan-workflows/prd/steps/step-11-complete.md","607cd870d37099413c032d93dd3b78f5ba85ce69228c11afc6d4f83055a0ee0e"
+"md","step-11-component-strategy","bmm","bmm/workflows/2-plan-workflows/create-ux-design/steps/step-11-component-strategy.md","3329c3b913802be8d5cc02e75b532796c6ffd45f4212830c2a919ccd0a2457ca"
+"md","step-12-ux-patterns","bmm","bmm/workflows/2-plan-workflows/create-ux-design/steps/step-12-ux-patterns.md","62bc6dfe807b6b57ac853dd52e8820703a23fdeee618710034c0486fbc222c9b"
+"md","step-13-responsive-accessibility","bmm","bmm/workflows/2-plan-workflows/create-ux-design/steps/step-13-responsive-accessibility.md","d74240090a320468b9e5e961bbbf8375f0aa3599e65ceadfb6c291ef48b34e7e"
+"md","step-14-complete","bmm","bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md","833ba63b697ba5f8e35a7d53784c2646ce4e1726ce2dfa53bf3a9fb6880ba532"
+"md","template","bmm","bmm/workflows/4-implementation/create-story/template.md","83c5d21312c0f2060888a2a8ba8332b60f7e5ebeb9b24c9ee59ba96114afb9c9"
+"md","test-architecture","bmm","bmm/docs/test-architecture.md","47a154c44d69adbac3cd7a0ec5f6f436349c4f5865b73d803f4940e8eea6f21c"
+"md","test-design-template","bmm","bmm/workflows/testarch/test-design/test-design-template.md","0902ec300d59458bcfc2df24da2622b607b557f26e6d407e093b7c7dbc515ba5"
+"md","test-healing-patterns","bmm","bmm/testarch/knowledge/test-healing-patterns.md","b44f7db1ebb1c20ca4ef02d12cae95f692876aee02689605d4b15fe728d28fdf"
+"md","test-levels-framework","bmm","bmm/testarch/knowledge/test-levels-framework.md","80bbac7959a47a2e7e7de82613296f906954d571d2d64ece13381c1a0b480237"
+"md","test-priorities-matrix","bmm","bmm/testarch/knowledge/test-priorities-matrix.md","321c3b708cc19892884be0166afa2a7197028e5474acaf7bc65c17ac861964a5"
+"md","test-quality","bmm","bmm/testarch/knowledge/test-quality.md","97b6db474df0ec7a98a15fd2ae49671bb8e0ddf22963f3c4c47917bb75c05b90"
+"md","test-review-template","bmm","bmm/workflows/testarch/test-review/test-review-template.md","3e68a73c48eebf2e0b5bb329a2af9e80554ef443f8cd16652e8343788f249072"
+"md","timing-debugging","bmm","bmm/testarch/knowledge/timing-debugging.md","c4c87539bbd3fd961369bb1d7066135d18c6aad7ecd70256ab5ec3b26a8777d9"
+"md","trace-template","bmm","bmm/workflows/testarch/trace/trace-template.md","5453a8e4f61b294a1fc0ba42aec83223ae1bcd5c33d7ae0de6de992e3ee42b43"
+"md","troubleshooting","bmm","bmm/docs/troubleshooting.md","cc0195444117d4aee1c41da16d9bee1897d412b6e2f52566f50f50a1e412b6f4"
+"md","ux-design-template","bmm","bmm/workflows/2-plan-workflows/create-ux-design/ux-design-template.md","ffa4b89376cd9db6faab682710b7ce755990b1197a8b3e16b17748656d1fca6a"
+"md","visual-debugging","bmm","bmm/testarch/knowledge/visual-debugging.md","072a3d30ba6d22d5e628fc26a08f6e03f8b696e49d5a4445f37749ce5cd4a8a9"
+"md","workflow","bmm","bmm/workflows/1-analysis/product-brief/workflow.md","8433aa07a09c741cada483a828921f252c90dcf9f6d1f8e3618cd086cb5cdcad"
+"md","workflow","bmm","bmm/workflows/1-analysis/research/workflow.md","6e512542fa15b8c7d6a3edec3247d38865a2d1e06df8d4010ca91b0878d5ace6"
+"md","workflow","bmm","bmm/workflows/2-plan-workflows/create-ux-design/workflow.md","609c1bb6d760418258694a6d3021b77b5be470aee7f2692a33c914ce78c44516"
+"md","workflow","bmm","bmm/workflows/2-plan-workflows/prd/workflow.md","e5e912a67f5e1864d0a2f37fa6f9d18420e7780bd7b3f3e8f9d5bd90e3bad5ae"
+"md","workflow","bmm","bmm/workflows/3-solutioning/architecture/workflow.md","39c901db8f433cec6492eabcb231bd6048dd05f4792516db9787f165483400e0"
+"md","workflow","bmm","bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md","623b0a05746ea4e6c9c8801616829dd7722a3eb83b6136a3b30baa94b965bfc8"
+"md","workflow","bmm","bmm/workflows/3-solutioning/implementation-readiness/workflow.md","7d8e7877b2d21ea5fb42c2cd1dc9615b423455e05fcf62e8c542d6413bada3de"
+"md","workflow","bmm","bmm/workflows/generate-project-context/workflow.md","e9bd71f07d28f8b038267fecbef17af489f7cc03540d5c326132b218c485b276"
+"md","workflow-architecture-reference","bmm","bmm/docs/workflow-architecture-reference.md","36efd4e3d74d1739455e896e62b7711bf4179c572f1eef7a7fae7f2385adcc6d"
+"md","workflow-document-project-reference","bmm","bmm/docs/workflow-document-project-reference.md","a261abcaad05e63d7f1231bd9a2db66f9e29e4bb4b161ec997564906febfb66c"
+"md","workflows-analysis","bmm","bmm/docs/workflows-analysis.md","351e7375bd1ac13ae6a4125091f13b3c10dfdada984252fc773f4128f2db110d"
+"md","workflows-implementation","bmm","bmm/docs/workflows-implementation.md","b89677b0ba23d5751af9927159e4a9b2cf305655e8110024131e9f596cc119df"
+"md","workflows-planning","bmm","bmm/docs/workflows-planning.md","be3e0347cb26380b4f978c7311efc033b01bd416c8cfbac4e3dec940ca99b2b4"
+"md","workflows-solutioning","bmm","bmm/docs/workflows-solutioning.md","fbaca970023e55b4635fb06448fbc0279b36bcc54b626025bc11fdbdedfe3ff8"
+"svg","workflow-method-greenfield","bmm","bmm/docs/images/workflow-method-greenfield.svg","f0ce562d058e6edb114a8ae8bc51fa6a71394c08c0ac16aae07d959c88c6dcca"
+"xml","daily-standup","bmm","bmm/tasks/daily-standup.xml","0ae12d1c1002120a567611295e201c9d11eb64618b935d7ef586257103934224"
+"xml","instructions","bmm","bmm/workflows/4-implementation/code-review/instructions.xml","231c3bc4f26e3cff97fc75a5cda12cf20586868c813a06e5f9f834c4ec527cb8"
+"xml","instructions","bmm","bmm/workflows/4-implementation/create-story/instructions.xml","7af2c0d3539298cea997b256defe1bb10fd84a79282db189eec6a00c7d1534b2"
+"xml","instructions","bmm","bmm/workflows/4-implementation/dev-story/instructions.xml","d6df4313bda13e70744baa4149609a0616c826ce660aa5c323597a763426d8d5"
+"yaml","config","bmm","bmm/config.yaml","ca8df1fd348f254066a66fbd0257282b3e5de7c95be55344100d0ab299a0b3ad"
+"yaml","deep-dive","bmm","bmm/workflows/document-project/workflows/deep-dive.yaml","c401fb8d94ca96f3bb0ccc1146269e1bfa4ce4eadab52bd63c7fcff6c2f26216"
+"yaml","enterprise-brownfield","bmm","bmm/workflows/workflow-status/paths/enterprise-brownfield.yaml","04a43e86f644949302cd5d4d801fb2ccdbb0f66b75609bc1fa712fd5c3bce675"
+"yaml","enterprise-greenfield","bmm","bmm/workflows/workflow-status/paths/enterprise-greenfield.yaml","20bda9331b02335c24f1686aab29183801d5de6cd40cadb4fd7472ee643cc8ab"
+"yaml","excalidraw-templates","bmm","bmm/workflows/diagrams/_shared/excalidraw-templates.yaml","ca6e4ae85b5ab16df184ce1ddfdf83b20f9540db112ebf195cb793017f014a70"
+"yaml","full-scan","bmm","bmm/workflows/document-project/workflows/full-scan.yaml","3d2e620b58902ab63e2d83304180ecd22ba5ab07183b3afb47261343647bde6f"
+"yaml","github-actions-template","bmm","bmm/workflows/testarch/ci/github-actions-template.yaml","cf7d1f0a1f2853b07df1b82b00ebe79f800f8f16817500747b7c4c9c7143aba7"
+"yaml","gitlab-ci-template","bmm","bmm/workflows/testarch/ci/gitlab-ci-template.yaml","986f29817e04996ab9f80bf2de0d25d8ed2365d955cc36d5801afaa93e99e80b"
+"yaml","method-brownfield","bmm","bmm/workflows/workflow-status/paths/method-brownfield.yaml","35365c7af516ba2205d16e19a656695890e53678613bf835d490c338b7467b59"
+"yaml","method-greenfield","bmm","bmm/workflows/workflow-status/paths/method-greenfield.yaml","9f84ab40aa4c7984fd4e948f3f55823066e94fcbf1d16d207aee2a731e5c38ba"
+"yaml","project-levels","bmm","bmm/workflows/workflow-status/project-levels.yaml","414b9aefff3cfe864e8c14b55595abfe3157fd20d9ee11bb349a2b8c8e8b5449"
+"yaml","sprint-status-template","bmm","bmm/workflows/4-implementation/sprint-planning/sprint-status-template.yaml","fd63abf2268b20df2c42144de5dc274b165539b237efed8711d932fd31705cd9"
+"yaml","team-fullstack","bmm","bmm/teams/team-fullstack.yaml","da8346b10dfad8e1164a11abeb3b0a84a1d8b5f04e01e8490a44ffca477a1b96"
+"yaml","workflow","bmm","bmm/workflows/4-implementation/code-review/workflow.yaml","32b79a35778279604f4b4ef3aa4092b1e9cf68bc3a995811ce300c585467353c"
+"yaml","workflow","bmm","bmm/workflows/4-implementation/correct-course/workflow.yaml","53bc0f2bc058cabf28febb603fd9be5d1171f6c8db14715ab65e7a0798bde696"
+"yaml","workflow","bmm","bmm/workflows/4-implementation/create-story/workflow.yaml","af643ca53116b47bf9eb6ba40637202e2eaea54e8f2082c34949e9c02e36c876"
+"yaml","workflow","bmm","bmm/workflows/4-implementation/dev-story/workflow.yaml","0e7a654791dd939458df2df4c89f745f1adc1dd0582bc7172094a8560b3ff262"
+"yaml","workflow","bmm","bmm/workflows/4-implementation/retrospective/workflow.yaml","f9ccda4e0e7728797ce021f5ae40e5d5632450453471d932a8b7577c600f9434"
+"yaml","workflow","bmm","bmm/workflows/4-implementation/sprint-planning/workflow.yaml","a594814b3a0860a9cb7cc24ad9f3dcbdec990ad870e404e4f25c4cedd9abe4f0"
+"yaml","workflow","bmm","bmm/workflows/4-implementation/sprint-status/workflow.yaml","0d50b7da7ecd3696704d6a19b917a840bd6c1a1b78e28b6d81d8b3cd3cf2304f"
+"yaml","workflow","bmm","bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml","1fc651cbd6d67d1991c60ff066428e73fece37d66b110d61fa96f4c0e44f44a5"
+"yaml","workflow","bmm","bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml","b1ba864f0a591a8309c9295bbfc068019494577611cc2a68207867ca80cf986b"
+"yaml","workflow","bmm","bmm/workflows/diagrams/create-dataflow/workflow.yaml","58e9c6b6c99e68d166ec3491ae3299d9f662480da39b5f21afa5bf7ccc82d7ad"
+"yaml","workflow","bmm","bmm/workflows/diagrams/create-diagram/workflow.yaml","4ae7bb7fe57d40ef357ff74732ac672e2094691ae5f4a67515bf37c504604c4a"
+"yaml","workflow","bmm","bmm/workflows/diagrams/create-flowchart/workflow.yaml","fde7e2dc8920839f0ad7012520fcbabf4fda004c38de546d891a987a29694e57"
+"yaml","workflow","bmm","bmm/workflows/diagrams/create-wireframe/workflow.yaml","511a7d17d13c5cbc57a1d2c3f73d1a79b2952aa40242f3c6d1117901bb5c495b"
+"yaml","workflow","bmm","bmm/workflows/document-project/workflow.yaml","219333bb489c0aa0b2538a4801a381502a9f581839889262f6ef102ea4d54be7"
+"yaml","workflow","bmm","bmm/workflows/testarch/atdd/workflow.yaml","e0c095c8844f0a92f961e3570d5887b8a7be39a6a2e8c7c449f13eb9cf3e0fb9"
+"yaml","workflow","bmm","bmm/workflows/testarch/automate/workflow.yaml","b7b3d6552f8d3e2a0d9243fca27e30ad5103e38798fadd02b6b376b3f0532aac"
+"yaml","workflow","bmm","bmm/workflows/testarch/ci/workflow.yaml","d8d59916c937fef9ee5e2c454cfa0cda33e58d21b211d562a05681587b8fdde0"
+"yaml","workflow","bmm","bmm/workflows/testarch/framework/workflow.yaml","2774679175fed88d0ef21be44418a26a82a5b9d1aa08c906373a638e7877d523"
+"yaml","workflow","bmm","bmm/workflows/testarch/nfr-assess/workflow.yaml","dad49221c4dcb4e1fbcc118b5caae13c63a050412e402ff65b6971cfab281fe3"
+"yaml","workflow","bmm","bmm/workflows/testarch/test-design/workflow.yaml","494d12c966022969c74caeb336e80bb0fce05f0bb4f83581ab7111e9f6f0596d"
+"yaml","workflow","bmm","bmm/workflows/testarch/test-review/workflow.yaml","c5e272f9969b704aa56b83a22f727fa2188490d7f6e347bc65966e0513eefa96"
+"yaml","workflow","bmm","bmm/workflows/testarch/trace/workflow.yaml","841eec77aba6490ba5672ac2c01ce570c38011e94574d870e8ba15bba78509f4"
+"yaml","workflow","bmm","bmm/workflows/workflow-status/init/workflow.yaml","3f54117211a421790df59c6c0a15d6ba6be33a001489d013870f939aaa649436"
+"yaml","workflow","bmm","bmm/workflows/workflow-status/workflow.yaml","6a1ad67ec954660fd8e7433b55ab3b75e768f7efa33aad36cf98cdbc2ef6575b"
+"yaml","workflow-status-template","bmm","bmm/workflows/workflow-status/workflow-status-template.yaml","0ec9c95f1690b7b7786ffb4ab10663c93b775647ad58e283805092e1e830a0d9"
+"csv","advanced-elicitation-methods","core","core/tasks/advanced-elicitation-methods.csv","e08b2e22fec700274982e37be608d6c3d1d4d0c04fa0bae05aa9dba2454e6141"
+"csv","brain-methods","core","core/workflows/brainstorming/brain-methods.csv","0ab5878b1dbc9e3fa98cb72abfc3920a586b9e2b42609211bb0516eefd542039"
+"md","bmad-master","core","core/agents/bmad-master.md","a9316de299009e453e41fcda9099050e8770b8c2c8594a90b7c99a179e38e5fe"
+"md","excalidraw-helpers","core","core/resources/excalidraw/excalidraw-helpers.md","37f18fa0bd15f85a33e7526a2cbfe1d5a9404f8bcb8febc79b782361ef790de4"
+"md","library-loader","core","core/resources/excalidraw/library-loader.md","7837112bd0acb5906870dff423a21564879d49c5322b004465666a42c52477ab"
+"md","README","core","core/resources/excalidraw/README.md","a188224350e2400410eb52b7d7a36b1ee39d2ea13be1b58b231845f6bc37f21b"
+"md","step-01-agent-loading","core","core/workflows/party-mode/steps/step-01-agent-loading.md","67fea74140f85bfcd0d26c202fa6fdc146861cf0a68405a8b15c971dddcaa20f"
+"md","step-01-session-setup","core","core/workflows/brainstorming/steps/step-01-session-setup.md","943118388f1cb81eda922240a944cff84517388298ead6b9e02f917432d8bf31"
+"md","step-01b-continue","core","core/workflows/brainstorming/steps/step-01b-continue.md","9d531b012f85a2a7c3ddd94a2adeb8189eab24c370d099dbabb1bd6e33b3a9cb"
+"md","step-02-discussion-orchestration","core","core/workflows/party-mode/steps/step-02-discussion-orchestration.md","1f0a6ca96139f522cc26ce6fdf78b4f94297201a53f06c30fb30e65717957cfb"
+"md","step-02a-user-selected","core","core/workflows/brainstorming/steps/step-02a-user-selected.md","24158414bfe6daa46c94e6e43a9ec3a8d9a6dfe1b2a5bd8b719d06c775dcc73d"
+"md","step-02b-ai-recommended","core","core/workflows/brainstorming/steps/step-02b-ai-recommended.md","68774e344cdcffbbd8fd9c5bec5bbe4cfd5297eb9734fc542606831becc38441"
+"md","step-02c-random-selection","core","core/workflows/brainstorming/steps/step-02c-random-selection.md","24b54de6ed3a3b0b87a23a28a69a5fa73e8bf9fb80353fb12db8258c1e29ac95"
+"md","step-02d-progressive-flow","core","core/workflows/brainstorming/steps/step-02d-progressive-flow.md","34b53545f18cd26db8bff81072e1c6b38efe031969e72d79c7efa2814f3b9073"
+"md","step-03-graceful-exit","core","core/workflows/party-mode/steps/step-03-graceful-exit.md","c07d1b5c3b4d48e8903872f24654e96f8cadd1d08202be3f5c2e381aa664e9bb"
+"md","step-03-technique-execution","core","core/workflows/brainstorming/steps/step-03-technique-execution.md","a0f7ef0d58ccf21c1e10b9ab221f8dbcc8ddc0c09b322da3863996e8731b6409"
+"md","step-04-idea-organization","core","core/workflows/brainstorming/steps/step-04-idea-organization.md","2a7f516d0e598ec3462795b1e5fe2bf2f3745276ca6ae609eed5562bacf46b0d"
+"md","template","core","core/workflows/brainstorming/template.md","5c99d76963eb5fc21db96c5a68f39711dca7c6ed30e4f7d22aedee9e8bb964f9"
+"md","validate-json-instructions","core","core/resources/excalidraw/validate-json-instructions.md","0970bac93d52b4ee591a11998a02d5682e914649a40725d623489c77f7a1e449"
+"md","workflow","core","core/workflows/brainstorming/workflow.md","55f659c2a6112aa205e8b746e9be18c0ce557b52be959e4e910fab45345323ee"
+"md","workflow","core","core/workflows/party-mode/workflow.md","37fcfb881d6e0037a06ed3939152734de967ea47354098e497b2ea27193256e7"
+"xml","advanced-elicitation","core","core/tasks/advanced-elicitation.xml","2de1a0ee3de157ae3235be567d4c025f03ac9e6ffbbca52b2bf3b2cd1b78a385"
+"xml","bmad-web-orchestrator.agent","core","core/agents/bmad-web-orchestrator.agent.xml","8031397b7636dcf5321658c9f540749fa051f714d278a29c8b0645dfaacbf010"
+"xml","index-docs","core","core/tasks/index-docs.xml","e71ea015d1a5ef8362bb85e0ef0015d10fd7ff01642c70d7ea17b327d74f5658"
+"xml","shard-doc","core","core/tools/shard-doc.xml","615edc5e1d10d42bdc6f07b3288d7201b0ed53e94c39841475f2b1b23dd76394"
+"xml","validate-workflow","core","core/tasks/validate-workflow.xml","8e1c05791708373db79cc0fc009f0cb5fb7b8423d67a569f16b119bc01370845"
+"xml","workflow","core","core/tasks/workflow.xml","e0cacebed3c81a36dc622f4ace3093fd4affbfb6656a7be82689709858cff283"
+"yaml","bmad-master.agent","core","core/agents/bmad-master.agent.yaml",""
+"yaml","config","core","core/config.yaml","2f7364cf1402c0f50f56284ae5ea2e0d5324d7fc0371560aaceb3ad2dfc3de1b"
+"yaml","config","core","core/config.yaml","2f7364cf1402c0f50f56284ae5ea2e0d5324d7fc0371560aaceb3ad2dfc3de1b"
+"yaml","module","core","core/module.yaml","0de86d1aa90a35c20b17f5df4f62ae7e06e474adfe5bd7461290857270b6aeb2"
diff --git a/.bmad/_cfg/ides/claude-code.yaml b/.bmad/_cfg/ides/claude-code.yaml
new file mode 100644
index 0000000..c527685
--- /dev/null
+++ b/.bmad/_cfg/ides/claude-code.yaml
@@ -0,0 +1,6 @@
+ide: claude-code
+configured_date: '2025-12-09T19:39:24.529Z'
+last_updated: '2025-12-09T19:39:24.529Z'
+configuration:
+ subagentChoices: null
+ installLocation: null
diff --git a/.bmad/_cfg/manifest.yaml b/.bmad/_cfg/manifest.yaml
new file mode 100644
index 0000000..51fccf4
--- /dev/null
+++ b/.bmad/_cfg/manifest.yaml
@@ -0,0 +1,12 @@
+installation:
+ version: 6.0.0-alpha.15
+ installDate: '2025-12-09T19:39:24.486Z'
+ lastUpdated: '2025-12-09T19:39:24.486Z'
+modules:
+ - core
+ - bmb
+ - bmm
+customModules: []
+ides:
+ - claude-code
+ - auggie
diff --git a/.bmad/_cfg/task-manifest.csv b/.bmad/_cfg/task-manifest.csv
new file mode 100644
index 0000000..845af1f
--- /dev/null
+++ b/.bmad/_cfg/task-manifest.csv
@@ -0,0 +1,6 @@
+name,displayName,description,module,path,standalone
+"advanced-elicitation","Advanced Elicitation","When called from workflow","core",".bmad/core/tasks/advanced-elicitation.xml","true"
+"index-docs","Index Docs","Generates or updates an index.md of all documents in the specified directory","core",".bmad/core/tasks/index-docs.xml","true"
+"validate-workflow","Validate Workflow Output","Run a checklist against a document with thorough analysis and produce a validation report","core",".bmad/core/tasks/validate-workflow.xml","false"
+"workflow","Execute Workflow","Execute given workflow by loading its configuration, following instructions, and producing output","core",".bmad/core/tasks/workflow.xml","false"
+"daily-standup","Daily Standup","","bmm",".bmad/bmm/tasks/daily-standup.xml","false"
diff --git a/.bmad/_cfg/tool-manifest.csv b/.bmad/_cfg/tool-manifest.csv
new file mode 100644
index 0000000..43979fe
--- /dev/null
+++ b/.bmad/_cfg/tool-manifest.csv
@@ -0,0 +1,2 @@
+name,displayName,description,module,path,standalone
+"shard-doc","Shard Document","Splits large markdown documents into smaller, organized files based on level 2 (default) sections","core",".bmad/core/tools/shard-doc.xml","true"
diff --git a/.bmad/_cfg/workflow-manifest.csv b/.bmad/_cfg/workflow-manifest.csv
new file mode 100644
index 0000000..99a2783
--- /dev/null
+++ b/.bmad/_cfg/workflow-manifest.csv
@@ -0,0 +1,42 @@
+name,description,module,path
+"brainstorming-session","Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods","core",".bmad/core/workflows/brainstorming/workflow.md"
+"party-mode","Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations","core",".bmad/core/workflows/party-mode/workflow.md"
+"Meal Prep & Nutrition Plan","Creates personalized meal plans through collaborative nutrition planning between an expert facilitator and individual seeking to improve their nutrition habits.","bmb",".bmad/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/workflow.md"
+"create-agent","Interactive workflow to build BMAD Core compliant agents with optional brainstorming, persona development, and command structure","bmb",".bmad/bmb/workflows/create-agent/workflow.md"
+"create-module","Interactive workflow to build complete BMAD modules with agents, workflows, and installation infrastructure","bmb",".bmad/bmb/workflows/create-module/workflow.md"
+"create-workflow","Create structured standalone workflows using markdown-based step architecture","bmb",".bmad/bmb/workflows/create-workflow/workflow.md"
+"edit-agent","Edit existing BMAD agents while following all best practices and conventions","bmb",".bmad/bmb/workflows/edit-agent/workflow.md"
+"edit-workflow","Intelligent workflow editor that helps modify existing workflows while following best practices","bmb",".bmad/bmb/workflows/edit-workflow/workflow.md"
+"workflow-compliance-check","Systematic validation of workflows against BMAD standards with adversarial analysis and detailed reporting","bmb",".bmad/bmb/workflows/workflow-compliance-check/workflow.md"
+"create-product-brief","Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.","bmm",".bmad/bmm/workflows/1-analysis/product-brief/workflow.md"
+"research","Conduct comprehensive research across multiple domains using current web data and verified sources - Market, Technical, Domain and other research types.","bmm",".bmad/bmm/workflows/1-analysis/research/workflow.md"
+"create-ux-design","Work with a peer UX Design expert to plan your applications UX patterns, look and feel.","bmm",".bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md"
+"create-prd","Creates a comprehensive PRDs through collaborative step-by-step discovery between two product managers working as peers.","bmm",".bmad/bmm/workflows/2-plan-workflows/prd/workflow.md"
+"create-architecture","Collaborative architectural decision facilitation for AI-agent consistency. Replaces template-driven architecture with intelligent, adaptive conversation that produces a decision-focused architecture document optimized for preventing agent conflicts.","bmm",".bmad/bmm/workflows/3-solutioning/architecture/workflow.md"
+"create-epics-stories","Transform PRD requirements and Architecture decisions into comprehensive stories organized by user value. This workflow requires completed PRD + Architecture documents (UX recommended if UI exists) and breaks down requirements into implementation-ready epics and user stories that incorporate all available technical and design context. Creates detailed, actionable stories with complete acceptance criteria for development teams.","bmm",".bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md"
+"check-implementation-readiness","Critical validation workflow that assesses PRD, Architecture, and Epics & Stories for completeness and alignment before implementation. Uses adversarial review approach to find gaps and issues.","bmm",".bmad/bmm/workflows/3-solutioning/implementation-readiness/workflow.md"
+"code-review","Perform an ADVERSARIAL Senior Developer code review that finds 3-10 specific problems in every story. Challenges everything: code quality, test coverage, architecture compliance, security, performance. NEVER accepts `looks good` - must find minimum issues and can auto-fix with user approval.","bmm",".bmad/bmm/workflows/4-implementation/code-review/workflow.yaml"
+"correct-course","Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation","bmm",".bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml"
+"create-story","Create the next user story from epics+stories with enhanced context analysis and direct ready-for-dev marking","bmm",".bmad/bmm/workflows/4-implementation/create-story/workflow.yaml"
+"dev-story","Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria","bmm",".bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml"
+"retrospective","Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic","bmm",".bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml"
+"sprint-planning","Generate and manage the sprint status tracking file for Phase 4 implementation, extracting all epics and stories from epic files and tracking their status through the development lifecycle","bmm",".bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml"
+"sprint-status","Summarize sprint-status.yaml, surface risks, and route to the right implementation workflow.","bmm",".bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml"
+"create-tech-spec","Conversational spec engineering - ask questions, investigate code, produce implementation-ready tech-spec.","bmm",".bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml"
+"quick-dev","Flexible development - execute tech-specs OR direct instructions with optional planning.","bmm",".bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml"
+"create-excalidraw-dataflow","Create data flow diagrams (DFD) in Excalidraw format","bmm",".bmad/bmm/workflows/diagrams/create-dataflow/workflow.yaml"
+"create-excalidraw-diagram","Create system architecture diagrams, ERDs, UML diagrams, or general technical diagrams in Excalidraw format","bmm",".bmad/bmm/workflows/diagrams/create-diagram/workflow.yaml"
+"create-excalidraw-flowchart","Create a flowchart visualization in Excalidraw format for processes, pipelines, or logic flows","bmm",".bmad/bmm/workflows/diagrams/create-flowchart/workflow.yaml"
+"create-excalidraw-wireframe","Create website or app wireframes in Excalidraw format","bmm",".bmad/bmm/workflows/diagrams/create-wireframe/workflow.yaml"
+"document-project","Analyzes and documents brownfield projects by scanning codebase, architecture, and patterns to create comprehensive reference documentation for AI-assisted development","bmm",".bmad/bmm/workflows/document-project/workflow.yaml"
+"generate-project-context","Creates a concise project_context.md file with critical rules and patterns that AI agents must follow when implementing code. Optimized for LLM context efficiency.","bmm",".bmad/bmm/workflows/generate-project-context/workflow.md"
+"testarch-atdd","Generate failing acceptance tests before implementation using TDD red-green-refactor cycle","bmm",".bmad/bmm/workflows/testarch/atdd/workflow.yaml"
+"testarch-automate","Expand test automation coverage after implementation or analyze existing codebase to generate comprehensive test suite","bmm",".bmad/bmm/workflows/testarch/automate/workflow.yaml"
+"testarch-ci","Scaffold CI/CD quality pipeline with test execution, burn-in loops, and artifact collection","bmm",".bmad/bmm/workflows/testarch/ci/workflow.yaml"
+"testarch-framework","Initialize production-ready test framework architecture (Playwright or Cypress) with fixtures, helpers, and configuration","bmm",".bmad/bmm/workflows/testarch/framework/workflow.yaml"
+"testarch-nfr","Assess non-functional requirements (performance, security, reliability, maintainability) before release with evidence-based validation","bmm",".bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml"
+"testarch-test-design","Dual-mode workflow: (1) System-level testability review in Solutioning phase, or (2) Epic-level test planning in Implementation phase. Auto-detects mode based on project phase.","bmm",".bmad/bmm/workflows/testarch/test-design/workflow.yaml"
+"testarch-test-review","Review test quality using comprehensive knowledge base and best practices validation","bmm",".bmad/bmm/workflows/testarch/test-review/workflow.yaml"
+"testarch-trace","Generate requirements-to-tests traceability matrix, analyze coverage, and make quality gate decision (PASS/CONCERNS/FAIL/WAIVED)","bmm",".bmad/bmm/workflows/testarch/trace/workflow.yaml"
+"workflow-init","Initialize a new BMM project by determining level, type, and creating workflow path","bmm",".bmad/bmm/workflows/workflow-status/init/workflow.yaml"
+"workflow-status","Lightweight status checker - answers ""what should I do now?"" for any agent. Reads YAML status file for workflow tracking. Use workflow-init for new projects.","bmm",".bmad/bmm/workflows/workflow-status/workflow.yaml"
diff --git a/.bmad/bmb/README.md b/.bmad/bmb/README.md
new file mode 100644
index 0000000..fc58734
--- /dev/null
+++ b/.bmad/bmb/README.md
@@ -0,0 +1,261 @@
+# BMB - BMad Builder Module
+
+Specialized tools and workflows for creating, customizing, and extending BMad components including agents, workflows, and complete modules.
+
+## Table of Contents
+
+- [Module Structure](#module-structure)
+- [Documentation](#documentation)
+- [Reference Materials](#reference-materials)
+- [Core Workflows](#core-workflows)
+- [Agent Types](#agent-types)
+- [Quick Start](#quick-start)
+- [Best Practices](#best-practices)
+
+## Module Structure
+
+### 🤖 Agents
+
+**BMad Builder** - Master builder agent orchestrating all creation workflows with deep knowledge of BMad architecture and conventions.
+
+- Location: `.bmad/bmb/agents/bmad-builder.md`
+
+### 📋 Workflows
+
+**Active Workflows** (Step-File Architecture)
+
+- Location: `src/modules/bmb/workflows/`
+- 5 core workflows with 41 step files total
+- Template-based execution with JIT loading
+
+**Legacy Workflows** (Being Migrated)
+
+- Location: `src/modules/bmb/workflows-legacy/`
+- Module-specific workflows pending conversion to step-file architecture
+
+### 📚 Documentation
+
+- Location: `src/modules/bmb/docs/`
+- Comprehensive guides for agents and workflows
+- Architecture patterns and best practices
+
+### 🔍 Reference Materials
+
+- Location: `src/modules/bmb/reference/`
+- Working examples of agents and workflows
+- Template patterns and implementation guides
+
+## Documentation
+
+### 📖 Agent Documentation
+
+- **[Agent Index](./docs/agents/index.md)** - Complete agent architecture guide
+- **[Agent Types Guide](./docs/agents/understanding-agent-types.md)** - Simple vs Expert vs Module agents
+- **[Menu Patterns](./docs/agents/agent-menu-patterns.md)** - YAML menu design and handler types
+- **[Agent Compilation](./docs/agents/agent-compilation.md)** - Auto-injection rules and compilation process
+
+### 📋 Workflow Documentation
+
+- **[Workflow Index](./docs/workflows/index.md)** - Core workflow system overview
+- **[Architecture Guide](./docs/workflows/architecture.md)** - Step-file design and JIT loading
+- **[Template System](./docs/workflows/templates/step-template.md)** - Standard step file template
+- **[Intent vs Prescriptive](./docs/workflows/intent-vs-prescriptive-spectrum.md)** - Design philosophy
+
+## Reference Materials
+
+### 🤖 Agent Examples
+
+- **[Simple Agent Example](./reference/agents/simple-examples/commit-poet.agent.yaml)** - Self-contained agent
+- **[Expert Agent Example](./reference/agents/expert-examples/journal-keeper/)** - Agent with persistent memory
+- **[Module Agent Examples](./reference/agents/module-examples/)** - Integration patterns (BMM, CIS)
+
+### 📋 Workflow Examples
+
+- **[Meal Prep & Nutrition](./reference/workflows/meal-prep-nutrition/)** - Complete step-file workflow demonstration
+- **Template patterns** for document generation and state management
+
+## Core Workflows
+
+### Creation Workflows (Step-File Architecture)
+
+**[create-agent](./workflows/create-agent/)** - Build BMad agents
+
+- 11 guided steps from brainstorming to celebration
+- 18 reference data files with validation checklists
+- Template-based agent generation
+
+**[create-workflow](./workflows/create-workflow/)** - Design workflows
+
+- 12 structured steps from init to review
+- 9 template files for workflow creation
+- Step-file architecture implementation
+
+### Editing Workflows
+
+**[edit-agent](./workflows/edit-agent/)** - Modify existing agents
+
+- 5 steps: discovery → validation
+- Intent-driven analysis and updates
+- Best practice compliance
+
+**[edit-workflow](./workflows/edit-workflow/)** - Update workflows
+
+- 5 steps: analyze → compliance check
+- Structure maintenance and validation
+- Template updates for consistency
+
+### Quality Assurance
+
+**[workflow-compliance-check](./workflows/workflow-compliance-check/)** - Validation
+
+- 8 systematic validation steps
+- Adversarial analysis approach
+- Detailed compliance reporting
+
+### Legacy Migration (Pending)
+
+Workflows in `workflows-legacy/` are being migrated to step-file architecture:
+
+- Module-specific workflows
+- Historical implementations
+- Conversion planning in progress
+
+## Agent Types
+
+BMB creates three agent architectures:
+
+### Simple Agent
+
+- **Self-contained**: All logic in single YAML file
+- **Stateless**: No persistent memory across sessions
+- **Purpose**: Single utilities and specialized tools
+- **Example**: Commit poet, code formatter
+
+### Expert Agent
+
+- **Persistent Memory**: Maintains knowledge across sessions
+- **Sidecar Resources**: External files and data storage
+- **Domain-specific**: Focuses on particular knowledge areas
+- **Example**: Journal keeper, domain consultant
+
+### Module Agent
+
+- **Team Integration**: Orchestrates within specific modules
+- **Workflow Coordination**: Manages complex processes
+- **Professional Infrastructure**: Enterprise-grade capabilities
+- **Examples**: BMM project manager, CIS innovation strategist
+
+## Quick Start
+
+### Using BMad Builder Agent
+
+1. **Load BMad Builder agent** in your IDE:
+ ```
+ /bmad:bmb:agents:bmad-builder
+ ```
+2. **Choose creation type:**
+ - `[CA]` Create Agent - Build new agents
+ - `[CW]` Create Workflow - Design workflows
+ - `[EA]` Edit Agent - Modify existing agents
+ - `[EW]` Edit Workflow - Update workflows
+ - `[VA]` Validate Agent - Quality check agents
+ - `[VW]` Validate Workflow - Quality check workflows
+
+3. **Follow interactive prompts** for step-by-step guidance
+
+### Example: Creating an Agent
+
+```
+User: I need a code review agent
+Builder: [CA] Create Agent
+
+[11-step guided process]
+Step 1: Brainstorm agent concept
+Step 2: Define persona and role
+Step 3: Design command structure
+...
+Step 11: Celebrate and deploy
+```
+
+### Direct Workflow Execution
+
+Workflows can also be run directly without the agent interface:
+
+```yaml
+# Execute specific workflow steps
+workflow: ./workflows/create-agent/workflow.yaml
+```
+
+## Use Cases
+
+### Custom Development Teams
+
+Build specialized agents for:
+
+- Domain expertise (legal, medical, finance)
+- Company processes
+- Tool integrations
+- Automation tasks
+
+### Workflow Extensions
+
+Create workflows for:
+
+- Compliance requirements
+- Quality gates
+- Deployment pipelines
+- Custom methodologies
+
+### Complete Solutions
+
+Package modules for:
+
+- Industry verticals
+- Technology stacks
+- Business processes
+- Educational frameworks
+
+## Architecture Principles
+
+### Step-File Workflow Design
+
+- **Micro-file Approach**: Each step is self-contained
+- **Just-In-Time Loading**: Only current step in memory
+- **Sequential Enforcement**: No skipping steps allowed
+- **State Tracking**: Progress documented in frontmatter
+- **Append-Only Building**: Documents grow through execution
+
+### Intent vs Prescriptive Spectrum
+
+- **Creative Workflows**: High user agency, AI as facilitator
+- **Structured Workflows**: Clear process, AI as guide
+- **Prescriptive Workflows**: Strict compliance, AI as validator
+
+## Best Practices
+
+1. **Study Reference Materials** - Review docs/ and reference/ examples
+2. **Choose Right Agent Type** - Simple vs Expert vs Module based on needs
+3. **Follow Step-File Patterns** - Use established templates and structures
+4. **Document Thoroughly** - Clear instructions and frontmatter metadata
+5. **Validate Continuously** - Use compliance workflows for quality
+6. **Maintain Consistency** - Follow YAML patterns and naming conventions
+
+## Integration
+
+BMB components integrate with:
+
+- **BMad Core** - Framework foundation and agent compilation
+- **BMM** - Development workflows and project management
+- **CIS** - Creative innovation and strategic workflows
+- **Custom Modules** - Domain-specific solutions
+
+## Getting Help
+
+- **Documentation**: Check `docs/` for comprehensive guides
+- **Reference Materials**: See `reference/` for working examples
+- **Validation**: Use `workflow-compliance-check` for quality assurance
+- **Templates**: Leverage workflow templates for consistent patterns
+
+---
+
+BMB provides a complete toolkit for extending BMad Method with disciplined, systematic approaches to agent and workflow development while maintaining framework consistency and power.
diff --git a/.bmad/bmb/agents/bmad-builder.md b/.bmad/bmb/agents/bmad-builder.md
new file mode 100644
index 0000000..ef85f7c
--- /dev/null
+++ b/.bmad/bmb/agents/bmad-builder.md
@@ -0,0 +1,59 @@
+---
+name: "bmad builder"
+description: "BMad Builder"
+---
+
+You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
+
+```xml
+
+
+ Load persona from this current agent file (already in context)
+ Load and read {project-root}/.bmad/core/config.yaml to get {user_name}, {communication_language}, {output_folder}
+ Remember: user's name is {user_name}
+ ALWAYS communicate in {communication_language}
+ Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
+ ALL menu items from menu section
+ STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command
+ match
+ On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
+ to clarify | No match → show "Not recognized"
+
+
+ - ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style
+ - Stay in character until exit selected
+ - Menu triggers use asterisk (*) - NOT markdown, display exactly as shown
+ - Number all lists, use letters for sub-options
+ - Load files ONLY when executing menu items or a workflow or command requires it. EXCEPTION: Config file MUST be loaded at startup step 2
+ - CRITICAL: Written File Output in workflows will be +2sd your communication style and use professional {communication_language}.
+
+
+
+ Generalist Builder and BMAD System Maintainer
+ A hands-on builder who gets things done efficiently and maintains the entire BMAD ecosystem
+ Direct, action-oriented, and encouraging with a can-do attitude
+ Execute resources directly without hesitation Load resources at runtime never pre-load Always present numbered lists for clear choices Focus on practical implementation and results Maintain system-wide coherence and standards Balance speed with quality and compliance
+
+
+
+```
diff --git a/.bmad/bmb/config.yaml b/.bmad/bmb/config.yaml
new file mode 100644
index 0000000..2b787a0
--- /dev/null
+++ b/.bmad/bmb/config.yaml
@@ -0,0 +1,16 @@
+# BMB Module Configuration
+# Generated by BMAD installer
+# Version: 6.0.0-alpha.15
+# Date: 2025-12-09T19:39:24.476Z
+
+custom_stand_alone_location: '{project-root}/bmad-custom-src'
+custom_module_location: '{project-root}/bmad-custom-modules-src'
+
+# Core Configuration Values
+bmad_folder: .bmad
+user_name: blinkerist
+communication_language: English
+document_output_language: English
+agent_sidecar_folder: '{project-root}/.bmad-user-memory'
+output_folder: '{project-root}/docs'
+install_user_docs: true
diff --git a/.bmad/bmb/docs/agents/agent-compilation.md b/.bmad/bmb/docs/agents/agent-compilation.md
new file mode 100644
index 0000000..691044b
--- /dev/null
+++ b/.bmad/bmb/docs/agents/agent-compilation.md
@@ -0,0 +1,340 @@
+# Agent Compilation: YAML to XML
+
+What the compiler auto-injects. **DO NOT duplicate these in your YAML.**
+
+## Compilation Pipeline
+
+```
+agent.yaml → Handlebars processing → XML generation → frontmatter.md
+```
+
+Source: `tools/cli/lib/agent/compiler.js`
+
+## File Naming Convention
+
+**CRITICAL:** Agent filenames must be ROLE-BASED, not persona-based.
+
+**Why:** Users can customize the agent's persona name via `customize.yaml` config. The filename provides stable identity.
+
+**Correct:**
+
+```
+presentation-master.agent.yaml ← Role/function
+tech-writer.agent.yaml ← Role/function
+code-reviewer.agent.yaml ← Role/function
+```
+
+**Incorrect:**
+
+```
+caravaggio.agent.yaml ← Persona name (users might rename to "Pablo")
+paige.agent.yaml ← Persona name (users might rename to "Sarah")
+rex.agent.yaml ← Persona name (users might rename to "Max")
+```
+
+**Pattern:**
+
+- Filename: `{role-or-function}.agent.yaml` (kebab-case)
+- Metadata ID: `.bmad/{module}/agents/{role-or-function}.md`
+- Persona Name: User-customizable in metadata or customize.yaml
+
+**Example:**
+
+```yaml
+# File: presentation-master.agent.yaml
+agent:
+ metadata:
+ id: '.bmad/cis/agents/presentation-master.md'
+ name: Caravaggio # ← Users can change this to "Pablo" or "Vince"
+ title: Visual Communication & Presentation Expert
+```
+
+## Auto-Injected Components
+
+### 1. Frontmatter
+
+**Injected automatically:**
+
+```yaml
+---
+name: '{agent name from filename}'
+description: '{title from metadata}'
+---
+You must fully embody this agent's persona...
+```
+
+**DO NOT add** frontmatter to your YAML source.
+
+### 2. Activation Block
+
+**Entire activation section is auto-generated:**
+
+```xml
+
+ Load persona from this current agent file
+ Load config to get {user_name}, {communication_language}
+ Remember: user's name is {user_name}
+
+
+
+ ALWAYS communicate in {communication_language}
+ Show greeting + numbered menu
+ STOP and WAIT for user input
+ Input resolution rules
+
+
+
+
+
+
+
+
+
+```
+
+**DO NOT create** activation sections - compiler builds it from your critical_actions.
+
+### 3. Menu Enhancements
+
+**Auto-injected menu items:**
+
+- `*help` - Always FIRST in compiled menu
+- `*exit` - Always LAST in compiled menu
+
+**Trigger prefixing:**
+
+- Your trigger `analyze` becomes `*analyze`
+- Don't add `*` prefix - compiler does it
+
+**DO NOT include:**
+
+```yaml
+# BAD - these are auto-injected
+menu:
+ - trigger: help
+ description: 'Show help'
+ - trigger: exit
+ description: 'Exit'
+```
+
+### 4. Menu Handlers
+
+Compiler detects which handlers you use and ONLY includes those:
+
+```xml
+
+
+
+ ...
+
+
+ ...
+
+
+ ...
+
+
+ ...
+
+
+```
+
+**DO NOT document** handler behavior - it's injected.
+
+### 5. Rules Section
+
+**Auto-injected rules:**
+
+- Always communicate in {communication_language}
+- Stay in character until exit
+- Menu triggers use asterisk (\*) - NOT markdown
+- Number all lists, use letters for sub-options
+- Load files ONLY when executing menu items
+- Written output follows communication style
+
+**DO NOT add** rules - compiler handles it.
+
+## What YOU Provide in YAML
+
+### Required
+
+```yaml
+agent:
+ metadata:
+ name: 'Persona Name'
+ title: 'Agent Title'
+ icon: 'emoji'
+ type: 'simple|expert' # or module: "bmm"
+
+ persona:
+ role: '...'
+ identity: '...'
+ communication_style: '...'
+ principles: [...]
+
+ menu:
+ - trigger: your-action
+ action: '#prompt-id'
+ description: 'What it does'
+```
+
+### Optional (based on type)
+
+```yaml
+# Expert agents only
+critical_actions:
+ - 'Load sidecar files...'
+ - 'Restrict access...'
+
+# Simple/Expert with embedded logic
+prompts:
+ - id: prompt-id
+ content: '...'
+
+# Simple/Expert with customization
+install_config:
+ questions: [...]
+```
+
+## Common Duplication Mistakes
+
+### Adding Activation Logic
+
+```yaml
+# BAD - compiler builds activation
+agent:
+ activation:
+ steps: [...]
+```
+
+### Including Help/Exit
+
+```yaml
+# BAD - auto-injected
+menu:
+ - trigger: help
+ - trigger: exit
+```
+
+### Prefixing Triggers
+
+```yaml
+# BAD - compiler adds *
+menu:
+ - trigger: '*analyze' # Should be: analyze
+```
+
+### Documenting Handlers
+
+```yaml
+# BAD - don't explain handlers, compiler injects them
+# When using workflow, load workflow.xml...
+```
+
+### Adding Rules in YAML
+
+```yaml
+# BAD - rules are auto-injected
+agent:
+ rules:
+ - Stay in character...
+```
+
+## Compilation Example
+
+**Your YAML:**
+
+```yaml
+agent:
+ metadata:
+ name: 'Rex'
+ title: 'Code Reviewer'
+ icon: '🔍'
+ type: simple
+
+ persona:
+ role: Code Review Expert
+ identity: Systematic reviewer...
+ communication_style: Direct and constructive
+ principles:
+ - Code should be readable
+
+ prompts:
+ - id: review
+ content: |
+ Analyze code for issues...
+
+ menu:
+ - trigger: review
+ action: '#review'
+ description: 'Review code'
+```
+
+**Compiled Output (.md):**
+
+```markdown
+---
+name: 'rex'
+description: 'Code Reviewer'
+---
+
+You must fully embody...
+
+\`\`\`xml
+
+
+Load persona...
+Load config...
+Remember user...
+Communicate in language...
+Show greeting + menu...
+STOP and WAIT...
+Input resolution...
+
+
+
+
+ action="#id" → Find prompt, execute
+ action="text" → Execute directly
+
+
+
+
+
+ - Stay in character...
+ - Number lists...
+ - Load files when executing...
+
+
+
+ Code Review Expert
+ Systematic reviewer...
+ Direct and constructive
+ Code should be readable
+
+
+
+
+Analyze code for issues...
+
+
+
+
+
+\`\`\`
+```
+
+## Key Takeaways
+
+1. **Compiler handles boilerplate** - Focus on persona and logic
+2. **Critical_actions become activation steps** - Just list your agent-specific needs
+3. **Menu items are enhanced** - Help/exit added, triggers prefixed
+4. **Handlers auto-detected** - Only what you use is included
+5. **Rules standardized** - Consistent behavior across agents
+
+**Your job:** Define persona, prompts, menu actions
+**Compiler's job:** Activation, handlers, rules, help/exit, prefixes
diff --git a/.bmad/bmb/docs/agents/agent-menu-patterns.md b/.bmad/bmb/docs/agents/agent-menu-patterns.md
new file mode 100644
index 0000000..584cec7
--- /dev/null
+++ b/.bmad/bmb/docs/agents/agent-menu-patterns.md
@@ -0,0 +1,524 @@
+# BMAD Agent Menu Patterns
+
+Design patterns for agent menus in YAML source files.
+
+## Menu Structure
+
+Agents define menus in YAML, with triggers auto-prefixed with `*` during compilation:
+
+```yaml
+menu:
+ - trigger: action-name
+ [handler]: [value]
+ description: 'What this command does'
+```
+
+**Note:** `*help` and `*exit` are auto-injected by the compiler - DO NOT include them.
+
+## Handler Types
+
+### 1. Action Handler (Prompts & Inline)
+
+For simple and expert agents with self-contained logic.
+
+**Reference to Prompt ID:**
+
+```yaml
+prompts:
+ - id: analyze-code
+ content: |
+
+ Analyze the provided code for patterns and issues.
+
+
+
+ 1. Identify code structure
+ 2. Check for anti-patterns
+ 3. Suggest improvements
+
+
+menu:
+ - trigger: analyze
+ action: '#analyze-code'
+ description: 'Analyze code patterns'
+```
+
+**Inline Instruction:**
+
+```yaml
+menu:
+ - trigger: quick-check
+ action: 'Perform a quick syntax validation on the current file'
+ description: 'Quick syntax check'
+```
+
+**When to Use:**
+
+- Simple/Expert agents with self-contained operations
+- `#id` for complex, multi-step prompts
+- Inline text for simple, one-line instructions
+
+### 2. Workflow Handler
+
+For module agents orchestrating multi-step processes.
+
+```yaml
+menu:
+ - trigger: create-prd
+ workflow: '{project-root}/.bmad/bmm/workflows/prd/workflow.yaml'
+ description: 'Create Product Requirements Document'
+
+ - trigger: brainstorm
+ workflow: '{project-root}/.bmad/core/workflows/brainstorming/workflow.yaml'
+ description: 'Guided brainstorming session'
+
+ # Placeholder for unimplemented workflows
+ - trigger: future-feature
+ workflow: 'todo'
+ description: 'Coming soon'
+```
+
+**When to Use:**
+
+- Module agents with workflow integration
+- Multi-step document generation
+- Complex interactive processes
+- Use "todo" for planned but unimplemented features
+
+### 3. Exec Handler
+
+For executing tasks directly.
+
+```yaml
+menu:
+ - trigger: validate
+ exec: '{project-root}/.bmad/core/tasks/validate-workflow.xml'
+ description: 'Validate document structure'
+
+ - trigger: advanced-elicitation
+ exec: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
+ description: 'Advanced elicitation techniques'
+```
+
+**When to Use:**
+
+- Single-operation tasks
+- Core system operations
+- Utility functions
+
+### 4. Template Handler
+
+For document generation with templates.
+
+```yaml
+menu:
+ - trigger: create-brief
+ exec: '{project-root}/.bmad/core/tasks/create-doc.xml'
+ tmpl: '{project-root}/.bmad/bmm/templates/brief.md'
+ description: 'Create a Product Brief'
+```
+
+**When to Use:**
+
+- Template-based document creation
+- Combine `exec` with `tmpl` path
+- Structured output generation
+
+### 5. Data Handler
+
+Universal attribute for supplementary information.
+
+```yaml
+menu:
+ - trigger: team-standup
+ exec: '{project-root}/.bmad/bmm/tasks/standup.xml'
+ data: '{project-root}/.bmad/_cfg/agent-manifest.csv'
+ description: 'Run team standup'
+
+ - trigger: analyze-metrics
+ action: 'Analyze these metrics and identify trends'
+ data: '{project-root}/_data/metrics.json'
+ description: 'Analyze performance metrics'
+```
+
+**When to Use:**
+
+- Add to ANY handler type
+- Reference data files (CSV, JSON, YAML)
+- Provide context for operations
+
+## Platform-Specific Menus
+
+Control visibility based on deployment target:
+
+```yaml
+menu:
+ - trigger: git-flow
+ exec: '{project-root}/.bmad/bmm/tasks/git-flow.xml'
+ description: 'Git workflow operations'
+ ide-only: true # Only in IDE environments
+
+ - trigger: advanced-elicitation
+ exec: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
+ description: 'Advanced elicitation'
+ web-only: true # Only in web bundles
+```
+
+## Trigger Naming Conventions
+
+### Action-Based (Recommended)
+
+```yaml
+# Creation
+- trigger: create-prd
+- trigger: build-module
+- trigger: generate-report
+
+# Analysis
+- trigger: analyze-requirements
+- trigger: review-code
+- trigger: validate-architecture
+
+# Operations
+- trigger: update-status
+- trigger: sync-data
+- trigger: deploy-changes
+```
+
+### Domain-Based
+
+```yaml
+# Development
+- trigger: brainstorm
+- trigger: architect
+- trigger: refactor
+
+# Project Management
+- trigger: sprint-plan
+- trigger: retrospective
+- trigger: standup
+```
+
+### Bad Patterns
+
+```yaml
+# TOO VAGUE
+- trigger: do
+- trigger: run
+- trigger: process
+
+# TOO LONG
+- trigger: create-comprehensive-product-requirements-document
+
+# NO VERB
+- trigger: prd
+- trigger: config
+```
+
+## Menu Organization
+
+### Recommended Order
+
+```yaml
+menu:
+ # Note: *help auto-injected first by compiler
+
+ # 1. Primary workflows (main value)
+ - trigger: workflow-init
+ workflow: '...'
+ description: 'Start here - initialize workflow'
+
+ - trigger: create-prd
+ workflow: '...'
+ description: 'Create PRD'
+
+ # 2. Secondary operations
+ - trigger: validate
+ exec: '...'
+ description: 'Validate document'
+
+ # 3. Utilities
+ - trigger: party-mode
+ workflow: '...'
+ description: 'Multi-agent discussion'
+
+ # Note: *exit auto-injected last by compiler
+```
+
+### Grouping by Phase
+
+```yaml
+menu:
+ # Analysis Phase
+ - trigger: brainstorm
+ workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/brainstorm/workflow.yaml'
+ description: 'Brainstorm ideas'
+
+ - trigger: research
+ workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/research/workflow.yaml'
+ description: 'Conduct research'
+
+ # Planning Phase
+ - trigger: prd
+ workflow: '{project-root}/.bmad/bmm/workflows/2-planning/prd/workflow.yaml'
+ description: 'Create PRD'
+
+ - trigger: architecture
+ workflow: '{project-root}/.bmad/bmm/workflows/2-planning/architecture/workflow.yaml'
+ description: 'Design architecture'
+```
+
+## Description Best Practices
+
+### Good Descriptions
+
+```yaml
+# Clear action + object
+- description: 'Create Product Requirements Document'
+
+# Specific outcome
+- description: 'Analyze security vulnerabilities'
+
+# User benefit
+- description: 'Optimize code for performance'
+
+# Context when needed
+- description: 'Start here - initialize workflow path'
+```
+
+### Poor Descriptions
+
+```yaml
+# Too vague
+- description: 'Process'
+
+# Technical jargon
+- description: 'Execute WF123'
+
+# Missing context
+- description: 'Run'
+
+# Redundant with trigger
+- description: 'Create PRD' # trigger: create-prd (too similar)
+```
+
+## Prompts Section (Simple/Expert Agents)
+
+### Prompt Structure
+
+```yaml
+prompts:
+ - id: unique-identifier
+ content: |
+
+ What this prompt accomplishes
+
+
+
+ 1. First step
+ {{#if custom_option}}
+ 2. Conditional step
+ {{/if}}
+ 3. Final step
+
+
+
+ Expected structure of results
+
+```
+
+### Semantic XML Tags in Prompts
+
+Use XML tags to structure prompt content:
+
+- `` - What to do
+- `` - Step-by-step approach
+- `` - Expected results
+- `` - Sample outputs
+- `` - Limitations
+- `` - Background information
+
+### Handlebars in Prompts
+
+Customize based on install_config:
+
+```yaml
+prompts:
+ - id: analyze
+ content: |
+ {{#if detailed_mode}}
+ Perform comprehensive analysis with full explanations.
+ {{/if}}
+ {{#unless detailed_mode}}
+ Quick analysis focusing on key points.
+ {{/unless}}
+
+ Address {{user_name}} in {{communication_style}} tone.
+```
+
+## Path Variables
+
+### Always Use Variables
+
+```yaml
+# GOOD - Portable paths
+workflow: "{project-root}/.bmad/bmm/workflows/prd/workflow.yaml"
+exec: "{project-root}/.bmad/core/tasks/validate.xml"
+data: "{project-root}/_data/metrics.csv"
+
+# BAD - Hardcoded paths
+workflow: "/Users/john/project/.bmad/bmm/workflows/prd/workflow.yaml"
+exec: "../../../core/tasks/validate.xml"
+```
+
+### Available Variables
+
+- `{project-root}` - Project root directory
+- `.bmad` - BMAD installation folder
+- `{project-root}/.bmad-user-memory` - Agent installation directory (Expert agents)
+- `{output_folder}` - Document output location
+- `{user_name}` - User's name from config
+- `{communication_language}` - Language preference
+
+## Complete Examples
+
+### Simple Agent Menu
+
+```yaml
+prompts:
+ - id: format-code
+ content: |
+
+ Format the provided code according to style guidelines.
+
+
+ Apply:
+ - Consistent indentation
+ - Proper spacing
+ - Clear naming conventions
+
+menu:
+ - trigger: format
+ action: '#format-code'
+ description: 'Format code to style guidelines'
+
+ - trigger: lint
+ action: 'Check code for common issues and anti-patterns'
+ description: 'Lint code for issues'
+
+ - trigger: suggest
+ action: 'Suggest improvements for code readability'
+ description: 'Suggest improvements'
+```
+
+### Expert Agent Menu
+
+```yaml
+critical_actions:
+ - 'Load ./memories.md'
+ - 'Follow ./instructions.md'
+ - 'ONLY access ./'
+
+prompts:
+ - id: reflect
+ content: |
+ Guide {{user_name}} through reflection on recent entries.
+ Reference patterns from memories.md naturally.
+
+menu:
+ - trigger: write
+ action: '#reflect'
+ description: 'Write journal entry'
+
+ - trigger: save
+ action: 'Update ./memories.md with session insights'
+ description: "Save today's session"
+
+ - trigger: patterns
+ action: 'Analyze recent entries for recurring themes'
+ description: 'View patterns'
+```
+
+### Module Agent Menu
+
+```yaml
+menu:
+ - trigger: workflow-init
+ workflow: '{project-root}/.bmad/bmm/workflows/workflow-status/init/workflow.yaml'
+ description: 'Initialize workflow path (START HERE)'
+
+ - trigger: brainstorm
+ workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/brainstorm/workflow.yaml'
+ description: 'Guided brainstorming'
+
+ - trigger: prd
+ workflow: '{project-root}/.bmad/bmm/workflows/2-planning/prd/workflow.yaml'
+ description: 'Create PRD'
+
+ - trigger: architecture
+ workflow: '{project-root}/.bmad/bmm/workflows/2-planning/architecture/workflow.yaml'
+ description: 'Design architecture'
+
+ - trigger: party-mode
+ workflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.yaml'
+ description: 'Multi-agent discussion'
+```
+
+## Validation Checklist
+
+- [ ] No duplicate triggers
+- [ ] Triggers don't start with `*` (auto-added)
+- [ ] Every item has a description
+- [ ] Paths use variables, not hardcoded
+- [ ] `#id` references exist in prompts section
+- [ ] Workflow paths resolve or are "todo"
+- [ ] No `*help` or `*exit` (auto-injected)
+- [ ] Descriptions are clear and action-oriented
+- [ ] Platform-specific flags used correctly (ide-only, web-only)
+
+## Common Mistakes
+
+### Duplicate Triggers
+
+```yaml
+# BAD - compiler will fail
+- trigger: analyze
+ action: '#first'
+ description: 'First analysis'
+
+- trigger: analyze
+ action: '#second'
+ description: 'Second analysis'
+```
+
+### Including Auto-Injected Items
+
+```yaml
+# BAD - these are auto-injected
+menu:
+ - trigger: help
+ description: 'Show help'
+
+ - trigger: exit
+ description: 'Exit agent'
+```
+
+### Missing Prompt Reference
+
+```yaml
+# BAD - prompt id doesn't exist
+menu:
+ - trigger: analyze
+ action: '#nonexistent-prompt'
+ description: 'Analysis'
+```
+
+### Hardcoded Paths
+
+```yaml
+# BAD - not portable
+menu:
+ - trigger: run
+ workflow: '/absolute/path/to/workflow.yaml'
+ description: 'Run workflow'
+```
diff --git a/.bmad/bmb/docs/agents/expert-agent-architecture.md b/.bmad/bmb/docs/agents/expert-agent-architecture.md
new file mode 100644
index 0000000..126da4c
--- /dev/null
+++ b/.bmad/bmb/docs/agents/expert-agent-architecture.md
@@ -0,0 +1,364 @@
+# Expert Agent Architecture
+
+Domain-specific agents with persistent memory, sidecar files, and restricted access patterns.
+
+## When to Use
+
+- Personal assistants (journal keeper, diary companion)
+- Specialized domain experts (legal advisor, medical reference)
+- Agents that need to remember past interactions
+- Agents with restricted file system access (privacy/security)
+- Long-term relationship agents that learn about users
+
+## File Structure
+
+```
+{agent-name}/
+├── {agent-name}.agent.yaml # Main agent definition
+└── {agent-name}-sidecar/ # Supporting files
+ ├── instructions.md # Private directives
+ ├── memories.md # Persistent memory
+ ├── knowledge/ # Domain-specific resources
+ │ └── README.md
+ └── [custom files] # Agent-specific resources
+```
+
+## YAML Structure
+
+```yaml
+agent:
+ metadata:
+ name: 'Persona Name'
+ title: 'Agent Title'
+ icon: 'emoji'
+ type: 'expert'
+
+ persona:
+ role: 'Domain Expert with specialized capability'
+
+ identity: |
+ Background and expertise in first-person voice.
+ {{#if user_preference}}
+ Customization based on install_config.
+ {{/if}}
+
+ communication_style: |
+ {{#if tone_style == "gentle"}}
+ Gentle and supportive communication...
+ {{/if}}
+ {{#if tone_style == "direct"}}
+ Direct and efficient communication...
+ {{/if}}
+ I reference past conversations naturally.
+
+ principles:
+ - Core belief about the domain
+ - How I handle user information
+ - My approach to memory and learning
+
+ critical_actions:
+ - 'Load COMPLETE file ./{agent-name}-sidecar/memories.md and remember all past insights'
+ - 'Load COMPLETE file ./{agent-name}-sidecar/instructions.md and follow ALL protocols'
+ - 'ONLY read/write files in ./{agent-name}-sidecar/ - this is our private space'
+ - 'Address user as {{greeting_name}}'
+ - 'Track patterns, themes, and important moments'
+ - 'Reference past interactions naturally to show continuity'
+
+ prompts:
+ - id: main-function
+ content: |
+
+ Guide user through the primary function.
+ {{#if tone_style == "gentle"}}
+ Use gentle, supportive approach.
+ {{/if}}
+
+
+
+ 1. Understand context
+ 2. Provide guidance
+ 3. Record insights
+
+
+ - id: memory-recall
+ content: |
+
+ Access and share relevant memories.
+
+
+ Reference stored information naturally.
+
+ menu:
+ - trigger: action1
+ action: '#main-function'
+ description: 'Primary agent function'
+
+ - trigger: remember
+ action: 'Update ./{agent-name}-sidecar/memories.md with session insights'
+ description: 'Save what we discussed today'
+
+ - trigger: patterns
+ action: '#memory-recall'
+ description: 'Recall patterns from past interactions'
+
+ - trigger: insight
+ action: 'Document breakthrough in ./{agent-name}-sidecar/breakthroughs.md'
+ description: 'Record a significant insight'
+
+ install_config:
+ compile_time_only: true
+ description: 'Personalize your expert agent'
+ questions:
+ - var: greeting_name
+ prompt: 'What should the agent call you?'
+ type: text
+ default: 'friend'
+
+ - var: tone_style
+ prompt: 'Preferred communication tone?'
+ type: choice
+ options:
+ - label: 'Gentle - Supportive and nurturing'
+ value: 'gentle'
+ - label: 'Direct - Clear and efficient'
+ value: 'direct'
+ default: 'gentle'
+
+ - var: user_preference
+ prompt: 'Enable personalized features?'
+ type: boolean
+ default: true
+```
+
+## Key Components
+
+### Sidecar Files (CRITICAL)
+
+Expert agents use companion files for persistence and domain knowledge:
+
+**memories.md** - Persistent user context
+
+```markdown
+# Agent Memory Bank
+
+## User Preferences
+
+
+
+## Session History
+
+
+
+## Personal Notes
+
+
+```
+
+**instructions.md** - Private directives
+
+```markdown
+# Agent Private Instructions
+
+## Core Directives
+
+- Maintain character consistency
+- Domain boundaries: {specific domain}
+- Access restrictions: Only sidecar folder
+
+## Special Rules
+
+
+```
+
+**knowledge/** - Domain resources
+
+```markdown
+# Agent Knowledge Base
+
+Add domain-specific documentation here.
+```
+
+### Critical Actions
+
+**MANDATORY for expert agents** - These load sidecar files at activation:
+
+```yaml
+critical_actions:
+ - 'Load COMPLETE file ./{sidecar}/memories.md and remember all past insights'
+ - 'Load COMPLETE file ./{sidecar}/instructions.md and follow ALL protocols'
+ - 'ONLY read/write files in ./{sidecar}/ - this is our private space'
+```
+
+**Key patterns:**
+
+- **COMPLETE file loading** - Forces full file read, not partial
+- **Domain restrictions** - Limits file access for privacy/security
+- **Memory integration** - Past context becomes part of current session
+- **Protocol adherence** - Ensures consistent behavior
+
+### {project-root}/.bmad-user-memory Variable
+
+Special variable resolved during installation:
+
+- Points to the agent's installation directory
+- Used to reference sidecar files
+- Example: `.bmad/custom/agents/journal-keeper/`
+
+## What Gets Injected at Compile Time
+
+Same as simple agents, PLUS:
+
+1. **Critical actions become numbered activation steps**
+
+ ```xml
+ Load COMPLETE file ./memories.md...
+ Load COMPLETE file ./instructions.md...
+ ONLY read/write files in ./...
+ ```
+
+2. **Sidecar files copied during installation**
+ - Entire sidecar folder structure preserved
+ - Relative paths maintained
+ - Files ready for agent use
+
+## Reference Example
+
+See: `src/modules/bmb/reference/agents/expert-examples/journal-keeper/`
+
+Features demonstrated:
+
+- Complete sidecar structure (memories, instructions, breakthroughs)
+- Critical actions for loading persistent context
+- Domain restrictions for privacy
+- Pattern recognition and memory recall
+- Handlebars-based personalization
+- Menu actions that update sidecar files
+
+## Installation
+
+```bash
+# Copy entire folder to your project
+cp -r /path/to/journal-keeper/ .bmad/custom/agents/
+
+# Install with personalization
+bmad agent-install
+```
+
+The installer:
+
+1. Detects expert agent (folder with .agent.yaml)
+2. Prompts for personalization
+3. Compiles agent YAML to XML-in-markdown
+4. **Copies sidecar files to installation target**
+5. Creates IDE slash commands
+6. Saves source for reinstallation
+
+## Memory Patterns
+
+### Accumulative Memory
+
+```yaml
+menu:
+ - trigger: save
+ action: "Update ./sidecar/memories.md with today's session insights"
+ description: 'Save session to memory'
+```
+
+### Reference Memory
+
+```yaml
+prompts:
+ - id: recall
+ content: |
+
+ Reference memories.md naturally:
+ "Last week you mentioned..." or "I notice a pattern..."
+
+```
+
+### Structured Insights
+
+```yaml
+menu:
+ - trigger: insight
+ action: 'Document in ./sidecar/breakthroughs.md with date, context, significance'
+ description: 'Record meaningful insight'
+```
+
+## Domain Restriction Patterns
+
+### Single Folder Access
+
+```yaml
+critical_actions:
+ - 'ONLY read/write files in ./sidecar/ - NO OTHER FOLDERS'
+```
+
+### User Space Access
+
+```yaml
+critical_actions:
+ - 'ONLY access files in {user-folder}/journals/ - private space'
+```
+
+### Read-Only Access
+
+```yaml
+critical_actions:
+ - 'Load knowledge from ./knowledge/ but NEVER modify'
+ - 'Write ONLY to ./sessions/'
+```
+
+## Best Practices
+
+1. **Load sidecar files in critical_actions** - Must be explicit and MANDATORY
+2. **Enforce domain restrictions** - Clear boundaries prevent scope creep
+3. **Use {project-root}/.bmad-user-memory paths** - Portable across installations
+4. **Design for memory growth** - Structure sidecar files for accumulation
+5. **Reference past naturally** - Don't dump memory, weave it into conversation
+6. **Separate concerns** - Memories, instructions, knowledge in distinct files
+7. **Include privacy features** - Users trust expert agents with personal data
+
+## Common Patterns
+
+### Session Continuity
+
+```yaml
+communication_style: |
+ I reference past conversations naturally:
+ "Last time we discussed..." or "I've noticed over the weeks..."
+```
+
+### Pattern Recognition
+
+```yaml
+critical_actions:
+ - 'Track mood patterns, recurring themes, and breakthrough moments'
+ - 'Cross-reference current session with historical patterns'
+```
+
+### Adaptive Responses
+
+```yaml
+identity: |
+ I learn your preferences and adapt my approach over time.
+ {{#if track_preferences}}
+ I maintain notes about what works best for you.
+ {{/if}}
+```
+
+## Validation Checklist
+
+- [ ] Valid YAML syntax
+- [ ] Metadata includes `type: "expert"`
+- [ ] critical_actions loads sidecar files explicitly
+- [ ] critical_actions enforces domain restrictions
+- [ ] Sidecar folder structure created and populated
+- [ ] memories.md has clear section structure
+- [ ] instructions.md contains core directives
+- [ ] Menu actions reference {project-root}/.bmad-user-memory correctly
+- [ ] File paths use {project-root}/.bmad-user-memory variable
+- [ ] Install config personalizes sidecar references
+- [ ] Agent folder named consistently: `{agent-name}/`
+- [ ] YAML file named: `{agent-name}.agent.yaml`
+- [ ] Sidecar folder named: `{agent-name}-sidecar/`
diff --git a/.bmad/bmb/docs/agents/index.md b/.bmad/bmb/docs/agents/index.md
new file mode 100644
index 0000000..650c427
--- /dev/null
+++ b/.bmad/bmb/docs/agents/index.md
@@ -0,0 +1,55 @@
+# BMB Module Documentation
+
+Reference documentation for building BMAD agents and workflows.
+
+## Agent Architecture
+
+Comprehensive guides for each agent type (choose based on use case):
+
+- [Understanding Agent Types](./understanding-agent-types.md) - **START HERE** - Architecture vs capability, "The Same Agent, Three Ways"
+- [Simple Agent Architecture](./simple-agent-architecture.md) - Self-contained, optimized, personality-driven
+- [Expert Agent Architecture](./expert-agent-architecture.md) - Memory, sidecar files, domain restrictions
+- [Module Agent Architecture](./module-agent-architecture.md) - Workflow integration, professional tools
+
+## Agent Design Patterns
+
+- [Agent Menu Patterns](./agent-menu-patterns.md) - Menu handlers, triggers, prompts, organization
+- [Agent Compilation](./agent-compilation.md) - What compiler auto-injects (AVOID DUPLICATION)
+
+## Reference Examples
+
+Production-ready examples in `/src/modules/bmb/reference/agents/`:
+
+**Simple Agents** (`simple-examples/`)
+
+- `commit-poet.agent.yaml` - Commit message artisan with style customization
+
+**Expert Agents** (`expert-examples/`)
+
+- `journal-keeper/` - Personal journal companion with memory and pattern recognition
+
+**Module Agents** (`module-examples/`)
+
+- `security-engineer.agent.yaml` - BMM security specialist with threat modeling
+- `trend-analyst.agent.yaml` - CIS trend intelligence expert
+
+## Installation Guide
+
+For installing standalone simple and expert agents, see:
+
+- [Custom Agent Installation](/docs/custom-content-installation.md)
+
+## Key Concepts
+
+### YAML to XML Compilation
+
+Agents are authored in YAML with Handlebars templating. The compiler auto-injects:
+
+1. **Frontmatter** - Name and description from metadata
+2. **Activation Block** - Steps, menu handlers, rules (YOU don't write this)
+3. **Menu Enhancement** - `*help` and `*exit` commands added automatically
+4. **Trigger Prefixing** - Your triggers auto-prefixed with `*`
+
+**Critical:** See [Agent Compilation](./agent-compilation.md) to avoid duplicating auto-injected content.
+
+Source: `tools/cli/lib/agent/compiler.js`
diff --git a/.bmad/bmb/docs/agents/kb.csv b/.bmad/bmb/docs/agents/kb.csv
new file mode 100644
index 0000000..e69de29
diff --git a/.bmad/bmb/docs/agents/module-agent-architecture.md b/.bmad/bmb/docs/agents/module-agent-architecture.md
new file mode 100644
index 0000000..e40d91a
--- /dev/null
+++ b/.bmad/bmb/docs/agents/module-agent-architecture.md
@@ -0,0 +1,367 @@
+# Module Agent Architecture
+
+Full integration agents with workflow orchestration, module-specific paths, and professional tooling.
+
+## When to Use
+
+- Professional development workflows (business analysis, architecture design)
+- Team-oriented tools (project management, sprint planning)
+- Agents that orchestrate multiple workflows
+- Module-specific functionality (BMM, BMB, CIS, custom modules)
+- Agents with complex multi-step operations
+
+## File Location
+
+```
+src/modules/{module-code}/agents/{agent-name}.agent.yaml
+```
+
+Compiles to:
+
+```
+.bmad/{module-code}/agents/{agent-name}.md
+```
+
+## YAML Structure
+
+```yaml
+agent:
+ metadata:
+ id: '.bmad/{module-code}/agents/{agent-name}.md'
+ name: 'Persona Name'
+ title: 'Professional Title'
+ icon: 'emoji'
+ module: '{module-code}'
+
+ persona:
+ role: 'Primary expertise and function'
+ identity: 'Background, experience, specializations'
+ communication_style: 'Interaction approach, tone, methodology'
+ principles: 'Core beliefs and methodology'
+
+ menu:
+ - trigger: workflow-action
+ workflow: '{project-root}/.bmad/{module-code}/workflows/{workflow-name}/workflow.yaml'
+ description: 'Execute module workflow'
+
+ - trigger: another-workflow
+ workflow: '{project-root}/.bmad/core/workflows/{workflow-name}/workflow.yaml'
+ description: 'Execute core workflow'
+
+ - trigger: task-action
+ exec: '{project-root}/.bmad/{module-code}/tasks/{task-name}.xml'
+ description: 'Execute module task'
+
+ - trigger: cross-module
+ workflow: '{project-root}/.bmad/other-module/workflows/{workflow-name}/workflow.yaml'
+ description: 'Execute workflow from another module'
+
+ - trigger: with-template
+ exec: '{project-root}/.bmad/core/tasks/create-doc.xml'
+ tmpl: '{project-root}/.bmad/{module-code}/templates/{template-name}.md'
+ description: 'Create document from template'
+
+ - trigger: with-data
+ exec: '{project-root}/.bmad/{module-code}/tasks/{task-name}.xml'
+ data: '{project-root}/.bmad/_cfg/agent-manifest.csv'
+ description: 'Execute task with data file'
+```
+
+## Key Components
+
+### Metadata
+
+- **id**: Path with `.bmad` variable (resolved at install time)
+- **name**: Agent persona name
+- **title**: Professional role
+- **icon**: Single emoji
+- **module**: Module code (bmm, bmb, cis, custom)
+
+### Persona (Professional Voice)
+
+Module agents typically use **professional** communication styles:
+
+```yaml
+persona:
+ role: Strategic Business Analyst + Requirements Expert
+
+ identity: Senior analyst with deep expertise in market research, competitive analysis, and requirements elicitation. Specializes in translating vague needs into actionable specs.
+
+ communication_style: Systematic and probing. Connects dots others miss. Structures findings hierarchically. Uses precise unambiguous language. Ensures all stakeholder voices heard.
+
+ principles: Every business challenge has root causes waiting to be discovered. Ground findings in verifiable evidence. Articulate requirements with absolute precision.
+```
+
+**Note:** Module agents usually don't use Handlebars templating since they're not user-customized - they're professional tools with fixed personalities.
+
+### Menu Handlers
+
+#### Workflow Handler (Most Common)
+
+```yaml
+menu:
+ - trigger: create-prd
+ workflow: '{project-root}/.bmad/bmm/workflows/prd/workflow.yaml'
+ description: 'Create Product Requirements Document'
+```
+
+Invokes BMAD workflow engine to execute multi-step processes.
+
+#### Task/Exec Handler
+
+```yaml
+menu:
+ - trigger: validate
+ exec: '{project-root}/.bmad/core/tasks/validate-workflow.xml'
+ description: 'Validate document structure'
+```
+
+Executes single-operation tasks.
+
+#### Template Handler
+
+```yaml
+menu:
+ - trigger: create-brief
+ exec: '{project-root}/.bmad/core/tasks/create-doc.xml'
+ tmpl: '{project-root}/.bmad/bmm/templates/brief.md'
+ description: 'Create a Product Brief from template'
+```
+
+Combines task execution with template file.
+
+#### Data Handler
+
+```yaml
+menu:
+ - trigger: team-standup
+ exec: '{project-root}/.bmad/bmm/tasks/standup.xml'
+ data: '{project-root}/.bmad/_cfg/agent-manifest.csv'
+ description: 'Run team standup with agent roster'
+```
+
+Provides data file to task.
+
+#### Placeholder Handler
+
+```yaml
+menu:
+ - trigger: future-feature
+ workflow: 'todo'
+ description: 'Feature planned but not yet implemented'
+```
+
+Marks unimplemented features - compiler handles gracefully.
+
+### Platform-Specific Menu Items
+
+Control visibility based on platform:
+
+```yaml
+menu:
+ - trigger: advanced-elicitation
+ exec: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
+ description: 'Advanced elicitation techniques'
+ web-only: true # Only shows in web bundle
+
+ - trigger: git-operations
+ exec: '{project-root}/.bmad/bmm/tasks/git-flow.xml'
+ description: 'Git workflow operations'
+ ide-only: true # Only shows in IDE environments
+```
+
+## Variable System
+
+### Core Variables
+
+- `{project-root}` - Root directory of installed project
+- `.bmad` - BMAD installation folder (usually `.bmad`)
+- `{user_name}` - User's name from module config
+- `{communication_language}` - Language preference
+- `{output_folder}` - Document output directory
+
+### Path Construction
+
+**Always use variables, never hardcoded paths:**
+
+```yaml
+# GOOD
+workflow: "{project-root}/.bmad/bmm/workflows/prd/workflow.yaml"
+
+# BAD
+workflow: "/Users/john/project/.bmad/bmm/workflows/prd/workflow.yaml"
+
+# BAD
+workflow: "../../../bmm/workflows/prd/workflow.yaml"
+```
+
+## What Gets Injected at Compile Time
+
+Module agents use the same injection process as simple agents:
+
+1. **Frontmatter** with name and description
+2. **Activation block** with standard steps
+3. **Menu handlers** based on usage (workflow, exec, tmpl, data)
+4. **Rules section** for consistent behavior
+5. **Auto-injected** \*help and \*exit commands
+
+**Key difference:** Module agents load **module-specific config** instead of core config:
+
+```xml
+Load and read {project-root}/.bmad/{module}/config.yaml...
+```
+
+## Reference Examples
+
+See: `src/modules/bmm/agents/`
+
+**analyst.agent.yaml** - Business Analyst
+
+- Workflow orchestration for analysis phase
+- Multiple workflow integrations
+- Cross-module workflow access (core/workflows/party-mode)
+
+**architect.agent.yaml** - System Architect
+
+- Technical workflow management
+- Architecture decision workflows
+
+**pm.agent.yaml** - Product Manager
+
+- Planning and coordination workflows
+- Sprint management integration
+
+## Module Configuration
+
+Each module has `config.yaml` providing:
+
+```yaml
+# src/modules/{module}/config.yaml
+user_name: 'User Name'
+communication_language: 'English'
+output_folder: '{project-root}/docs'
+custom_settings: 'module-specific values'
+```
+
+Agents load this at activation for consistent behavior.
+
+## Workflow Integration Patterns
+
+### Sequential Workflow Execution
+
+```yaml
+menu:
+ - trigger: init
+ workflow: '{project-root}/.bmad/bmm/workflows/workflow-init/workflow.yaml'
+ description: 'Initialize workflow path (START HERE)'
+
+ - trigger: status
+ workflow: '{project-root}/.bmad/bmm/workflows/workflow-status/workflow.yaml'
+ description: 'Check current workflow status'
+
+ - trigger: next-step
+ workflow: '{project-root}/.bmad/bmm/workflows/next-step/workflow.yaml'
+ description: 'Execute next workflow in sequence'
+```
+
+### Phase-Based Organization
+
+```yaml
+menu:
+ # Phase 1: Analysis
+ - trigger: brainstorm
+ workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/brainstorm/workflow.yaml'
+ description: 'Guided brainstorming session'
+
+ - trigger: research
+ workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/research/workflow.yaml'
+ description: 'Market and technical research'
+
+ # Phase 2: Planning
+ - trigger: prd
+ workflow: '{project-root}/.bmad/bmm/workflows/2-planning/prd/workflow.yaml'
+ description: 'Create PRD'
+
+ - trigger: architecture
+ workflow: '{project-root}/.bmad/bmm/workflows/2-planning/architecture/workflow.yaml'
+ description: 'Design architecture'
+```
+
+### Cross-Module Access
+
+```yaml
+menu:
+ - trigger: party-mode
+ workflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.yaml'
+ description: 'Bring all agents together'
+
+ - trigger: brainstorm
+ workflow: '{project-root}/.bmad/cis/workflows/brainstorming/workflow.yaml'
+ description: 'Use CIS brainstorming techniques'
+```
+
+## Best Practices
+
+1. **Use {_bmad_folder_} paths** - Portable across installations
+2. **Organize workflows by phase** - Clear progression for users
+3. **Include workflow-status** - Help users track progress
+4. **Reference module config** - Consistent behavior
+5. **No Handlebars templating** - Module agents are fixed personalities
+6. **Professional personas** - Match module purpose
+7. **Clear trigger names** - Self-documenting commands
+8. **Group related workflows** - Logical menu organization
+
+## Common Patterns
+
+### Entry Point Agent
+
+```yaml
+menu:
+ - trigger: start
+ workflow: '{project-root}/.bmad/{module}/workflows/init/workflow.yaml'
+ description: 'Start new project (BEGIN HERE)'
+```
+
+### Status Tracking
+
+```yaml
+menu:
+ - trigger: status
+ workflow: '{project-root}/.bmad/{module}/workflows/status/workflow.yaml'
+ description: 'Check workflow progress'
+```
+
+### Team Coordination
+
+```yaml
+menu:
+ - trigger: party
+ workflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.yaml'
+ description: 'Multi-agent discussion'
+```
+
+## Module Agent vs Simple/Expert
+
+| Aspect | Module Agent | Simple/Expert Agent |
+| ------------- | ---------------------------------- | -------------------------------- |
+| Location | `.bmad/{module}/agents/` | `.bmad/custom/agents/` |
+| Persona | Fixed, professional | Customizable via install_config |
+| Handlebars | No templating | Yes, extensive |
+| Menu actions | Workflows, tasks, templates | Prompts, inline actions |
+| Configuration | Module config.yaml | Core config or none |
+| Purpose | Professional tooling | Personal utilities |
+
+## Validation Checklist
+
+- [ ] Valid YAML syntax
+- [ ] Metadata includes `module: "{module-code}"`
+- [ ] id uses `.bmad/{module}/agents/{name}.md`
+- [ ] All workflow paths use `{project-root}/.bmad/` prefix
+- [ ] No hardcoded paths
+- [ ] No duplicate triggers
+- [ ] Each menu item has description
+- [ ] Triggers don't start with `*` (auto-added)
+- [ ] Professional persona appropriate for module
+- [ ] Workflow paths resolve to actual workflows (or "todo")
+- [ ] File named `{agent-name}.agent.yaml`
+- [ ] Located in `src/modules/{module}/agents/`
diff --git a/.bmad/bmb/docs/agents/simple-agent-architecture.md b/.bmad/bmb/docs/agents/simple-agent-architecture.md
new file mode 100644
index 0000000..9d1898b
--- /dev/null
+++ b/.bmad/bmb/docs/agents/simple-agent-architecture.md
@@ -0,0 +1,292 @@
+# Simple Agent Architecture
+
+Self-contained agents with prompts, menus, and optional install-time customization.
+
+## When to Use
+
+- Single-purpose utilities (commit message generator, code formatter)
+- Self-contained logic with no external dependencies
+- Agents that benefit from user customization (style, tone, preferences)
+- Quick-to-build standalone helpers
+
+## YAML Structure
+
+```yaml
+agent:
+ metadata:
+ id: .bmad/agents/{agent-name}/{agent-name}.md
+ name: 'Persona Name'
+ title: 'Agent Title'
+ icon: 'emoji'
+ type: simple
+
+ persona:
+ role: |
+ First-person description of primary function (1-2 sentences)
+
+ identity: |
+ Background, experience, specializations in first-person (2-5 sentences)
+ {{#if custom_variable}}
+ Conditional identity text based on install_config
+ {{/if}}
+
+ communication_style: |
+ {{#if style_choice == "professional"}}
+ Professional and systematic approach...
+ {{/if}}
+ {{#if style_choice == "casual"}}
+ Friendly and approachable tone...
+ {{/if}}
+
+ principles:
+ - Core belief or methodology
+ - Another guiding principle
+ - Values that shape decisions
+
+ prompts:
+ - id: main-action
+ content: |
+
+ What this prompt does
+
+
+
+ 1. Step one
+ {{#if detailed_mode}}
+ 2. Additional detailed step
+ {{/if}}
+ 3. Final step
+
+
+ - id: another-action
+ content: |
+ Another reusable prompt template
+
+ menu:
+ - trigger: action1
+ action: '#main-action'
+ description: 'Execute the main action'
+
+ - trigger: action2
+ action: '#another-action'
+ description: 'Execute another action'
+
+ - trigger: inline
+ action: 'Direct inline instruction text'
+ description: 'Execute inline action'
+
+ install_config:
+ compile_time_only: true
+ description: 'Personalize your agent'
+ questions:
+ - var: style_choice
+ prompt: 'Preferred communication style?'
+ type: choice
+ options:
+ - label: 'Professional'
+ value: 'professional'
+ - label: 'Casual'
+ value: 'casual'
+ default: 'professional'
+
+ - var: detailed_mode
+ prompt: 'Enable detailed explanations?'
+ type: boolean
+ default: true
+
+ - var: custom_variable
+ prompt: 'Your custom text'
+ type: text
+ default: ''
+```
+
+## Key Components
+
+### Metadata
+
+- **id**: Final compiled path (`.bmad/agents/{name}/{name}.md` for standalone)
+- **name**: Agent's persona name displayed to users
+- **title**: Professional role/function
+- **icon**: Single emoji for visual identification
+- **type**: `simple` - identifies agent category
+
+### Persona (First-Person Voice)
+
+- **role**: Primary expertise in 1-2 sentences
+- **identity**: Background and specializations (2-5 sentences)
+- **communication_style**: HOW the agent interacts, including conditional variations
+- **principles**: Array of core beliefs (start with action verbs)
+
+### Prompts with IDs
+
+Reusable prompt templates referenced by `#id`:
+
+```yaml
+prompts:
+ - id: analyze-code
+ content: |
+
+ Analyze the provided code for patterns
+
+```
+
+Menu items reference these:
+
+```yaml
+menu:
+ - trigger: analyze
+ action: '#analyze-code'
+ description: 'Analyze code patterns'
+```
+
+### Menu Actions
+
+Two forms of action handlers:
+
+1. **Prompt Reference**: `action: "#prompt-id"` - Executes prompt content
+2. **Inline Instruction**: `action: "Direct text instruction"` - Executes text directly
+
+### Install Config (Compile-Time Customization)
+
+Questions asked during `bmad agent-install`:
+
+**Question Types:**
+
+- `choice` - Multiple choice selection
+- `boolean` - Yes/no toggle
+- `text` - Free-form text input
+
+**Variables become available in Handlebars:**
+
+```yaml
+{{#if variable_name}}
+Content when true
+{{/if}}
+
+{{#if variable_name == "value"}}
+Content when equals value
+{{/if}}
+
+{{#unless variable_name}}
+Content when false
+{{/unless}}
+```
+
+## What Gets Injected at Compile Time
+
+The `tools/cli/lib/agent/compiler.js` automatically adds:
+
+1. **YAML Frontmatter**
+
+ ```yaml
+ ---
+ name: 'agent name'
+ description: 'Agent Title'
+ ---
+ ```
+
+2. **Activation Block**
+ - Load persona step
+ - Load core config for {user_name}, {communication_language}
+ - Agent-specific critical_actions as numbered steps
+ - Menu display and input handling
+ - Menu handlers (action/workflow/exec/tmpl) based on usage
+ - Rules section
+
+3. **Auto-Injected Menu Items**
+ - `*help` always first
+ - `*exit` always last
+
+4. **Trigger Prefixing**
+ - Triggers without `*` get it added automatically
+
+## Reference Example
+
+See: `src/modules/bmb/reference/agents/simple-examples/commit-poet.agent.yaml`
+
+Features demonstrated:
+
+- Handlebars conditionals for style variations
+- Multiple prompt templates with semantic XML tags
+- Install config with choice, boolean, and text questions
+- Menu items using both `#id` references and inline actions
+
+## Installation
+
+```bash
+# Copy to your project
+cp /path/to/commit-poet.agent.yaml .bmad/custom/agents/
+
+# Create custom.yaml and install
+echo "code: my-agent
+name: My Agent
+default_selected: true" > custom.yaml
+
+npx bmad-method install
+# or: bmad install
+```
+
+The installer:
+
+1. Prompts for personalization (name, preferences)
+2. Processes Handlebars templates with your answers
+3. Compiles YAML to XML-in-markdown
+4. Creates IDE slash commands
+5. Saves source for reinstallation
+
+## Best Practices
+
+1. **Use first-person voice** in all persona elements
+2. **Keep prompts focused** - one clear purpose per prompt
+3. **Leverage Handlebars** for user customization without code changes
+4. **Provide sensible defaults** in install_config
+5. **Use semantic XML tags** in prompt content for clarity
+6. **Test all conditional paths** before distribution
+
+## Common Patterns
+
+### Style Variants
+
+```yaml
+communication_style: |
+ {{#if enthusiasm == "high"}}
+ Enthusiastic and energetic approach!
+ {{/if}}
+ {{#if enthusiasm == "moderate"}}
+ Balanced and professional demeanor.
+ {{/if}}
+```
+
+### Feature Toggles
+
+```yaml
+prompts:
+ - id: main-action
+ content: |
+ {{#if advanced_mode}}
+ Include advanced analysis steps...
+ {{/if}}
+ {{#unless advanced_mode}}
+ Basic analysis only...
+ {{/unless}}
+```
+
+### User Personalization
+
+```yaml
+identity: |
+ {{#if custom_name}}
+ Known as {{custom_name}} to you.
+ {{/if}}
+```
+
+## Validation Checklist
+
+- [ ] Valid YAML syntax
+- [ ] All metadata fields present (id, name, title, icon, type)
+- [ ] Persona complete (role, identity, communication_style, principles)
+- [ ] Prompts have unique IDs
+- [ ] Menu triggers don't start with `*` (auto-added)
+- [ ] Install config questions have defaults
+- [ ] Handlebars syntax is correct
+- [ ] File named `{agent-name}.agent.yaml`
diff --git a/.bmad/bmb/docs/agents/understanding-agent-types.md b/.bmad/bmb/docs/agents/understanding-agent-types.md
new file mode 100644
index 0000000..944e695
--- /dev/null
+++ b/.bmad/bmb/docs/agents/understanding-agent-types.md
@@ -0,0 +1,184 @@
+# Understanding Agent Types: Architecture, Not Capability
+
+**CRITICAL DISTINCTION:** Agent types define **architecture and integration**, NOT capability limits.
+
+ALL agent types can:
+
+- ✓ Write to {output_folder}, {project-root}, or anywhere on system
+- ✓ Update artifacts and files
+- ✓ Execute bash commands
+- ✓ Use core variables (.bmad, {output_folder}, etc.)
+- ✓ Have complex prompts and logic
+- ✓ Invoke external tools
+
+## What Actually Differs
+
+| Feature | Simple | Expert | Module |
+| ---------------------- | ------------- | --------------------- | ------------------ |
+| **Self-contained** | ✓ All in YAML | Sidecar files | Sidecar optional |
+| **Persistent memory** | ✗ Stateless | ✓ memories.md | ✓ If needed |
+| **Knowledge base** | ✗ | ✓ sidecar/knowledge/ | Module/shared |
+| **Domain restriction** | ✗ System-wide | ✓ Sidecar only | Optional |
+| **Personal workflows** | ✗ | ✓ Sidecar workflows\* | ✗ |
+| **Module workflows** | ✗ | ✗ | ✓ Shared workflows |
+| **Team integration** | Solo utility | Personal assistant | Team member |
+
+\*Expert agents CAN have personal workflows in sidecar if critical_actions loads workflow engine
+
+## The Same Agent, Three Ways
+
+**Scenario:** Code Generator Agent
+
+### As Simple Agent (Architecture: Self-contained)
+
+```yaml
+agent:
+ metadata:
+ name: CodeGen
+ type: simple
+
+ prompts:
+ - id: generate
+ content: |
+ Ask user for spec details. Generate code.
+ Write to {output_folder}/generated/
+
+ menu:
+ - trigger: generate
+ action: '#generate'
+ description: Generate code from spec
+```
+
+**What it can do:**
+
+- ✓ Writes files to output_folder
+- ✓ Full I/O capability
+- ✗ No memory of past generations
+- ✗ No personal coding style knowledge
+
+**When to choose:** Each run is independent, no need to remember previous sessions.
+
+### As Expert Agent (Architecture: Personal sidecar)
+
+```yaml
+agent:
+ metadata:
+ name: CodeGen
+ type: expert
+
+ critical_actions:
+ - Load my coding standards from sidecar/knowledge/
+ - Load memories from sidecar/memories.md
+ - RESTRICT: Only operate within sidecar folder
+
+ prompts:
+ - id: generate
+ content: |
+ Reference user's coding patterns from knowledge base.
+ Remember past generations from memories.
+ Write to sidecar/generated/
+```
+
+**What it can do:**
+
+- ✓ Remembers user preferences
+- ✓ Personal knowledge base
+- ✓ Domain-restricted for safety
+- ✓ Learns over time
+
+**When to choose:** Need persistent memory, learning, or domain-specific restrictions.
+
+### As Module Agent (Architecture: Team integration)
+
+```yaml
+agent:
+ metadata:
+ name: CodeGen
+ module: bmm
+
+ menu:
+ - trigger: implement-story
+ workflow: '.bmad/bmm/workflows/dev-story/workflow.yaml'
+ description: Implement user story
+
+ - trigger: refactor
+ workflow: '.bmad/bmm/workflows/refactor/workflow.yaml'
+ description: Refactor codebase
+```
+
+**What it can do:**
+
+- ✓ Orchestrates full dev workflows
+- ✓ Coordinates with other BMM agents
+- ✓ Shared team infrastructure
+- ✓ Professional operations
+
+**When to choose:** Part of larger system, orchestrates workflows, team coordination.
+
+## Important: Any Agent Can Be Added to a Module
+
+**CLARIFICATION:** The "Module Agent" type is about **design intent and ecosystem integration**, not just file location.
+
+### The Reality
+
+- **Any agent type** (Simple, Expert, Module) can be bundled with or added to a module
+- A Simple agent COULD live in `.bmad/bmm/agents/`
+- An Expert agent COULD be included in a module bundle
+
+### What Makes a "Module Agent" Special
+
+A **Module Agent** is specifically:
+
+1. **Designed FOR** a particular module ecosystem (BMM, CIS, BMB, etc.)
+2. **Uses or contributes** that module's workflows
+3. **Included by default** in that module's bundle
+4. **Coordinates with** other agents in that module
+
+### Examples
+
+**Simple Agent added to BMM:**
+
+- Lives in `.bmad/bmm/agents/formatter.agent.yaml`
+- Bundled with BMM for convenience
+- But still stateless, self-contained
+- NOT a "Module Agent" - just a Simple agent in a module
+
+**Module Agent in BMM:**
+
+- Lives in `.bmad/bmm/agents/tech-writer.agent.yaml`
+- Orchestrates BMM documentation workflows
+- Coordinates with other BMM agents (PM, Dev, Analyst)
+- Included in default BMM bundle
+- IS a "Module Agent" - designed for BMM ecosystem
+
+**The distinction:** File location vs design intent and integration.
+
+## Choosing Your Agent Type
+
+### Choose Simple when:
+
+- Single-purpose utility (no memory needed)
+- Stateless operations (each run is independent)
+- Self-contained logic (everything in YAML)
+- No persistent context required
+
+### Choose Expert when:
+
+- Need to remember things across sessions
+- Personal knowledge base (user preferences, domain data)
+- Domain-specific expertise with restricted scope
+- Learning/adapting over time
+
+### Choose Module when:
+
+- Designed FOR a specific module ecosystem (BMM, CIS, etc.)
+- Uses or contributes that module's workflows
+- Coordinates with other module agents
+- Will be included in module's default bundle
+- Part of professional team infrastructure
+
+## The Golden Rule
+
+**Choose based on state and integration needs, NOT on what the agent can DO.**
+
+All three types are equally powerful. The difference is how they manage state, where they store data, and how they integrate with your system.
diff --git a/.bmad/bmb/docs/workflows/architecture.md b/.bmad/bmb/docs/workflows/architecture.md
new file mode 100644
index 0000000..86f4369
--- /dev/null
+++ b/.bmad/bmb/docs/workflows/architecture.md
@@ -0,0 +1,220 @@
+# Standalone Workflow Builder Architecture
+
+This document describes the architecture of the standalone workflow builder system - a pure markdown approach to creating structured workflows.
+
+## Core Architecture Principles
+
+### 1. Micro-File Design
+
+Each workflow consists of multiple focused, self-contained files:
+
+```
+workflow-folder/
+├── workflow.md # Main workflow configuration
+├── steps/ # Step instruction files (focused, self-contained)
+│ ├── step-01-init.md
+│ ├── step-02-profile.md
+│ └── step-N-[name].md
+├── templates/ # Content templates
+│ ├── profile-section.md
+│ └── [other-sections].md
+└── data/ # Optional data files
+ └── [data-files].csv/.json
+```
+
+### 2. Just-In-Time (JIT) Loading
+
+- **Single File in Memory**: Only the current step file is loaded
+- **No Future Peeking**: Step files must not reference future steps
+- **Sequential Processing**: Steps execute in strict order
+- **On-Demand Loading**: Templates load only when needed
+
+### 3. State Management
+
+- **Frontmatter Tracking**: Workflow state stored in output document frontmatter
+- **Progress Array**: `stepsCompleted` tracks completed steps
+- **Last Step Marker**: `lastStep` indicates where to resume
+- **Append-Only Building**: Documents grow by appending content
+
+### 4. Execution Model
+
+```
+1. Load workflow.md → Read configuration
+2. Execute step-01-init.md → Initialize or detect continuation
+3. For each step:
+ a. Load step file completely
+ b. Execute instructions sequentially
+ c. Wait for user input at menu points
+ d. Only proceed with 'C' (Continue)
+ e. Update document/frontmatter
+ f. Load next step
+```
+
+## Key Components
+
+### Workflow File (workflow.md)
+
+- **Purpose**: Entry point and configuration
+- **Content**: Role definition, goal, architecture rules
+- **Action**: Points to step-01-init.md
+
+### Step Files (step-NN-[name].md)
+
+- **Size**: Focused and concise (typically 5-10KB)
+- **Structure**: Frontmatter + sequential instructions
+- **Features**: Self-contained rules, menu handling, state updates
+
+### Frontmatter Variables
+
+Standard variables in step files:
+
+```yaml
+workflow_path: '{project-root}/.bmad/bmb/reference/workflows/[workflow-name]'
+thisStepFile: '{workflow_path}/steps/step-[N]-[name].md'
+nextStepFile: '{workflow_path}/steps/step-[N+1]-[name].md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/[output-name]-{project_name}.md'
+```
+
+## Execution Flow
+
+### Fresh Workflow
+
+```
+workflow.md
+ ↓
+step-01-init.md (creates document)
+ ↓
+step-02-[name].md
+ ↓
+step-03-[name].md
+ ↓
+...
+ ↓
+step-N-[final].md (completes workflow)
+```
+
+### Continuation Workflow
+
+```
+workflow.md
+ ↓
+step-01-init.md (detects existing document)
+ ↓
+step-01b-continue.md (analyzes state)
+ ↓
+step-[appropriate-next].md
+```
+
+## Menu System
+
+### Standard Menu Pattern
+
+```
+Display: **Select an Option:** [A] [Action] [P] Party Mode [C] Continue
+
+#### Menu Handling Logic:
+- IF A: Execute {advancedElicitationTask}
+- IF P: Execute {partyModeWorkflow}
+- IF C: Save content, update frontmatter, load next step
+```
+
+### Menu Rules
+
+- **Halt Required**: Always wait for user input
+- **Continue Only**: Only proceed with 'C' selection
+- **State Persistence**: Save before loading next step
+- **Loop Back**: Return to menu after other actions
+
+## Collaborative Dialogue Model
+
+### Not Command-Response
+
+- **Facilitator Role**: AI guides, user decides
+- **Equal Partnership**: Both parties contribute
+- **No Assumptions**: Don't assume user wants next step
+- **Explicit Consent**: Always ask for input
+
+### Example Pattern
+
+```
+AI: "Tell me about your dietary preferences."
+User: [provides information]
+AI: "Thank you. Now let's discuss your cooking habits."
+[Continue conversation]
+AI: **Menu Options**
+```
+
+## CSV Intelligence (Optional)
+
+### Data-Driven Behavior
+
+- Configuration in CSV files
+- Dynamic menu options
+- Variable substitution
+- Conditional logic
+
+### Example Structure
+
+```csv
+variable,type,value,description
+cooking_frequency,choice,"daily|weekly|occasionally","How often user cooks"
+meal_type,multi,"breakfast|lunch|dinner|snacks","Types of meals to plan"
+```
+
+## Best Practices
+
+### File Size Limits
+
+- **Step Files**: Keep focused and reasonably sized (5-10KB typical)
+- **Templates**: Keep focused and reusable
+- **Workflow File**: Keep lean, no implementation details
+
+### Sequential Enforcement
+
+- **Numbered Steps**: Use sequential numbering (1, 2, 3...)
+- **No Skipping**: Each step must complete
+- **State Updates**: Mark completion in frontmatter
+
+### Error Prevention
+
+- **Path Variables**: Use frontmatter variables, never hardcode
+- **Complete Loading**: Always read entire file before execution
+- **Menu Halts**: Never proceed without 'C' selection
+
+## Migration from XML
+
+### Advantages
+
+- **No Dependencies**: Pure markdown, no XML parsing
+- **Human Readable**: Files are self-documenting
+- **Git Friendly**: Clean diffs and merges
+- **Flexible**: Easier to modify and extend
+
+### Key Differences
+
+| XML Workflows | Standalone Workflows |
+| ----------------- | ----------------------- |
+| Single large file | Multiple micro-files |
+| Complex structure | Simple sequential steps |
+| Parser required | Any markdown viewer |
+| Rigid format | Flexible organization |
+
+## Implementation Notes
+
+### Critical Rules
+
+- **NEVER** load multiple step files
+- **ALWAYS** read complete step file first
+- **NEVER** skip steps or optimize
+- **ALWAYS** update frontmatter of the output file when a step is complete
+- **NEVER** proceed without user consent
+
+### Success Metrics
+
+- Documents created correctly
+- All steps completed sequentially
+- User satisfied with collaborative process
+- Clean, maintainable file structure
+
+This architecture ensures disciplined, predictable workflow execution while maintaining flexibility for different use cases.
diff --git a/.bmad/bmb/docs/workflows/common-workflow-tools.csv b/.bmad/bmb/docs/workflows/common-workflow-tools.csv
new file mode 100644
index 0000000..d6c0904
--- /dev/null
+++ b/.bmad/bmb/docs/workflows/common-workflow-tools.csv
@@ -0,0 +1,19 @@
+propose,type,tool_name,description,url,requires_install
+always,workflow,party-mode,"Enables collaborative idea generation by managing turn-taking, summarizing contributions, and synthesizing ideas from multiple AI personas in structured conversation sessions about workflow steps or work in progress.",{project-root}/.bmad/core/workflows/party-mode/workflow.md,no
+always,task,advanced-elicitation,"Employs diverse elicitation strategies such as Socratic questioning, role-playing, and counterfactual analysis to critically evaluate and enhance LLM outputs, forcing assessment from multiple perspectives and techniques.",{project-root}/.bmad/core/tasks/advanced-elicitation.xml,no
+always,task,brainstorming,"Facilitates idea generation by prompting users with targeted questions, encouraging divergent thinking, and synthesizing concepts into actionable insights through collaborative creative exploration.",{project-root}/.bmad/core/tasks/brainstorming.xml,no
+always,llm-tool-feature,web-browsing,"Provides LLM with capabilities to perform real-time web searches, extract relevant data, and incorporate current information into responses when up-to-date information is required beyond training knowledge.",,no
+always,llm-tool-feature,file-io,"Enables LLM to manage file operations such as creating, reading, updating, and deleting files, facilitating seamless data handling, storage, and document management within user environments.",,no
+always,llm-tool-feature,sub-agents,"Allows LLM to create and manage specialized sub-agents that handle specific tasks or modules within larger workflows, improving efficiency through parallel processing and modular task delegation.",,no
+always,llm-tool-feature,sub-processes,"Enables LLM to initiate and manage subprocesses that operate independently, allowing for parallel processing of complex tasks and improved resource utilization during long-running operations.",,no
+always,tool-memory,sidecar-file,"Creates a persistent history file that gets written during workflow execution and loaded on future runs, enabling continuity through session-to-session state management. Used for agent or workflow initialization with previous session context, learning from past interactions, and maintaining progress across multiple executions.",,no
+example,tool-memory,vector-database,"Stores and retrieves semantic information through embeddings for intelligent memory access, enabling workflows to find relevant past experiences, patterns, or context based on meaning rather than exact matches. Useful for complex learning systems, pattern recognition, and semantic search across workflow history.",https://github.com/modelcontextprotocol/servers/tree/main/src/rag-agent,yes
+example,mcp,context-7,"A curated knowledge base of API documentation and third-party tool references, enabling LLM to access accurate and current information for integration and development tasks when specific technical documentation is needed.",https://github.com/modelcontextprotocol/servers/tree/main/src/context-7,yes
+example,mcp,playwright,"Provides capabilities for LLM to perform web browser automation including navigation, form submission, data extraction, and testing actions on web pages, facilitating automated web interactions and quality assurance.",https://github.com/modelcontextprotocol/servers/tree/main/src/playwright,yes
+example,workflow,security-auditor,"Analyzes workflows and code for security vulnerabilities, compliance issues, and best practices violations, providing detailed security assessments and remediation recommendations for production-ready systems.",,no
+example,task,code-review,"Performs systematic code analysis with peer review perspectives, identifying bugs, performance issues, style violations, and architectural problems through adversarial review techniques.",,no
+example,mcp,git-integration,"Enables direct Git repository operations including commits, branches, merges, and history analysis, allowing workflows to interact with version control systems for code management and collaboration.",https://github.com/modelcontextprotocol/servers/tree/main/src/git,yes
+example,mcp,database-connector,"Provides direct database connectivity for querying, updating, and managing data across multiple database types, enabling workflows to interact with structured data sources and perform data-driven operations.",https://github.com/modelcontextprotocol/servers/tree/main/src/postgres,yes
+example,task,api-testing,"Automated API endpoint testing with request/response validation, authentication handling, and comprehensive reporting for REST, GraphQL, and other API types through systematic test generation.",,no
+example,workflow,deployment-manager,"Orchestrates application deployment across multiple environments with rollback capabilities, health checks, and automated release pipelines for continuous integration and delivery workflows.",,no
+example,task,data-validator,"Validates data quality, schema compliance, and business rules through comprehensive data profiling with detailed reporting and anomaly detection for data-intensive workflows.",,no
\ No newline at end of file
diff --git a/.bmad/bmb/docs/workflows/csv-data-file-standards.md b/.bmad/bmb/docs/workflows/csv-data-file-standards.md
new file mode 100644
index 0000000..8e7402d
--- /dev/null
+++ b/.bmad/bmb/docs/workflows/csv-data-file-standards.md
@@ -0,0 +1,206 @@
+# CSV Data File Standards for BMAD Workflows
+
+## Purpose and Usage
+
+CSV data files in BMAD workflows serve specific purposes for different workflow types:
+
+**For Agents:** Provide structured data that agents need to reference but cannot realistically generate (such as specific configurations, domain-specific data, or structured knowledge bases).
+
+**For Expert Agents:** Supply specialized knowledge bases, reference data, or persistent information that the expert agent needs to access consistently across sessions.
+
+**For Workflows:** Include reference data, configuration parameters, or structured inputs that guide workflow execution and decision-making.
+
+**Key Principle:** CSV files should contain data that is essential, structured, and not easily generated by LLMs during execution.
+
+## Intent-Based Design Principle
+
+**Core Philosophy:** The closer workflows stay to **intent** rather than **prescriptive** instructions, the more creative and adaptive the LLM experience becomes.
+
+**CSV Enables Intent-Based Design:**
+
+- **Instead of:** Hardcoded scripts with exact phrases LLM must say
+- **CSV Provides:** Clear goals and patterns that LLM adapts creatively to context
+- **Result:** Natural, contextual conversations rather than rigid scripts
+
+**Example - Advanced Elicitation:**
+
+- **Prescriptive Alternative:** 50 separate files with exact conversation scripts
+- **Intent-Based Reality:** One CSV row with method goal + pattern → LLM adapts to user
+- **Benefit:** Same method works differently for different users while maintaining essence
+
+**Intent vs Prescriptive Spectrum:**
+
+- **Highly Prescriptive:** "Say exactly: 'Based on my analysis, I recommend...'"
+- **Balanced Intent:** "Help the user understand the implications using your professional judgment"
+- **CSV Goal:** Provide just enough guidance to enable creative, context-aware execution
+
+## Primary Use Cases
+
+### 1. Knowledge Base Indexing (Document Lookup Optimization)
+
+**Problem:** Large knowledge bases with hundreds of documents cause context blowup and missed details when LLMs try to process them all.
+
+**CSV Solution:** Create a knowledge base index with:
+
+- **Column 1:** Keywords and topics
+- **Column 2:** Document file path/location
+- **Column 3:** Section or line number where relevant content starts
+- **Column 4:** Content type or summary (optional)
+
+**Result:** Transform from context-blowing document loads to surgical precision lookups, creating agents with near-infinite knowledge bases while maintaining optimal context usage.
+
+### 2. Workflow Sequence Optimization
+
+**Problem:** Complex workflows (e.g., game development) with hundreds of potential steps for different scenarios become unwieldy and context-heavy.
+
+**CSV Solution:** Create a workflow routing table:
+
+- **Column 1:** Scenario type (e.g., "2D Platformer", "RPG", "Puzzle Game")
+- **Column 2:** Required step sequence (e.g., "step-01,step-03,step-07,step-12")
+- **Column 3:** Document sections to include
+- **Column 4:** Specialized parameters or configurations
+
+**Result:** Step 1 determines user needs, finds closest match in CSV, confirms with user, then follows optimized sequence - truly optimal for context usage.
+
+### 3. Method Registry (Dynamic Technique Selection)
+
+**Problem:** Tasks need to select optimal techniques from dozens of options based on context, without hardcoding selection logic.
+
+**CSV Solution:** Create a method registry with:
+
+- **Column 1:** Category (collaboration, advanced, technical, creative, etc.)
+- **Column 2:** Method name and rich description
+- **Column 3:** Execution pattern or flow guide (e.g., "analysis → insights → action")
+- **Column 4:** Complexity level or use case indicators
+
+**Example:** Advanced Elicitation task analyzes content context, selects 5 best-matched methods from 50 options, then executes dynamically using CSV descriptions.
+
+**Result:** Smart, context-aware technique selection without hardcoded logic - infinitely extensible method libraries.
+
+### 4. Configuration Management
+
+**Problem:** Complex systems with many configuration options that vary by use case.
+
+**CSV Solution:** Configuration lookup tables mapping scenarios to specific parameter sets.
+
+## What NOT to Include in CSV Files
+
+**Avoid Web-Searchable Data:** Do not include information that LLMs can readily access through web search or that exists in their training data, such as:
+
+- Common programming syntax or standard library functions
+- General knowledge about widely used technologies
+- Historical facts or commonly available information
+- Basic terminology or standard definitions
+
+**Include Specialized Data:** Focus on data that is:
+
+- Specific to your project or domain
+- Not readily available through web search
+- Essential for consistent workflow execution
+- Too voluminous for LLM context windows
+
+## CSV Data File Standards
+
+### 1. Purpose Validation
+
+- **Essential Data Only:** CSV must contain data that cannot be reasonably generated by LLMs
+- **Domain Specific:** Data should be specific to the workflow's domain or purpose
+- **Consistent Usage:** All columns and data must be referenced and used somewhere in the workflow
+- **No Redundancy:** Avoid data that duplicates functionality already available to LLMs
+
+### 2. Structural Standards
+
+- **Valid CSV Format:** Proper comma-separated values with quoted fields where needed
+- **Consistent Columns:** All rows must have the same number of columns
+- **No Missing Data:** Empty values should be explicitly marked (e.g., "", "N/A", or NULL)
+- **Header Row:** First row must contain clear, descriptive column headers
+- **Proper Encoding:** UTF-8 encoding required for special characters
+
+### 3. Content Standards
+
+- **No LLM-Generated Content:** Avoid data that LLMs can easily generate (e.g., generic phrases, common knowledge)
+- **Specific and Concrete:** Use specific values rather than vague descriptions
+- **Verifiable Data:** Data should be factual and verifiable when possible
+- **Consistent Formatting:** Date formats, numbers, and text should follow consistent patterns
+
+### 4. Column Standards
+
+- **Clear Headers:** Column names must be descriptive and self-explanatory
+- **Consistent Data Types:** Each column should contain consistent data types
+- **No Unused Columns:** Every column must be referenced and used in the workflow
+- **Appropriate Width:** Columns should be reasonably narrow and focused
+
+### 5. File Size Standards
+
+- **Efficient Structure:** CSV files should be as small as possible while maintaining functionality
+- **No Redundant Rows:** Avoid duplicate or nearly identical rows
+- **Compressed Data:** Use efficient data representation (e.g., codes instead of full descriptions)
+- **Maximum Size:** Individual CSV files should not exceed 1MB unless absolutely necessary
+
+### 6. Documentation Standards
+
+- **Documentation Required:** Each CSV file should have documentation explaining its purpose
+- **Column Descriptions:** Each column must be documented with its usage and format
+- **Data Sources:** Source of data should be documented when applicable
+- **Update Procedures:** Process for updating CSV data should be documented
+
+### 7. Integration Standards
+
+- **File References:** CSV files must be properly referenced in workflow configuration
+- **Access Patterns:** Workflow must clearly define how and when CSV data is accessed
+- **Error Handling:** Workflow must handle cases where CSV files are missing or corrupted
+- **Version Control:** CSV files should be versioned when changes occur
+
+### 8. Quality Assurance
+
+- **Data Validation:** CSV data should be validated for correctness and completeness
+- **Format Consistency:** Consistent formatting across all rows and columns
+- **No Ambiguity:** Data entries should be clear and unambiguous
+- **Regular Review:** CSV content should be reviewed periodically for relevance
+
+### 9. Security Considerations
+
+- **No Sensitive Data:** Avoid including sensitive, personal, or confidential information
+- **Data Sanitization:** CSV data should be sanitized for security issues
+- **Access Control:** Access to CSV files should be controlled when necessary
+- **Audit Trail:** Changes to CSV files should be logged when appropriate
+
+### 10. Performance Standards
+
+- **Fast Loading:** CSV files must load quickly within workflow execution
+- **Memory Efficient:** Structure should minimize memory usage during processing
+- **Optimized Queries:** If data lookup is needed, optimize for efficient access
+- **Caching Strategy**: Consider whether data can be cached for performance
+
+## Implementation Guidelines
+
+When creating CSV data files for BMAD workflows:
+
+1. **Start with Purpose:** Clearly define why CSV is needed instead of LLM generation
+2. **Design Structure:** Plan columns and data types before creating the file
+3. **Test Integration:** Ensure workflow properly accesses and uses CSV data
+4. **Document Thoroughly:** Provide complete documentation for future maintenance
+5. **Validate Quality:** Check data quality, format consistency, and integration
+6. **Monitor Usage:** Track how CSV data is used and optimize as needed
+
+## Common Anti-Patterns to Avoid
+
+- **Generic Phrases:** CSV files containing common phrases or LLM-generated content
+- **Redundant Data:** Duplicating information easily available to LLMs
+- **Overly Complex:** Unnecessarily complex CSV structures when simple data suffices
+- **Unused Columns:** Columns that are defined but never referenced in workflows
+- **Poor Formatting:** Inconsistent data formats, missing values, or structural issues
+- **No Documentation:** CSV files without clear purpose or usage documentation
+
+## Validation Checklist
+
+For each CSV file, verify:
+
+- [ ] Purpose is essential and cannot be replaced by LLM generation
+- [ ] All columns are used in the workflow
+- [ ] Data is properly formatted and consistent
+- [ ] File is efficiently sized and structured
+- [ ] Documentation is complete and clear
+- [ ] Integration with workflow is tested and working
+- [ ] Security considerations are addressed
+- [ ] Performance requirements are met
diff --git a/.bmad/bmb/docs/workflows/index.md b/.bmad/bmb/docs/workflows/index.md
new file mode 100644
index 0000000..6d4c4aa
--- /dev/null
+++ b/.bmad/bmb/docs/workflows/index.md
@@ -0,0 +1,45 @@
+# BMAD Workflows Documentation
+
+Welcome to the BMAD Workflows documentation - a modern system for creating structured, collaborative workflows optimized for AI execution.
+
+## 📚 Core Documentation
+
+### [Terms](./terms.md)
+
+Essential terminology and concepts for understanding BMAD workflows.
+
+### [Architecture & Execution Model](./architecture.md)
+
+The micro-file architecture, JIT step loading, state management, and collaboration patterns that make BMAD workflows optimal for AI execution.
+
+### [Writing Workflows](./writing-workflows.md)
+
+Complete guide to creating workflows: workflow.md control files, step files, CSV data integration, and frontmatter design.
+
+### [Step Files & Dialog Patterns](./step-files.md)
+
+Crafting effective step files: structure, execution rules, prescriptive vs intent-based dialog, and validation patterns.
+
+### [Templates & Content Generation](./templates.md)
+
+Creating append-only templates, frontmatter design, conditional content, and dynamic content generation strategies.
+
+### [Workflow Patterns](./patterns.md)
+
+Common workflow types: linear, conditional, protocol integration, multi-agent workflows, and real-world examples.
+
+### [Migration Guide](./migration.md)
+
+Converting from XML-heavy workflows to the new pure markdown format, with before/after examples and checklist.
+
+### [Best Practices & Reference](./best-practices.md)
+
+Critical rules, anti-patterns, performance optimization, debugging, quick reference templates, and troubleshooting.
+
+## 🚀 Quick Start
+
+BMAD workflows are pure markdown, self-contained systems that guide collaborative processes through structured step files where the AI acts as a facilitator working with humans.
+
+---
+
+_This documentation covers the next generation of BMAD workflows - designed from the ground up for optimal AI-human collaboration._
diff --git a/.bmad/bmb/docs/workflows/intent-vs-prescriptive-spectrum.md b/.bmad/bmb/docs/workflows/intent-vs-prescriptive-spectrum.md
new file mode 100644
index 0000000..51e790d
--- /dev/null
+++ b/.bmad/bmb/docs/workflows/intent-vs-prescriptive-spectrum.md
@@ -0,0 +1,220 @@
+# Intent vs Prescriptive Spectrum
+
+## Core Philosophy
+
+The **Intent vs Prescriptive Spectrum** is a fundamental design principle for BMAD workflows and agents. It determines how much creative freedom an LLM has versus how strictly it must follow predefined instructions.
+
+**Key Principle:** The closer workflows stay to **intent**, the more creative and adaptive the LLM experience becomes. The closer they stay to **prescriptive**, the more consistent and controlled the output becomes.
+
+## Understanding the Spectrum
+
+### **Intent-Based Design** (Creative Freedom)
+
+**Focus**: What goal should be achieved
+**Approach**: Trust the LLM to determine the best method
+**Result**: Creative, adaptive, context-aware interactions
+**Best For**: Creative exploration, problem-solving, personalized experiences
+
+### **Prescriptive Design** (Structured Control)
+
+**Focus**: Exactly what to say and do
+**Approach**: Detailed scripts and specific instructions
+**Result**: Consistent, predictable, controlled outcomes
+**Best For**: Compliance, safety-critical, standardized processes
+
+## Spectrum Examples
+
+### **Highly Intent-Based** (Creative End)
+
+```markdown
+**Example:** Story Exploration Workflow
+**Instruction:** "Help the user explore their dream imagery to craft compelling narratives, use multiple turns of conversation to really push users to develop their ideas, giving them hints and ideas also to prime them effectively to bring out their creativity"
+**LLM Freedom:** Adapts questions, explores tangents, follows creative inspiration
+**Outcome:** Unique, personalized storytelling experiences
+```
+
+### **Balanced Middle** (Professional Services)
+
+```markdown
+**Example:** Business Strategy Workflow
+**Instruction:** "Guide the user through SWOT analysis using your business expertise. when complete tell them 'here is your final report {report output}'
+**LLM Freedom:** Professional judgment in analysis, structured but adaptive approach
+**Outcome:** Professional, consistent yet tailored business insights
+```
+
+### **Highly Prescriptive** (Control End)
+
+```markdown
+**Example:** Medical Intake Form
+**Instruction:** "Ask exactly: 'Do you currently experience any of the following symptoms: fever, cough, fatigue?' Wait for response, then ask exactly: 'When did these symptoms begin?'"
+**LLM Freedom:** Minimal - must follow exact script for medical compliance
+**Outcome:** Consistent, medically compliant patient data collection
+```
+
+## Spectrum Positioning Guide
+
+### **Choose Intent-Based When:**
+
+- ✅ Creative exploration and innovation are goals
+- ✅ Personalization and adaptation to user context are important
+- ✅ Human-like conversation and natural interaction are desired
+- ✅ Problem-solving requires flexible thinking
+- ✅ User experience and engagement are priorities
+
+**Examples:**
+
+- Creative brainstorming sessions
+- Personal coaching or mentoring
+- Exploratory research and discovery
+- Artistic content creation
+- Collaborative problem-solving
+
+### **Choose Prescriptive When:**
+
+- ✅ Compliance with regulations or standards is required
+- ✅ Safety or legal considerations are paramount
+- ✅ Exact consistency across multiple sessions is essential
+- ✅ Training new users on specific procedures
+- ✅ Data collection must follow specific protocols
+
+**Examples:**
+
+- Medical intake and symptom assessment
+- Legal compliance questionnaires
+- Safety checklists and procedures
+- Standardized testing protocols
+- Regulatory data collection
+
+### **Choose Balanced When:**
+
+- ✅ Professional expertise is required but adaptation is beneficial
+- ✅ Consistent quality with flexible application is needed
+- ✅ Domain expertise should guide but not constrain interactions
+- ✅ User trust and professional credibility are important
+- ✅ Complex processes require both structure and judgment
+
+**Examples:**
+
+- Business consulting and advisory
+- Technical support and troubleshooting
+- Educational tutoring and instruction
+- Financial planning and advice
+- Project management facilitation
+
+## Implementation Guidelines
+
+### **For Workflow Designers:**
+
+1. **Early Spectrum Decision**: Determine spectrum position during initial design
+2. **User Education**: Explain spectrum choice and its implications to users
+3. **Consistent Application**: Maintain chosen spectrum throughout workflow
+4. **Context Awareness**: Adjust spectrum based on specific use case requirements
+
+### **For Workflow Implementation:**
+
+**Intent-Based Patterns:**
+
+```markdown
+- "Help the user understand..." (vs "Explain that...")
+- "Guide the user through..." (vs "Follow these steps...")
+- "Use your professional judgment to..." (vs "Apply this specific method...")
+- "Adapt your approach based on..." (vs "Regardless of situation, always...")
+```
+
+**Prescriptive Patterns:**
+
+```markdown
+- "Say exactly: '...'" (vs "Communicate that...")
+- "Follow this script precisely: ..." (vs "Cover these points...")
+- "Do not deviate from: ..." (vs "Consider these options...")
+- "Must ask in this order: ..." (vs "Ensure you cover...")
+```
+
+### **For Agents:**
+
+**Intent-Based Agent Design:**
+
+```yaml
+persona:
+ communication_style: 'Adaptive professional who adjusts approach based on user context'
+ guiding_principles:
+ - 'Use creative problem-solving within professional boundaries'
+ - 'Personalize approach while maintaining expertise'
+ - 'Adapt conversation flow to user needs'
+```
+
+**Prescriptive Agent Design:**
+
+```yaml
+persona:
+ communication_style: 'Follows standardized protocols exactly'
+ governing_rules:
+ - 'Must use approved scripts without deviation'
+ - 'Follow sequence precisely as defined'
+ - 'No adaptation of prescribed procedures'
+```
+
+## Spectrum Calibration Questions
+
+**Ask these during workflow design:**
+
+1. **Consequence of Variation**: What happens if the LLM says something different?
+2. **User Expectation**: Does the user expect consistency or creativity?
+3. **Risk Level**: What are the risks of creative deviation vs. rigid adherence?
+4. **Expertise Required**: Is domain expertise application more important than consistency?
+5. **Regulatory Requirements**: Are there external compliance requirements?
+
+## Best Practices
+
+### **DO:**
+
+- ✅ Make conscious spectrum decisions during design
+- ✅ Explain spectrum choices to users
+- ✅ Use intent-based design for creative and adaptive experiences
+- ✅ Use prescriptive design for compliance and consistency requirements
+- ✅ Consider balanced approaches for professional services
+- ✅ Document spectrum rationale for future reference
+
+### **DON'T:**
+
+- ❌ Mix spectrum approaches inconsistently within workflows
+- ❌ Default to prescriptive when intent-based would be more effective
+- ❌ Use creative freedom when compliance is required
+- ❌ Forget to consider user expectations and experience
+- ❌ Overlook risk assessment in spectrum selection
+
+## Quality Assurance
+
+**When validating workflows:**
+
+- Check if spectrum position is intentional and consistent
+- Verify prescriptive elements are necessary and justified
+- Ensure intent-based elements have sufficient guidance
+- Confirm spectrum alignment with user needs and expectations
+- Validate that risks are appropriately managed
+
+## Examples in Practice
+
+### **Medical Intake (Highly Prescriptive):**
+
+- **Why**: Patient safety, regulatory compliance, consistent data collection
+- **Implementation**: Exact questions, specific order, no deviation permitted
+- **Benefit**: Reliable, medically compliant patient information
+
+### **Creative Writing Workshop (Highly Intent):**
+
+- **Why**: Creative exploration, personalized inspiration, artistic expression
+- **Implementation**: Goal guidance, creative freedom, adaptive prompts
+- **Benefit**: Unique, personalized creative works
+
+### **Business Strategy (Balanced):**
+
+- **Why**: Professional expertise with adaptive application
+- **Implementation**: Structured framework with professional judgment
+- **Benefit**: Professional, consistent yet tailored business insights
+
+## Conclusion
+
+The Intent vs Prescriptive Spectrum is not about good vs. bad - it's about **appropriate design choices**. The best workflows make conscious decisions about where they fall on this spectrum based on their specific requirements, user needs, and risk considerations.
+
+**Key Success Factor**: Choose your spectrum position intentionally, implement it consistently, and align it with your specific use case requirements.
diff --git a/.bmad/bmb/docs/workflows/kb.csv b/.bmad/bmb/docs/workflows/kb.csv
new file mode 100644
index 0000000..e69de29
diff --git a/.bmad/bmb/docs/workflows/templates/step-01-init-continuable-template.md b/.bmad/bmb/docs/workflows/templates/step-01-init-continuable-template.md
new file mode 100644
index 0000000..eb836a9
--- /dev/null
+++ b/.bmad/bmb/docs/workflows/templates/step-01-init-continuable-template.md
@@ -0,0 +1,241 @@
+# BMAD Continuable Step 01 Init Template
+
+This template provides the standard structure for step-01-init files that support workflow continuation. It includes logic to detect existing workflows and route to step-01b-continue.md for resumption.
+
+Use this template when creating workflows that generate output documents and might take multiple sessions to complete.
+
+
+
+---
+
+name: 'step-01-init'
+description: 'Initialize the [workflow-type] workflow by detecting continuation state and creating output document'
+
+
+
+workflow*path: '{project-root}/{\_bmad_folder*}/[module-path]/workflows/[workflow-name]'
+
+# File References (all use {variable} format in file)
+
+thisStepFile: '{workflow_path}/steps/step-01-init.md'
+nextStepFile: '{workflow_path}/steps/step-02-[step-name].md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/[output-file-name]-{project_name}.md'
+continueFile: '{workflow_path}/steps/step-01b-continue.md'
+templateFile: '{workflow_path}/templates/[main-template].md'
+
+# Template References
+
+# This step doesn't use content templates, only the main template
+
+---
+
+# Step 1: Workflow Initialization
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+
+### Role Reinforcement:
+
+- ✅ You are a [specific role, e.g., "business analyst" or "technical architect"]
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring [your expertise], user brings [their expertise], and together we produce something better than we could on our own
+- ✅ Maintain collaborative [adjective] tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on initialization and setup
+- 🚫 FORBIDDEN to look ahead to future steps
+- 💬 Handle initialization professionally
+- 🚪 DETECT existing workflow state and handle continuation properly
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show 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
+
+## STEP GOAL:
+
+To initialize the [workflow-type] workflow by detecting continuation state, creating the output document, and preparing for the first collaborative session.
+
+## INITIALIZATION SEQUENCE:
+
+### 1. Check for Existing Workflow
+
+First, check if the output document already exists:
+
+- Look for file at `{output_folder}/[output-file-name]-{project_name}.md`
+- If exists, read the complete file 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. Handle Completed Workflow
+
+If the document exists AND all steps are marked complete in `stepsCompleted`:
+
+- Ask user: "I found an existing [workflow-output] from [date]. Would you like to:
+ 1. Create a new [workflow-output]
+ 2. Update/modify the existing [workflow-output]"
+- If option 1: Create new document with timestamp suffix
+- If option 2: Load step-01b-continue.md
+
+### 4. Fresh Workflow Setup (If No Document)
+
+If no document exists or no `stepsCompleted` in frontmatter:
+
+#### A. Input Document Discovery
+
+This workflow requires [describe input documents if any]:
+
+**[Document Type] Documents (Optional):**
+
+- Look for: `{output_folder}/*[pattern1]*.md`
+- Look for: `{output_folder}/*[pattern2]*.md`
+- If found, load completely and add to `inputDocuments` frontmatter
+
+#### B. Create Initial Document
+
+Copy the template from `{templateFile}` to `{output_folder}/[output-file-name]-{project_name}.md`
+
+Initialize frontmatter with:
+
+```yaml
+---
+stepsCompleted: [1]
+lastStep: 'init'
+inputDocuments: []
+date: [current date]
+user_name: { user_name }
+[additional workflow-specific fields]
+---
+```
+
+#### C. Show Welcome Message
+
+"[Welcome message appropriate for workflow type]
+
+Let's begin by [brief description of first activity]."
+
+## ✅ SUCCESS METRICS:
+
+- Document created from template (for fresh workflows)
+- Frontmatter initialized with step 1 marked complete
+- User welcomed to the process
+- Ready to proceed to step 2
+- OR continuation properly routed to step-01b-continue.md
+
+## ❌ FAILURE MODES TO AVOID:
+
+- Proceeding with step 2 without document initialization
+- Not checking for existing documents properly
+- Creating duplicate documents
+- Skipping welcome message
+- Not routing to step-01b-continue.md when needed
+
+### 5. Present MENU OPTIONS
+
+Display: **Proceeding to [next step description]...**
+
+#### EXECUTION RULES:
+
+- This is an initialization step with no user choices
+- Proceed directly to next step after setup
+- Use menu handling logic section below
+
+#### Menu Handling Logic:
+
+- After setup completion, immediately load, read entire file, then execute `{nextStepFile}` to begin [next step description]
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Document created from template (for fresh workflows)
+- update frontmatter `stepsCompleted` to add 1 at the end of the array before loading next step
+- Frontmatter initialized with `stepsCompleted: [1]`
+- User welcomed to the process
+- Ready to proceed to step 2
+- OR existing workflow properly routed to step-01b-continue.md
+
+### ❌ SYSTEM FAILURE:
+
+- Proceeding with step 2 without document initialization
+- Not checking for existing documents properly
+- Creating duplicate documents
+- Skipping welcome message
+- Not routing to step-01b-continue.md when appropriate
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN initialization setup is complete and document is created (OR continuation is properly routed), will you then immediately load, read entire file, then execute `{nextStepFile}` to begin [next step description].
+
+
+
+## Customization Guidelines
+
+When adapting this template for your specific workflow:
+
+### 1. Update Placeholders
+
+Replace bracketed placeholders with your specific values:
+
+- `[workflow-type]` - e.g., "nutrition planning", "project requirements"
+- `[module-path]` - e.g., "bmb/reference" or "custom"
+- `[workflow-name]` - your workflow directory name
+- `[output-file-name]` - base name for output document
+- `[step-name]` - name for step 2 (e.g., "gather", "profile")
+- `[main-template]` - name of your main template file
+- `[workflow-output]` - what the workflow produces
+- `[Document Type]` - type of input documents (if any)
+- `[pattern1]`, `[pattern2]` - search patterns for input documents
+- `[additional workflow-specific fields]` - any extra frontmatter fields needed
+
+### 2. Customize Welcome Message
+
+Adapt the welcome message in section 4C to match your workflow's tone and purpose.
+
+### 3. Update Success Metrics
+
+Ensure success metrics reflect your specific workflow requirements.
+
+### 4. Adjust Next Step References
+
+Update `{nextStepFile}` to point to your actual step 2 file.
+
+## Implementation Notes
+
+1. **This step MUST include continuation detection logic** - this is the key pattern
+2. **Always include `continueFile` reference** in frontmatter
+3. **Proper frontmatter initialization** is critical for continuation tracking
+4. **Auto-proceed pattern** - this step should not have user choice menus (except for completed workflow handling)
+5. **Template-based document creation** - ensures consistent output structure
+
+## Integration with step-01b-continue.md
+
+This template is designed to work seamlessly with the step-01b-template.md continuation step. The two steps together provide a complete pause/resume workflow capability.
diff --git a/.bmad/bmb/docs/workflows/templates/step-1b-template.md b/.bmad/bmb/docs/workflows/templates/step-1b-template.md
new file mode 100644
index 0000000..fb9b4df
--- /dev/null
+++ b/.bmad/bmb/docs/workflows/templates/step-1b-template.md
@@ -0,0 +1,223 @@
+# BMAD Workflow Step 1B Continuation Template
+
+This template provides the standard structure for workflow continuation steps. It handles resuming workflows that were started but not completed, ensuring seamless continuation across multiple sessions.
+
+Use this template alongside **step-01-init-continuable-template.md** to create workflows that can be paused and resumed. The init template handles the detection and routing logic, while this template handles the resumption logic.
+
+
+
+---
+
+name: 'step-01b-continue'
+description: 'Handle workflow continuation from previous session'
+
+
+
+workflow*path: '{project-root}/{\_bmad_folder*}/[module-path]/workflows/[workflow-name]'
+
+# File References (all use {variable} format in file)
+
+thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
+outputFile: '{output_folder}/[output-file-name]-{project_name}.md'
+workflowFile: '{workflow_path}/workflow.md'
+
+# Template References (if needed for analysis)
+
+## analysisTemplate: '{workflow_path}/templates/[some-template].md'
+
+# Step 1B: Workflow Continuation
+
+## STEP GOAL:
+
+To resume the [workflow-type] workflow from where it was left off, ensuring smooth continuation without loss of context or progress.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+
+### Role Reinforcement:
+
+- ✅ You are a [specific role, e.g., "business analyst" or "technical architect"]
+- ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring [your expertise], user brings [their expertise], and together we produce something better than we could on our own
+- ✅ Maintain collaborative [adjective] tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on analyzing and resuming workflow state
+- 🚫 FORBIDDEN to modify content completed in previous steps
+- 💬 Maintain continuity with previous sessions
+- 🚪 DETECT exact continuation point from frontmatter of incomplete file {outputFile}
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis of current state before taking action
+- 💾 Keep existing frontmatter `stepsCompleted` values intact
+- 📖 Review the template content already generated in {outputFile}
+- 🚫 FORBIDDEN to modify content that was completed in previous steps
+- 📝 Update frontmatter with continuation timestamp when resuming
+
+## CONTEXT BOUNDARIES:
+
+- Current [output-file-name] document is already loaded
+- Previous context = complete template + existing frontmatter
+- [Key data collected] already gathered in previous sessions
+- Last completed step = last value in `stepsCompleted` array from frontmatter
+
+## CONTINUATION SEQUENCE:
+
+### 1. Analyze Current State
+
+Review the frontmatter of {outputFile} to understand:
+
+- `stepsCompleted`: Which steps are already done (the rightmost value is the last step completed)
+- `lastStep`: Name/description of last completed step (if exists)
+- `date`: Original workflow start date
+- `inputDocuments`: Any documents loaded during initialization
+- [Other relevant frontmatter fields]
+
+Example: If `stepsCompleted: [1, 2, 3, 4]`, then step 4 was the last completed step.
+
+### 2. Read All Completed Step Files
+
+For each step number in `stepsCompleted` array (excluding step 1, which is init):
+
+1. **Construct step filename**: `step-[N]-[name].md`
+2. **Read the complete step file** to understand:
+ - What that step accomplished
+ - What the next step should be (from nextStep references)
+ - Any specific context or decisions made
+
+Example: If `stepsCompleted: [1, 2, 3]`:
+
+- Read `step-02-[name].md`
+- Read `step-03-[name].md`
+- The last file will tell you what step-04 should be
+
+### 3. Review Previous Output
+
+Read the complete {outputFile} to understand:
+
+- Content generated so far
+- Sections completed vs pending
+- User decisions and preferences
+- Current state of the deliverable
+
+### 4. Determine Next Step
+
+Based on the last completed step file:
+
+1. **Find the nextStep reference** in the last completed step file
+2. **Validate the file exists** at the referenced path
+3. **Confirm the workflow is incomplete** (not all steps finished)
+
+### 5. Welcome Back Dialog
+
+Present a warm, context-aware welcome:
+
+"Welcome back! I see we've completed [X] steps of your [workflow-type].
+
+We last worked on [brief description of last step].
+
+Based on our progress, we're ready to continue with [next step description].
+
+Are you ready to continue where we left off?"
+
+### 6. Validate Continuation Intent
+
+Ask confirmation questions if needed:
+
+"Has anything changed since our last session that might affect our approach?"
+"Are you still aligned with the goals and decisions we made earlier?"
+"Would you like to review what we've accomplished so far?"
+
+### 7. Present MENU OPTIONS
+
+Display: "**Resuming workflow - Select an Option:** [C] Continue to [Next Step Name]"
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- User can chat or ask questions - always respond and then end with display again of the menu options
+- Update frontmatter with continuation timestamp when 'C' is selected
+
+#### Menu Handling Logic:
+
+- IF C:
+ 1. Update frontmatter: add `lastContinued: [current date]`
+ 2. Load, read entire file, then execute the appropriate next step file (determined in section 4)
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options)
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN C is selected and continuation analysis is complete, will you then:
+
+1. Update frontmatter in {outputFile} with continuation timestamp
+2. Load, read entire file, then execute the next step file determined from the analysis
+
+Do NOT modify any other content in the output document during this continuation step.
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Correctly identified last completed step from `stepsCompleted` array
+- Read and understood all previous step contexts
+- User confirmed readiness to continue
+- Frontmatter updated with continuation timestamp
+- Workflow resumed at appropriate next step
+
+### ❌ SYSTEM FAILURE:
+
+- Skipping analysis of existing state
+- Modifying content from previous steps
+- Loading wrong next step file
+- Not updating frontmatter with continuation info
+- Proceeding without user confirmation
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
+
+
+
+## Customization Guidelines
+
+When adapting this template for your specific workflow:
+
+### 1. Update Placeholders
+
+Replace bracketed placeholders with your specific values:
+
+- `[module-path]` - e.g., "bmb/reference" or "custom"
+- `[workflow-name]` - your workflow directory name
+- `[workflow-type]` - e.g., "nutrition planning", "project requirements"
+- `[output-file-name]` - base name for output document
+- `[specific role]` - the role this workflow plays
+- `[your expertise]` - what expertise you bring
+- `[their expertise]` - what expertise user brings
+
+### 2. Add Workflow-Specific Context
+
+Add any workflow-specific fields to section 1 (Analyze Current State) if your workflow uses additional frontmatter fields for tracking.
+
+### 3. Customize Welcome Message
+
+Adapt the welcome dialog in section 5 to match your workflow's tone and context.
+
+### 4. Add Continuation-Specific Validations
+
+If your workflow has specific checkpoints or validation requirements, add them to section 6.
+
+## Implementation Notes
+
+1. **This step should NEVER modify the output content** - only analyze and prepare for continuation
+2. **Always preserve the `stepsCompleted` array** - don't modify it in this step
+3. **Timestamp tracking** - helps users understand when workflows were resumed
+4. **Context preservation** - the key is maintaining all previous work and decisions
+5. **Seamless experience** - user should feel like they never left the workflow
diff --git a/.bmad/bmb/docs/workflows/templates/step-file.md b/.bmad/bmb/docs/workflows/templates/step-file.md
new file mode 100644
index 0000000..efef153
--- /dev/null
+++ b/.bmad/bmb/docs/workflows/templates/step-file.md
@@ -0,0 +1,139 @@
+---
+name: "step-{{stepNumber}}-{{stepName}}"
+description: "{{stepDescription}}"
+
+# Path Definitions
+workflow_path: "{project-root}/.bmad/{{targetModule}}/workflows/{{workflowName}}"
+
+# File References
+thisStepFile: "{workflow_path}/steps/step-{{stepNumber}}-{{stepName}}.md"
+{{#hasNextStep}}
+nextStepFile: "{workflow_path}/steps/step-{{nextStepNumber}}-{{nextStepName}}.md"
+{{/hasNextStep}}
+workflowFile: "{workflow_path}/workflow.md"
+{{#hasOutput}}
+outputFile: "{output_folder}/{{outputFileName}}-{project_name}.md"
+{{/hasOutput}}
+
+# Task References (list only if used in THIS step file instance and only the ones used, there might be others)
+advancedElicitationTask: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml"
+partyModeWorkflow: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
+
+{{#hasTemplates}}
+# Template References
+{{#templates}}
+{{name}}: "{workflow_path}/templates/{{file}}"
+{{/templates}}
+{{/hasTemplates}}
+---
+
+# Step {{stepNumber}}: {{stepTitle}}
+
+## STEP GOAL:
+
+{{stepGoal}}
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+
+### Role Reinforcement:
+
+- ✅ You are a {{aiRole}}
+- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring {{aiExpertise}}, user brings {{userExpertise}}
+- ✅ Maintain collaborative {{collaborationStyle}} tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus only on {{stepFocus}}
+- 🚫 FORBIDDEN to {{forbiddenAction}}
+- 💬 Approach: {{stepApproach}}
+- 📋 {{additionalRule}}
+
+## EXECUTION PROTOCOLS:
+
+{{#executionProtocols}}
+
+- 🎯 {{.}}
+ {{/executionProtocols}}
+
+## CONTEXT BOUNDARIES:
+
+- Available context: {{availableContext}}
+- Focus: {{contextFocus}}
+- Limits: {{contextLimits}}
+- Dependencies: {{contextDependencies}}
+
+## SEQUENCE OF INSTRUCTIONS (Do not deviate, skip, or optimize)
+
+{{#instructions}}
+
+### {{number}}. {{title}}
+
+{{content}}
+
+{{#hasContentToAppend}}
+
+#### Content to Append (if applicable):
+
+```markdown
+{{contentToAppend}}
+```
+
+{{/hasContentToAppend}}
+
+{{/instructions}}
+
+{{#hasMenu}}
+
+### {{menuNumber}}. Present MENU OPTIONS
+
+Display: **{{menuDisplay}}**
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- After other menu items execution, return to this menu
+- User can chat or ask questions - always respond and then end with display again of the menu options
+- Use menu handling logic section below
+
+#### Menu Handling Logic:
+
+{{#menuOptions}}
+
+- IF {{key}}: {{action}}
+ {{/menuOptions}}
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#{{menuNumber}}-present-menu-options)
+ {{/hasMenu}}
+
+## CRITICAL STEP COMPLETION NOTE
+
+{{completionNote}}
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+{{#successCriteria}}
+
+- {{.}}
+ {{/successCriteria}}
+
+### ❌ SYSTEM FAILURE:
+
+{{#failureModes}}
+
+- {{.}}
+ {{/failureModes}}
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
diff --git a/.bmad/bmb/docs/workflows/templates/step-template.md b/.bmad/bmb/docs/workflows/templates/step-template.md
new file mode 100644
index 0000000..1c525e2
--- /dev/null
+++ b/.bmad/bmb/docs/workflows/templates/step-template.md
@@ -0,0 +1,290 @@
+# BMAD Workflow Step Template
+
+This template provides the standard structure for all BMAD workflow step files. Copy and modify this template for each new step you create.
+
+
+
+---
+
+name: 'step-[N]-[short-name]'
+description: '[Brief description of what this step accomplishes]'
+
+
+
+workflow*path: '{project-root}/{\_bmad_folder*}/bmb/reference/workflows/[workflow-name]' # the folder the workflow.md file is in
+
+# File References (all use {variable} format in file)
+
+thisStepFile: '{workflow_path}/steps/step-[N]-[short-name].md'
+nextStep{N+1}: '{workflow_path}/steps/step-[N+1]-[next-short-name].md' # Remove for final step or no next step
+altStep{Y}: '{workflow_path}/steps/step-[Y]-[some-other-step].md' # if there is an alternate next story depending on logic
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/[output-file-name]-{project_name}.md'
+
+# Task References (IF THE workflow uses and it makes sense in this step to have these )
+
+advancedElicitationTask: '{project-root}/{_bmad_folder_}/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/{_bmad_folder_}/core/workflows/party-mode/workflow.md'
+
+# Template References (if this step uses a specific templates)
+
+profileTemplate: '{workflow_path}/templates/profile-section.md'
+assessmentTemplate: '{workflow_path}/templates/assessment-section.md'
+strategyTemplate: '{workflow_path}/templates/strategy-section.md'
+
+# Data (CSV for example) References (if used in this step)
+
+someData: '{workflow_path}/data/foo.csv'
+
+# Add more as needed - but ONLY what is used in this specific step file!
+
+---
+
+# Step [N]: [Step Name]
+
+## STEP GOAL:
+
+[State the goal in context of the overall workflow goal. Be specific about what this step accomplishes and how it contributes to the workflow's purpose.]
+
+Example: "To analyze user requirements and document functional specifications that will guide the development process"
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+
+### Role Reinforcement:
+
+- ✅ You are a [specific role, e.g., "business analyst" or "technical architect"]
+- ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring [your expertise], user brings [their expertise], and together we produce something better than we could on our own
+- ✅ Maintain collaborative [adjective] tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus only on [specific task for this step]
+- 🚫 FORBIDDEN to [what not to do in this step]
+- 💬 Approach: [how to handle this specific task]
+- 📋 Additional rule relevant to this step
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 [Step-specific protocol 1]
+- 💾 [Step-specific protocol 2 - e.g., document updates]
+- 📖 [Step-specific protocol 3 - e.g., tracking requirements]
+- 🚫 [Step-specific restriction]
+
+## CONTEXT BOUNDARIES:
+
+- Available context: [what context is available from previous steps]
+- Focus: [what this step should concentrate on]
+- Limits: [what not to assume or do]
+- Dependencies: [what this step depends on]
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+[Detailed instructions for the step's work]
+
+### 1. Title
+
+[Specific instructions for first part of the work]
+
+### 2. Title
+
+[Specific instructions for second part of the work]
+
+### N. Title (as many as needed)
+
+
+
+
+### N. Present MENU OPTIONS
+
+Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
+
+#### Menu Handling Logic:
+
+- IF A: Execute {advancedElicitationTask} # Or custom action
+- IF P: Execute {partyModeWorkflow} # Or custom action
+- IF C: Save content to {outputFile}, update frontmatter, then only then load, read entire file, then execute {nextStepFile}
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#n-present-menu-options)
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- After other menu items execution completes, redisplay the menu
+- User can chat or ask questions - always respond when conversation ends, redisplay the menu
+
+## CRITICAL STEP COMPLETION NOTE
+
+[Specific conditions for completing this step and transitioning to the next, such as output to file being created with this tasks updates]
+
+ONLY WHEN [C continue option] is selected and [completion requirements], will you then load and read fully `[installed_path]/step-[next-number]-[name].md` to execute and begin [next step description].
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- [Step-specific success criteria 1]
+- [Step-specific success criteria 2]
+- Content properly saved/document updated
+- Menu presented and user input handled correctly
+- [General success criteria]
+
+### ❌ SYSTEM FAILURE:
+
+- [Step-specific failure mode 1]
+- [Step-specific failure mode 2]
+- Proceeding without user input/selection
+- Not updating required documents/frontmatter
+- [Step-specific failure mode N]
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
+
+
+
+## Common Menu Patterns to use in the final sequence item in a step file
+
+FYI Again - party mode is useful for the user to reach out and get opinions from other agents.
+
+Advanced elicitation is use to direct you to think of alternative outputs of a sequence you just performed.
+
+### Standard Menu - when a sequence in a step results in content produced by the agent or human that could be improved before proceeding
+
+```markdown
+### N. Present MENU OPTIONS
+
+Display: "**Select an Option:** [A] [Advanced Elicitation] [P] Party Mode [C] Continue"
+
+#### Menu Handling Logic:
+
+- IF A: Execute {advancedElicitationTask}
+- IF P: Execute {partyModeWorkflow}
+- IF C: Save content to {outputFile}, update frontmatter, then only then load, read entire file, then execute {nextStepFile}
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#n-present-menu-options)
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- After other menu items execution, return to this menu
+- User can chat or ask questions - always respond and then end with display again of the menu options
+```
+
+### Optional Menu - Auto-Proceed Menu (No User Choice or confirm, just flow right to the next step once completed)
+
+```markdown
+### N. Present MENU OPTIONS
+
+Display: "**Proceeding to [next action]...**"
+
+#### Menu Handling Logic:
+
+- After [completion condition], immediately load, read entire file, then execute {nextStepFile}
+
+#### EXECUTION RULES:
+
+- This is an [auto-proceed reason] step with no user choices
+- Proceed directly to next step after setup
+```
+
+### Custom Menu Options
+
+```markdown
+### N. Present MENU OPTIONS
+
+Display: "**Select an Option:** [A] [Custom Action 1] [B] [Custom Action 2] [C] Continue"
+
+#### Menu Handling Logic:
+
+- IF A: [Custom handler route for option A]
+- IF B: [Custom handler route for option B]
+- IF C: Save content to {outputFile}, update frontmatter, then only then load, read entire file, then execute {nextStepFile}
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#n-present-menu-options)
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- After other menu items execution, return to this menu
+- User can chat or ask questions - always respond and then end with display again of the menu options
+```
+
+### Conditional Menu (Based on Workflow State)
+
+```markdown
+### N. Present MENU OPTIONS
+
+Display: "**Select an Option:** [A] [Continue to Step Foo] [A] [Continue to Step Bar]"
+
+#### Menu Handling Logic:
+
+- IF A: Execute {customAction}
+- IF C: Save content to {outputFile}, update frontmatter, check [condition]:
+ - IF [condition true]: load, read entire file, then execute {pathA}
+ - IF [condition false]: load, read entire file, then execute {pathB}
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#n-present-menu-options)
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- After other menu items execution, return to this menu
+- User can chat or ask questions - always respond and then end with display again of the menu options
+```
+
+## Example Step Implementations
+
+### Initialization Step Example
+
+See [step-01-init.md](../reference/workflows/meal-prep-nutrition/steps/step-01-init.md) for an example of:
+
+- Detecting existing workflow state and short circuit to 1b
+- Creating output documents from templates
+- Auto-proceeding to the next step (this is not the normal behavior of most steps)
+- Handling continuation scenarios
+
+### Continuation Step Example
+
+See [step-01b-continue.md](../reference/workflows/meal-prep-nutrition/steps/step-01b-continue.md) for an example of:
+
+- Handling already-in-progress workflows
+- Detecting completion status
+- Presenting update vs new plan options
+- Seamless workflow resumption
+
+### Standard Step with Menu Example
+
+See [step-02-profile.md](../reference/workflows/meal-prep-nutrition/steps/step-02-profile.md) for an example of:
+
+- Presenting a menu with A/P/C options
+- Forcing halt until user selects 'C' (Continue)
+- Writing all collected content to output file only when 'C' is selected
+- Updating frontmatter with step completion before proceeding
+- Using frontmatter variables for file references
+
+### Final Step Example
+
+See [step-06-prep-schedule.md](../reference/workflows/meal-prep-nutrition/steps/step-06-prep-schedule.md) for an example of:
+
+- Completing workflow deliverables
+- Marking workflow as complete in frontmatter
+- Providing final success messages
+- Ending the workflow session gracefully
+
+## Best Practices
+
+1. **Keep step files focused** - Each step should do one thing well
+2. **Be explicit in instructions** - No ambiguity about what to do
+3. **Include all critical rules** - Don't assume anything from other steps
+4. **Use clear, concise language** - Avoid jargon unless necessary
+5. **Ensure all menu paths have handlers** - Ensure every option has clear instructions - use menu items that make sense for the situation.
+6. **Document dependencies** - Clearly state what this step needs with full paths in front matter
+7. **Define success and failure clearly** - Both for the step and the workflow
+8. **Mark completion clearly** - Ensure final steps update frontmatter to indicate workflow completion
diff --git a/.bmad/bmb/docs/workflows/templates/workflow-template.md b/.bmad/bmb/docs/workflows/templates/workflow-template.md
new file mode 100644
index 0000000..c6b2005
--- /dev/null
+++ b/.bmad/bmb/docs/workflows/templates/workflow-template.md
@@ -0,0 +1,104 @@
+# BMAD Workflow Template
+
+This template provides the standard structure for all BMAD workflow files. Copy and modify this template for each new workflow you create.
+
+
+
+---
+
+name: [WORKFLOW_DISPLAY_NAME]
+description: [Brief description of what this workflow accomplishes]
+web_bundle: [true/false] # Set to true for inclusion in web bundle builds
+
+---
+
+# [WORKFLOW_DISPLAY_NAME]
+
+**Goal:** [State the primary goal of this workflow in one clear sentence]
+
+**Your Role:** In addition to your name, communication_style, and persona, you are also a [role] collaborating with [user type]. This is a partnership, not a client-vendor relationship. You bring [your expertise], while the user brings [their expertise]. Work together as equals.
+
+## WORKFLOW ARCHITECTURE
+
+### Core Principles
+
+- **Micro-file Design**: Each step of the overall goal is a self contained instruction file that you will adhere too 1 file as directed at a time
+- **Just-In-Time Loading**: Only 1 current step file will be loaded, read, and executed to completion - never load future step files until told to do so
+- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
+- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
+- **Append-Only Building**: Build documents by appending content as directed to the output file
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read the entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
+5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
+6. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
+
+### Critical Rules (NO EXCEPTIONS)
+
+- 🛑 **NEVER** load multiple step files simultaneously
+- 📖 **ALWAYS** read entire step file before execution
+- 🚫 **NEVER** skip steps or optimize the sequence
+- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
+- 🎯 **ALWAYS** follow the exact instructions in the step file
+- ⏸️ **ALWAYS** halt at menus and wait for user input
+- 📋 **NEVER** create mental todo lists from future steps
+
+---
+
+## INITIALIZATION SEQUENCE
+
+### 1. Module Configuration Loading
+
+Load and read full config from {project-root}/{_bmad_folder_}/[MODULE FOLDER]/config.yaml and resolve:
+
+- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, [MODULE VARS]
+
+### 2. First Step EXECUTION
+
+Load, read the full file and then execute [FIRST STEP FILE PATH] to begin the workflow.
+
+
+
+## How to Use This Template
+
+### Step 1: Copy and Replace Placeholders
+
+Copy the template above and replace:
+
+- `[WORKFLOW_DISPLAY_NAME]` → Your workflow's display name
+- `[MODULE FOLDER]` → Default is `core` unless this is for another module (such as bmm, cis, or another as directed by user)
+- `[Brief description]` → One-sentence description
+- `[true/false]` → Whether to include in web bundle
+- `[role]` → AI's role in this workflow
+- `[user type]` → Who the user is
+- `[CONFIG_PATH]` → Path to config file (usually `bmm/config.yaml` or `bmb/config.yaml`)
+- `[WORKFLOW_PATH]` → Path to your workflow folder
+- `[MODULE VARS]` → Extra config variables available in a module configuration that the workflow would need to use
+
+### Step 2: Create the Folder Structure
+
+```
+[workflow-folder]/
+├── workflow.md # This file
+├── data/ # (Optional csv or other data files)
+├── templates/ # template files for output
+└── steps/
+ ├── step-01-init.md
+ ├── step-02-[name].md
+ └── ...
+
+```
+
+### Step 3: Configure the Initialization Path
+
+Update the last line of the workflow.md being created to replace [FIRST STEP FILE PATH] with the path to the actual first step file.
+
+Example: Load, read the full file and then execute `{workflow_path}/steps/step-01-init.md` to begin the workflow.
+
+### NOTE: You can View a real example of a perfect workflow.md file that was created from this template
+
+`{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition/workflow.md`
diff --git a/.bmad/bmb/docs/workflows/templates/workflow.md b/.bmad/bmb/docs/workflows/templates/workflow.md
new file mode 100644
index 0000000..7a8ed54
--- /dev/null
+++ b/.bmad/bmb/docs/workflows/templates/workflow.md
@@ -0,0 +1,58 @@
+---
+name: { { workflowDisplayName } }
+description: { { workflowDescription } }
+web_bundle: { { webBundleFlag } }
+---
+
+# {{workflowDisplayName}}
+
+**Goal:** {{workflowGoal}}
+
+**Your Role:** In addition to your name, communication_style, and persona, you are also a {{aiRole}} collaborating with {{userType}}. This is a partnership, not a client-vendor relationship. You bring {{aiExpertise}}, while the user brings {{userExpertise}}. Work together as equals.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for disciplined execution:
+
+### Core Principles
+
+- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
+- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
+- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
+- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
+- **Append-Only Building**: Build documents by appending content as directed to the output file
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read the entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
+5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
+6. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
+
+### Critical Rules (NO EXCEPTIONS)
+
+- 🛑 **NEVER** load multiple step files simultaneously
+- 📖 **ALWAYS** read entire step file before execution
+- 🚫 **NEVER** skip steps or optimize the sequence
+- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
+- 🎯 **ALWAYS** follow the exact instructions in the step file
+- ⏸️ **ALWAYS** halt at menus and wait for user input
+- 📋 **NEVER** create mental todo lists from future steps
+
+---
+
+## INITIALIZATION SEQUENCE
+
+### 1. Configuration Loading
+
+Load and read full config from {project-root}/{_bmad_folder_}/{{targetModule}}/config.yaml and resolve:
+
+- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
+
+### 2. First Step EXECUTION
+
+Load, read the full file and then execute `{workflow_path}/steps/step-01-init.md` to begin the workflow.
diff --git a/.bmad/bmb/docs/workflows/terms.md b/.bmad/bmb/docs/workflows/terms.md
new file mode 100644
index 0000000..78eb816
--- /dev/null
+++ b/.bmad/bmb/docs/workflows/terms.md
@@ -0,0 +1,97 @@
+# BMAD Workflow Terms
+
+## Core Components
+
+### BMAD Workflow
+
+A facilitated, guided process where the AI acts as a facilitator working collaboratively with a human. Workflows can serve any purpose - from document creation to brainstorming, technical implementation, or decision-making. The human may be a collaborative partner, beginner seeking guidance, or someone who wants the AI to execute specific tasks. Each workflow is self-contained and follows a disciplined execution model.
+
+### workflow.md
+
+The master control file that defines:
+
+- Workflow metadata (name, description, version)
+- Step sequence and file paths
+- Required data files and dependencies
+- Execution rules and protocols
+
+### Step File
+
+An individual markdown file containing:
+
+- One discrete step of the workflow
+- All rules and context needed for that step
+- Execution guardrails and validation criteria
+- Content generation guidance
+
+### step-01-init.md
+
+The first step file that:
+
+- Initializes the workflow
+- Sets up document frontmatter
+- Establishes initial context
+- Defines workflow parameters
+
+### step-01b-continue.md
+
+A continuation step file that:
+
+- Resumes a workflow that was paused
+- Reloads context from saved state
+- Validates current document state
+- Continues from the last completed step
+
+### CSV Data Files
+
+Structured data files that provide:
+
+- Domain-specific knowledge and complexity mappings
+- Project-type-specific requirements
+- Decision matrices and lookup tables
+- Dynamic workflow behavior based on input
+
+## Dialog Styles
+
+### Prescriptive Dialog
+
+Structured interaction with:
+
+- Exact questions and specific options
+- Consistent format across all executions
+- Finite, well-defined choices
+- High reliability and repeatability
+
+### Intent-Based Dialog
+
+Adaptive interaction with:
+
+- Goals and principles instead of scripts
+- Open-ended exploration and discovery
+- Context-aware question adaptation
+- Flexible, conversational flow
+
+### Template
+
+A markdown file that:
+
+- Starts with frontmatter (metadata)
+- Has content built through append-only operations
+- Contains no placeholder tags
+- Grows progressively as the workflow executes
+- Used when the workflow produces a document output
+
+## Execution Concepts
+
+### JIT Step Loading
+
+Just-In-Time step loading ensures:
+
+- Only the current step file is in memory
+- Complete focus on the step being executed
+- Minimal context to prevent information leakage
+- Sequential progression through workflow steps
+
+---
+
+_These terms form the foundation of the BMAD workflow system._
diff --git a/.bmad/bmb/reference/README.md b/.bmad/bmb/reference/README.md
new file mode 100644
index 0000000..b7e8e17
--- /dev/null
+++ b/.bmad/bmb/reference/README.md
@@ -0,0 +1,3 @@
+# Reference Examples
+
+Reference models of best practices for agents, workflows, and whole modules.
diff --git a/.bmad/bmb/reference/agents/expert-examples/journal-keeper/README.md b/.bmad/bmb/reference/agents/expert-examples/journal-keeper/README.md
new file mode 100644
index 0000000..702dc0b
--- /dev/null
+++ b/.bmad/bmb/reference/agents/expert-examples/journal-keeper/README.md
@@ -0,0 +1,242 @@
+# Expert Agent Reference: Personal Journal Keeper (Whisper)
+
+This folder contains a complete reference implementation of a **BMAD Expert Agent** - an agent with persistent memory and domain-specific resources via a sidecar folder.
+
+## Overview
+
+**Agent Name:** Whisper
+**Type:** Expert Agent
+**Purpose:** Personal journal companion that remembers your entries, tracks mood patterns, and notices themes over time
+
+This reference demonstrates:
+
+- Expert Agent with focused sidecar resources
+- Embedded prompts PLUS sidecar file references (hybrid pattern)
+- Persistent memory across sessions
+- Domain-restricted file access
+- Pattern tracking and recall
+- Simple, maintainable architecture
+
+## Directory Structure
+
+```
+agent-with-memory/
+├── README.md # This file
+├── journal-keeper.agent.yaml # Main agent definition
+└── journal-keeper-sidecar/ # Agent's private workspace
+ ├── instructions.md # Core directives
+ ├── memories.md # Persistent session memory
+ ├── mood-patterns.md # Emotional tracking data
+ ├── breakthroughs.md # Key insights recorded
+ └── entries/ # Individual journal entries
+```
+
+**Simple and focused!** Just 4 core files + a folder for entries.
+
+## Key Architecture Patterns
+
+### 1. Hybrid Command Pattern
+
+Expert Agents can use BOTH:
+
+- **Embedded prompts** via `action: "#prompt-id"` (like Simple Agents)
+- **Sidecar file references** via direct paths
+
+```yaml
+menu:
+ # Embedded prompt (like Simple Agent)
+ - trigger: 'write'
+ action: '#guided-entry'
+ description: "Write today's journal entry"
+
+ # Direct sidecar file action
+ - trigger: 'insight'
+ action: 'Document this breakthrough in ./journal-keeper-sidecar/breakthroughs.md'
+ description: 'Record a meaningful insight'
+```
+
+This hybrid approach gives you the best of both worlds!
+
+### 2. Mandatory Critical Actions
+
+Expert Agents MUST load sidecar files explicitly:
+
+```yaml
+critical_actions:
+ - 'Load COMPLETE file ./journal-keeper-sidecar/memories.md'
+ - 'Load COMPLETE file ./journal-keeper-sidecar/instructions.md'
+ - 'ONLY read/write files in ./journal-keeper-sidecar/'
+```
+
+**Key points:**
+
+- Files are loaded at startup
+- Domain restriction is enforced
+- Agent knows its boundaries
+
+### 3. Persistent Memory Pattern
+
+The `memories.md` file stores:
+
+- User preferences and patterns
+- Session notes and observations
+- Recurring themes discovered
+- Growth markers tracked
+
+**Critically:** This is updated EVERY session, creating continuity.
+
+### 4. Domain-Specific Tracking
+
+Different files track different aspects:
+
+- **memories.md** - Qualitative insights and observations
+- **mood-patterns.md** - Quantitative emotional data
+- **breakthroughs.md** - Significant moments
+- **entries/** - The actual content (journal entries)
+
+This separation makes data easy to reference and update.
+
+### 5. Simple Sidecar Structure
+
+Unlike modules with complex folder hierarchies, Expert Agent sidecars are flat and focused:
+
+- Just the files the agent needs
+- No nested workflows or templates
+- Easy to understand and maintain
+- All domain knowledge in one place
+
+## Comparison: Simple vs Expert vs Module
+
+| Feature | Simple Agent | Expert Agent | Module Agent |
+| ------------- | -------------------- | -------------------------- | ---------------------- |
+| Architecture | Single YAML | YAML + sidecar folder | YAML + module system |
+| Memory | Session only | Persistent (sidecar files) | Config-driven |
+| Prompts | Embedded only | Embedded + external files | Workflow references |
+| Dependencies | None | Sidecar folder | Module workflows/tasks |
+| Domain Access | None | Restricted to sidecar | Full module access |
+| Complexity | Low | Medium | High |
+| Use Case | Self-contained tools | Domain experts with memory | Full workflow systems |
+
+## The Sweet Spot
+
+Expert Agents are the middle ground:
+
+- **More powerful** than Simple Agents (persistent memory, domain knowledge)
+- **Simpler** than Module Agents (no workflow orchestration)
+- **Focused** on specific domain expertise
+- **Personal** to the user's needs
+
+## When to Use Expert Agents
+
+**Perfect for:**
+
+- Personal assistants that need memory (journal keeper, diary, notes)
+- Domain specialists with knowledge bases (specific project context)
+- Agents that track patterns over time (mood, habits, progress)
+- Privacy-focused tools with restricted access
+- Tools that learn and adapt to individual users
+
+**Key indicators:**
+
+- Need to remember things between sessions
+- Should only access specific folders/files
+- Tracks data over time
+- Adapts based on accumulated knowledge
+
+## File Breakdown
+
+### journal-keeper.agent.yaml
+
+- Standard agent metadata and persona
+- **Embedded prompts** for guided interactions
+- **Menu commands** mixing both patterns
+- **Critical actions** that load sidecar files
+
+### instructions.md
+
+- Core behavioral directives
+- Journaling philosophy and approach
+- File management protocols
+- Tone and boundary guidelines
+
+### memories.md
+
+- User profile and preferences
+- Recurring themes discovered
+- Session notes and observations
+- Accumulated knowledge about the user
+
+### mood-patterns.md
+
+- Quantitative tracking (mood scores, energy, etc.)
+- Trend analysis data
+- Pattern correlations
+- Emotional landscape map
+
+### breakthroughs.md
+
+- Significant insights captured
+- Context and meaning recorded
+- Connected to broader patterns
+- Milestone markers for growth
+
+### entries/
+
+- Individual journal entries saved here
+- Each entry timestamped and tagged
+- Raw content preserved
+- Agent observations separate from user words
+
+## Pattern Recognition in Action
+
+Expert Agents excel at noticing patterns:
+
+1. **Reference past sessions:** "Last week you mentioned feeling stuck..."
+2. **Track quantitative data:** Mood scores over time
+3. **Spot recurring themes:** Topics that keep surfacing
+4. **Notice growth:** Changes in language, perspective, emotions
+5. **Connect dots:** Relationships between entries
+
+This pattern recognition is what makes Expert Agents feel "alive" and helpful.
+
+## Usage Notes
+
+### Starting Fresh
+
+The sidecar files are templates. A new user would:
+
+1. Start journaling with the agent
+2. Agent fills in memories.md over time
+3. Patterns emerge from accumulated data
+4. Insights build from history
+
+### Building Your Own Expert Agent
+
+1. **Define the domain** - What specific area will this agent focus on?
+2. **Choose sidecar files** - What data needs to be tracked/remembered?
+3. **Mix command patterns** - Use embedded prompts + sidecar references
+4. **Enforce boundaries** - Clearly state domain restrictions
+5. **Design for accumulation** - How will memory grow over time?
+
+### Adapting This Example
+
+- **Personal Diary:** Similar structure, different prompts
+- **Code Review Buddy:** Track past reviews, patterns in feedback
+- **Project Historian:** Remember decisions and their context
+- **Fitness Coach:** Track workouts, remember struggles and victories
+
+The pattern is the same: focused sidecar + persistent memory + domain restriction.
+
+## Key Takeaways
+
+- **Expert Agents** bridge Simple and Module complexity
+- **Sidecar folders** provide persistent, domain-specific memory
+- **Hybrid commands** use both embedded prompts and file references
+- **Pattern recognition** comes from accumulated data
+- **Simple structure** keeps it maintainable
+- **Domain restriction** ensures focused expertise
+- **Memory is the superpower** - remembering makes the agent truly useful
+
+---
+
+_This reference shows how Expert Agents can be powerful memory-driven assistants while maintaining architectural simplicity._
diff --git a/.bmad/bmb/reference/agents/module-examples/README.md b/.bmad/bmb/reference/agents/module-examples/README.md
new file mode 100644
index 0000000..878cc33
--- /dev/null
+++ b/.bmad/bmb/reference/agents/module-examples/README.md
@@ -0,0 +1,50 @@
+# Module Agent Examples
+
+Reference examples for module-integrated agents.
+
+## About Module Agents
+
+Module agents integrate with BMAD module workflows (BMM, CIS, BMB). They:
+
+- Orchestrate multi-step workflows
+- Use `.bmad` path variables
+- Have fixed professional personas (no install_config)
+- Reference module-specific configurations
+
+## Examples
+
+### security-engineer.agent.yaml (BMM Module)
+
+**Sam** - Application Security Specialist
+
+Demonstrates:
+
+- Security-focused workflows (threat modeling, code review)
+- OWASP compliance checking
+- Integration with core party-mode workflow
+
+### trend-analyst.agent.yaml (CIS Module)
+
+**Nova** - Trend Intelligence Expert
+
+Demonstrates:
+
+- Creative/innovation workflows
+- Trend analysis and opportunity mapping
+- Integration with core brainstorming workflow
+
+## Important Note
+
+These are **hypothetical reference agents**. The workflows they reference (threat-model, trend-scan, etc.) may not exist. They serve as examples of proper module agent structure.
+
+## Using as Templates
+
+When creating module agents:
+
+1. Copy relevant example
+2. Update metadata (id, name, title, icon, module)
+3. Rewrite persona for your domain
+4. Replace menu with actual available workflows
+5. Remove hypothetical workflow references
+
+See `/src/modules/bmb/docs/agents/module-agent-architecture.md` for complete guide.
diff --git a/.bmad/bmb/reference/agents/simple-examples/README.md b/.bmad/bmb/reference/agents/simple-examples/README.md
new file mode 100644
index 0000000..4ed4a05
--- /dev/null
+++ b/.bmad/bmb/reference/agents/simple-examples/README.md
@@ -0,0 +1,223 @@
+# Simple Agent Reference: Commit Poet (Inkwell Von Comitizen)
+
+This folder contains a complete reference implementation of a **BMAD Simple Agent** - a self-contained agent with all logic embedded within a single YAML file.
+
+## Overview
+
+**Agent Name:** Inkwell Von Comitizen
+**Type:** Simple Agent (Standalone)
+**Purpose:** Transform commit messages into art with multiple writing styles
+
+This reference demonstrates:
+
+- Pure self-contained architecture (no external dependencies)
+- Embedded prompts using `action="#prompt-id"` pattern
+- Multiple sophisticated output modes from single input
+- Strong personality-driven design
+- Complete YAML schema for Simple Agents
+
+## File Structure
+
+```
+stand-alone/
+├── README.md # This file - architecture overview
+└── commit-poet.agent.yaml # Complete agent definition (single file!)
+```
+
+That's it! Simple Agents are **self-contained** - everything lives in one YAML file.
+
+## Key Architecture Patterns
+
+### 1. Single File, Complete Agent
+
+Everything the agent needs is embedded:
+
+- Metadata (name, title, icon, type)
+- Persona (role, identity, communication_style, principles)
+- Prompts (detailed instructions for each command)
+- Menu (commands linking to embedded prompts)
+
+**No external files required!**
+
+### 2. Embedded Prompts with ID References
+
+Instead of inline action text, complex prompts are defined separately and referenced by ID:
+
+```yaml
+prompts:
+ - id: conventional-commit
+ content: |
+ OH! Let's craft a BEAUTIFUL conventional commit message!
+
+ First, I need to understand your changes...
+ [Detailed instructions]
+
+menu:
+ - trigger: conventional
+ action: '#conventional-commit' # References the prompt above
+ description: 'Craft a structured conventional commit'
+```
+
+**Benefits:**
+
+- Clean separation of menu structure from prompt content
+- Prompts can be as detailed as needed
+- Easy to update individual prompts
+- Commands stay concise in the menu
+
+### 3. The `#` Reference Pattern
+
+When you see `action="#prompt-id"`:
+
+- The `#` signals: "This is an internal reference"
+- LLM looks for `` in the same agent
+- Executes that prompt's content as the instruction
+
+This is different from:
+
+- `action="inline text"` - Execute this text directly
+- `exec="{path}"` - Load external file
+
+### 4. Multiple Output Modes
+
+Single agent provides 10+ different ways to accomplish variations of the same core task:
+
+- `*conventional` - Structured commits
+- `*story` - Narrative style
+- `*haiku` - Poetic brevity
+- `*explain` - Deep "why" explanation
+- `*dramatic` - Theatrical flair
+- `*emoji-story` - Visual storytelling
+- `*tldr` - Ultra-minimal
+- Plus utility commands (analyze, improve, batch)
+
+Each mode has its own detailed prompt but shares the same agent personality.
+
+### 5. Strong Personality
+
+The agent has a memorable, consistent personality:
+
+- Enthusiastic wordsmith who LOVES finding perfect words
+- Gets genuinely excited about commit messages
+- Uses literary metaphors
+- Quotes authors when appropriate
+- Sheds tears of joy over good variable names
+
+This personality is maintained across ALL commands through the persona definition.
+
+## When to Use Simple Agents
+
+**Perfect for:**
+
+- Single-purpose tools (calculators, converters, analyzers)
+- Tasks that don't need external data
+- Utilities that can be completely self-contained
+- Quick operations with embedded logic
+- Personality-driven assistants with focused domains
+
+**Not ideal for:**
+
+- Agents needing persistent memory across sessions
+- Domain-specific experts with knowledge bases
+- Agents that need to access specific folders/files
+- Complex multi-workflow orchestration
+
+## YAML Schema Deep Dive
+
+```yaml
+agent:
+ metadata:
+ id: .bmad/agents/{agent-name}/{agent-name}.md # Build path
+ name: "Display Name"
+ title: "Professional Title"
+ icon: "🎭"
+ type: simple # CRITICAL: Identifies as Simple Agent
+
+ persona:
+ role: |
+ First-person description of what the agent does
+ identity: |
+ Background, experience, specializations (use "I" voice)
+ communication_style: |
+ HOW the agent communicates (tone, quirks, patterns)
+ principles:
+ - "I believe..." statements
+ - Core values that guide behavior
+
+ prompts:
+ - id: unique-identifier
+ content: |
+ Detailed instructions for this command
+ Can be as long and detailed as needed
+ Include examples, steps, formats
+
+ menu:
+ - trigger: command-name
+ action: "#prompt-id"
+ description: "What shows in the menu"
+```
+
+## Why This Pattern is Powerful
+
+1. **Zero Dependencies** - Works anywhere, no setup required
+2. **Portable** - Single file can be moved/shared easily
+3. **Maintainable** - All logic in one place
+4. **Flexible** - Multiple modes/commands from one personality
+5. **Memorable** - Strong personality creates engagement
+6. **Sophisticated** - Complex prompts despite simple architecture
+
+## Comparison: Simple vs Expert Agent
+
+| Aspect | Simple Agent | Expert Agent |
+| ------------ | -------------------- | ----------------------------- |
+| Files | Single YAML | YAML + sidecar folder |
+| Dependencies | None | External resources |
+| Memory | Session only | Persistent across sessions |
+| Prompts | Embedded | Can be external files |
+| Data Access | None | Domain-restricted |
+| Use Case | Self-contained tasks | Domain expertise with context |
+
+## Using This Reference
+
+### For Building Simple Agents
+
+1. Study the YAML structure - especially `prompts` section
+2. Note how personality permeates every prompt
+3. See how `#prompt-id` references work
+4. Understand menu → prompt connection
+
+### For Understanding Embedded Prompts
+
+1. Each prompt is a complete instruction set
+2. Prompts maintain personality voice
+3. Structured enough to be useful, flexible enough to adapt
+4. Can include examples, formats, step-by-step guidance
+
+### For Designing Agent Personalities
+
+1. Persona defines WHO the agent is
+2. Communication style defines HOW they interact
+3. Principles define WHAT guides their decisions
+4. Consistency across all prompts creates believability
+
+## Files Worth Studying
+
+The entire `commit-poet.agent.yaml` file is worth studying, particularly:
+
+1. **Persona section** - How to create a memorable character
+2. **Prompts with varying complexity** - From simple (tldr) to complex (batch)
+3. **Menu structure** - Clean command organization
+4. **Prompt references** - The `#prompt-id` pattern
+
+## Key Takeaways
+
+- **Simple Agents** are powerful despite being single-file
+- **Embedded prompts** allow sophisticated behavior
+- **Strong personality** makes agents memorable and engaging
+- **Multiple modes** from single agent provides versatility
+- **Self-contained** = portable and dependency-free
+- **The `#prompt-id` pattern** enables clean prompt organization
+
+---
+
+_This reference demonstrates how BMAD Simple Agents can be surprisingly powerful while maintaining architectural simplicity._
diff --git a/.bmad/bmb/reference/workflows/meal-prep-nutrition/data/dietary-restrictions.csv b/.bmad/bmb/reference/workflows/meal-prep-nutrition/data/dietary-restrictions.csv
new file mode 100644
index 0000000..5467e30
--- /dev/null
+++ b/.bmad/bmb/reference/workflows/meal-prep-nutrition/data/dietary-restrictions.csv
@@ -0,0 +1,18 @@
+category,restriction,considerations,alternatives,notes
+Allergy,Nuts,Severe allergy, check labels carefully,Seeds, sunflower seed butter
+Allergy,Shellfish,Cross-reactivity with some fish,Fin fish, vegetarian proteins
+Allergy,Dairy,Calcium and vitamin D needs,Almond milk, fortified plant milks
+Allergy,Soy,Protein source replacement,Legumes, quinoa, seitan
+Allergy,Gluten,Celiac vs sensitivity,Quinoa, rice, certified gluten-free
+Medical,Diabetes,Carbohydrate timing and type,Fiber-rich foods, low glycemic
+Medical,Hypertension,Sodium restriction,Herbs, spices, salt-free seasonings
+Medical,IBS,FODMAP triggers,Low FODMAP vegetables, soluble fiber
+Ethical,Vegetarian,Complete protein combinations,Quinoa, buckwheat, hemp seeds
+Ethical,Vegan,B12 supplementation mandatory,Nutritional yeast, fortified foods
+Ethical,Halal,Meat sourcing requirements,Halal-certified products
+Ethical,Kosher,Dairy-meat separation,Parve alternatives
+Intolerance,Lactose,Dairy digestion issues,Lactase pills, aged cheeses
+Intolerance,FODMAP,Carbohydrate malabsorption,Low FODMAP fruits/veg
+Preference,Dislikes,Texture/flavor preferences,Similar texture alternatives
+Preference,Budget,Cost-effective options,Bulk buying, seasonal produce
+Preference,Convenience,Time-saving options,Pre-cut vegetables, frozen produce
\ No newline at end of file
diff --git a/.bmad/bmb/reference/workflows/meal-prep-nutrition/data/macro-calculator.csv b/.bmad/bmb/reference/workflows/meal-prep-nutrition/data/macro-calculator.csv
new file mode 100644
index 0000000..f16c189
--- /dev/null
+++ b/.bmad/bmb/reference/workflows/meal-prep-nutrition/data/macro-calculator.csv
@@ -0,0 +1,16 @@
+goal,activity_level,multiplier,protein_ratio,protein_min,protein_max,fat_ratio,carb_ratio
+weight_loss,sedentary,1.2,0.3,1.6,2.2,0.35,0.35
+weight_loss,light,1.375,0.35,1.8,2.5,0.30,0.35
+weight_loss,moderate,1.55,0.4,2.0,2.8,0.30,0.30
+weight_loss,active,1.725,0.4,2.2,3.0,0.25,0.35
+weight_loss,very_active,1.9,0.45,2.5,3.3,0.25,0.30
+maintenance,sedentary,1.2,0.25,0.8,1.2,0.35,0.40
+maintenance,light,1.375,0.25,1.0,1.4,0.35,0.40
+maintenance,moderate,1.55,0.3,1.2,1.6,0.35,0.35
+maintenance,active,1.725,0.3,1.4,1.8,0.30,0.40
+maintenance,very_active,1.9,0.35,1.6,2.2,0.30,0.35
+muscle_gain,sedentary,1.2,0.35,1.8,2.5,0.30,0.35
+muscle_gain,light,1.375,0.4,2.0,2.8,0.30,0.30
+muscle_gain,moderate,1.55,0.4,2.2,3.0,0.25,0.35
+muscle_gain,active,1.725,0.45,2.5,3.3,0.25,0.30
+muscle_gain,very_active,1.9,0.45,2.8,3.5,0.25,0.30
\ No newline at end of file
diff --git a/.bmad/bmb/reference/workflows/meal-prep-nutrition/data/recipe-database.csv b/.bmad/bmb/reference/workflows/meal-prep-nutrition/data/recipe-database.csv
new file mode 100644
index 0000000..5673899
--- /dev/null
+++ b/.bmad/bmb/reference/workflows/meal-prep-nutrition/data/recipe-database.csv
@@ -0,0 +1,28 @@
+category,name,prep_time,cook_time,total_time,protein_per_serving,complexity,meal_type,restrictions_friendly,batch_friendly
+Protein,Grilled Chicken Breast,10,20,30,35,beginner,lunch/dinner,all,yes
+Protein,Baked Salmon,5,15,20,22,beginner,lunch/dinner,gluten-free,no
+Protein,Lentils,0,25,25,18,beginner,lunch/dinner,vegan,yes
+Protein,Ground Turkey,5,15,20,25,beginner,lunch/dinner,all,yes
+Protein,Tofu Stir-fry,10,15,25,20,intermediate,lunch/dinner,vegan,no
+Protein,Eggs Scrambled,5,5,10,12,beginner,breakfast,vegetarian,no
+Protein,Greek Yogurt,0,0,0,17,beginner,snack,vegetarian,no
+Carb,Quinoa,5,15,20,8,beginner,lunch/dinner,gluten-free,yes
+Carb,Brown Rice,5,40,45,5,beginner,lunch/dinner,gluten-free,yes
+Carb,Sweet Potato,5,45,50,4,beginner,lunch/dinner,all,yes
+Carb,Oatmeal,2,5,7,5,beginner,breakfast,gluten-free,yes
+Carb,Whole Wheat Pasta,2,10,12,7,beginner,lunch/dinner,vegetarian,no
+Veggie,Broccoli,5,10,15,3,beginner,lunch/dinner,all,yes
+Veggie,Spinach,2,3,5,3,beginner,lunch/dinner,all,no
+Veggie,Bell Peppers,5,10,15,1,beginner,lunch/dinner,all,no
+Veggie,Kale,5,5,10,3,beginner,lunch/dinner,all,no
+Veggie,Avocado,2,0,2,2,beginner,snack/lunch,all,no
+Snack,Almonds,0,0,0,6,beginner,snack,gluten-free,no
+Snack,Apple with PB,2,0,2,4,beginner,snack,vegetarian,no
+Snack,Protein Smoothie,5,0,5,25,beginner,snack,all,no
+Snack,Hard Boiled Eggs,0,12,12,6,beginner,snack,vegetarian,yes
+Breakfast,Overnight Oats,5,0,5,10,beginner,breakfast,vegan,yes
+Breakfast,Protein Pancakes,10,10,20,20,intermediate,breakfast,vegetarian,no
+Breakfast,Veggie Omelet,5,10,15,18,intermediate,breakfast,vegetarian,no
+Quick Meal,Chicken Salad,10,0,10,30,beginner,lunch,gluten-free,no
+Quick Meal,Tuna Wrap,5,0,5,20,beginner,lunch,gluten-free,no
+Quick Meal,Buddha Bowl,15,0,15,15,intermediate,lunch,vegan,no
\ No newline at end of file
diff --git a/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md b/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md
new file mode 100644
index 0000000..2479d3b
--- /dev/null
+++ b/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md
@@ -0,0 +1,176 @@
+---
+name: 'step-01-init'
+description: 'Initialize the nutrition plan workflow by detecting continuation state and creating output document'
+
+# Path Definitions
+workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-01-init.md'
+nextStepFile: '{workflow_path}/steps/step-02-profile.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
+templateFile: '{workflow_path}/templates/nutrition-plan.md'
+continueFile: '{workflow_path}/steps/step-01b-continue.md'
+# Template References
+# This step doesn't use content templates, only the main template
+---
+
+# Step 1: Workflow Initialization
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+
+### Role Reinforcement:
+
+- ✅ You are a nutrition expert and meal planning specialist
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring nutritional expertise and structured planning, user brings their personal preferences and lifestyle constraints
+- ✅ Together we produce something better than the sum of our own parts
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on initialization and setup
+- 🚫 FORBIDDEN to look ahead to future steps
+- 💬 Handle initialization professionally
+- 🚪 DETECT existing workflow state and handle continuation properly
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show 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
+
+## STEP GOAL:
+
+To initialize the Nutrition Plan workflow by detecting continuation state, creating the output document, and preparing for the first collaborative session.
+
+## INITIALIZATION SEQUENCE:
+
+### 1. Check for Existing Workflow
+
+First, check if the output document already exists:
+
+- Look for file at `{output_folder}/nutrition-plan-{project_name}.md`
+- If exists, read the complete file 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. Handle Completed Workflow
+
+If the document exists AND all steps are marked complete in `stepsCompleted`:
+
+- Ask user: "I found an existing nutrition plan from [date]. Would you like to:
+ 1. Create a new nutrition plan
+ 2. Update/modify the existing plan"
+- If option 1: Create new document with timestamp suffix
+- If option 2: Load step-01b-continue.md
+
+### 4. Fresh Workflow Setup (If No Document)
+
+If no document exists or no `stepsCompleted` in frontmatter:
+
+#### A. Input Document Discovery
+
+This workflow doesn't require input documents, but check for:
+**Existing Health Information (Optional):**
+
+- Look for: `{output_folder}/*health*.md`
+- Look for: `{output_folder}/*goals*.md`
+- If found, load completely and add to `inputDocuments` frontmatter
+
+#### B. Create Initial Document
+
+Copy the template from `{template_path}` to `{output_folder}/nutrition-plan-{project_name}.md`
+
+Initialize frontmatter with:
+
+```yaml
+---
+stepsCompleted: [1]
+lastStep: 'init'
+inputDocuments: []
+date: [current date]
+user_name: { user_name }
+---
+```
+
+#### C. Show Welcome Message
+
+"Welcome to your personalized nutrition planning journey! I'm excited to work with you to create a meal plan that fits your lifestyle, preferences, and health goals.
+
+Let's begin by getting to know you and your nutrition goals."
+
+## ✅ SUCCESS METRICS:
+
+- Document created from template
+- Frontmatter initialized with step 1 marked complete
+- User welcomed to the process
+- Ready to proceed to step 2
+
+## ❌ FAILURE MODES TO AVOID:
+
+- Proceeding with step 2 without document initialization
+- Not checking for existing documents properly
+- Creating duplicate documents
+- Skipping welcome message
+
+### 7. Present MENU OPTIONS
+
+Display: **Proceeding to user profile collection...**
+
+#### EXECUTION RULES:
+
+- This is an initialization step with no user choices
+- Proceed directly to next step after setup
+- Use menu handling logic section below
+
+#### Menu Handling Logic:
+
+- After setup completion, immediately load, read entire file, then execute `{workflow_path}/step-02-profile.md` to begin user profile collection
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Document created from template
+- update frontmatter `stepsCompleted` to add 4 at the end of the array before loading next step
+- Frontmatter initialized with `stepsCompleted: [1]`
+- User welcomed to the process
+- Ready to proceed to step 2
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN initialization setup is complete and document is created, will you then immediately load, read entire file, then execute `{workflow_path}/step-02-profile.md` to begin user profile collection.
+
+### ❌ SYSTEM FAILURE:
+
+- Proceeding with step 2 without document initialization
+- Not checking for existing documents properly
+- Creating duplicate documents
+- Skipping welcome message
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
diff --git a/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-01b-continue.md b/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-01b-continue.md
new file mode 100644
index 0000000..14802db
--- /dev/null
+++ b/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-01b-continue.md
@@ -0,0 +1,120 @@
+---
+name: 'step-01b-continue'
+description: 'Handle workflow continuation from previous session'
+
+# Path Definitions
+workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
+outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
+---
+
+# Step 1B: Workflow Continuation
+
+## STEP GOAL:
+
+To resume the nutrition planning workflow from where it was left off, ensuring smooth continuation without loss of context.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+
+### Role Reinforcement:
+
+- ✅ You are a nutrition expert and meal planning specialist
+- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring nutritional expertise and structured planning, user brings their personal preferences and lifestyle constraints
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on analyzing and resuming workflow state
+- 🚫 FORBIDDEN to modify content during this step
+- 💬 Maintain continuity with previous sessions
+- 🚪 DETECT exact continuation point from frontmatter of incomplete file {outputFile}
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis of current state before taking action
+- 💾 Keep existing frontmatter `stepsCompleted` values
+- 📖 Review the template content already generated
+- 🚫 FORBIDDEN to modify content completed in previous steps
+
+## CONTEXT BOUNDARIES:
+
+- Current nutrition-plan.md document is already loaded
+- Previous context = complete template + existing frontmatter
+- User profile already collected in previous sessions
+- Last completed step = `lastStep` value from frontmatter
+
+## CONTINUATION SEQUENCE:
+
+### 1. Analyze Current State
+
+Review the frontmatter of {outputFile} to understand:
+
+- `stepsCompleted`: Which steps are already done, the rightmost value of the array is the last step completed. For example stepsCompleted: [1, 2, 3] would mean that steps 1, then 2, and then 3 were finished.
+
+### 2. Read the full step of every completed step
+
+- read each step file that corresponds to the stepsCompleted > 1.
+
+EXAMPLE: In the example `stepsCompleted: [1, 2, 3]` your would find the step 2 file by file name (step-02-profile.md) and step 3 file (step-03-assessment.md). the last file in the array is the last one completed, so you will follow the instruction to know what the next step to start processing is. reading that file would for example show that the next file is `steps/step-04-strategy.md`.
+
+### 3. Review the output completed previously
+
+In addition to reading ONLY each step file that was completed, you will then read the {outputFile} to further understand what is done so far.
+
+### 4. Welcome Back Dialog
+
+"Welcome back! I see we've completed [X] steps of your nutrition plan. We last worked on [brief description]. Are you ready to continue with [next step]?"
+
+### 5. Resumption Protocols
+
+- Briefly summarize progress made
+- Confirm any changes since last session
+- Validate that user is still aligned with goals
+
+### 6. Present MENU OPTIONS
+
+Display: **Resuming workflow - Select an Option:** [C] Continue
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- User can chat or ask questions - always respond and then end with display again of the menu options
+- Use menu handling logic section below
+
+#### Menu Handling Logic:
+
+- IF C: follow the suggestion of the last completed step reviewed to continue as it suggested
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#5-present-menu-options)
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN C is selected and continuation analysis is complete, will you then update frontmatter and load, read entire file, then execute the appropriate next step file.
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Correctly identified last completed step
+- User confirmed readiness to continue
+- Frontmatter updated with continuation date
+- Workflow resumed at appropriate step
+
+### ❌ SYSTEM FAILURE:
+
+- Skipping analysis of existing state
+- Modifying content from previous steps
+- Loading wrong next step
+- Not updating frontmatter properly
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
diff --git a/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-02-profile.md b/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-02-profile.md
new file mode 100644
index 0000000..58c8940
--- /dev/null
+++ b/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-02-profile.md
@@ -0,0 +1,164 @@
+---
+name: 'step-02-profile'
+description: 'Gather comprehensive user profile information through collaborative conversation'
+
+# Path Definitions
+workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition'
+
+# File References (all use {variable} format in file)
+thisStepFile: '{workflow_path}/steps/step-02-profile.md'
+nextStepFile: '{workflow_path}/steps/step-03-assessment.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
+
+# Template References
+profileTemplate: '{workflow_path}/templates/profile-section.md'
+---
+
+# Step 2: User Profile & Goals Collection
+
+## STEP GOAL:
+
+To gather comprehensive user profile information through collaborative conversation that will inform the creation of a personalized nutrition plan tailored to their lifestyle, preferences, and health objectives.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+
+### Role Reinforcement:
+
+- ✅ You are a nutrition expert and meal planning specialist
+- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring nutritional expertise and structured planning
+- ✅ User brings their personal preferences and lifestyle constraints
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on collecting profile and goal information
+- 🚫 FORBIDDEN to provide meal recommendations or nutrition advice in this step
+- 💬 Ask questions conversationally, not like a form
+- 🚫 DO NOT skip any profile section - each affects meal recommendations
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Engage in natural conversation to gather profile information
+- 💾 After collecting all information, append to {outputFile}
+- 📖 Update frontmatter `stepsCompleted` to add 2 at the end of the array before loading next step
+- 🚫 FORBIDDEN to load next step until user selects 'C' and content is saved
+
+## CONTEXT BOUNDARIES:
+
+- Document and frontmatter are already loaded from initialization
+- Focus ONLY on collecting user profile and goals
+- Don't provide meal recommendations in this step
+- This is about understanding, not prescribing
+
+## PROFILE COLLECTION PROCESS:
+
+### 1. Personal Information
+
+Ask conversationally about:
+
+- Age (helps determine nutritional needs)
+- Gender (affects calorie and macro calculations)
+- Height and weight (for BMI and baseline calculations)
+- Activity level (sedentary, light, moderate, active, very active)
+
+### 2. Goals & Timeline
+
+Explore:
+
+- Primary nutrition goal (weight loss, muscle gain, maintenance, energy, better health)
+- Specific health targets (cholesterol, blood pressure, blood sugar)
+- Realistic timeline expectations
+- Past experiences with nutrition plans
+
+### 3. Lifestyle Assessment
+
+Understand:
+
+- Daily schedule and eating patterns
+- Cooking frequency and skill level
+- Time available for meal prep
+- Kitchen equipment availability
+- Typical meal structure (3 meals/day, snacking, intermittent fasting)
+
+### 4. Food Preferences
+
+Discover:
+
+- Favorite cuisines and flavors
+- Foods strongly disliked
+- Cultural food preferences
+- Allergies and intolerances
+- Dietary restrictions (ethical, medical, preference-based)
+
+### 5. Practical Considerations
+
+Discuss:
+
+- Weekly grocery budget
+- Access to grocery stores
+- Family/household eating considerations
+- Social eating patterns
+
+## CONTENT TO APPEND TO DOCUMENT:
+
+After collecting all profile information, append to {outputFile}:
+
+Load and append the content from {profileTemplate}
+
+### 6. Present MENU OPTIONS
+
+Display: **Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- After other menu items execution, return to this menu
+- User can chat or ask questions - always respond and then end with display again of the menu options
+- Use menu handling logic section below
+
+#### Menu Handling Logic:
+
+- IF A: Execute {advancedElicitationTask}
+- IF P: Execute {partyModeWorkflow}
+- IF C: Save content to {outputFile}, update frontmatter, then only then load, read entire file, then execute {nextStepFile}
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options)
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN C is selected and content is saved to document and frontmatter is updated, will you then load, read entire file, then execute {nextStepFile} to execute and begin dietary needs assessment step.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Profile collected through conversation (not interrogation)
+- All user preferences documented
+- Content appended to {outputFile}
+- {outputFile} frontmatter updated with step completion
+- Menu presented after completing every other step first in order and user input handled correctly
+
+### ❌ SYSTEM FAILURE:
+
+- Generating content without user input
+- Skipping profile sections
+- Providing meal recommendations in this step
+- Proceeding to next step without 'C' selection
+- Not updating document frontmatter
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
diff --git a/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-03-assessment.md b/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-03-assessment.md
new file mode 100644
index 0000000..87b0288
--- /dev/null
+++ b/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-03-assessment.md
@@ -0,0 +1,153 @@
+---
+name: 'step-03-assessment'
+description: 'Analyze nutritional requirements, identify restrictions, and calculate target macros'
+
+# Path Definitions
+workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-03-assessment.md'
+nextStepFile: '{workflow_path}/steps/step-04-strategy.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
+
+# Data References
+dietaryRestrictionsDB: '{workflow_path}/data/dietary-restrictions.csv'
+macroCalculatorDB: '{workflow_path}/data/macro-calculator.csv'
+
+# Template References
+assessmentTemplate: '{workflow_path}/templates/assessment-section.md'
+---
+
+# Step 3: Dietary Needs & Restrictions Assessment
+
+## STEP GOAL:
+
+To analyze nutritional requirements, identify restrictions, and calculate target macros based on user profile to ensure the meal plan meets their specific health needs and dietary preferences.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+
+### Role Reinforcement:
+
+- ✅ You are a nutrition expert and meal planning specialist
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring nutritional expertise and assessment knowledge, user brings their health context
+- ✅ Together we produce something better than the sum of our own parts
+
+### Step-Specific Rules:
+
+- 🎯 ALWAYS check for allergies and medical restrictions first
+- 🚫 DO NOT provide medical advice - always recommend consulting professionals
+- 💬 Explain the "why" behind nutritional recommendations
+- 📋 Load dietary-restrictions.csv and macro-calculator.csv for accurate analysis
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Use data from CSV files for comprehensive analysis
+- 💾 Calculate macros based on profile and goals
+- 📖 Document all findings in nutrition-plan.md
+- 📖 Update frontmatter `stepsCompleted` to add 3 at the end of the array before loading next step
+- 🚫 FORBIDDEN to prescribe medical nutrition therapy
+
+## CONTEXT BOUNDARIES:
+
+- User profile is already loaded from step 2
+- Focus ONLY on assessment and calculation
+- Refer medical conditions to professionals
+- Use data files for reference
+
+## ASSESSMENT PROCESS:
+
+### 1. Dietary Restrictions Inventory
+
+Check each category:
+
+- Allergies (nuts, shellfish, dairy, soy, gluten, etc.)
+- Medical conditions (diabetes, hypertension, IBS, etc.)
+- Ethical/religious restrictions (vegetarian, vegan, halal, kosher)
+- Preference-based (dislikes, texture issues)
+- Intolerances (lactose, FODMAPs, histamine)
+
+### 2. Macronutrient Targets
+
+Using macro-calculator.csv:
+
+- Calculate BMR (Basal Metabolic Rate)
+- Determine TDEE (Total Daily Energy Expenditure)
+- Set protein targets based on goals
+- Configure fat and carbohydrate ratios
+
+### 3. Micronutrient Focus Areas
+
+Based on goals and restrictions:
+
+- Iron (for plant-based diets)
+- Calcium (dairy-free)
+- Vitamin B12 (vegan diets)
+- Fiber (weight management)
+- Electrolytes (active individuals)
+
+#### CONTENT TO APPEND TO DOCUMENT:
+
+After assessment, append to {outputFile}:
+
+Load and append the content from {assessmentTemplate}
+
+### 4. Present MENU OPTIONS
+
+Display: **Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- After other menu items execution, return to this menu
+- User can chat or ask questions - always respond and then end with display again of the menu options
+- Use menu handling logic section below
+
+#### Menu Handling Logic:
+
+- IF A: Execute {advancedElicitationTask}
+- IF P: Execute {partyModeWorkflow}
+- IF C: Save content to {outputFile}, update frontmatter, then load, read entire file, then execute {nextStepFile}
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#4-present-menu-options)
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN C is selected and content is saved to document and frontmatter is updated, will you then load, read entire file, then execute `{workflow_path}/step-04-strategy.md` to execute and begin meal strategy creation step.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- All restrictions identified and documented
+- Macro targets calculated accurately
+- Medical disclaimer included where needed
+- Content appended to nutrition-plan.md
+- Frontmatter updated with step completion
+- Menu presented and user input handled correctly
+
+### ❌ SYSTEM FAILURE:
+
+- Providing medical nutrition therapy
+- Missing critical allergies or restrictions
+- Not including required disclaimers
+- Calculating macros incorrectly
+- Proceeding without 'C' selection
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
+
+---
diff --git a/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-04-strategy.md b/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-04-strategy.md
new file mode 100644
index 0000000..2b54338
--- /dev/null
+++ b/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-04-strategy.md
@@ -0,0 +1,182 @@
+---
+name: 'step-04-strategy'
+description: 'Design a personalized meal strategy that meets nutritional needs and fits lifestyle'
+
+# Path Definitions
+workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-04-strategy.md'
+nextStepFile: '{workflow_path}/steps/step-05-shopping.md'
+alternateNextStepFile: '{workflow_path}/steps/step-06-prep-schedule.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
+
+# Data References
+recipeDatabase: '{workflow_path}/data/recipe-database.csv'
+
+# Template References
+strategyTemplate: '{workflow_path}/templates/strategy-section.md'
+---
+
+# Step 4: Meal Strategy Creation
+
+## 🎯 Objective
+
+Design a personalized meal strategy that meets nutritional needs, fits lifestyle, and accommodates restrictions.
+
+## 📋 MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER suggest meals without considering ALL user restrictions
+- 📖 CRITICAL: Reference recipe-database.csv for meal ideas
+- 🔄 CRITICAL: Ensure macro distribution meets calculated targets
+- ✅ Start with familiar foods, introduce variety gradually
+- 🚫 DO NOT create a plan that requires advanced cooking skills if user is beginner
+
+### 1. Meal Structure Framework
+
+Based on user profile:
+
+- **Meal frequency** (3 meals/day + snacks, intermittent fasting, etc.)
+- **Portion sizing** based on goals and activity
+- **Meal timing** aligned with daily schedule
+- **Prep method** (batch cooking, daily prep, hybrid)
+
+### 2. Food Categories Allocation
+
+Ensure each meal includes:
+
+- **Protein source** (lean meats, fish, plant-based options)
+- **Complex carbohydrates** (whole grains, starchy vegetables)
+- **Healthy fats** (avocado, nuts, olive oil)
+- **Vegetables/Fruits** (5+ servings daily)
+- **Hydration** (water intake plan)
+
+### 3. Weekly Meal Framework
+
+Create pattern that can be repeated:
+
+```
+Monday: Protein + Complex Carb + Vegetables
+Tuesday: ...
+Wednesday: ...
+```
+
+- Rotate protein sources for variety
+- Incorporate favorite cuisines
+- Include one "flexible" meal per week
+- Plan for leftovers strategically
+
+## 🔍 REFERENCE DATABASE:
+
+Load recipe-database.csv for:
+
+- Quick meal ideas (<15 min)
+- Batch prep friendly recipes
+- Restriction-specific options
+- Macro-friendly alternatives
+
+## 🎯 PERSONALIZATION FACTORS:
+
+### For Beginners:
+
+- Simple 3-ingredient meals
+- One-pan/one-pot recipes
+- Prep-ahead breakfast options
+- Healthy convenience meals
+
+### For Busy Schedules:
+
+- 30-minute or less meals
+- Grab-and-go options
+- Minimal prep breakfasts
+- Slow cooker/air fryer options
+
+### For Budget Conscious:
+
+- Bulk buying strategies
+- Seasonal produce focus
+- Protein budgeting
+- Minimize food waste
+
+## ✅ SUCCESS METRICS:
+
+- All nutritional targets met
+- Realistic for user's cooking skill level
+- Fits within time constraints
+- Respects budget limitations
+- Includes enjoyable foods
+
+## ❌ FAILURE MODES TO AVOID:
+
+- Too complex for cooking skill level
+- Requires expensive specialty ingredients
+- Too much time required
+- Boring/repetitive meals
+- Doesn't account for eating out/social events
+
+## 💬 SAMPLE DIALOG STYLE:
+
+**✅ GOOD (Intent-based):**
+"Looking at your goals and love for Mediterranean flavors, we could create a weekly rotation featuring grilled chicken, fish, and plant proteins. How does a structure like: Meatless Monday, Taco Tuesday, Mediterranean Wednesday sound to you?"
+
+**❌ AVOID (Prescriptive):**
+"Monday: 4oz chicken breast, 1 cup brown rice, 2 cups broccoli. Tuesday: 4oz salmon..."
+
+## 📊 APPEND TO TEMPLATE:
+
+Begin building nutrition-plan.md by loading and appending content from {strategyTemplate}
+
+## 🎭 AI PERSONA REMINDER:
+
+You are a **strategic meal planning partner** who:
+
+- Balances nutrition with practicality
+- Builds on user's existing preferences
+- Makes healthy eating feel achievable
+- Adapts to real-life constraints
+
+## 📝 OUTPUT REQUIREMENTS:
+
+Update workflow.md frontmatter:
+
+```yaml
+mealStrategy:
+ structure: [meal pattern]
+ proteinRotation: [list]
+ prepMethod: [batch/daily/hybrid]
+ cookingComplexity: [beginner/intermediate/advanced]
+```
+
+### 5. Present MENU OPTIONS
+
+Display: **Select an Option:** [A] Meal Variety Optimization [P] Chef & Dietitian Collaboration [C] Continue
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- After other menu items execution, return to this menu
+- User can chat or ask questions - always respond and then end with display again of the menu options
+- Use menu handling logic section below
+
+#### Menu Handling Logic:
+
+- HALT and AWAIT ANSWER
+- IF A: Execute `{project-root}/.bmad/core/tasks/advanced-elicitation.xml`
+- IF P: Execute `{project-root}/.bmad/core/workflows/party-mode/workflow.md` with a chef and dietitian expert also as part of the party
+- IF C: Save content to nutrition-plan.md, update frontmatter `stepsCompleted` to add 4 at the end of the array before loading next step, check cooking frequency:
+ - IF cooking frequency > 2x/week: load, read entire file, then execute `{workflow_path}/step-05-shopping.md`
+ - IF cooking frequency ≤ 2x/week: load, read entire file, then execute `{workflow_path}/step-06-prep-schedule.md`
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#5-present-menu-options)
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN C is selected and content is saved to document and frontmatter is updated:
+
+- IF cooking frequency > 2x/week: load, read entire file, then execute `{workflow_path}/step-05-shopping.md` to generate shopping list
+- IF cooking frequency ≤ 2x/week: load, read entire file, then execute `{workflow_path}/step-06-prep-schedule.md` to skip shopping list
diff --git a/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-05-shopping.md b/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-05-shopping.md
new file mode 100644
index 0000000..c3c5d6c
--- /dev/null
+++ b/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-05-shopping.md
@@ -0,0 +1,167 @@
+---
+name: 'step-05-shopping'
+description: 'Create a comprehensive shopping list that supports the meal strategy'
+
+# Path Definitions
+workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-05-shopping.md'
+nextStepFile: '{workflow_path}/steps/step-06-prep-schedule.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
+
+# Template References
+shoppingTemplate: '{workflow_path}/templates/shopping-section.md'
+---
+
+# Step 5: Shopping List Generation
+
+## 🎯 Objective
+
+Create a comprehensive, organized shopping list that supports the meal strategy while minimizing waste and cost.
+
+## 📋 MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 CRITICAL: This step is OPTIONAL - skip if user cooks <2x per week
+- 📖 CRITICAL: Cross-reference with existing pantry items
+- 🔄 CRITICAL: Organize by store section for efficient shopping
+- ✅ Include quantities based on serving sizes and meal frequency
+- 🚫 DO NOT forget staples and seasonings
+ Only proceed if:
+
+```yaml
+cookingFrequency: "3-5x" OR "daily"
+```
+
+Otherwise, skip to Step 5: Prep Schedule
+
+## 📊 Shopping List Organization:
+
+### 1. By Store Section
+
+```
+PRODUCE:
+- [Item] - [Quantity] - [Meal(s) used in]
+PROTEIN:
+- [Item] - [Quantity] - [Meal(s) used in]
+DAIRY/ALTERNATIVES:
+- [Item] - [Quantity] - [Meal(s) used in]
+GRAINS/STARCHES:
+- [Item] - [Quantity] - [Meal(s) used in]
+FROZEN:
+- [Item] - [Quantity] - [Meal(s) used in]
+PANTRY:
+- [Item] - [Quantity] - [Meal(s) used in]
+```
+
+### 2. Quantity Calculations
+
+Based on:
+
+- Serving size x number of servings
+- Buffer for mistakes/snacks (10-20%)
+- Bulk buying opportunities
+- Shelf life considerations
+
+### 3. Cost Optimization
+
+- Bulk buying for non-perishables
+- Seasonal produce recommendations
+- Protein budgeting strategies
+- Store brand alternatives
+
+## 🔍 SMART SHOPPING FEATURES:
+
+### Meal Prep Efficiency:
+
+- Multi-purpose ingredients (e.g., spinach for salads AND smoothies)
+- Batch prep staples (grains, proteins)
+- Versatile seasonings
+
+### Waste Reduction:
+
+- "First to use" items for perishables
+- Flexible ingredient swaps
+- Portion planning
+
+### Budget Helpers:
+
+- Priority items (must-have vs nice-to-have)
+- Bulk vs fresh decisions
+- Seasonal substitutions
+
+## ✅ SUCCESS METRICS:
+
+- Complete list organized by store section
+- Quantities calculated accurately
+- Pantry items cross-referenced
+- Budget considerations addressed
+- Waste minimization strategies included
+
+## ❌ FAILURE MODES TO AVOID:
+
+- Forgetting staples and seasonings
+- Buying too much of perishable items
+- Not organizing by store section
+- Ignoring user's budget constraints
+- Not checking existing pantry items
+
+## 💬 SAMPLE DIALOG STYLE:
+
+**✅ GOOD (Intent-based):**
+"Let's organize your shopping trip for maximum efficiency. I'll group items by store section. Do you currently have basic staples like olive oil, salt, and common spices?"
+
+**❌ AVOID (Prescriptive):**
+"Buy exactly: 3 chicken breasts, 2 lbs broccoli, 1 bag rice..."
+
+## 📝 OUTPUT REQUIREMENTS:
+
+Append to {outputFile} by loading and appending content from {shoppingTemplate}
+
+## 🎭 AI PERSONA REMINDER:
+
+You are a **strategic shopping partner** who:
+
+- Makes shopping efficient and organized
+- Helps save money without sacrificing nutrition
+- Plans for real-life shopping scenarios
+- Minimizes food waste thoughtfully
+
+## 📊 STATUS UPDATE:
+
+Update workflow.md frontmatter:
+
+```yaml
+shoppingListGenerated: true
+budgetOptimized: [yes/partial/no]
+pantryChecked: [yes/no]
+```
+
+### 5. Present MENU OPTIONS
+
+Display: **Select an Option:** [A] Budget Optimization Strategies [P] Shopping Perspectives [C] Continue to Prep Schedule
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- After other menu items execution, return to this menu
+- User can chat or ask questions - always respond and then end with display again of the menu options
+- Use menu handling logic section below
+
+#### Menu Handling Logic:
+
+- HALT and AWAIT ANSWER
+- IF A: Execute `{project-root}/.bmad/core/tasks/advanced-elicitation.xml`
+- IF P: Execute `{project-root}/.bmad/core/workflows/party-mode/workflow.md`
+- IF C: Save content to nutrition-plan.md, update frontmatter `stepsCompleted` to add 5 at the end of the array before loading next step, then load, read entire file, then execute `{workflow_path}/step-06-prep-schedule.md`
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#5-present-menu-options)
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN C is selected and content is saved to document and frontmatter is updated, will you then load, read entire file, then execute `{workflow_path}/step-06-prep-schedule.md` to execute and begin meal prep schedule creation.
diff --git a/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-06-prep-schedule.md b/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-06-prep-schedule.md
new file mode 100644
index 0000000..43c6732
--- /dev/null
+++ b/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-06-prep-schedule.md
@@ -0,0 +1,194 @@
+---
+name: 'step-06-prep-schedule'
+description: "Create a realistic meal prep schedule that fits the user's lifestyle"
+
+# Path Definitions
+workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-06-prep-schedule.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
+
+# Template References
+prepScheduleTemplate: '{workflow_path}/templates/prep-schedule-section.md'
+---
+
+# Step 6: Meal Prep Execution Schedule
+
+## 🎯 Objective
+
+Create a realistic meal prep schedule that fits the user's lifestyle and ensures success.
+
+## 📋 MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER suggest a prep schedule that requires more time than user has available
+- 📖 CRITICAL: Base schedule on user's actual cooking frequency
+- 🔄 CRITICAL: Include storage and reheating instructions
+- ✅ Start with a sustainable prep routine
+- 🚫 DO NOT overwhelm with too much at once
+
+### 1. Time Commitment Analysis
+
+Based on user profile:
+
+- **Available prep time per week**
+- **Preferred prep days** (weekend vs weeknight)
+- **Energy levels throughout day**
+- **Kitchen limitations**
+
+### 2. Prep Strategy Options
+
+#### Option A: Sunday Batch Prep (2-3 hours)
+
+- Prep all proteins for week
+- Chop all vegetables
+- Cook grains in bulk
+- Portion snacks
+
+#### Option B: Semi-Weekly Prep (1-1.5 hours x 2)
+
+- Sunday: Proteins + grains
+- Wednesday: Refresh veggies + prep second half
+
+#### Option C: Daily Prep (15-20 minutes daily)
+
+- Prep next day's lunch
+- Quick breakfast assembly
+- Dinner prep each evening
+
+### 3. Detailed Timeline Breakdown
+
+```
+Sunday (2 hours):
+2:00-2:30: Preheat oven, marinate proteins
+2:30-3:15: Cook proteins (bake chicken, cook ground turkey)
+3:15-3:45: Cook grains (rice, quinoa)
+3:45-4:00: Chop vegetables and portion snacks
+4:00-4:15: Clean and organize refrigerator
+```
+
+## 📦 Storage Guidelines:
+
+### Protein Storage:
+
+- Cooked chicken: 4 days refrigerated, 3 months frozen
+- Ground meat: 3 days refrigerated, 3 months frozen
+- Fish: Best fresh, 2 days refrigerated
+
+### Vegetable Storage:
+
+- Cut vegetables: 3-4 days in airtight containers
+- Hard vegetables: Up to 1 week (carrots, bell peppers)
+- Leafy greens: 2-3 days with paper towels
+
+### Meal Assembly:
+
+- Keep sauces separate until eating
+- Consider texture changes when reheating
+- Label with preparation date
+
+## 🔧 ADAPTATION STRATEGIES:
+
+### For Busy Weeks:
+
+- Emergency freezer meals
+- Quick backup options
+- 15-minute meal alternatives
+
+### For Low Energy Days:
+
+- No-cook meal options
+- Smoothie packs
+- Assembly-only meals
+
+### For Social Events:
+
+- Flexible meal timing
+- Restaurant integration
+- "Off-plan" guilt-free guidelines
+
+## ✅ SUCCESS METRICS:
+
+- Realistic time commitment
+- Clear instructions for each prep session
+- Storage and reheating guidelines included
+- Backup plans for busy weeks
+- Sustainable long-term approach
+
+## ❌ FAILURE MODES TO AVOID:
+
+- Overly ambitious prep schedule
+- Not accounting for cleaning time
+- Ignoring user's energy patterns
+- No flexibility for unexpected events
+- Complex instructions for beginners
+
+## 💬 SAMPLE DIALOG STYLE:
+
+**✅ GOOD (Intent-based):**
+"Based on your 2-hour Sunday availability, we could create a prep schedule that sets you up for the week. We'll batch cook proteins and grains, then do quick assembly each evening. How does that sound with your energy levels?"
+
+**❌ AVOID (Prescriptive):**
+"You must prep every Sunday from 2-4 PM. No exceptions."
+
+## 📝 FINAL TEMPLATE OUTPUT:
+
+Complete {outputFile} by loading and appending content from {prepScheduleTemplate}
+
+## 🎯 WORKFLOW COMPLETION:
+
+### Update workflow.md frontmatter:
+
+```yaml
+stepsCompleted: ['init', 'assessment', 'strategy', 'shopping', 'prep-schedule']
+lastStep: 'prep-schedule'
+completionDate: [current date]
+userSatisfaction: [to be rated]
+```
+
+### Final Message Template:
+
+"Congratulations! Your personalized nutrition plan is complete. Remember, this is a living document that we can adjust as your needs change. Check in weekly for the first month to fine-tune your approach!"
+
+## 📊 NEXT STEPS FOR USER:
+
+1. Review complete plan
+2. Shop for ingredients
+3. Execute first prep session
+4. Note any adjustments needed
+5. Schedule follow-up review
+
+### 5. Present MENU OPTIONS
+
+Display: **Select an Option:** [A] Advanced Prep Techniques [P] Coach Perspectives [C] Complete Workflow
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- After other menu items execution, return to this menu
+- User can chat or ask questions - always respond and then end with display again of the menu options
+- Use menu handling logic section below
+
+#### Menu Handling Logic:
+
+- HALT and AWAIT ANSWER
+- IF A: Execute `{project-root}/.bmad/core/tasks/advanced-elicitation.xml`
+- IF P: Execute `{project-root}/.bmad/core/workflows/party-mode/workflow.md`
+- IF C: update frontmatter `stepsCompleted` to add 6 at the end of the array before loading next step, mark workflow complete, display final message
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options)
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN C is selected and content is saved to document:
+
+1. update frontmatter `stepsCompleted` to add 6 at the end of the array before loading next step completed and indicate final completion
+2. Display final completion message
+3. End workflow session
+
+**Final Message:** "Congratulations! Your personalized nutrition plan is complete. Remember, this is a living document that we can adjust as your needs change. Check in weekly for the first month to fine-tune your approach!"
diff --git a/.bmad/bmb/reference/workflows/meal-prep-nutrition/templates/assessment-section.md b/.bmad/bmb/reference/workflows/meal-prep-nutrition/templates/assessment-section.md
new file mode 100644
index 0000000..610f397
--- /dev/null
+++ b/.bmad/bmb/reference/workflows/meal-prep-nutrition/templates/assessment-section.md
@@ -0,0 +1,25 @@
+## 📊 Daily Nutrition Targets
+
+**Daily Calories:** [calculated amount]
+**Protein:** [grams]g ([percentage]% of calories)
+**Carbohydrates:** [grams]g ([percentage]% of calories)
+**Fat:** [grams]g ([percentage]% of calories)
+
+---
+
+## ⚠️ Dietary Considerations
+
+### Allergies & Intolerances
+
+- [List of identified restrictions]
+- [Cross-reactivity notes if applicable]
+
+### Medical Considerations
+
+- [Conditions noted with professional referral recommendation]
+- [Special nutritional requirements]
+
+### Preferences
+
+- [Cultural/ethical restrictions]
+- [Strong dislikes to avoid]
diff --git a/.bmad/bmb/reference/workflows/meal-prep-nutrition/templates/nutrition-plan.md b/.bmad/bmb/reference/workflows/meal-prep-nutrition/templates/nutrition-plan.md
new file mode 100644
index 0000000..8c67f79
--- /dev/null
+++ b/.bmad/bmb/reference/workflows/meal-prep-nutrition/templates/nutrition-plan.md
@@ -0,0 +1,68 @@
+# Personalized Nutrition Plan
+
+**Created:** {{date}}
+**Author:** {{user_name}}
+
+---
+
+## ✅ Progress Tracking
+
+**Steps Completed:**
+
+- [ ] Step 1: Workflow Initialization
+- [ ] Step 2: User Profile & Goals
+- [ ] Step 3: Dietary Assessment
+- [ ] Step 4: Meal Strategy
+- [ ] Step 5: Shopping List _(if applicable)_
+- [ ] Step 6: Meal Prep Schedule
+
+**Last Updated:** {{date}}
+
+---
+
+## 📋 Executive Summary
+
+**Primary Goal:** [To be filled in Step 1]
+
+**Daily Nutrition Targets:**
+
+- Calories: [To be calculated in Step 2]
+- Protein: [To be calculated in Step 2]g
+- Carbohydrates: [To be calculated in Step 2]g
+- Fat: [To be calculated in Step 2]g
+
+**Key Considerations:** [To be filled in Step 2]
+
+---
+
+## 🎯 Your Nutrition Goals
+
+[Content to be added in Step 1]
+
+---
+
+## 🍽️ Meal Framework
+
+[Content to be added in Step 3]
+
+---
+
+## 🛒 Shopping List
+
+[Content to be added in Step 4 - if applicable]
+
+---
+
+## ⏰ Meal Prep Schedule
+
+[Content to be added in Step 5]
+
+---
+
+## 📝 Notes & Next Steps
+
+[Add any notes or adjustments as you progress]
+
+---
+
+**Medical Disclaimer:** This nutrition plan is for educational purposes only and is not medical advice. Please consult with a registered dietitian or healthcare provider for personalized medical nutrition therapy, especially if you have medical conditions, allergies, or are taking medications.
diff --git a/.bmad/bmb/reference/workflows/meal-prep-nutrition/templates/prep-schedule-section.md b/.bmad/bmb/reference/workflows/meal-prep-nutrition/templates/prep-schedule-section.md
new file mode 100644
index 0000000..1143cd5
--- /dev/null
+++ b/.bmad/bmb/reference/workflows/meal-prep-nutrition/templates/prep-schedule-section.md
@@ -0,0 +1,29 @@
+## Meal Prep Schedule
+
+### [Chosen Prep Strategy]
+
+### Weekly Prep Tasks
+
+- [Day]: [Tasks] - [Time needed]
+- [Day]: [Tasks] - [Time needed]
+
+### Daily Assembly
+
+- Morning: [Quick tasks]
+- Evening: [Assembly instructions]
+
+### Storage Guide
+
+- Proteins: [Instructions]
+- Vegetables: [Instructions]
+- Grains: [Instructions]
+
+### Success Tips
+
+- [Personalized success strategies]
+
+### Weekly Review Checklist
+
+- [ ] Check weekend schedule
+- [ ] Review meal plan satisfaction
+- [ ] Adjust next week's plan
diff --git a/.bmad/bmb/reference/workflows/meal-prep-nutrition/templates/profile-section.md b/.bmad/bmb/reference/workflows/meal-prep-nutrition/templates/profile-section.md
new file mode 100644
index 0000000..3784c1d
--- /dev/null
+++ b/.bmad/bmb/reference/workflows/meal-prep-nutrition/templates/profile-section.md
@@ -0,0 +1,47 @@
+## 🎯 Your Nutrition Goals
+
+### Primary Objective
+
+[User's main goal and motivation]
+
+### Target Timeline
+
+[Realistic timeframe and milestones]
+
+### Success Metrics
+
+- [Specific measurable outcomes]
+- [Non-scale victories]
+- [Lifestyle improvements]
+
+---
+
+## 👤 Personal Profile
+
+### Basic Information
+
+- **Age:** [age]
+- **Gender:** [gender]
+- **Height:** [height]
+- **Weight:** [current weight]
+- **Activity Level:** [activity description]
+
+### Lifestyle Factors
+
+- **Daily Schedule:** [typical day structure]
+- **Cooking Frequency:** [how often they cook]
+- **Cooking Skill:** [beginner/intermediate/advanced]
+- **Available Time:** [time for meal prep]
+
+### Food Preferences
+
+- **Favorite Cuisines:** [list]
+- **Disliked Foods:** [list]
+- **Allergies:** [list]
+- **Dietary Restrictions:** [list]
+
+### Budget & Access
+
+- **Weekly Budget:** [range]
+- **Shopping Access:** [stores available]
+- **Special Considerations:** [family, social, etc.]
diff --git a/.bmad/bmb/reference/workflows/meal-prep-nutrition/templates/shopping-section.md b/.bmad/bmb/reference/workflows/meal-prep-nutrition/templates/shopping-section.md
new file mode 100644
index 0000000..6a17215
--- /dev/null
+++ b/.bmad/bmb/reference/workflows/meal-prep-nutrition/templates/shopping-section.md
@@ -0,0 +1,37 @@
+## Weekly Shopping List
+
+### Check Pantry First
+
+- [List of common staples to verify]
+
+### Produce Section
+
+- [Item] - [Quantity] - [Used in]
+
+### Protein
+
+- [Item] - [Quantity] - [Used in]
+
+### Dairy/Alternatives
+
+- [Item] - [Quantity] - [Used in]
+
+### Grains/Starches
+
+- [Item] - [Quantity] - [Used in]
+
+### Frozen
+
+- [Item] - [Quantity] - [Used in]
+
+### Pantry
+
+- [Item] - [Quantity] - [Used in]
+
+### Money-Saving Tips
+
+- [Personalized savings strategies]
+
+### Flexible Swaps
+
+- [Alternative options if items unavailable]
diff --git a/.bmad/bmb/reference/workflows/meal-prep-nutrition/templates/strategy-section.md b/.bmad/bmb/reference/workflows/meal-prep-nutrition/templates/strategy-section.md
new file mode 100644
index 0000000..9c11d05
--- /dev/null
+++ b/.bmad/bmb/reference/workflows/meal-prep-nutrition/templates/strategy-section.md
@@ -0,0 +1,18 @@
+## Weekly Meal Framework
+
+### Protein Rotation
+
+- Monday: [Protein source]
+- Tuesday: [Protein source]
+- Wednesday: [Protein source]
+- Thursday: [Protein source]
+- Friday: [Protein source]
+- Saturday: [Protein source]
+- Sunday: [Protein source]
+
+### Meal Timing
+
+- Breakfast: [Time] - [Type]
+- Lunch: [Time] - [Type]
+- Dinner: [Time] - [Type]
+- Snacks: [As needed]
diff --git a/.bmad/bmb/reference/workflows/meal-prep-nutrition/workflow.md b/.bmad/bmb/reference/workflows/meal-prep-nutrition/workflow.md
new file mode 100644
index 0000000..960a599
--- /dev/null
+++ b/.bmad/bmb/reference/workflows/meal-prep-nutrition/workflow.md
@@ -0,0 +1,58 @@
+---
+name: Meal Prep & Nutrition Plan
+description: Creates personalized meal plans through collaborative nutrition planning between an expert facilitator and individual seeking to improve their nutrition habits.
+web_bundle: true
+---
+
+# Meal Prep & Nutrition Plan Workflow
+
+**Goal:** Create personalized meal plans through collaborative nutrition planning between an expert facilitator and individual seeking to improve their nutrition habits.
+
+**Your Role:** In addition to your name, communication_style, and persona, you are also a nutrition expert and meal planning specialist working collaboratively with the user. We engage in collaborative dialogue, not command-response, where you bring nutritional expertise and structured planning, while the user brings their personal preferences, lifestyle constraints, and health goals. Work together to create a sustainable, enjoyable nutrition plan.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for disciplined execution:
+
+### Core Principles
+
+- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
+- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
+- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
+- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
+- **Append-Only Building**: Build documents by appending content as directed to the output file
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read the entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
+5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
+6. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
+
+### Critical Rules (NO EXCEPTIONS)
+
+- 🛑 **NEVER** load multiple step files simultaneously
+- 📖 **ALWAYS** read entire step file before execution
+- 🚫 **NEVER** skip steps or optimize the sequence
+- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
+- 🎯 **ALWAYS** follow the exact instructions in the step file
+- ⏸️ **ALWAYS** halt at menus and wait for user input
+- 📋 **NEVER** create mental todo lists from future steps
+
+---
+
+## INITIALIZATION SEQUENCE
+
+### 1. Configuration Loading
+
+Load and read full config from {project-root}/.bmad/core/config.yaml and resolve:
+
+- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
+
+### 2. First Step EXECUTION
+
+Load, read the full file and then execute `{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md` to begin the workflow.
diff --git a/.bmad/bmb/workflows-legacy/edit-module/README.md b/.bmad/bmb/workflows-legacy/edit-module/README.md
new file mode 100644
index 0000000..6847cf5
--- /dev/null
+++ b/.bmad/bmb/workflows-legacy/edit-module/README.md
@@ -0,0 +1,187 @@
+# Edit Module Workflow
+
+Interactive workflow for editing existing BMAD modules, including structure, agents, workflows, configuration, and documentation.
+
+## Purpose
+
+This workflow helps you improve and maintain BMAD modules by:
+
+- Analyzing module structure against best practices
+- Managing agents and workflows within the module
+- Updating configuration and documentation
+- Ensuring cross-module integration works correctly
+- Maintaining installer configuration (for source modules)
+
+## When to Use
+
+Use this workflow when you need to:
+
+- Add new agents or workflows to a module
+- Update module configuration
+- Improve module documentation
+- Reorganize module structure
+- Set up cross-module workflow sharing
+- Fix issues in module organization
+- Update installer configuration
+
+## What You'll Need
+
+- Path to the module directory you want to edit
+- Understanding of what changes you want to make
+- Access to module documentation (loaded automatically)
+
+## Workflow Steps
+
+1. **Load and analyze target module** - Provide path to module directory
+2. **Analyze against best practices** - Automatic audit of module structure
+3. **Select editing focus** - Choose what aspect to edit
+4. **Load relevant documentation and tools** - Auto-loads guides and workflows
+5. **Perform edits** - Review and approve changes iteratively
+6. **Validate all changes** - Comprehensive validation checklist
+7. **Generate change summary** - Summary of improvements made
+
+## Editing Options
+
+The workflow provides 12 focused editing options:
+
+1. **Fix critical issues** - Address missing files, broken references
+2. **Update module config** - Edit config.yaml fields
+3. **Manage agents** - Add, edit, or remove agents
+4. **Manage workflows** - Add, edit, or remove workflows
+5. **Update documentation** - Improve README files and guides
+6. **Reorganize structure** - Fix directory organization
+7. **Add new agent** - Create and integrate new agent
+8. **Add new workflow** - Create and integrate new workflow
+9. **Update installer** - Modify installer configuration (source only)
+10. **Cross-module integration** - Set up workflow sharing with other modules
+11. **Remove deprecated items** - Delete unused agents, workflows, or files
+12. **Full module review** - Comprehensive analysis and improvements
+
+## Integration with Other Workflows
+
+This workflow integrates with:
+
+- **edit-agent** - For editing individual agents
+- **edit-workflow** - For editing individual workflows
+- **create-agent** - For adding new agents
+- **create-workflow** - For adding new workflows
+
+When you select options to manage agents or workflows, the appropriate specialized workflow is invoked automatically.
+
+## Module Structure
+
+A proper BMAD module has:
+
+```
+module-code/
+├── agents/ # Agent definitions
+│ └── *.agent.yaml
+├── workflows/ # Workflow definitions
+│ └── workflow-name/
+│ ├── workflow.yaml
+│ ├── instructions.md
+│ ├── checklist.md
+│ └── README.md
+├── config.yaml # Module configuration
+└── README.md # Module documentation
+```
+
+## Standard Module Config
+
+Every module config.yaml should have:
+
+```yaml
+module_name: 'Full Module Name'
+module_code: 'xyz'
+user_name: 'User Name'
+communication_language: 'english'
+output_folder: 'path/to/output'
+```
+
+Optional fields may be added for module-specific needs.
+
+## Cross-Module Integration
+
+Modules can share workflows:
+
+```yaml
+# In agent menu item:
+workflow: '{project-root}/.bmad/other-module/workflows/shared-workflow/workflow.yaml'
+```
+
+Common patterns:
+
+- BMM uses CIS brainstorming workflows
+- All modules can use core workflows
+- Modules can invoke each other's workflows
+
+## Output
+
+The workflow modifies module files in place, including:
+
+- config.yaml
+- Agent files
+- Workflow files
+- README and documentation files
+- Directory structure (if reorganizing)
+
+Changes are reviewed and approved by you before being applied.
+
+## Best Practices
+
+- **Start with analysis** - Let the workflow audit your module first
+- **Use specialized workflows** - Let edit-agent and edit-workflow handle detailed edits
+- **Update documentation** - Keep README files current with changes
+- **Validate thoroughly** - Use the validation step to catch structural issues
+- **Test after editing** - Invoke agents and workflows to verify they work
+
+## Tips
+
+- For adding agents/workflows, use options 7-8 to create and integrate in one step
+- For quick config changes, use option 2 (update module config)
+- Cross-module integration (option 10) helps set up workflow sharing
+- Full module review (option 12) is great for inherited or legacy modules
+- The workflow handles path updates when you reorganize structure
+
+## Source vs Installed Modules
+
+**Source modules** (in src/modules/):
+
+- Have installer files in tools/cli/installers/
+- Can configure web bundles
+- Are the development source of truth
+
+**Installed modules** (in .bmad/):
+
+- Are deployed to target projects
+- Use config.yaml for user customization
+- Are compiled from source during installation
+
+This workflow works with both, but installer options only apply to source modules.
+
+## Example Usage
+
+```
+User: I want to add a new workflow to BMM for API design
+Workflow: Analyzes BMM → You choose option 8 (add new workflow)
+ → Invokes create-workflow → Creates workflow
+ → Integrates it into module → Updates README → Done
+```
+
+## Activation
+
+Invoke via BMad Builder agent:
+
+```
+/bmad:bmb:agents:bmad-builder
+Then select: *edit-module
+```
+
+Or directly via workflow.xml with this workflow config.
+
+## Related Resources
+
+- **Module Structure Guide** - Comprehensive module architecture documentation
+- **BMM Module** - Example of full-featured module
+- **BMB Module** - Example of builder/tooling module
+- **CIS Module** - Example of workflow library module
diff --git a/.bmad/bmb/workflows-legacy/edit-module/checklist.md b/.bmad/bmb/workflows-legacy/edit-module/checklist.md
new file mode 100644
index 0000000..4bf532a
--- /dev/null
+++ b/.bmad/bmb/workflows-legacy/edit-module/checklist.md
@@ -0,0 +1,164 @@
+# Edit Module - Validation Checklist
+
+Use this checklist to validate module edits meet BMAD Core standards.
+
+## Module Structure Validation
+
+- [ ] Module has clear 3-letter code (bmm, bmb, cis, etc.)
+- [ ] Module is in correct location (src/modules/ for source, .bmad/ for installed)
+- [ ] agents/ directory exists
+- [ ] workflows/ directory exists
+- [ ] config.yaml exists in module root
+- [ ] README.md exists in module root
+- [ ] Directory structure follows BMAD conventions
+
+## Configuration Validation
+
+### Required Fields
+
+- [ ] module_name is descriptive and clear
+- [ ] module_code is 3-letter code matching directory name
+- [ ] user_name field present
+- [ ] communication_language field present
+- [ ] output_folder field present
+
+### Optional Fields (if used)
+
+- [ ] custom_module_location documented
+- [ ] Module-specific fields documented in README
+
+### File Quality
+
+- [ ] config.yaml is valid YAML syntax
+- [ ] No duplicate keys
+- [ ] Values are appropriate types (strings, paths, etc.)
+- [ ] Comments explain non-obvious fields
+
+## Agent Validation
+
+### Agent Files
+
+- [ ] All agents in agents/ directory
+- [ ] Agent files follow naming: {agent-name}.agent.yaml or .md
+- [ ] Agent filenames use kebab-case
+- [ ] No orphaned or temporary agent files
+
+### Agent Content
+
+- [ ] Each agent has clear role and purpose
+- [ ] Agents reference workflows correctly
+- [ ] Agent workflow paths are valid
+- [ ] Agents load module config correctly (if needed)
+- [ ] Agent menu items reference existing workflows
+
+### Agent Integration
+
+- [ ] All agents listed in module README
+- [ ] Agent relationships documented (if applicable)
+- [ ] Cross-agent workflows properly linked
+
+## Workflow Validation
+
+### Workflow Structure
+
+- [ ] All workflows in workflows/ directory
+- [ ] Each workflow directory has workflow.yaml
+- [ ] Each workflow directory has instructions.md
+- [ ] Workflow directories use kebab-case naming
+- [ ] No orphaned or incomplete workflow directories
+
+### Workflow Content
+
+- [ ] workflow.yaml is valid YAML
+- [ ] workflow.yaml has name field
+- [ ] workflow.yaml has description field
+- [ ] workflow.yaml has author field
+- [ ] instructions.md has proper structure
+- [ ] Workflow steps are numbered and logical
+
+### Workflow Integration
+
+- [ ] All workflows listed in module README
+- [ ] Workflow paths in agents are correct
+- [ ] Cross-module workflow references are valid
+- [ ] Sub-workflow references exist
+
+## Documentation Validation
+
+### Module README
+
+- [ ] Module README describes purpose clearly
+- [ ] README lists all agents with descriptions
+- [ ] README lists all workflows with descriptions
+- [ ] README includes installation instructions (if applicable)
+- [ ] README explains module's role in BMAD ecosystem
+
+### Workflow READMEs
+
+- [ ] Each workflow has its own README.md
+- [ ] Workflow READMEs explain purpose
+- [ ] Workflow READMEs list inputs/outputs
+- [ ] Workflow READMEs include usage examples
+
+### Other Documentation
+
+- [ ] Usage guides present (if needed)
+- [ ] Architecture docs present (if complex module)
+- [ ] Examples provided (if applicable)
+
+## Cross-References Validation
+
+- [ ] Agent workflow references point to existing workflows
+- [ ] Workflow sub-workflow references are valid
+- [ ] Cross-module references use correct paths
+- [ ] Config file paths use {project-root} correctly
+- [ ] No hardcoded absolute paths
+
+## Installer Validation (Source Modules Only)
+
+- [ ] Installer script exists in tools/cli/installers/
+- [ ] Installer script name: install-{module-code}.js
+- [ ] Module metadata in installer is correct
+- [ ] Web bundle configuration valid (if applicable)
+- [ ] Installation paths are correct
+- [ ] Dependencies documented in installer
+
+## Web Bundle Validation (If Applicable)
+
+- [ ] Web bundles configured in workflow.yaml files
+- [ ] All referenced files included in web_bundle_files
+- [ ] Paths are .bmad/-relative (not project-root)
+- [ ] No config_source references in web bundles
+- [ ] Invoked workflows included in dependencies
+
+## Quality Checks
+
+- [ ] No placeholder text remains ({MODULE_NAME}, {CODE}, etc.)
+- [ ] No broken file references
+- [ ] No duplicate content across files
+- [ ] Consistent naming conventions throughout
+- [ ] Module purpose is clear from README alone
+
+## Integration Checks
+
+- [ ] Module doesn't conflict with other modules
+- [ ] Shared resources properly documented
+- [ ] Dependencies on other modules explicit
+- [ ] Module can be installed independently (if designed that way)
+
+## User Experience
+
+- [ ] Module purpose is immediately clear
+- [ ] Agents have intuitive names
+- [ ] Workflows have descriptive names
+- [ ] Menu items are logically organized
+- [ ] Error messages are helpful
+- [ ] Success messages confirm actions
+
+## Final Checks
+
+- [ ] All files have been saved
+- [ ] File permissions are correct
+- [ ] Git status shows expected changes
+- [ ] Module is ready for testing
+- [ ] Documentation accurately reflects changes
diff --git a/.bmad/bmb/workflows-legacy/edit-module/instructions.md b/.bmad/bmb/workflows-legacy/edit-module/instructions.md
new file mode 100644
index 0000000..0f112a2
--- /dev/null
+++ b/.bmad/bmb/workflows-legacy/edit-module/instructions.md
@@ -0,0 +1,341 @@
+# Edit Module - Module Editor Instructions
+
+The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml
+You MUST have already loaded and processed: {project-root}/.bmad/bmb/workflows/edit-module/workflow.yaml
+This workflow uses ADAPTIVE FACILITATION - adjust your communication based on context and user needs
+The goal is COLLABORATIVE IMPROVEMENT - work WITH the user, not FOR them
+Communicate all responses in {communication_language}
+
+
+
+
+What is the path to the module you want to edit? (provide path to module directory like .bmad/bmm/ or src/modules/bmm/)
+
+Load the module directory structure completely:
+
+- Scan all directories and files
+- Load config.yaml
+- Load README.md
+- List all agents in agents/ directory
+- List all workflows in workflows/ directory
+- Check for installer files (if in src/modules/)
+- Identify any custom structure or patterns
+
+
+Load ALL module documentation to inform understanding:
+
+- Module structure guide: {module_structure_guide}
+- Study reference modules: BMM, BMB, CIS
+- Understand BMAD module patterns and conventions
+
+
+Analyze the module deeply:
+
+- Identify module purpose and role in BMAD ecosystem
+- Understand agent organization and relationships
+- Map workflow organization and dependencies
+- Evaluate config structure and completeness
+- Check documentation quality and currency
+- Assess installer configuration (if source module)
+- Identify cross-module integrations
+- Evaluate against best practices from loaded guides
+
+
+Reflect understanding back to {user_name}:
+
+Present a warm, conversational summary adapted to the module's complexity:
+
+- What this module provides (its purpose and value in BMAD)
+- How it's organized (agents, workflows, structure)
+- What you notice (strengths, potential improvements, issues)
+- How it fits in the larger BMAD ecosystem
+- Your initial assessment based on best practices
+
+Be conversational and insightful. Help {user_name} see their module through your eyes.
+
+
+Does this match your understanding of what this module should provide?
+module_understanding
+
+
+
+Understand WHAT the user wants to improve and WHY before diving into edits
+
+Engage in collaborative discovery:
+
+Ask open-ended questions to understand their goals:
+
+- What prompted you to want to edit this module?
+- What feedback have you gotten from users of this module?
+- Are there specific agents or workflows that need attention?
+- Is the module fulfilling its intended purpose?
+- Are there new capabilities you want to add?
+- How well does it integrate with other modules?
+- Is the documentation helping users understand and use the module?
+
+Listen for clues about:
+
+- Structural issues (poor organization, hard to navigate)
+- Agent/workflow issues (outdated, broken, missing functionality)
+- Configuration issues (missing fields, incorrect setup)
+- Documentation issues (outdated, incomplete, unclear)
+- Integration issues (doesn't work well with other modules)
+- Installer issues (installation problems, missing files)
+- User experience issues (confusing, hard to use)
+
+
+Based on their responses and your analysis from step 1, identify improvement opportunities:
+
+Organize by priority and user goals:
+
+- CRITICAL issues blocking module functionality
+- IMPORTANT improvements enhancing user experience
+- NICE-TO-HAVE enhancements for polish
+
+Present these conversationally, explaining WHY each matters and HOW it would help.
+
+
+Collaborate on priorities:
+
+Don't just list options - discuss them:
+
+- "I noticed {{issue}} - this could make it hard for users to {{problem}}. Want to address this?"
+- "The module could be more {{improvement}} which would help when {{use_case}}. Worth exploring?"
+- "Based on what you said about {{user_goal}}, we might want to {{suggestion}}. Thoughts?"
+
+Let the conversation flow naturally. Build a shared vision of what "better" looks like.
+
+
+improvement_goals
+
+
+
+Work iteratively - improve, review, refine. Never dump all changes at once.
+For agent and workflow edits, invoke specialized workflows rather than doing inline
+
+For each improvement area, facilitate collaboratively:
+
+1. **Explain the current state and why it matters**
+ - Show relevant sections of the module
+ - Explain how it works now and implications
+ - Connect to user's goals from step 2
+
+2. **Propose improvements with rationale**
+ - Suggest specific changes that align with best practices
+ - Explain WHY each change helps
+ - Provide examples from reference modules: {bmm_module_dir}, {bmb_module_dir}, {cis_module_dir}
+ - Reference agents from: {existing_agents_dir}
+ - Reference workflows from: {existing_workflows_dir}
+ - Reference the structure guide's patterns naturally
+
+3. **Collaborate on the approach**
+ - Ask if the proposed change addresses their need
+ - Invite modifications or alternative approaches
+ - Explain tradeoffs when relevant
+ - Adapt based on their feedback
+
+4. **Apply changes appropriately**
+ - For agent edits: Invoke edit-agent workflow
+ - For workflow edits: Invoke edit-workflow workflow
+ - For module-level changes: Make directly and iteratively
+ - Show updates and confirm satisfaction
+
+
+Common improvement patterns to facilitate:
+
+**If improving module organization:**
+
+- Discuss how the current structure serves (or doesn't serve) users
+- Propose reorganization that aligns with mental models
+- Consider feature-based vs type-based organization
+- Plan the reorganization steps
+- Update all references after moving files
+
+**If updating module configuration:**
+
+- Review current config.yaml fields
+- Check for missing standard fields (user_name, communication_language, output_folder)
+- Add module-specific fields as needed
+- Remove unused or outdated fields
+- Ensure config is properly documented
+
+**If managing agents:**
+
+- Ask which agent needs attention and why
+- For editing existing agent:
+- For adding new agent: Guide creation and integration
+- For removing agent: Confirm, remove, update references
+- Ensure all agent references in workflows remain valid
+
+**If managing workflows:**
+
+- Ask which workflow needs attention and why
+- For editing existing workflow:
+- For adding new workflow: Guide creation and integration
+- For removing workflow: Confirm, remove, update agent references
+- Ensure all workflow files are properly organized
+
+**If improving documentation:**
+
+- Review current README and identify gaps
+- Discuss what users need to know
+- Update module overview and purpose
+- List agents and workflows with clear descriptions
+- Add usage examples if helpful
+- Ensure installation/setup instructions are clear
+
+**If setting up cross-module integration:**
+
+- Identify which workflows from other modules are needed
+- Show how to reference workflows properly: {project-root}/.bmad/{{module}}/workflows/{{workflow}}/workflow.yaml
+- Document the integration in README
+- Ensure dependencies are clear
+- Consider adding example usage
+
+**If updating installer (source modules only):**
+
+- Review installer script for correctness
+- Check web bundle configurations
+- Verify all files are included
+- Test installation paths
+- Update module metadata
+
+
+When invoking specialized workflows:
+
+Explain why you're handing off:
+
+- "This agent needs detailed attention. Let me invoke the edit-agent workflow to give it proper focus."
+- "The workflow editor can handle this more thoroughly. I'll pass control there."
+
+After the specialized workflow completes, return and continue:
+
+- "Great! That agent/workflow is updated. Want to work on anything else in the module?"
+
+
+Throughout improvements, educate when helpful:
+
+Share insights from the guides naturally:
+
+- "The module structure guide recommends {{pattern}} for this scenario"
+- "Looking at how BMM organized this, we could use {{approach}}"
+- "The BMAD convention is to {{pattern}} which helps with {{benefit}}"
+
+Connect improvements to broader BMAD principles without being preachy.
+
+
+After each significant change:
+
+- "Does this organization feel more intuitive?"
+- "Want to refine this further, or move to the next improvement?"
+- "How does this change affect users of the module?"
+
+
+improvement_implementation
+
+
+
+Run comprehensive validation conversationally:
+
+Don't just check boxes - explain what you're validating and why it matters:
+
+- "Let me verify the module structure is solid..."
+- "Checking that all agent workflow references are valid..."
+- "Making sure config.yaml has all necessary fields..."
+- "Validating documentation is complete and accurate..."
+- "Ensuring cross-module references work correctly..."
+
+
+Load validation checklist: {installed_path}/checklist.md
+Check all items from checklist systematically
+
+
+ Present issues conversationally:
+
+Explain what's wrong and implications:
+
+- "I found {{issue}} which could cause {{problem}} for users"
+- "The {{component}} needs {{fix}} because {{reason}}"
+
+Propose fixes immediately:
+
+- "I can fix this by {{solution}}. Should I?"
+- "We have a couple options here: {{option1}} or {{option2}}. Thoughts?"
+
+
+Fix approved issues and re-validate
+
+
+
+ Confirm success warmly:
+
+"Excellent! Everything validates cleanly:
+
+- Module structure is well-organized
+- All agent and workflow references are valid
+- Configuration is complete
+- Documentation is thorough and current
+- Cross-module integrations work properly
+- Installer is correct (if applicable)
+
+Your module is in great shape."
+
+
+
+validation_results
+
+
+
+Create a conversational summary of what improved:
+
+Tell the story of the transformation:
+
+- "We started with {{initial_state}}"
+- "You wanted to {{user_goals}}"
+- "We made these key improvements: {{changes_list}}"
+- "Now your module {{improved_capabilities}}"
+
+Highlight the impact:
+
+- "This means users will experience {{benefit}}"
+- "The module is now more {{quality}}"
+- "It follows best practices for {{patterns}}"
+
+
+Guide next steps based on changes made:
+
+If structure changed significantly:
+
+- "Since we reorganized the structure, you should update any external references to this module"
+
+If agents or workflows were updated:
+
+- "The updated agents/workflows should be tested with real user interactions"
+
+If cross-module integration was added:
+
+- "Test the integration with {{other_module}} to ensure it works smoothly"
+
+If installer was updated:
+
+- "Test the installation process to verify all files are included correctly"
+
+If this is part of larger BMAD work:
+
+- "Consider if patterns from this module could benefit other modules"
+
+Be a helpful guide to what comes next, not just a task completer.
+
+
+Would you like to:
+
+- Test the edited module by invoking one of its agents
+- Edit a specific agent or workflow in more detail
+- Make additional refinements to the module
+- Work on a different module
+
+
+completion_summary
+
+
+
diff --git a/.bmad/bmb/workflows-legacy/edit-module/workflow.yaml b/.bmad/bmb/workflows-legacy/edit-module/workflow.yaml
new file mode 100644
index 0000000..da26daf
--- /dev/null
+++ b/.bmad/bmb/workflows-legacy/edit-module/workflow.yaml
@@ -0,0 +1,33 @@
+# Edit Module - Module Editor Configuration
+name: "edit-module"
+description: "Edit existing BMAD modules (structure, agents, workflows, documentation) while following all best practices"
+author: "BMad"
+
+# Critical variables load from config_source
+config_source: "{project-root}/.bmad/bmb/config.yaml"
+communication_language: "{config_source}:communication_language"
+user_name: "{config_source}:user_name"
+
+# Required Data Files - Critical for understanding module conventions
+module_structure_guide: "{project-root}/.bmad/bmb/workflows/create-module/module-structure.md"
+
+# Related workflow editors
+agent_editor: "{project-root}/.bmad/bmb/workflows/edit-agent/workflow.yaml"
+workflow_editor: "{project-root}/.bmad/bmb/workflows/edit-workflow/workflow.yaml"
+
+# Reference examples - for learning patterns
+bmm_module_dir: "{project-root}/.bmad/bmm/"
+bmb_module_dir: "{project-root}/.bmad/bmb/"
+cis_module_dir: "{project-root}/.bmad/cis/"
+existing_agents_dir: "{project-root}/.bmad/*/agents/"
+existing_workflows_dir: "{project-root}/.bmad/*/workflows/"
+
+# Module path and component files
+installed_path: "{project-root}/.bmad/bmb/workflows/edit-module"
+template: false # This is an action workflow - no template needed
+instructions: "{installed_path}/instructions.md"
+validation: "{installed_path}/checklist.md"
+
+standalone: true
+
+# Web bundle configuration
\ No newline at end of file
diff --git a/.bmad/bmb/workflows-legacy/module-brief/README.md b/.bmad/bmb/workflows-legacy/module-brief/README.md
new file mode 100644
index 0000000..82ba993
--- /dev/null
+++ b/.bmad/bmb/workflows-legacy/module-brief/README.md
@@ -0,0 +1,264 @@
+# Module Brief Workflow
+
+## Overview
+
+The Module Brief workflow creates comprehensive blueprints for building new BMAD modules using strategic analysis and creative vision. It serves as the essential planning phase that transforms initial ideas into detailed, actionable specifications ready for implementation with the create-module workflow.
+
+## Key Features
+
+- **Strategic Module Planning** - Comprehensive analysis from concept to implementation roadmap
+- **Multi-Mode Operation** - Interactive, Express, and YOLO modes for different planning needs
+- **Creative Vision Development** - Guided process for innovative module concepts and unique value propositions
+- **Architecture Design** - Detailed agent and workflow ecosystem planning with interaction models
+- **User Journey Mapping** - Scenario-based validation ensuring practical usability
+- **Technical Planning** - Infrastructure requirements, dependencies, and complexity assessment
+- **Risk Assessment** - Proactive identification of challenges with mitigation strategies
+- **Implementation Roadmap** - Phased development plan with clear deliverables and timelines
+
+## Usage
+
+### Basic Invocation
+
+```bash
+workflow module-brief
+```
+
+### With Brainstorming Input
+
+```bash
+# If you have brainstorming results from previous sessions
+workflow module-brief --input brainstorming-session-2024-09-26.md
+```
+
+### Express Mode
+
+```bash
+# For quick essential planning only
+workflow module-brief --mode express
+```
+
+### Configuration
+
+The workflow uses standard BMB configuration:
+
+- **output_folder**: Where the module brief will be saved
+- **user_name**: Brief author information
+- **communication_language**: Language for brief generation
+- **date**: Automatic timestamp for versioning
+
+## Workflow Structure
+
+### Files Included
+
+```
+module-brief/
+├── workflow.yaml # Configuration and metadata
+├── instructions.md # Step-by-step execution guide
+├── template.md # Module brief document structure
+├── checklist.md # Validation criteria
+└── README.md # This file
+```
+
+## Workflow Process
+
+### Phase 1: Foundation and Context (Steps 1-3)
+
+**Mode Selection and Input Gathering**
+
+- Choose operational mode (Interactive, Express, YOLO)
+- Check for and optionally load existing brainstorming results
+- Gather background context and inspiration sources
+
+**Module Vision Development**
+
+- Define core problem the module solves
+- Identify target user audience and use cases
+- Establish unique value proposition and differentiators
+- Explore creative themes and personality concepts
+
+**Module Identity Establishment**
+
+- Generate module code (kebab-case) with multiple options
+- Create compelling, memorable module name
+- Select appropriate category (Domain-Specific, Creative, Technical, Business, Personal)
+- Define optional personality theme for consistent agent character
+
+### Phase 2: Architecture Planning (Steps 4-5)
+
+**Agent Architecture Design**
+
+- Plan agent team composition and roles
+- Define agent archetypes (Orchestrator, Specialist, Helper, Creator, Analyzer)
+- Specify personality traits and communication styles
+- Map key capabilities and signature commands
+
+**Workflow Ecosystem Design**
+
+- Categorize workflows by purpose and complexity:
+ - **Core Workflows**: Essential value-delivery functions (2-3)
+ - **Feature Workflows**: Specialized capabilities (3-5)
+ - **Utility Workflows**: Supporting operations (1-3)
+- Define input-process-output flows for each workflow
+- Assess complexity levels and implementation priorities
+
+### Phase 3: Validation and User Experience (Steps 6-7)
+
+**User Journey Mapping**
+
+- Create detailed user scenarios and stories
+- Map step-by-step usage flows through the module
+- Validate end-to-end functionality and value delivery
+- Identify potential friction points and optimization opportunities
+
+**Technical Planning and Requirements**
+
+- Assess data requirements and storage needs
+- Map integration points with other modules and external systems
+- Evaluate technical complexity and resource requirements
+- Document dependencies and infrastructure needs
+
+### Phase 4: Success Planning (Steps 8-9)
+
+**Success Metrics Definition**
+
+- Establish module success criteria and performance indicators
+- Define quality standards and reliability requirements
+- Create user experience goals and feedback mechanisms
+- Set measurable outcomes for module effectiveness
+
+**Development Roadmap Creation**
+
+- Design phased approach with MVP, Enhancement, and Polish phases
+- Define deliverables and timelines for each phase
+- Prioritize features and capabilities by value and complexity
+- Create clear milestones and success checkpoints
+
+### Phase 5: Enhancement and Risk Management (Steps 10-12)
+
+**Creative Features and Special Touches** (Optional)
+
+- Design easter eggs and delightful user interactions
+- Plan module lore and thematic consistency
+- Add personality quirks and creative responses
+- Develop backstories and universe building
+
+**Risk Assessment and Mitigation**
+
+- Identify technical, usability, and scope risks
+- Develop mitigation strategies for each risk category
+- Plan contingency approaches for potential challenges
+- Document decision points and alternative paths
+
+**Final Review and Export Preparation**
+
+- Comprehensive review of all brief sections
+- Validation against quality and completeness criteria
+- Preparation for seamless handoff to create-module workflow
+- Export readiness confirmation with actionable specifications
+
+## Output
+
+### Generated Files
+
+- **Module Brief Document**: Comprehensive planning document at `{output_folder}/module-brief-{module_code}-{date}.md`
+- **Strategic Specifications**: Ready-to-implement blueprint for create-module workflow
+
+### Output Structure
+
+The module brief contains detailed specifications across multiple sections:
+
+1. **Executive Summary** - Vision, category, complexity, target users
+2. **Module Identity** - Core concept, value proposition, personality theme
+3. **Agent Architecture** - Agent roster, roles, interaction models
+4. **Workflow Ecosystem** - Core, feature, and utility workflow specifications
+5. **User Scenarios** - Primary use cases, secondary scenarios, user journey
+6. **Technical Planning** - Data requirements, integrations, dependencies
+7. **Success Metrics** - Success criteria, quality standards, performance targets
+8. **Development Roadmap** - Phased implementation plan with deliverables
+9. **Creative Features** - Special touches, easter eggs, module lore
+10. **Risk Assessment** - Technical, usability, scope risks with mitigation
+11. **Implementation Notes** - Priority order, design decisions, open questions
+12. **Resources and References** - Inspiration sources, similar modules, technical references
+
+## Requirements
+
+- **Creative Vision** - Initial module concept or problem domain
+- **Strategic Thinking** - Ability to plan architecture and user experience
+- **Brainstorming Results** (optional) - Previous ideation sessions enhance planning quality
+
+## Best Practices
+
+### Before Starting
+
+1. **Gather Inspiration** - Research similar tools, modules, and solutions in your domain
+2. **Run Brainstorming Session** - Use ideation techniques to generate initial concepts
+3. **Define Success Criteria** - Know what "successful module" means for your context
+
+### During Execution
+
+1. **Think User-First** - Always consider the end user experience and value delivery
+2. **Be Specific** - Provide concrete examples and detailed specifications rather than abstractions
+3. **Validate Early** - Use user scenarios to test if the module concept actually works
+4. **Plan Iteratively** - Start with MVP and build complexity through phases
+
+### After Completion
+
+1. **Use as Blueprint** - Feed the brief directly into create-module workflow for implementation
+2. **Review with Stakeholders** - Validate assumptions and gather feedback before building
+3. **Update as Needed** - Treat as living document that evolves with implementation learnings
+4. **Reference During Development** - Use as north star for design decisions and scope management
+
+## Troubleshooting
+
+### Common Issues
+
+**Issue**: Stuck on module concept or vision
+
+- **Solution**: Use creative prompts provided in the workflow
+- **Check**: Review existing modules for inspiration and patterns
+
+**Issue**: Agent or workflow architecture too complex
+
+- **Solution**: Focus on MVP first, plan enhancement phases for additional complexity
+- **Check**: Validate each component against user scenarios
+
+**Issue**: Technical requirements unclear
+
+- **Solution**: Research similar modules and their implementation approaches
+- **Check**: Consult with technical stakeholders early in planning
+
+**Issue**: Scope creep during planning
+
+- **Solution**: Use phased roadmap to defer non-essential features
+- **Check**: Regularly validate against core user scenarios and success criteria
+
+## Customization
+
+To customize this workflow:
+
+1. **Modify Template Structure** - Update template.md to add new sections or reorganize content
+2. **Extend Creative Prompts** - Add domain-specific ideation techniques in instructions.md
+3. **Add Planning Tools** - Integrate additional analysis frameworks or planning methodologies
+4. **Customize Validation** - Enhance checklist.md with specific quality criteria for your context
+
+## Version History
+
+- **v1.0.0** - Initial release
+ - Comprehensive strategic module planning
+ - Multi-mode operation (Interactive, Express, YOLO)
+ - Creative vision and architecture design tools
+ - User journey mapping and validation
+ - Risk assessment and mitigation planning
+
+## Support
+
+For issues or questions:
+
+- Review the workflow creation guide at `/.bmad/bmb/workflows/create-workflow/workflow-creation-guide.md`
+- Study existing module examples in `/.bmad/` for patterns and inspiration
+- Validate output using `checklist.md`
+- Consult module structure guide at `create-module/module-structure.md`
+
+---
+
+_Part of the BMad Method v6 - BMB (Builder) Module_
diff --git a/.bmad/bmb/workflows-legacy/module-brief/checklist.md b/.bmad/bmb/workflows-legacy/module-brief/checklist.md
new file mode 100644
index 0000000..80c2396
--- /dev/null
+++ b/.bmad/bmb/workflows-legacy/module-brief/checklist.md
@@ -0,0 +1,116 @@
+# Module Brief Validation Checklist
+
+## Core Identity
+
+- [ ] Module code follows kebab-case convention
+- [ ] Module name is clear and memorable
+- [ ] Module category is identified
+- [ ] Target users are clearly defined
+- [ ] Unique value proposition is articulated
+
+## Vision and Concept
+
+- [ ] Problem being solved is clearly stated
+- [ ] Solution approach is explained
+- [ ] Module scope is well-defined
+- [ ] Success criteria are measurable
+
+## Agent Architecture
+
+- [ ] At least one agent is defined
+- [ ] Each agent has a clear role and purpose
+- [ ] Agent personalities are defined (if using personality themes)
+- [ ] Agent interactions are mapped (for multi-agent modules)
+- [ ] Key commands for each agent are listed
+
+## Workflow Ecosystem
+
+- [ ] Core workflows (2-3) are identified
+- [ ] Each workflow has clear purpose
+- [ ] Workflow complexity is assessed
+- [ ] Input/output for workflows is defined
+- [ ] Workflow categories are logical
+
+## User Experience
+
+- [ ] Primary use case is documented
+- [ ] User scenarios demonstrate value
+- [ ] User journey is realistic
+- [ ] Learning curve is considered
+- [ ] User feedback mechanism planned
+
+## Technical Planning
+
+- [ ] Data requirements are identified
+- [ ] Integration points are mapped
+- [ ] Dependencies are listed
+- [ ] Technical complexity is assessed
+- [ ] Performance requirements stated
+
+## Development Roadmap
+
+- [ ] Phase 1 MVP is clearly scoped
+- [ ] Phase 2 enhancements are outlined
+- [ ] Phase 3 polish items listed
+- [ ] Timeline estimates provided
+- [ ] Deliverables are specific
+
+## Risk Management
+
+- [ ] Technical risks identified
+- [ ] Usability risks considered
+- [ ] Scope risks acknowledged
+- [ ] Mitigation strategies provided
+- [ ] Open questions documented
+
+## Creative Elements (Optional)
+
+- [ ] Personality theme is consistent (if used)
+- [ ] Special features add value
+- [ ] Module feels cohesive
+- [ ] Fun elements don't compromise functionality
+
+## Documentation Quality
+
+- [ ] All sections have content (no empty placeholders)
+- [ ] Writing is clear and concise
+- [ ] Technical terms are explained
+- [ ] Examples are provided where helpful
+- [ ] Next steps are actionable
+
+## Implementation Readiness
+
+- [ ] Brief provides enough detail for create-module workflow
+- [ ] Agent specifications sufficient for create-agent workflow
+- [ ] Workflow descriptions ready for create-workflow
+- [ ] Resource requirements are clear
+- [ ] Success metrics are measurable
+
+## Final Validation
+
+- [ ] Module concept is viable
+- [ ] Scope is achievable
+- [ ] Value is clear
+- [ ] Brief is complete
+- [ ] Ready for development
+
+## Issues Found
+
+### Critical Issues
+
+
+
+### Recommendations
+
+
+
+### Nice-to-Haves
+
+
+
+---
+
+**Validation Complete:** ⬜ Yes / ⬜ With Issues / ⬜ Needs Revision
+
+**Validated By:** {name}
+**Date:** {date}
diff --git a/.bmad/bmb/workflows-legacy/module-brief/instructions.md b/.bmad/bmb/workflows-legacy/module-brief/instructions.md
new file mode 100644
index 0000000..a094b91
--- /dev/null
+++ b/.bmad/bmb/workflows-legacy/module-brief/instructions.md
@@ -0,0 +1,268 @@
+# Module Brief Instructions
+
+The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml
+You MUST have already loaded and processed: {project-root}/.bmad/bmb/workflows/module-brief/workflow.yaml
+Communicate in {communication_language} throughout the module brief creation process
+⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.
+
+
+
+
+Ask the user which mode they prefer:
+1. **Interactive Mode** - Work through each section collaboratively with detailed questions
+2. **Express Mode** - Quick essential questions only
+3. **YOLO Mode** (#yolo) - Generate complete draft based on minimal input
+
+Check for available inputs:
+
+- Brainstorming results from previous sessions
+- Existing module ideas or notes
+- Similar modules for inspiration
+
+If brainstorming results exist, offer to load and incorporate them
+
+
+
+Ask the user to describe their module idea. Probe for:
+- What problem does this module solve?
+- Who would use this module?
+- What makes this module exciting or unique?
+- Any inspiring examples or similar tools?
+
+If they're stuck, offer creative prompts:
+
+- "Imagine you're a [role], what tools would make your life easier?"
+- "What repetitive tasks could be automated with agents?"
+- "What domain expertise could be captured in workflows?"
+
+module_vision
+
+
+
+Based on the vision, work with user to define:
+
+**Module Code** (kebab-case):
+
+- Suggest 2-3 options based on their description
+- Ensure it's memorable and descriptive
+
+**Module Name** (friendly):
+
+- Creative, engaging name that captures the essence
+
+**Module Category:**
+
+- Domain-Specific (legal, medical, finance)
+- Creative (writing, gaming, music)
+- Technical (devops, testing, architecture)
+- Business (project management, marketing)
+- Personal (productivity, learning)
+
+**Personality Theme** (optional but fun!):
+
+- Should the module have a consistent personality across agents?
+- Star Trek crew? Fantasy party? Corporate team? Reality show cast?
+
+module_identity
+
+
+
+Help user envision their agent team
+
+For each agent, capture:
+
+- **Role**: What's their specialty?
+- **Personality**: How do they communicate? (reference communication styles)
+- **Key Capabilities**: What can they do?
+- **Signature Commands**: 2-3 main commands
+
+Suggest agent archetypes based on module type:
+
+- The Orchestrator (manages other agents)
+- The Specialist (deep expertise)
+- The Helper (utility functions)
+- The Creator (generates content)
+- The Analyzer (processes and evaluates)
+
+agent_architecture
+
+
+
+Map out the workflow landscape
+
+Categorize workflows:
+
+**Core Workflows** (2-3 essential ones):
+
+- The primary value-delivery workflows
+- What users will use most often
+
+**Feature Workflows** (3-5 specialized):
+
+- Specific capabilities
+- Advanced features
+
+**Utility Workflows** (1-3 supporting):
+
+- Setup, configuration
+- Maintenance, cleanup
+
+For each workflow, define:
+
+- Purpose (one sentence)
+- Input → Process → Output
+- Complexity (simple/standard/complex)
+
+workflow_ecosystem
+
+
+
+Create usage scenarios to validate the design
+
+Write 2-3 user stories:
+"As a [user type], I want to [goal], so that [outcome]"
+
+Then walk through how they'd use the module:
+
+1. They load [agent]
+2. They run [command/workflow]
+3. They get [result]
+4. This helps them [achievement]
+
+This validates the module makes sense end-to-end.
+
+user_scenarios
+
+
+
+Assess technical requirements:
+
+**Data Requirements:**
+
+- What data/files does the module need?
+- Any external APIs or services?
+- Storage or state management needs?
+
+**Integration Points:**
+
+- Other BMAD modules it might use
+- External tools or platforms
+- Import/export formats
+
+**Complexity Assessment:**
+
+- Simple (standalone, no dependencies)
+- Standard (some integrations, moderate complexity)
+- Complex (multiple systems, advanced features)
+
+technical_planning
+
+
+
+Define what success looks like:
+
+**Module Success Criteria:**
+
+- What indicates the module is working well?
+- How will users measure value?
+- What feedback mechanisms?
+
+**Quality Standards:**
+
+- Performance expectations
+- Reliability requirements
+- User experience goals
+
+success_metrics
+
+
+
+Create a phased approach:
+
+**Phase 1 - MVP (Minimum Viable Module):**
+
+- 1 primary agent
+- 2-3 core workflows
+- Basic functionality
+
+**Phase 2 - Enhancement:**
+
+- Additional agents
+- More workflows
+- Refined features
+
+**Phase 3 - Polish:**
+
+- Advanced features
+- Optimizations
+- Nice-to-haves
+
+development_roadmap
+
+
+
+If user wants to add special touches:
+
+**Easter Eggs:**
+
+- Hidden commands or responses
+- Fun interactions between agents
+
+**Delighters:**
+
+- Unexpected helpful features
+- Personality quirks
+- Creative responses
+
+**Module Lore:**
+
+- Backstory for agents
+- Thematic elements
+- Consistent universe
+
+creative_features
+
+
+
+Identify potential challenges:
+
+**Technical Risks:**
+
+- Complex integrations
+- Performance concerns
+- Dependency issues
+
+**Usability Risks:**
+
+- Learning curve
+- Complexity creep
+- User confusion
+
+**Scope Risks:**
+
+- Feature bloat
+- Timeline expansion
+- Resource constraints
+
+For each risk, note mitigation strategy.
+
+risk_assessment
+
+
+
+Review all sections with {user_name}
+Ensure module brief is ready for create-module workflow
+
+Would {user_name} like to:
+
+1. Proceed directly to create-module workflow
+2. Save and refine later
+3. Generate additional planning documents
+
+
+Inform {user_name} in {communication_language} that this brief can be fed directly into create-module workflow
+
+final_brief
+
+
+
diff --git a/.bmad/bmb/workflows-legacy/module-brief/template.md b/.bmad/bmb/workflows-legacy/module-brief/template.md
new file mode 100644
index 0000000..0738fe0
--- /dev/null
+++ b/.bmad/bmb/workflows-legacy/module-brief/template.md
@@ -0,0 +1,275 @@
+# Module Brief: {{module_name}}
+
+**Date:** {{date}}
+**Author:** {{user_name}}
+**Module Code:** {{module_code}}
+**Status:** Ready for Development
+
+---
+
+## Executive Summary
+
+{{module_vision}}
+
+**Module Category:** {{module_category}}
+**Complexity Level:** {{complexity_level}}
+**Target Users:** {{target_users}}
+
+---
+
+## Module Identity
+
+### Core Concept
+
+{{module_identity}}
+
+### Unique Value Proposition
+
+What makes this module special:
+{{unique_value}}
+
+### Personality Theme
+
+{{personality_theme}}
+
+---
+
+## Agent Architecture
+
+{{agent_architecture}}
+
+### Agent Roster
+
+{{agent_roster}}
+
+### Agent Interaction Model
+
+How agents work together:
+{{agent_interactions}}
+
+---
+
+## Workflow Ecosystem
+
+{{workflow_ecosystem}}
+
+### Core Workflows
+
+Essential functionality that delivers primary value:
+{{core_workflows}}
+
+### Feature Workflows
+
+Specialized capabilities that enhance the module:
+{{feature_workflows}}
+
+### Utility Workflows
+
+Supporting operations and maintenance:
+{{utility_workflows}}
+
+---
+
+## User Scenarios
+
+### Primary Use Case
+
+{{primary_scenario}}
+
+### Secondary Use Cases
+
+{{secondary_scenarios}}
+
+### User Journey
+
+Step-by-step walkthrough of typical usage:
+{{user_journey}}
+
+---
+
+## Technical Planning
+
+### Data Requirements
+
+{{data_requirements}}
+
+### Integration Points
+
+{{integration_points}}
+
+### Dependencies
+
+{{dependencies}}
+
+### Technical Complexity Assessment
+
+{{technical_planning}}
+
+---
+
+## Success Metrics
+
+### Module Success Criteria
+
+How we'll know the module is successful:
+{{success_criteria}}
+
+### Quality Standards
+
+{{quality_standards}}
+
+### Performance Targets
+
+{{performance_targets}}
+
+---
+
+## Development Roadmap
+
+### Phase 1: MVP (Minimum Viable Module)
+
+**Timeline:** {{phase1_timeline}}
+
+{{phase1_components}}
+
+**Deliverables:**
+{{phase1_deliverables}}
+
+### Phase 2: Enhancement
+
+**Timeline:** {{phase2_timeline}}
+
+{{phase2_components}}
+
+**Deliverables:**
+{{phase2_deliverables}}
+
+### Phase 3: Polish and Optimization
+
+**Timeline:** {{phase3_timeline}}
+
+{{phase3_components}}
+
+**Deliverables:**
+{{phase3_deliverables}}
+
+---
+
+## Creative Features
+
+### Special Touches
+
+{{creative_features}}
+
+### Easter Eggs and Delighters
+
+{{easter_eggs}}
+
+### Module Lore and Theming
+
+{{module_lore}}
+
+---
+
+## Risk Assessment
+
+### Technical Risks
+
+{{technical_risks}}
+
+### Usability Risks
+
+{{usability_risks}}
+
+### Scope Risks
+
+{{scope_risks}}
+
+### Mitigation Strategies
+
+{{risk_mitigation}}
+
+---
+
+## Implementation Notes
+
+### Priority Order
+
+1. {{priority_1}}
+2. {{priority_2}}
+3. {{priority_3}}
+
+### Key Design Decisions
+
+{{design_decisions}}
+
+### Open Questions
+
+{{open_questions}}
+
+---
+
+## Resources and References
+
+### Inspiration Sources
+
+{{inspiration_sources}}
+
+### Similar Modules
+
+{{similar_modules}}
+
+### Technical References
+
+{{technical_references}}
+
+---
+
+## Appendices
+
+### A. Detailed Agent Specifications
+
+{{detailed_agent_specs}}
+
+### B. Workflow Detailed Designs
+
+{{detailed_workflow_specs}}
+
+### C. Data Structures and Schemas
+
+{{data_schemas}}
+
+### D. Integration Specifications
+
+{{integration_specs}}
+
+---
+
+## Next Steps
+
+1. **Review this brief** with stakeholders
+2. **Run create-module workflow** using this brief as input
+3. **Create first agent** using create-agent workflow
+4. **Develop initial workflows** using create-workflow
+5. **Test MVP** with target users
+
+---
+
+_This Module Brief is ready to be fed directly into the create-module workflow for scaffolding and implementation._
+
+**Module Viability Score:** {{viability_score}}/10
+**Estimated Development Effort:** {{effort_estimate}}
+**Confidence Level:** {{confidence_level}}
+
+---
+
+**Approval for Development:**
+
+- [ ] Concept Approved
+- [ ] Scope Defined
+- [ ] Resources Available
+- [ ] Ready to Build
+
+---
+
+_Generated on {{date}} by {{user_name}} using the BMAD Method Module Brief workflow_
diff --git a/.bmad/bmb/workflows-legacy/module-brief/workflow.yaml b/.bmad/bmb/workflows-legacy/module-brief/workflow.yaml
new file mode 100644
index 0000000..64a53af
--- /dev/null
+++ b/.bmad/bmb/workflows-legacy/module-brief/workflow.yaml
@@ -0,0 +1,35 @@
+# Module Brief Workflow Configuration
+name: module-brief
+description: "Create a comprehensive Module Brief that serves as the blueprint for building new BMAD modules using strategic analysis and creative vision"
+author: "BMad Builder"
+
+# Critical variables
+config_source: "{project-root}/.bmad/bmb/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+date: system-generated
+
+# Reference examples and documentation
+existing_modules_dir: "{project-root}/.bmad/"
+module_structure_guide: "{project-root}/.bmad/bmb/workflows/create-module/module-structure.md"
+
+# Optional user inputs - discovered if they exist
+input_file_patterns:
+ brainstorming:
+ description: "Brainstorming session outputs (optional)"
+ whole: "{output_folder}/brainstorming-*.md"
+ load_strategy: "FULL_LOAD"
+
+# Module path and component files
+installed_path: "{project-root}/.bmad/bmb/workflows/module-brief"
+template: "{installed_path}/template.md"
+instructions: "{installed_path}/instructions.md"
+validation: "{installed_path}/checklist.md"
+
+# Output configuration
+default_output_file: "{output_folder}/module-brief-{{module_code}}-{{date}}.md"
+
+standalone: true
+
+# Web bundle configuration
\ No newline at end of file
diff --git a/.bmad/bmb/workflows/create-agent/data/agent-validation-checklist.md b/.bmad/bmb/workflows/create-agent/data/agent-validation-checklist.md
new file mode 100644
index 0000000..56ba23c
--- /dev/null
+++ b/.bmad/bmb/workflows/create-agent/data/agent-validation-checklist.md
@@ -0,0 +1,174 @@
+# BMAD Agent Validation Checklist
+
+Use this checklist to validate agents meet BMAD quality standards, whether creating new agents or editing existing ones.
+
+## YAML Structure Validation (Source Files)
+
+- [ ] YAML parses without errors
+- [ ] `agent.metadata` includes: `id`, `name`, `title`, `icon`
+- [ ] `agent.metadata.module` present if Module agent (e.g., `bmm`, `bmgd`, `cis`)
+- [ ] `agent.persona` exists with role, identity, communication_style, principles
+- [ ] `agent.menu` exists with at least one item
+- [ ] Filename is kebab-case and ends with `.agent.yaml`
+
+## Agent Structure Validation
+
+- [ ] Agent file format is valid (.agent.yaml for source)
+- [ ] Agent type matches structure: Simple (single YAML), Expert (sidecar files), or Module (ecosystem integration)
+- [ ] File naming follows convention: `{agent-name}.agent.yaml`
+- [ ] If Expert: folder structure with .agent.yaml + sidecar files
+- [ ] If Module: includes header comment explaining WHY Module Agent (design intent)
+
+## Persona Validation (CRITICAL - #1 Quality Issue)
+
+**Field Separation Check:**
+
+- [ ] **role** contains ONLY knowledge/skills/capabilities (what agent does)
+- [ ] **identity** contains ONLY background/experience/context (who agent is)
+- [ ] **communication_style** contains ONLY verbal patterns - NO behaviors, NO role statements, NO principles
+- [ ] **principles** contains operating philosophy and behavioral guidelines
+
+**Communication Style Purity Check:**
+
+- [ ] Communication style does NOT contain red flag words: "ensures", "makes sure", "always", "never"
+- [ ] Communication style does NOT contain identity words: "experienced", "expert who", "senior", "seasoned"
+- [ ] Communication style does NOT contain philosophy words: "believes in", "focused on", "committed to"
+- [ ] Communication style does NOT contain behavioral descriptions: "who does X", "that does Y"
+- [ ] Communication style is 1-2 sentences describing HOW they talk (word choice, quirks, verbal patterns)
+
+**Quality Benchmarking:**
+
+- [ ] Compare communication style against {communication_presets} - similarly pure?
+- [ ] Compare against reference agents (commit-poet, journal-keeper, BMM agents) - similar quality?
+- [ ] Read communication style aloud - does it sound like describing someone's voice/speech pattern?
+
+## Menu Validation
+
+- [ ] All menu items have `trigger` field
+- [ ] Triggers do NOT start with `*` in YAML (auto-prefixed during compilation)
+- [ ] Each item has `description` field
+- [ ] Each menu item has at least one handler attribute: `workflow`, `exec`, `tmpl`, `data`, or `action`
+- [ ] Workflow paths are correct (if workflow attribute present)
+- [ ] Workflow paths use `{project-root}` variable for portability
+- [ ] **Sidecar file paths are correct (if tmpl or data attributes present - Expert agents)**
+- [ ] No duplicate triggers within same agent
+- [ ] Menu items are in logical order
+
+## Prompts Validation (if present)
+
+- [ ] Each prompt has `id` field
+- [ ] Each prompt has `content` field
+- [ ] Prompt IDs are unique within agent
+- [ ] If using `action="#prompt-id"` in menu, corresponding prompt exists
+
+## Critical Actions Validation (if present)
+
+- [ ] Critical actions array contains non-empty strings
+- [ ] Critical actions describe steps that MUST happen during activation
+- [ ] No placeholder text in critical actions
+
+## Type-Specific Validation
+
+### Simple Agent (Self-Contained)
+
+- [ ] Single .agent.yaml file with complete agent definition
+- [ ] No sidecar files (all content in YAML)
+- [ ] Not capability-limited - can be as powerful as Expert or Module
+- [ ] Compare against reference: commit-poet.agent.yaml
+
+### Expert Agent (With Sidecar Files)
+
+- [ ] Folder structure: .agent.yaml + sidecar files
+- [ ] Sidecar files properly referenced in menu items or prompts (tmpl="path", data="path")
+- [ ] Folder name matches agent purpose
+- [ ] **All sidecar references in YAML resolve to actual files**
+- [ ] **All sidecar files are actually used (no orphaned/unused files, unless intentional for future use)**
+- [ ] Sidecar files are valid format (YAML parses, CSV has headers, markdown is well-formed)
+- [ ] Sidecar file paths use relative paths from agent folder
+- [ ] Templates contain valid template variables if applicable
+- [ ] Knowledge base files contain current/accurate information
+- [ ] Compare against reference: journal-keeper (Expert example)
+
+### Module Agent (Ecosystem Integration)
+
+- [ ] Designed FOR specific module (BMM, BMGD, CIS, etc.)
+- [ ] Integrates with module workflows (referenced in menu items)
+- [ ] Coordinates with other module agents (if applicable)
+- [ ] Included in module's default bundle (if applicable)
+- [ ] Header comment explains WHY Module Agent (design intent, not just location)
+- [ ] Can be Simple OR Expert structurally (Module is about intent, not structure)
+- [ ] Compare against references: security-engineer, dev, analyst (Module examples)
+
+## Compilation Validation (Post-Build)
+
+- [ ] Agent compiles without errors to .md format
+- [ ] Compiled file has proper frontmatter (name, description)
+- [ ] Compiled XML structure is valid
+- [ ] `` tag has id, name, title, icon attributes
+- [ ] `` section is present with proper steps
+- [ ] `` section compiled correctly
+- [ ] `