bmad-enhanced 1.3.0 → 1.3.2

package/_bmad/bme/_vortex/workflows/product-vision/workflow.md

@@ -0,0 +1,55 @@
+---
+workflow: product-vision
+type: step-file
+description: Define product vision and strategic alignment before building
+author: Emma (contextualization-expert)
+version: 1.2.0
+---
+
+# Create Product Vision Workflow
+
+This workflow guides you through defining a clear, compelling product vision that aligns your team around the "why" before you build the "what."
+
+## What is a Product Vision?
+
+A product vision is a strategic statement that articulates:
+- **Why this product should exist** - The problem it solves and impact it creates
+- **Who it's for** - The specific users/market it serves
+- **What makes it different** - The unique approach or advantage
+- **Where it's headed** - The long-term direction (3-5 years)
+
+A good product vision:
+- **Inspires** - Gets people excited to build it
+- **Focuses** - Helps say "no" to distractions
+- **Aligns** - Ensures everyone is rowing in the same direction
+- **Guides decisions** - When in doubt, does this serve the vision?
+
+## Workflow Structure
+
+**Step-file architecture:**
+- Just-in-time loading (each step loads only when needed)
+- Sequential enforcement (must complete step N before step N+1)
+- State tracking in frontmatter (progress preserved)
+
+## Steps Overview
+
+1. **Define the Problem** - What problem are we solving? Why does it matter?
+2. **Identify Target Market** - Who specifically are we serving?
+3. **Articulate Unique Approach** - What makes our solution different/better?
+4. **Envision Future State** - What does success look like in 3-5 years?
+5. **Align on Principles** - What won't we compromise on?
+6. **Synthesize** - Create the final product vision document
+
+## Output
+
+**Artifact:** Product vision document in `{output_folder}/product-vision-{product-name}-{date}.md`
+
+**Template:** Uses [product-vision.template.md](product-vision.template.md)
+
+---
+
+## INITIALIZATION
+
+Load config from {project-root}/_bmad/bme/_vortex/config.yaml
+
+Load step: {project-root}/_bmad/bme/_vortex/workflows/product-vision/steps/step-01-define-problem.md

package/_bmad/bme/_vortex/workflows/proof-of-concept/proof-of-concept.template.md

@@ -0,0 +1,25 @@
+---
+title: "PoC: {poc-name}"
+date: {date}
+type: proof-of-concept
+status: {status}
+---
+
+# Proof-of-Concept: {poc-name}
+
+## Technical Risk
+
+{technical-risk}
+
+## PoC Results
+
+{results}
+
+## Feasibility Assessment
+
+{feasibility}
+
+---
+
+**Created with:** BMAD-Enhanced v1.2.0
+**Workflow:** proof-of-concept

package/_bmad/bme/_vortex/workflows/proof-of-concept/steps/step-01.md

@@ -0,0 +1,8 @@
+---
+step: 1
+workflow: proof-of-concept
+---
+
+# Step 1
+
+[PoC step 1 content]

package/_bmad/bme/_vortex/workflows/proof-of-concept/steps/step-02.md

@@ -0,0 +1,8 @@
+---
+step: 2
+workflow: proof-of-concept
+---
+
+# Step 2
+
+[PoC step 2 content]

package/_bmad/bme/_vortex/workflows/proof-of-concept/steps/step-03.md

@@ -0,0 +1,8 @@
+---
+step: 3
+workflow: proof-of-concept
+---
+
+# Step 3
+
+[PoC step 3 content]

package/_bmad/bme/_vortex/workflows/proof-of-concept/steps/step-04.md

@@ -0,0 +1,8 @@
+---
+step: 4
+workflow: proof-of-concept
+---
+
+# Step 4
+
+[PoC step 4 content]

package/_bmad/bme/_vortex/workflows/proof-of-concept/steps/step-05.md

@@ -0,0 +1,8 @@
+---
+step: 5
+workflow: proof-of-concept
+---
+
+# Step 5
+
+[PoC step 5 content]

package/_bmad/bme/_vortex/workflows/proof-of-concept/steps/step-06.md

@@ -0,0 +1,8 @@
+---
+step: 6
+workflow: proof-of-concept
+---
+
+# Step 6
+
+[PoC step 6 content]

package/_bmad/bme/_vortex/workflows/proof-of-concept/validate.md

@@ -0,0 +1,30 @@
+# Validate Proof of Concept
+
+**Status:** Coming in v1.2.0
+
+**Agent:** Wade (Lean Experiments Specialist)
+
+**Stream:** Externalize
+
+## Overview
+
+This validation workflow helps you review proof-of-concepts to ensure they answer the technical question without over-engineering.
+
+## What Gets Validated
+
+- Is the technical question clearly stated?
+- Is the approach appropriate (not over-engineered)?
+- Are implementation details documented?
+- Are results based on evidence?
+- Is the feasibility decision justified?
+- Does this focus on learning over production quality?
+
+## Coming in v1.2.0
+
+This validation workflow will be available alongside the proof-of-concept workflow in March 2026.
+
+## Questions?
+
+For questions or to request early access:
+- GitHub Issues: https://github.com/amalik/BMAD-Enhanced/issues
+- Tag with: `workflow:proof-of-concept` and `v1.2.0`

