bmad-enhanced 1.3.0 → 1.3.2

package/_bmad/bme/_vortex/workflows/product-vision/steps/step-01-define-problem.md

@@ -0,0 +1,89 @@
+---
+step: 1
+workflow: product-vision
+title: Define the Problem
+---
+
+# Step 1: Define the Problem
+
+Before envisioning the solution, we need crystal clarity on the problem we're solving.
+
+## Why This Matters
+
+A great product starts with a deep understanding of a meaningful problem. Without clarity on the problem:
+- You'll build features nobody needs
+- You won't know if you're making progress
+- You can't articulate why your product should exist
+- You'll struggle to say "no" to distractions
+
+## Your Task
+
+Answer these questions to define the problem:
+
+### 1. What's the core problem?
+Be specific. One sentence that captures the essence of what's broken.
+
+### 2. Who experiences this problem?
+Not "everyone" - be specific about who feels this pain most acutely.
+
+### 3. Why does this problem matter?
+What's the impact? Cost? Frustration? Missed opportunity?
+
+### 4. How big is this problem?
+- How many people experience it?
+- How often?
+- What's the total market opportunity?
+
+### 5. What evidence do you have?
+- User research? Market data?
+- Personal experience?
+- Industry reports?
+- Or is this a hypothesis?
+
+### 6. What alternatives exist today?
+How do people solve this now? What's limiting about those solutions?
+
+## Example
+
+**Core Problem:**
+Remote team managers lack real-time visibility into team progress, leading to surprises when deadlines are missed.
+
+**Who:**
+Managers of 5-20 person distributed software teams in fast-moving startups
+
+**Why It Matters:**
+- Missed deadlines damage customer relationships
+- Reactive firefighting instead of proactive planning
+- Manager anxiety and team frustration from constant status checks
+- Estimated $50K-200K annual cost per team in missed opportunities and churn
+
+**Market Size:**
+- 2M+ distributed software teams globally
+- Growing 25% YoY (remote work acceleration)
+- $15B total addressable market (team collaboration tools)
+
+**Evidence:**
+- 50 interviews with remote managers
+- 75% cited "lack of visibility" as top frustration
+- Survey of 500 distributed teams
+- Personal experience managing distributed teams for 5 years
+
+**Current Alternatives:**
+- Weekly status meetings (time-consuming, lag visibility)
+- Slack check-ins (noisy, easy to miss critical updates)
+- Project management tools (team doesn't update them consistently)
+- **Limitation:** All require manual updates or scheduled check-ins
+
+---
+
+## Your Turn
+
+Define the problem using the structure above.
+
+**Tip:** If you can't clearly articulate the problem, stop. Don't proceed to building a solution without problem clarity.
+
+## Next Step
+
+When you've defined the problem clearly, I'll load:
+
+{project-root}/_bmad/bme/_vortex/workflows/product-vision/steps/step-02-target-market.md

package/_bmad/bme/_vortex/workflows/product-vision/steps/step-02-target-market.md

@@ -0,0 +1,91 @@
+---
+step: 2
+workflow: product-vision
+title: Identify Target Market
+---
+
+# Step 2: Identify Target Market
+
+Now that we know the problem, let's get specific about WHO we're serving.
+
+## Why This Matters
+
+"Everyone" is not a target market. Trying to serve everyone means you serve no one well. Being specific about your target market:
+- Focuses your messaging and positioning
+- Guides product decisions (build for THESE users, not all users)
+- Helps you find early adopters
+- Makes your vision believable and achievable
+
+## Your Task
+
+Answer these questions about your target market:
+
+### 1. Who is your primary target user?
+The MOST important user segment. If you could only serve one group, who would it be?
+
+### 2. What are their characteristics?
+- Role/job title?
+- Company size/industry?
+- Technical sophistication?
+- Budget authority?
+
+### 3. Why start with this segment?
+- Easiest to reach?
+- Feel pain most acutely?
+- Willing to pay?
+- Will become advocates?
+
+### 4. Secondary target users?
+Who else might benefit (but deprioritize for now)?
+
+### 5. Market segments within target?
+Any sub-segments with different needs?
+
+### 6. Beachhead strategy?
+Where do you start to prove the concept before expanding?
+
+## Example
+
+**Primary Target:**
+Engineering managers at Series A-C startups (20-200 employees) managing distributed teams of 5-15 engineers
+
+**Characteristics:**
+- **Role:** Engineering Manager, Director of Engineering, VP Engineering
+- **Company:** VC-backed startups, product-led, remote-first culture
+- **Team Size:** 5-15 direct reports, distributed across 2-4 timezones
+- **Tech Stack:** Modern (GitHub, Slack, Linear/Jira)
+- **Budget Authority:** $5K-25K annual budget for team tools
+- **Pain Intensity:** HIGH - under pressure to ship fast, teams growing quickly
+
+**Why Start Here:**
+- Feel pain most acutely (fast growth + distributed teams = visibility crisis)
+- Budget to pay for solutions (not hobbyists or freelancers)
+- Influencers (speak at conferences, write blogs, shape industry)
+- Natural network effects (one manager adopts → tells peers)
+
+**Secondary Targets** (Deprioritize for now):
+- Product managers at similar companies
+- Tech leads managing cross-functional teams
+- Enterprise teams (different needs, slower sales cycles)
+
+**Market Segments:**
+- **Segment A:** First-time engineering managers (high pain, low budget)
+- **Segment B:** Experienced managers at growing startups (high pain, high budget) ← START HERE
+- **Segment C:** Directors/VPs managing managers (different workflow needs)
+
+**Beachhead:**
+YC companies (tight community, concentrated in SF/remote, high pain, willing to try new tools, natural advocates)
+
+---
+
+## Your Turn
+
+Identify your target market using the structure above.
+
+**Tip:** If you find yourself saying "and also this group, and also that group," you're not focused enough. Pick ONE primary target and commit.
+
+## Next Step
+
+When you've identified your target market, I'll load:
+
+{project-root}/_bmad/bme/_vortex/workflows/product-vision/steps/step-03-unique-approach.md

package/_bmad/bme/_vortex/workflows/product-vision/steps/step-03-unique-approach.md

@@ -0,0 +1,87 @@
+---
+step: 3
+workflow: product-vision
+title: Articulate Unique Approach
+---
+
+# Step 3: Articulate Unique Approach
+
+What makes your solution different from (and better than) the alternatives?
+
+## Why This Matters
+
+If your approach isn't meaningfully different, you're just another commodity in a crowded market. Your unique approach:
+- Gives people a reason to switch from their current solution
+- Creates defensibility (hard to copy)
+- Guides your product strategy
+- Becomes the core of your positioning and messaging
+
+## Your Task
+
+Answer these questions about your unique approach:
+
+### 1. What's your core insight?
+What do you understand about the problem/solution that others don't?
+
+### 2. What makes your approach different?
+How does your solution differ from existing alternatives?
+
+### 3. Why is your approach better?
+For your target users, what advantage does your approach provide?
+
+### 4. What's your unfair advantage?
+What do you have (or can build) that's hard for competitors to replicate?
+- Team expertise?
+- Proprietary data/technology?
+- Strategic partnerships?
+- Network effects?
+
+### 5. Why now?
+What's changed that makes your approach possible or necessary now?
+
+### 6. What trade-offs are you making?
+Every approach has trade-offs. What are you optimizing for (and what are you sacrificing)?
+
+## Example
+
+**Core Insight:**
+Team status shouldn't require manual updates or scheduled meetings - it should be automatically inferred from the team's existing workflow.
+
+**Different Approach:**
+Instead of asking teams to update another tool, we automatically aggregate signals from their existing tools (GitHub, Linear, Slack) to provide real-time status.
+
+**Why Better:**
+- **Zero overhead** - Team doesn't change their workflow
+- **Real-time** - Updates instantly as work happens, not weekly
+- **Proactive** - Surfaces problems before they're crises
+- **Accurate** - Based on actual work, not what people remember to report
+
+**Unfair Advantage:**
+- Deep expertise in distributed systems (founding team from Datadog, New Relic)
+- Existing integration partnerships with GitHub, Linear, Slack
+- AI/ML models trained on 50K+ engineering teams' workflow patterns
+- Network effects: More teams = better pattern recognition
+
+**Why Now:**
+- Remote work explosion created urgent need for passive visibility
+- Modern tools have APIs (possible to aggregate signals)
+- AI/ML maturity makes pattern recognition feasible
+- Gen Z engineers refuse to "update another tool"
+
+**Trade-offs:**
+- ✅ **Optimizing for:** Zero-overhead for team, real-time accuracy
+- ❌ **Sacrificing:** Fine-grained control (trusting automation), works only for teams using integrated tools, requires AI investment
+
+---
+
+## Your Turn
+
+Articulate your unique approach using the structure above.
+
+**Tip:** If your approach is "better UX" or "easier to use," that's not differentiated enough. WHY is it better? WHAT specifically makes it easier?
+
+## Next Step
+
+When you've articulated your unique approach, I'll load:
+
+{project-root}/_bmad/bme/_vortex/workflows/product-vision/steps/step-04-future-state.md

package/_bmad/bme/_vortex/workflows/product-vision/steps/step-04-future-state.md

@@ -0,0 +1,100 @@
+---
+step: 4
+workflow: product-vision
+title: Envision Future State
+---
+
+# Step 4: Envision Future State
+
+What does success look like 3-5 years from now?
+
+## Why This Matters
+
+A vision without a future state is just a feature list. Envisioning the future:
+- Inspires the team (gets people excited about where we're going)
+- Guides strategy (ensures today's decisions move toward that future)
+- Helps prioritize (does this feature get us closer to the vision?)
+- Creates alignment (everyone sees the same destination)
+
+## Your Task
+
+Answer these questions about your future state:
+
+### 1. Where are we headed? (3-5 years)
+Paint a picture of the future. What has changed? What impact have you created?
+
+### 2. What does success look like?
+- For users? (How has their life/work improved?)
+- For your business? (Revenue? Users? Market position?)
+- For the market? (What shift did you create?)
+
+### 3. Key milestones along the way?
+What are the major checkpoints on the path to that future?
+
+### 4. What capabilities will you have built?
+Not features - capabilities. What will you be uniquely good at?
+
+### 5. How will the world be different?
+What will be possible that isn't possible today?
+
+### 6. What's your North Star metric?
+The one metric that best captures progress toward this vision?
+
+## Example
+
+**Future State (3-5 Years):**
+Team status anxiety is a thing of the past. Engineering managers at 10,000+ high-growth companies have real-time confidence in their team's progress without ever asking for status updates.
+
+**Success Looks Like:**
+
+**For Users:**
+- Managers spend <5 min/day on status (vs. current 30-60 min)
+- Zero manual status updates required from team
+- Proactive alerts prevent 80% of deadline surprises
+- Manager confidence score: 9/10 (vs. current 4/10)
+
+**For Business:**
+- $50M ARR, growing 100% YoY
+- 10,000+ distributed engineering teams using the platform
+- Category leader in "Automated Team Intelligence"
+- 40% market share of Series A-C startup engineering teams
+
+**For Market:**
+- "Status meeting" becomes quaint relic (like fax machines)
+- Industry standard: Teams produce status signals, AI interprets them
+- Adjacent markets emerge (automated planning, predictive resource allocation)
+
+**Key Milestones:**
+- **Year 1:** 100 teams, product-market fit, $1M ARR
+- **Year 2:** 1,000 teams, category creation, $10M ARR
+- **Year 3:** 5,000 teams, enterprise expansion, $25M ARR
+- **Year 4-5:** 10,000+ teams, market leadership, $50M+ ARR
+
+**Capabilities We'll Build:**
+- Best-in-class integrations with engineering tools
+- Most accurate AI models for predicting software delivery
+- Largest dataset of engineering workflow patterns
+- Fastest time-to-insight (real-time, not batch)
+
+**World Differently:**
+- Engineering managers focus on coaching, not tracking
+- Teams focus on building, not reporting
+- Proactive planning replaces reactive firefighting
+- Distributed teams are MORE visible than co-located teams (paradox!)
+
+**North Star Metric:**
+**Manager Confidence Score** - Daily measure of "How confident are you that your team is on track?" (Target: 9/10 average)
+
+---
+
+## Your Turn
+
+Envision your future state using the structure above.
+
+**Tip:** Make it inspiring but believable. "We'll replace all software engineers with AI" isn't believable. "We'll save engineering managers 10 hours/week" is believable and inspiring.
+
+## Next Step
+
+When you've envisioned the future state, I'll load:
+
+{project-root}/_bmad/bme/_vortex/workflows/product-vision/steps/step-05-principles.md

package/_bmad/bme/_vortex/workflows/product-vision/steps/step-05-principles.md

@@ -0,0 +1,92 @@
+---
+step: 5
+workflow: product-vision
+title: Align on Principles
+---
+
+# Step 5: Align on Principles
+
+What won't you compromise on? What principles guide your decisions?
+
+## Why This Matters
+
+Principles are your decision-making framework when there's no clear answer. They help you:
+- Say "no" to tempting but misaligned opportunities
+- Make consistent decisions as you scale
+- Maintain product integrity
+- Align the team on values
+
+Without clear principles, you'll drift or make contradictory decisions.
+
+## Your Task
+
+Answer these questions about your guiding principles:
+
+### 1. What won't you compromise?
+Even if it means slower growth or harder sales? What are your non-negotiables?
+
+### 2. What do you say NO to?
+Equally important - what will you consciously NOT do?
+
+### 3. What are your core values?
+The beliefs that guide how you build and operate?
+
+### 4. How do you make trade-off decisions?
+When you must choose between competing goods, what wins?
+
+### 5. What's your product philosophy?
+Simple vs. powerful? Open vs. opinionated? Fast vs. perfect?
+
+### 6. What kind of company do you want to build?
+Your values shape your culture, which shapes your product.
+
+## Example
+
+**Won't Compromise:**
+1. **Zero overhead for engineering teams** - If it adds work for engineers, we won't build it
+2. **Privacy & security** - Never sell data, never compromise security for features
+3. **Real-time accuracy** - Stale dashboards are useless; we optimize for freshness
+
+**Say NO To:**
+- ❌ Manual time-tracking or status updates (violates zero-overhead principle)
+- ❌ "Works better with our project management tool" (should work with ANY tool)
+- ❌ Gamification/leaderboards (creates wrong incentives, stresses teams)
+- ❌ Enterprise-only features (no fragmentation between tiers on core value)
+
+**Core Values:**
+- **Respect eng team time** - Managers get value, teams pay no cost
+- **Truth over comfort** - Show reality, even if uncomfortable
+- **Automation over process** - Technology should reduce overhead, not create it
+- **Privacy by design** - Individual work stays private, only team patterns surface
+
+**Trade-off Framework:**
+When choosing between:
+- **Speed vs. Accuracy** → Accuracy wins (wrong data worse than no data)
+- **Simple vs. Powerful** → Simple wins (power users can use APIs)
+- **Privacy vs. Insight** → Privacy wins (aggregate patterns, not individual activity)
+- **Open vs. Opinionated** → Opinionated wins (best practices baked in)
+
+**Product Philosophy:**
+- **Opinionated simplicity** - Strong defaults, easy to start, hard to misconfigure
+- **Progressive disclosure** - Simple surface, power underneath
+- **Passive intelligence** - Works in background, surfaces insights proactively
+
+**Company We're Building:**
+- Remote-first (we're the customer)
+- Sustainable growth over hypergrowth
+- Engineering-led culture
+- Long-term thinking (10-year vision)
+
+---
+
+## Your Turn
+
+Define your guiding principles using the structure above.
+
+**Tip:** Principles are only useful if they're specific enough to guide decisions. "Quality is important" isn't a principle. "We won't ship features that haven't been tested with 10+ real users" is a principle.
+
+## Next Step
+
+When you've aligned on principles, I'll load:
+
+{project-root}/_bmad/bme/_vortex/workflows/product-vision/steps/step-06-synthesize.md

package/_bmad/bme/_vortex/workflows/product-vision/steps/step-06-synthesize.md

@@ -0,0 +1,155 @@
+---
+step: 6
+workflow: product-vision
+title: Synthesize
+---
+
+# Step 6: Synthesize
+
+Let's bring it all together into a cohesive product vision document.
+
+## Why This Matters
+
+Your product vision document becomes:
+- The alignment tool for your team (everyone sees the same destination)
+- The decision-making framework (does this serve the vision?)
+- The communication artifact (pitches, hiring, partnerships)
+- The strategic anchor (when you drift, come back to this)
+
+## Your Task
+
+Before I generate the final artifact, a few final questions:
+
+### 1. Craft your vision statement (1-2 sentences)
+
+This is the pithy, memorable version. Should be:
+- **Aspirational** - Inspiring and ambitious
+- **Specific** - Clear about what you're creating
+- **Focused** - One clear idea, not three ideas mashed together
+
+**Formula:** For [target users] who [problem], [product] is a [category] that [key benefit]. Unlike [alternatives], our product [unique differentiation].
+
+### 2. Identify your strategic assumptions
+
+What MUST be true for this vision to succeed?
+
+Examples:
+- "Remote work will continue to dominate software teams"
+- "Engineering managers value time savings over detailed control"
+- "Teams will trust AI-generated insights"
+
+Mark each as:
+- **CRITICAL** - If this is false, vision fails
+- **IMPORTANT** - If this is false, strategy needs adjustment
+- **NICE** - Would help but not essential
+
+### 3. Define validation plan
+
+How will you know if you're making progress toward this vision?
+
+- **Metrics to track?**
+- **Milestones to hit?**
+- **Assumptions to validate first?**
+- **Timeline for first validation?**
+
+### 4. Team alignment check
+
+On a scale of 1-10:
+- How aligned is the team on this vision?
+- What concerns or disagreements remain?
+- What questions are still open?
+
+## Example
+
+**Vision Statement:**
+"For engineering managers at high-growth startups who waste hours tracking distributed team status, TeamPulse is an automated team intelligence platform that provides real-time confidence without requiring any team overhead. Unlike project management tools that demand manual updates, TeamPulse automatically aggregates workflow signals to surface insights proactively."
+
+**Strategic Assumptions:**
+
+**CRITICAL:**
+- Remote/distributed engineering teams will remain dominant (70%+ of Series A-C startups)
+- Engineering managers value accuracy + time savings > manual control
+- Modern engineering tools will maintain/improve API access
+
+**IMPORTANT:**
+- AI inference quality continues to improve (enables better pattern recognition)
+- Teams trust automated insights (education/change management needed)
+- Integration ecosystem remains accessible (not walled gardens)
+
+**NICE:**
+- Async work continues to grow (makes status even harder)
+- Economic pressure to do more with less (increases value prop)
+
+**Validation Plan:**
+
+**Metrics to Track:**
+- **Week 1-4:** 20 manager interviews - validate problem intensity
+- **Month 1-3:** 10-team pilot - validate zero-overhead approach
+- **Month 4-6:** $10K MRR - validate willingness to pay
+- **Month 7-12:** 100 teams, $100K ARR - validate product-market fit
+- **Year 2:** 1,000 teams, $1M ARR - validate scalability
+
+**Assumptions to Validate FIRST:**
+1. Managers spend 5+ hours/week on status (interview validation)
+2. Teams won't update another tool (pilot validation)
+3. AI can accurately infer status from signals (technical validation)
+
+**Timeline:**
+- **Weeks 1-4:** Problem validation (interviews)
+- **Weeks 5-8:** Technical validation (proof-of-concept)
+- **Weeks 9-16:** Solution validation (10-team pilot)
+- **Month 4+:** Business model validation (pricing experiments)
+
+**Team Alignment:**
+
+**Alignment Score:** 8/10
+
+**Remaining Concerns:**
+- **Tech lead:** "Can we actually build accurate AI models?" → Need PoC
+- **Design lead:** "Will managers trust automated insights?" → Need user research
+- **Sales lead:** "Is $20/user sustainable pricing?" → Need pricing experiments
+
+**Open Questions:**
+- Should we start with GitHub-only integrations or multi-tool from day 1?
+- Do we need manager-only insights or should individual contributors see their own data?
+- How do we handle teams that don't use integrated tools?
+
+---
+
+## Your Turn
+
+Please provide:
+1. Your vision statement (using the formula)
+2. Your strategic assumptions (marked as CRITICAL/IMPORTANT/NICE)
+3. Your validation plan with metrics and timeline
+4. Your team alignment score and open questions
+
+## Final Step
+
+When you've provided this information, I'll:
+1. Generate your complete product vision document
+2. Save it to `{output_folder}/product-vision-{product-name}-{date}.md`
+3. Create a team alignment summary
+4. Suggest next workflows:
+   - **lean-persona** to detail your target users
+   - **contextualize-scope** to define problem space boundaries
+   - **Wade's mvp** to design your minimum viable product
+
+**Remember:** This vision is your north star, not your prison. As you learn, the vision can evolve. But change it deliberately, not drift unconsciously.
+
+---
+
+## Workflow Complete
+
+After synthesis, your product vision document will include:
+- Clear vision statement
+- Problem definition
+- Target market specificity
+- Unique approach and advantages
+- Future state (3-5 years)
+- Guiding principles
+- Strategic assumptions
+- Validation plan
+- Team alignment status
+
+This becomes your strategic foundation for all product decisions.

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

@@ -0,0 +1,30 @@
+# Validate Product Vision
+
+**Status:** Coming in v1.2.0
+
+**Agent:** Emma (Contextualization Expert)
+
+**Stream:** Contextualize
+
+## Overview
+
+This validation workflow helps you review product visions to ensure they're clear, compelling, and actionable.
+
+## What Gets Validated
+
+- Is the vision inspirational yet achievable?
+- Is the problem statement specific and evidence-based?
+- Are target users clearly defined?
+- Are success metrics measurable and meaningful?
+- Are key assumptions explicitly stated?
+- Does this align team around the "why"?
+
+## Coming in v1.2.0
+
+This validation workflow will be available alongside the product-vision workflow in March 2026.
+
+## Questions?
+
+For questions or to request early access:
+- GitHub Issues: https://github.com/amalik/BMAD-Enhanced/issues
+- Tag with: `workflow:product-vision` and `v1.2.0`