whiteport-design-studio 0.1.0

package/src/workflows/1-project-brief/project-brief/complete/steps-c/step-02-vision.md

@@ -0,0 +1,43 @@
+# Step 2: Capture Vision
+
+## Purpose
+
+Help user articulate their vision for the product.
+
+## Context for Agent
+
+You are exploring the big picture with the user. Your goal is to help them crystallize their aspirational vision into a clear statement that will guide all decisions.
+
+## Key Elements
+
+This step captures the high-level, aspirational direction that will guide all decisions.
+
+## Instructions
+
+1. **Ask vision question**
+   - "What's your vision for this product?"
+   - "If this project succeeds beyond your wildest dreams, what does that look like? Don't worry about being realistic yet - dream big."
+
+2. **Listen for key elements**
+   - Aspirational outcomes
+   - Impact on users
+   - Market position
+   - Emotional drivers
+
+3. **Reflect and crystallize**
+   - Reflect back what you heard
+   - Help crystallize into a clear vision statement
+   - Use collaborative language: "What I'm hearing is..." or "It sounds like..."
+
+## Next Step
+
+After capturing vision, proceed to step-03-positioning.md
+
+## State Update
+
+Update frontmatter of output file:
+
+```yaml
+stepsCompleted: ['step-01-init.md', 'step-02-vision.md']
+vision: '[captured vision statement]'
+```

package/src/workflows/1-project-brief/project-brief/complete/steps-c/step-03-positioning.md

@@ -0,0 +1,34 @@
+# Step 3: Define Positioning
+
+## Purpose
+
+Help user define clear positioning statement for their product.
+
+## Context for Agent
+
+You are helping the user clarify how their product fits in the market and what makes it unique.
+
+## Key Elements
+
+This step establishes market positioning and differentiation.
+
+## Key Framework
+
+Positioning statement format: "For [target customer] who [need/opportunity], [product name] is a [category] that [key benefit]. Unlike [alternatives], we [differentiator]."
+
+## Instructions
+
+Guide user through positioning framework. Ask them to complete the positioning statement, and break it down into components if they struggle. Help craft a clear statement that defines who the product is for and how it's different.
+
+## Next Step
+
+Load, read full file, and execute: `step-04-create-vtc.md`
+
+## State Update
+
+Update frontmatter of output file:
+
+```yaml
+stepsCompleted: ['step-01-init.md', 'step-02-vision.md', 'step-03-positioning.md']
+positioning: '[captured positioning statement]'
+```

package/src/workflows/1-project-brief/project-brief/complete/steps-c/step-04-create-vtc.md