package/_bmad/bme/_vortex/workflows/proof-of-concept/workflow.md

@@ -0,0 +1,26 @@
+---
+workflow: proof-of-concept
+type: step-file
+description: Validate technical feasibility before business case
+author: Wade (lean-experiments-specialist)
+version: 1.2.0
+---
+
+# Proof-of-Concept Workflow
+
+Validate that you CAN build this before validating that you SHOULD.
+
+## Steps Overview
+
+1. **Define Technical Risk** - What could prevent this from working?
+2. **Design PoC Scope** - Smallest test of technical feasibility
+3. **Build Prototype** - Create proof-of-concept
+4. **Test Technical Assumptions** - Does it work?
+5. **Evaluate Feasibility** - Can we build this at scale?
+6. **Document Findings** - What did we learn?
+
+---
+
+## INITIALIZATION
+
+Load step: {project-root}/_bmad/bme/_vortex/workflows/proof-of-concept/steps/step-01.md

package/_bmad/bme/_vortex/workflows/proof-of-value/proof-of-value.template.md

@@ -0,0 +1,29 @@
+---
+title: "PoV: {pov-name}"
+date: {date}
+type: proof-of-value
+status: {status}
+---
+
+# Proof-of-Value: {pov-name}
+
+## Value Hypothesis
+
+{value-hypothesis}
+
+## Market Test Results
+
+{results}
+
+## Business Case
+
+{business-case}
+
+## Decision
+
+{decision}
+
+---
+
+**Created with:** BMAD-Enhanced v1.2.0
+**Workflow:** proof-of-value

package/_bmad/bme/_vortex/workflows/proof-of-value/steps/step-01.md

@@ -0,0 +1,8 @@
+---
+step: 1
+workflow: proof-of-value
+---
+
+# Step 1
+
+[PoV step 1 content]

package/_bmad/bme/_vortex/workflows/proof-of-value/steps/step-02.md

@@ -0,0 +1,8 @@
+---
+step: 2
+workflow: proof-of-value
+---
+
+# Step 2
+
+[PoV step 2 content]

package/_bmad/bme/_vortex/workflows/proof-of-value/steps/step-03.md

@@ -0,0 +1,8 @@
+---
+step: 3
+workflow: proof-of-value
+---
+
+# Step 3
+
+[PoV step 3 content]

package/_bmad/bme/_vortex/workflows/proof-of-value/steps/step-04.md

@@ -0,0 +1,8 @@
+---
+step: 4
+workflow: proof-of-value
+---
+
+# Step 4
+
+[PoV step 4 content]

package/_bmad/bme/_vortex/workflows/proof-of-value/steps/step-05.md

@@ -0,0 +1,8 @@
+---
+step: 5
+workflow: proof-of-value
+---
+
+# Step 5
+
+[PoV step 5 content]

package/_bmad/bme/_vortex/workflows/proof-of-value/steps/step-06.md

@@ -0,0 +1,8 @@
+---
+step: 6
+workflow: proof-of-value
+---
+
+# Step 6
+
+[PoV step 6 content]

package/_bmad/bme/_vortex/workflows/proof-of-value/validate.md

@@ -0,0 +1,30 @@
+# Validate Proof of Value
+
+**Status:** Coming in v1.2.0
+
+**Agent:** Wade (Lean Experiments Specialist)
+
+**Stream:** Externalize
+
+## Overview
+
+This validation workflow helps you review proof-of-values to ensure they test real user value, not just feature interest.
+
+## What Gets Validated
+
+- Is the value hypothesis specific and testable?
+- Are target users clearly defined?
+- Is the validation approach appropriate?
+- Are results based on actual user feedback?
+- Is the business case justified by evidence?
+- Does this test value perception, not just feature desirability?
+
+## Coming in v1.2.0
+
+This validation workflow will be available alongside the proof-of-value workflow in March 2026.
+
+## Questions?
+
+For questions or to request early access:
+- GitHub Issues: https://github.com/amalik/BMAD-Enhanced/issues
+- Tag with: `workflow:proof-of-value` and `v1.2.0`

package/_bmad/bme/_vortex/workflows/proof-of-value/workflow.md

@@ -0,0 +1,26 @@
+---
+workflow: proof-of-value
+type: step-file
+description: Validate business value and market demand
+author: Wade (lean-experiments-specialist)
+version: 1.2.0
+---
+
+# Proof-of-Value Workflow
+
+Validate that you SHOULD build this (business case) after proving you CAN.
+
+## Steps Overview
+
+1. **Define Value Hypothesis** - What value does this create?
+2. **Design Value Test** - How will you validate demand?
+3. **Run Market Experiment** - Test with real users/customers
+4. **Measure Willingness to Pay** - Will they pay? How much?
+5. **Calculate Business Case** - Is this viable?
+6. **Document Decision** - Build, pivot, or kill?
+
+---
+
+## INITIALIZATION
+
+Load step: {project-root}/_bmad/bme/_vortex/workflows/proof-of-value/steps/step-01.md