@@ -0,0 +1,118 @@
+# Step 4: Create Value Trigger Chain
+
+## Purpose
+
+Create a simplified Value Trigger Chain (VTC) to crystallize strategic thinking early and guide all subsequent discovery.
+
+## Context for Agent
+
+You now have Vision and Positioning - the essential product idea. Before diving into detailed discovery, we'll create a VTC to serve as a **strategic benchmark**. This forces early clarity and ensures all subsequent work aligns with core strategy.
+
+This VTC will be used for:
+- **Strategic benchmark** - "Does this align with our VTC?"
+- **Guiding discovery** - Informs questions about users, success criteria, etc.
+- **Early validation** - If VTC isn't clear, vision needs work
+- **Quick reference** - One-page strategy throughout project
+
+## Instructions
+
+### 1. Explain VTC to User
+
+> "Now that we have your vision and positioning, let's create a Value Trigger Chain (VTC).
+> 
+> This is a strategic benchmark that will guide all remaining discovery work. It captures:
+> - **Business Goal** - What measurable outcome we want
+> - **Solution** - What we're building
+> - **User** - Who the primary user is
+> - **Driving Forces** - What motivates them (positive + negative)
+> - **Customer Awareness** - Where they start and where we move them
+> 
+> This takes 20-30 minutes but is incredibly valuable. It forces strategic clarity NOW and gives us a benchmark to evaluate all future decisions against.
+> 
+> As we continue discovery (business model, users, success criteria), we'll use this VTC to ensure everything aligns.
+> 
+> Shall we create the VTC now?"
+
+### 2. Route to VTC Workshop
+
+**If user agrees:**
+
+Load and execute the VTC Workshop Router:
+`{project-root}/{bmad_folder}/wds/workflows/shared/vtc-workshop/vtc-workshop-router.md`
+
+**Note:** Since Product Brief stage typically has NO Trigger Map yet, the router will likely send you to the **Creation Workshop**.
+
+### 3. Leverage Vision and Positioning Context
+
+**Important:** You have vision and positioning completed! Use it:
+
+- **Solution:** From vision (what we're building)
+- **Business Goal:** Infer from vision (what outcome we want)
+- **User:** From positioning (target_customer)
+- **Driving Forces:** Infer from positioning (need/opportunity, differentiator)
+- **Customer Awareness:** Infer from positioning (where they are now)
+
+**Don't start from zero** - use the strategic work already completed.
+
+**Note:** At this stage, estimates are fine. The VTC will be validated and refined as we discover more detail in later steps.
+
+### 4. Save VTC
+
+VTC should be saved to:
+`{output_folder}/A-Product-Brief/vtc-primary.yaml`
+
+### 5. Save VTC (Brief Integration Later)
+
+VTC is saved but NOT yet added to brief document.
+
+**Why:** Product Brief document isn't complete yet. We'll add VTC section during final synthesis (Step 11).
+
+**For now:** VTC exists as separate file and serves as strategic benchmark for remaining discovery steps.
+
+### 6. Confirm Completion and Set Expectation
+
+> "Excellent! We've created your Value Trigger Chain.
+> 
+> This VTC will serve as our strategic benchmark. As we continue discovery (business model, target users, success criteria, etc.), we'll use this VTC to ensure everything aligns.
+> 
+> If anything in remaining discovery contradicts this VTC, it means either:
+> - The VTC needs adjustment (vision wasn't clear enough)
+> - The discovery finding doesn't serve our strategy
+> 
+> We'll validate and refine the VTC during final synthesis if needed.
+> 
+> Let's continue with the detailed discovery!"
+
+## Next Step
+
+Load, read full file, and execute: `step-05-business-model.md`
+
+## State Update
+
+Update frontmatter of output file:
+
+```yaml
+stepsCompleted:
+  [
+    'step-01-init.md',
+    'step-02-vision.md',
+    'step-03-positioning.md',
+    'step-04-create-vtc.md',
+  ]
+status: 'in-progress'
+```
+
+## If User Declines VTC
+
+**If user says:** "Let's skip the VTC for now"
+
+**Response:**
+> "No problem! You can create a VTC later using:
+> `{bmad_folder}/wds/workflows/shared/vtc-workshop/vtc-workshop-router.md`
+> 
+> However, I recommend creating it before pitching to stakeholders or starting Phase 4 (UX Design). It takes 30 minutes and provides valuable strategic clarity.
+> 
+> Product Brief is complete. You can add VTC anytime."
+
+Then proceed to mark workflow as complete.
+

package/src/workflows/1-project-brief/project-brief/complete/steps-c/step-05-business-model.md

@@ -0,0 +1,26 @@
+# Step 4: Determine Business Model
+
+## Goal
+
+Help user identify whether their product is B2B, B2C, or both.
+
+## Key Elements
+
+Business model determines who buys/uses the product and affects all strategic decisions.
+
+## Instructions
+
+Ask user whether their product is B2B, B2C, or both. Present clear options and explain the implications of each choice.
+
+## Next Step
+
+After determining business model, proceed to step-05-business-customers.md if B2B or Both, or step-06-target-users.md if B2C
+
+## State Update
+
+Update frontmatter of output file:
+
+```yaml
+stepsCompleted: ['step-01-init.md', 'step-02-vision.md', 'step-03-positioning.md', 'step-04-create-vtc.md', 'step-05-business-model.md']
+business_model: '[b2b/b2c/both]'
+```

package/src/workflows/1-project-brief/project-brief/complete/steps-c/step-06-business-customers.md

@@ -0,0 +1,28 @@
+# Step 5: Identify Business Customers (B2B)
+
+## Goal
+
+Help user define their ideal business customer profile.
+
+## Key Elements
+
+Business customer profile determines who buys the product and influences purchasing decisions.
+
+## Instructions
+
+If business model is B2B or Both, guide user to define their ideal business customer. Ask about company size, industry, decision-making structure, and budget authority. Also identify buying roles (buyer vs. user).
+
+## Next Step
+
+After identifying business customers, proceed to step-06-target-users.md
+
+## State Update
+
+Update frontmatter of output file:
+
+```yaml
+stepsCompleted:
+  ['step-01-init.md', 'step-02-vision.md', 'step-03-positioning.md', 'step-04-create-vtc.md', 'step-05-business-model.md', 'step-06-business-customers.md']
+business_customer_profile: '[captured business customer profile]'
+buying_roles: '[captured buying roles]'
+```

package/src/workflows/1-project-brief/project-brief/complete/steps-c/step-07-target-users.md

@@ -0,0 +1,40 @@
+# Step 6: Identify Target Users
+
+## Purpose
+
+Help user define their ideal customer profile.
+
+## Context for Agent
+
+You are identifying who the product is for and what their needs are. This information will guide all design decisions.
+
+## Key Elements
+
+This step identifies who we're designing for and what their needs are.
+
+## Instructions
+
+Guide user to describe their ideal users in detail. Ask about their role, demographics, daily experience, frustrations, goals, and current solutions. Also identify any secondary users or stakeholders.
+
+## Next Step
+
+After identifying target users, proceed to step-07-success-criteria.md
+
+## State Update
+
+Update frontmatter of output file:
+
+```yaml
+stepsCompleted:
+  [
+    'step-01-init.md',
+    'step-02-vision.md',
+    'step-03-positioning.md',
+    'step-04-business-model.md',
+    'step-05-business-model.md',
+    'step-06-business-customers.md',
+    'step-07-target-users.md',
+  ]
+ideal_user_profile: '[captured user profile]'
+secondary_users: '[captured secondary users]'
+```

package/src/workflows/1-project-brief/project-brief/complete/steps-c/step-08-success-criteria.md

@@ -0,0 +1,40 @@
+# Step 7: Define Success Criteria
+
+## Purpose
+
+Help user define measurable success criteria for their project.
+
+## Context for Agent
+
+You are establishing how the project will know if it's successful. This will guide all future decisions.
+
+## Key Elements
+
+This step establishes measurable outcomes that indicate success.
+
+## Instructions
+
+Guide user to define metrics and outcomes that indicate success. Help them think about user behavior, business outcomes, experience quality, and timeline. Work with them to make criteria SMART (Specific, Measurable, Achievable, Relevant, Time-bound).
+
+## Next Step
+
+After defining success criteria, proceed to step-08-competitive-landscape.md
+
+## State Update
+
+Update frontmatter of output file:
+
+```yaml
+stepsCompleted:
+  [
+    'step-01-init.md',
+    'step-02-vision.md',
+    'step-03-positioning.md',
+    'step-04-business-model.md',
+    'step-05-business-customers.md',
+    'step-06-business-customers.md',
+    'step-07-target-users.md',
+    'step-08-success-criteria.md',
+  ]
+success_criteria: '[captured success criteria]'
+```

package/src/workflows/1-project-brief/project-brief/complete/steps-c/step-09-competitive-landscape.md

@@ -0,0 +1,42 @@
+# Step 8: Analyze Competitive Landscape
+
+## Purpose
+
+Help user understand alternatives and their unique advantage.
+
+## Context for Agent
+
+You are exploring what alternatives exist and what makes the product unique. This information will guide differentiation strategy.
+
+## Key Elements
+
+This step identifies competitive positioning and unique value proposition.
+
+## Instructions
+
+Guide user to understand alternatives including direct competitors, different approaches, manual solutions, or doing nothing. For each alternative, explore strengths, weaknesses, and why users might choose them. Help identify their unfair advantage.
+
+## Next Step
+
+After analyzing competitive landscape, proceed to step-09-constraints.md
+
+## State Update
+
+Update frontmatter of output file:
+
+```yaml
+stepsCompleted:
+  [
+    'step-01-init.md',
+    'step-02-vision.md',
+    'step-03-positioning.md',
+    'step-04-business-model.md',
+    'step-05-business-customers.md',
+    'step-06-target-users.md',
+    'step-07-target-users.md',
+    'step-08-success-criteria.md',
+    'step-09-competitive-landscape.md',
+  ]
+competitive_landscape: '[captured competitive analysis]'
+unfair_advantage: '[captured unfair advantage]'
+```

package/src/workflows/1-project-brief/project-brief/complete/steps-c/step-10-constraints.md

@@ -0,0 +1,43 @@
+# Step 9: Capture Constraints and Context
+
+## Purpose
+
+Help user identify constraints that should shape design decisions.
+
+## Context for Agent
+
+You are grounding the vision in reality by identifying limitations and context.
+
+## Key Elements
+
+This step identifies real-world limitations and additional context.
+
+## Instructions
+
+Guide user to identify constraints including timeline, budget, technical requirements, brand guidelines, regulatory needs, and integration requirements. Also ask for additional context like company stage, team capabilities, market conditions, or past attempts.
+
+## Next Step
+
+After capturing constraints, proceed to step-10a-platform-strategy.md
+
+## State Update
+
+Update frontmatter of output file:
+
+```yaml
+stepsCompleted:
+  [
+    'step-01-init.md',
+    'step-02-vision.md',
+    'step-03-positioning.md',
+    'step-04-business-model.md',
+    'step-05-business-customers.md',
+    'step-06-target-users.md',
+    'step-07-success-criteria.md',
+    'step-08-success-criteria.md',
+    'step-09-competitive-landscape.md',
+    'step-10-constraints.md',
+  ]
+constraints: '[captured constraints]'
+additional_context: '[captured additional context]'
+```

package/src/workflows/1-project-brief/project-brief/complete/steps-c/step-10a-platform-strategy.md

@@ -0,0 +1,73 @@
+# Step 10A: Define Platform & Device Strategy
+
+## Purpose
+
+Establish the technical platform strategy and device support requirements that will shape all design and development decisions.
+
+## Context for Agent
+
+You are helping the user make critical architectural decisions about what platforms and devices their product will support. These decisions affect scope, budget, timeline, technical complexity, and user experience design.
+
+## Key Elements
+
+This step identifies primary platform(s), device support requirements, interaction models, and platform rationale.
+
+## Instructions
+
+Guide user to define their platform strategy by asking about primary platform choice, supported devices, device priority, interaction models needed, offline functionality requirements, native device features needed, and platform rationale including constraints and future plans.
+
+**Common Platform Options:**
+
+1. **Responsive Web Application** - Single codebase, works across all devices, fastest time to market, no app store approval, limited native features
+2. **Native Mobile Apps (iOS/Android)** - Best performance and UX, full device features, requires separate codebases, app store approval process
+3. **Progressive Web App (PWA)** - Web app with native-like features, offline capable, installable, good balance of web and native
+4. **Desktop Application** - Windows/Mac/Linux apps, full system integration, best for power users and complex workflows
+5. **Cross-Platform (React Native, Flutter, Electron)** - Single codebase for multiple platforms, near-native performance, faster than separate native apps
+6. **Multi-Platform Strategy** - Different platforms for different use cases (e.g., web for setup/admin, mobile for daily use), higher complexity but optimized per context
+
+**Device Priority Options:**
+
+- **Mobile-first** - Design for phones, scale up to tablets/desktop
+- **Desktop-first** - Design for desktop, scale down to tablets/mobile
+- **Equal priority** - All devices equally important, universal design
+
+**Interaction Models:**
+
+- Touch (mobile, tablets)
+- Mouse and keyboard (desktop)
+- Voice commands
+- Gesture controls
+- Accessibility devices (screen readers, switch controls)
+
+Capture platform strategy, validate alignment with vision and constraints, and document in Product Brief under "Platform & Device Strategy" section including primary platform, supported devices, device priority with rationale, interaction models, technical requirements (offline, native features), platform rationale, constraints considered, future plans, and design/development implications.
+
+## Next Step
+
+After capturing platform strategy, proceed to step-11-tone-of-voice.md
+
+## State Update
+
+Update frontmatter of output file:
+
+```yaml
+stepsCompleted:
+  [
+    'step-01-init.md',
+    'step-02-vision.md',
+    'step-03-positioning.md',
+    'step-04-business-model.md',
+    'step-05-business-customers.md',
+    'step-06-target-users.md',
+    'step-07-success-criteria.md',
+    'step-08-competitive-landscape.md',
+    'step-09-constraints.md',
+    'step-10a-platform-strategy.md',
+  ]
+platform_strategy:
+  primary_platform: '{captured}'
+  supported_devices: '{captured}'
+  device_priority: '{captured}'
+  interaction_models: '{captured}'
+  offline_requirements: '{captured}'
+  native_features_needed: '{captured}'
+```

package/src/workflows/1-project-brief/project-brief/complete/steps-c/step-11-create-vtc.md

@@ -0,0 +1,133 @@
+# Step 11: Create Value Trigger Chain
+
+## Purpose
+
+Create a simplified Value Trigger Chain (VTC) to capture strategic essence for stakeholder communication.
+
+## Context for Agent
+
+The Product Brief contains comprehensive strategic foundation. Now we'll distill this into a focused VTC that captures the essential strategic chain: Business Goal → Solution → User → Driving Forces → Customer Awareness.
+
+This VTC will be used for:
+- Pitching the project to stakeholders
+- Quick strategic reference during design
+- Foundation for scenario-specific VTCs later
+
+## Instructions
+
+### 1. Explain VTC to User
+
+> "Before we finalize the Product Brief, let's create a Value Trigger Chain (VTC).
+> 
+> This is a simplified strategic summary that captures:
+> - **Business Goal** - What measurable outcome we want
+> - **Solution** - What we're building
+> - **User** - Who the primary user is
+> - **Driving Forces** - What motivates them (positive + negative)
+> - **Customer Awareness** - Where they start and where we move them
+> 
+> This will take about 20-30 minutes and gives you a powerful one-page strategic foundation.
+> 
+> Shall we create the VTC now?"
+
+### 2. Route to VTC Workshop
+
+**If user agrees:**
+
+Load and execute the VTC Workshop Router:
+`{project-root}/{bmad_folder}/wds/workflows/shared/vtc-workshop/vtc-workshop-router.md`
+
+**Note:** Since Product Brief stage typically has NO Trigger Map yet, the router will likely send you to the **Creation Workshop**.
+
+### 3. Leverage Product Brief Context
+
+**Important:** You have extensive context from the Product Brief! Use it:
+
+- **Business Goal:** From success_criteria
+- **Solution:** From vision
+- **User:** From ideal_user_profile
+- **Driving Forces:** Infer from positioning, need/opportunity, and user profile
+- **Customer Awareness:** Infer from positioning and target customer
+
+**Don't start from zero** - use the strategic work already completed.
+
+### 4. Save VTC
+
+VTC should be saved to:
+`{output_folder}/A-Product-Brief/vtc-primary.yaml`
+
+### 5. Add VTC to Brief
+
+After VTC is created, add it to the Product Brief document BEFORE the "Next Steps" section:
+
+```markdown
+---
+
+## Value Trigger Chain
+
+**Strategic Summary** - [View full VTC](./vtc-primary.yaml)
+
+- **Business Goal:** [primary goal]
+- **Solution:** [solution]
+- **User:** [user name/type]
+- **Driving Forces:**
+  - *Wants to:* [positive forces]
+  - *Wants to avoid:* [negative forces]
+- **Awareness Journey:** [start stage] → [end stage]
+
+This VTC provides quick strategic reference and will inform all design decisions.
+
+---
+```
+
+### 6. Confirm Completion
+
+> "Excellent! Your Product Brief now includes a Value Trigger Chain.
+> 
+> This VTC will:
+> - Help you pitch the project to stakeholders
+> - Guide early design decisions
+> - Serve as foundation for scenario-specific VTCs in Phase 4
+> 
+> Product Brief is now complete!"
+
+## Next Step
+
+Workflow complete. Update state and present completion.
+
+## State Update
+
+Update frontmatter of output file:
+
+```yaml
+stepsCompleted:
+  [
+    'step-01-init.md',
+    'step-02-vision.md',
+    'step-03-positioning.md',
+    'step-04-business-model.md',
+    'step-05-business-customers.md',
+    'step-06-target-users.md',
+    'step-07-success-criteria.md',
+    'step-08-competitive-landscape.md',
+    'step-09-constraints.md',
+    'step-10-synthesize.md',
+    'step-11-create-vtc.md',
+  ]
+status: 'complete'
+```
+
+## If User Declines VTC
+
+**If user says:** "Let's skip the VTC for now"
+
+**Response:**
+> "No problem! You can create a VTC later using:
+> `{bmad_folder}/wds/workflows/shared/vtc-workshop/vtc-workshop-router.md`
+> 
+> However, I recommend creating it before pitching to stakeholders or starting Phase 4 (UX Design). It takes 30 minutes and provides valuable strategic clarity.
+> 
+> Product Brief is complete. You can add VTC anytime."
+
+Then proceed to mark workflow as complete.
+