whiteport-design-studio 0.2.2 → 0.3.0

package/src/workflows/1-project-brief/vtc-workshop/steps-c/step-07b-review-and-save.md

@@ -1,191 +0,0 @@
----
-name: 'step-07b-review-and-save'
-description: 'Validate complete VTC with source attribution and save - final step of Selection Workshop'
-
-# File References
-workflowFile: '../../workflow.md'
-activityWorkflowFile: '../workflow.md'
----
-
-# Step 7: Review and Save VTC
-
-## STEP GOAL:
-Validate complete VTC, refine if needed, and save with source attribution back to the Trigger Map.
-
-## 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
-- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-- You are a Strategic Business Analyst completing the VTC Selection Workshop
-- If you already have been given a name, communication_style and persona, continue to use those while playing this new role
-- We engage in collaborative dialogue, not command-response
-- You bring structured thinking and facilitation skills, user brings domain expertise and product vision
-- Maintain collaborative and strategic tone throughout
-
-### Step-Specific Rules:
-- Focus: Read back VTC, final refinement check, validate with 4 questions, save with source metadata
-- FORBIDDEN: Do not skip source metadata or selection rationale documentation
-- Approach: Present VTC, check for map gaps, validate, save with traceability, communicate
-
-## EXECUTION PROTOCOLS:
-- Primary goal: VTC validated, saved with source attribution, user understands traceability
-- Save/document outputs appropriately
-- Avoid generating content without user input
-
-## CONTEXT BOUNDARIES:
-- Available context: All VTC elements from steps 1-6 plus Trigger Map
-- Focus: Review, validation, and save with source attribution
-- Limits: Finalizing, not starting new work
-- Dependencies: Steps 01b-06b completed
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Read Back Complete VTC
-
-```yaml
-vtc:
-  business_goal:
-    primary: "[From Trigger Map]"
-    priority: "[From map]"
-  solution: "[Newly defined]"
-  user:
-    name: "[From Trigger Map]"
-    description: "[From map]"
-    priority: "[From map]"
-  driving_forces:
-    positive: "[Selected from map]"
-    negative: "[Selected from map]"
-  customer_awareness:
-    start: "[Newly defined]"
-    end: "[Newly defined]"
-
-metadata:
-  source: "trigger_map"
-  trigger_map_path: "[path]"
-  extracted_date: "[today]"
-```
-
-### 2. Final Refinement Check
-
-> "Now that you see the complete VTC, did using the Trigger Map for this real scenario reveal anything we should capture?"
-
-**Ask:**
-- Missing elements we should add to VTC?
-- Wording that needs adjustment?
-- Gaps we should update in Trigger Map?
-
-**If refinements needed:**
-- Make adjustments to VTC
-- Document what should update in Trigger Map
-- Note: "Refinements made during final review: [changes]"
-
-**If refinements reveal major Trigger Map gaps:**
-- Consider pausing to update Trigger Map
-- Document urgency: "now/soon/later"
-
-**If VTC perfect as-is:**
-- Great! Trigger Map is robust
-
-### 3. Validation
-
-Same 4 questions as Creation Workshop:
-
-1. **Coherence:** Does this tell a coherent story?
-2. **Actionable:** Can designers make decisions from this?
-3. **Specific:** Are driving forces specific enough?
-4. **Realistic:** Does awareness progression make sense?
-
-**All YES?** -> Save
-**Any NO?** -> Refine and re-validate
-
-### 4. Save Location
-
-**Product Pitch:** `{output_folder}/A-Product-Brief/vtc-primary.yaml`
-**Scenario:** `{output_folder}/C-UX-Scenarios/[scenario-name]/vtc.yaml`
-
-### 5. Include Source Metadata
-
-```yaml
-metadata:
-  source: "trigger_map"
-  trigger_map_path: "[path to source map]"
-  extracted_date: "[date]"
-  business_goal_priority: "[from map]"
-  user_priority: "[from map]"
-
-notes: |
-  Extracted from Trigger Map for [purpose]
-
-  Selection rationale:
-  - Chose [goal] because [reason]
-  - Chose [user] because [reason]
-  - Selected these driving forces because [reason]
-
-  Refinements made during workshop:
-  - [Any changes/additions during selection]
-  - [What should update in Trigger Map]
-
-  Trigger Map update recommendations:
-  - Element: [what] | Urgency: [now/soon/later] | Reason: [why]
-```
-
-### 6. Communicate to User
-
-> "Excellent! We've extracted a focused VTC from your Trigger Map.
->
-> **Advantage:** This VTC is backed by your strategic research and remains consistent with your map's priorities.
->
-> **Traceability:** We've documented the source, so if your Trigger Map evolves, we can update this VTC accordingly."
-
-### 7. Define Next Actions
-
-Same as Creation Workshop - based on context (Pitch or Scenario).
-
-### 8. Completion Checklist
-
-- [ ] VTC validated
-- [ ] Saved to correct location
-- [ ] Source metadata included
-- [ ] Selection rationale documented
-- [ ] User understands traceability
-- [ ] Next actions defined
-
-### N. Present MENU OPTIONS
-Display: "**Select an Option:** [M] Return to workflow menu"
-
-#### Menu Handling Logic:
-- IF M: Return to {workflowFile} or {activityWorkflowFile}
-- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
-
-#### EXECUTION RULES:
-- ALWAYS halt and wait for user input after presenting menu
-- User can chat or ask questions - always respond and then redisplay menu options
-
-## CRITICAL STEP COMPLETION NOTE
-This is the FINAL step of the VTC Selection Workshop. Workshop is complete.
-
----
-
-## SYSTEM SUCCESS/FAILURE METRICS
-
-### SUCCESS:
-- Complete VTC presented with source attribution
-- Final refinement check completed
-- All 4 validation questions answered YES
-- VTC saved with source metadata and selection rationale
-- User understands traceability to Trigger Map
-- Next actions defined
-
-### FAILURE:
-- Skipped source metadata
-- Did not document selection rationale
-- Saved without traceability
-- Did not check for Trigger Map gaps
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/workflows/1-project-brief/vtc-workshop/workflow.md

@@ -1,209 +0,0 @@
----
-name: vtc-workshop
-description: Create or select VTC based on available strategic context (Trigger Map or from scratch)
-web_bundle: true
----
-
-# Value Trigger Chain (VTC) Workshop
-
-**Goal:** Create a Value Trigger Chain to connect business goals, user needs, and driving forces
-
-**Your Role:** Strategic facilitator helping create or select VTC based on available context (Trigger Map or from scratch)
-
----
-
-## WORKFLOW ARCHITECTURE
-
-This uses **step-file architecture** with **routing logic**:
-
-### Core Principles
-
-- **Context-Based Routing**: Selection (if Trigger Map exists) or Creation (from scratch)
-- **Strategic Foundation**: VTC connects business goals → solution → user → driving forces → awareness
-- **Flexibility**: Can be created early (Product Pitch) or scenario-specific
-- **YAML Output**: Structured format for reuse across project
-
-### Critical Rules
-
-- 🎯 **ALWAYS** determine context first (Trigger Map exists?)
-- 🔀 **ALWAYS** route to appropriate workshop based on context
-- 📊 **ALWAYS** output YAML format
-- 🎯 **ALWAYS** capture 2-5 driving forces (positive and negative)
-- 📍 **ALWAYS** define customer awareness journey (start → end)
-
----
-
-## WHEN TO USE
-
-Use this workflow when:
-- ✅ Creating Product Pitch (need primary VTC)
-- ✅ Defining new scenario (need scenario-specific VTC)
-- ✅ Need strategic clarity before design
-- ✅ Want to connect business goals to user needs
-
-Skip this workflow when:
-- ❌ VTC already exists for this context
-- ❌ No strategic planning needed (pure visual design)
-- ❌ Working from existing detailed requirements
-
----
-
-## ROUTING DECISION
-
-**First Question:** "Do you have a completed Trigger Map?"
-
-### Route A: VTC Selection Workshop
-**IF YES** - Trigger Map exists
-
-**Use when:**
-- Trigger Map is completed
-- Want to extract VTC from existing strategic work
-- Need consistency with Trigger Map
-- Multiple scenarios need VTCs
-
-**Benefits:**
-- Leverage existing research
-- Maintain consistency
-- Faster (select vs. imagine)
-
-**Steps folder:** `steps-c/` (step-01b through step-07b)
-
----
-
-### Route B: VTC Creation Workshop
-**IF NO** - No Trigger Map yet
-
-**Use when:**
-- No Trigger Map available
-- Early stage (Product Pitch)
-- Quick project needing lightweight approach
-- Standalone scenario/prototype
-
-**Benefits:**
-- Get started immediately
-- No Trigger Map overhead
-- Sufficient for simple projects
-
-**Steps folder:** `steps-c/` (step-01a through step-07a)
-
----
-
-## CONTEXT TO PROVIDE
-
-When routing to either workshop, gather:
-
-**Project Context:**
-- Project name
-- Current phase (Pitch or Scenario Definition)
-- Purpose of this VTC (what will it be used for?)
-
-**For Selection Workshop (if Trigger Map exists):**
-- Path to Trigger Map document
-- Number of business goals mapped
-- Number of users/personas mapped
-- Current scenario being defined (if applicable)
-
-**For Creation Workshop (if no map):**
-- Brief project description
-- Who is the primary user? (if known)
-- What problem are we solving? (if known)
-
----
-
-## AGENT INSTRUCTIONS
-
-1. Ask: "Do you have a completed Trigger Map?"
-2. Based on answer, route to appropriate workshop
-3. Provide context information to that workshop
-4. Run the selected workshop
-5. Save resulting VTC to appropriate location
-6. Confirm completion with user
-
-**Example Dialog:**
-
-```
-Agent: "I'll help you create a Value Trigger Chain for [context].
-        Do you have a completed Trigger Map for this project?"
-
-User: "No, not yet."
-
-Agent: "Perfect! I'll guide you through creating a VTC from scratch.
-        This will take about 30 minutes. Let's start with your
-        business goal..."
-
-[Proceeds to Creation Workshop]
-```
-
----
-
-## FIRST STEP EXECUTION
-
-**After routing decision:**
-
-**IF Selection Workshop:**
-Load, read and execute `steps-c/step-01b-load-trigger-map.md`
-
-**IF Creation Workshop:**
-Load, read and execute `steps-c/step-01a-define-business-goal.md`
-
-**Template:** `../templates/vtc-template.yaml`
-
----
-
-## OUTPUT
-
-**Completed VTC (YAML format):**
-
-```yaml
-businessGoal: [What business wants to achieve]
-solution: [How we help user achieve their goal]
-user: [Who we're helping]
-drivingForces:
-  positive:
-    - [What they want/hope for]
-    - [Another positive driver]
-  negative:
-    - [What they fear/avoid]
-    - [Another negative driver]
-customerAwareness:
-  start: [Where they are now]
-  end: [Where they need to be]
-```
-
-**Destination:**
-- Product Pitch: `docs/A-Product-Brief/vtc-primary.yaml`
-- Scenario: `docs/C-UX-Scenarios/[scenario-name]/vtc.yaml`
-
----
-
-## EXAMPLE USE CASES
-
-### Use Case 1: Product Pitch (No Trigger Map)
-→ Route to Creation Workshop
-→ Create primary VTC from scratch
-→ Save to `docs/A-Product-Brief/vtc-primary.yaml`
-
-### Use Case 2: Scenario Definition (Trigger Map Exists)
-→ Route to Selection Workshop
-→ Select business goal + user from Trigger Map
-→ Customize driving forces for scenario
-→ Save to `docs/C-UX-Scenarios/[scenario]/vtc.yaml`
-
-### Use Case 3: Multiple Scenarios
-→ Route to Selection Workshop for each
-→ Create variant VTCs from same Trigger Map
-→ Maintain consistency across scenarios
-
----
-
-## ALPHA STATUS
-
-**This workshop is in ALPHA** - feedback needed.
-
-Please document:
-- Where you got stuck
-- What took longer than estimated
-- What needs clarification
-- What's missing
-
-Add feedback to VTC file notes section.

package/src/workflows/4-ux-design/data/scenario-init/07-create-vtc.md

@@ -1,132 +0,0 @@
-# 6. Create Value Trigger Chain for Scenario
-
-**Purpose:** Crystallize scenario strategy before sketching
-
----
-
-## Why Now?
-
-You've defined:
-- ✅ Feature that delivers value
-- ✅ Entry point
-- ✅ Mental state
-- ✅ Mutual success
-- ✅ Shortest path
-
-**Perfect time to create a VTC** - you have everything needed.
-
-This VTC will guide every page, every interaction, every word in this scenario.
-
----
-
-## Agent Instructions
-
-> "Before we start sketching, let's create a Value Trigger Chain for this scenario.
-> 
-> This captures the strategic essence:
-> - Business Goal (from mutual success - business side)
-> - Solution (this scenario/feature)
-> - User (primary target group)
-> - Driving Forces (from mental state and Trigger Map)
-> - Customer Awareness (where they start → where they end up)
-> 
-> This takes 10-15 minutes since we have the Trigger Map. It'll guide every design decision.
-> 
-> Shall we create the scenario VTC?"
-
----
-
-## Route to VTC Workshop
-
-**If user agrees:**
-
-Load and execute the VTC Workshop Router:
-`{project-root}/_bmad/wds/workflows/1-project-brief/vtc-workshop/workflow.md`
-
-**Since Trigger Map exists:** Router will likely send you to **Selection Workshop** (10-15 mins).
-
----
-
-## Leverage Context
-
-**Important:** You have rich context from scenario init! Use it:
-
-- **Business Goal:** From mutual success (business side)
-- **Solution:** The feature/scenario just defined
-- **User:** Primary target group from Trigger Map
-- **Entry Point/Mental State:** For Customer Awareness starting point
-- **Mutual Success:** For Customer Awareness ending point
-- **Driving Forces:** From Trigger Map for this user
-
-**Scenario init IS strategic discovery** - use it!
-
----
-
-## Save VTC
-
-VTC should be saved to:
-`{output_folder}/C-UX-Scenarios/[scenario-name]/vtc.yaml`
-
-Example: `docs/C-UX-Scenarios/1.1-parent-onboarding/vtc.yaml`
-
----
-
-## Confirm and Set Expectation
-
-> "Excellent! This scenario now has its own VTC.
-> 
-> As we sketch each page, we'll use this VTC to ensure:
-> - Every interaction addresses these driving forces
-> - Every message moves them through awareness
-> - Every design choice serves mutual success
-> 
-> The VTC is your strategic compass. When in doubt, check the VTC.
-> 
-> Ready to start sketching?"
-
----
-
-## If User Declines VTC
-
-**If user says:** "Let's skip the VTC and sketch"
-
-**Response:**
-> "I strongly recommend creating the VTC first. Here's why:
-> 
-> Without it, design becomes opinion-based:
-> - 'I like this button here'
-> - 'This color feels right'
-> - 'Users probably want this'
-> 
-> With VTC, design becomes strategic:
-> - 'This button triggers their wish to [driving force]'
-> - 'This message addresses their fear of [driving force]'
-> - 'This moves them from [awareness start] to [awareness end]'
-> 
-> It takes 15 minutes and saves hours of redesign.
-> 
-> Still want to skip?"
-
-**If still declines:**
-> "Okay, but I recommend creating VTC before presenting to stakeholders. You can add it anytime using:
-> `{project-root}/_bmad/wds/workflows/1-project-brief/vtc-workshop/workflow.md`"
-
-Then proceed to sketching without VTC (not ideal).
-
----
-
-## Next Step
-
-After VTC is created:
-
-**Start sketching the scenario journey!**
-
-Each sketch should:
-- Serve the VTC driving forces
-- Move user through awareness progression
-- Support shortest path to mutual success
-
----
-
-*Strategic clarity achieved - now sketch with purpose!*
-

package/src/workflows/6-asset-generation/steps-c/step-01-load-vtc-context.md

@@ -1,150 +0,0 @@
----
-name: 'step-01-load-vtc-context'
-description: 'Establish the strategic foundation by loading Value Trigger Chain context for content creation'
-nextStepFile: './step-02-awareness-strategy.md'
----
-
-# Step 1: Load VTC Context
-
-## STEP GOAL:
-
-Load the Value Trigger Chain (VTC) that defines the strategic context — WHO we are serving, WHAT motivates them, and WHERE they are in their awareness journey — so that all content decisions are anchored in strategy, not guesswork.
-
-## 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
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a strategic content analyst loading the VTC foundation
-- ✅ 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 strategic methodology for VTC loading, user brings their project knowledge
-- ✅ Maintain a thorough, investigative tone — the VTC must be correct before proceeding
-
-### Step-Specific Rules:
-
-- 🎯 Focus ONLY on loading and validating the VTC context
-- 🚫 FORBIDDEN to generate content text or apply awareness strategy in this step
-- 💬 If no VTC exists, offer to route to VTC Workshop or flag risk
-- 📋 Ensure all VTC fields are populated before proceeding
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Follow the Sequence of Instructions exactly
-- 💾 Document VTC context for traceability
-- 📖 Check for existing VTCs in project documentation before asking user
-- 🚫 FORBIDDEN to proceed without a confirmed VTC
-
-## CONTEXT BOUNDARIES:
-
-- Available context: Purpose definition from Step 0, project configuration
-- Focus: Loading and validating the correct VTC for this content
-- Limits: Do not apply the VTC yet — just load and confirm it
-- Dependencies: Purpose definition from Step 0
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Check for Existing VTCs
-
-Search project documentation for VTCs:
-- Check project documentation and scenario definitions
-- Check page specifications
-- Look for VTC references in trigger map
-
-### 2. Identify the Correct VTC
-
-Ask: **"Which VTC applies to this content section?"**
-
-- Is there an existing VTC for this page/scenario?
-- If multiple VTCs exist, which one is active here?
-- If no VTC exists, offer to create one (route to VTC Workshop) or flag risk
-
-### 3. Present and Confirm VTC
-
-Display the selected VTC:
-
-```
-Business Goal: [goal]
-Solution: [solution being designed]
-User: [persona name and description]
-Driving Forces:
-  - Wish: [positive motivator]
-  - Fear: [negative motivator]
-Customer Awareness: [START level] → [END level]
-```
-
-Ask: **"Is this the correct VTC for this content? Any adjustments needed?"**
-
-### 4. Handle Missing VTC
-
-If no VTC exists:
-- Explain that VTC is needed for strategic content
-- Ask: "Should we create a VTC now?"
-- If YES: Route to VTC Workshop
-- If NO: Flag risk and continue with limited context
-
-### 5. Document VTC Context
-
-Save the confirmed VTC reference:
-
-```yaml
-vtc_reference:
-  business_goal: "[goal text]"
-  solution: "[solution name/description]"
-  user:
-    name: "[persona name]"
-    description: "[brief persona description]"
-  driving_forces:
-    positive: "[wish/aspiration]"
-    negative: "[fear/frustration]"
-  customer_awareness:
-    start: "[awareness level where user begins]"
-    end: "[awareness level we want them to reach]"
-```
-
-### 6. Present MENU OPTIONS
-
-Display: **"Select an Option:** [C] Continue"
-
-#### Menu Handling Logic:
-
-- IF C: Save VTC context, 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)
-
-#### 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
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN C is selected and the VTC is confirmed and documented will you load {nextStepFile} to begin applying the Customer Awareness Strategy.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- VTC is identified and loaded
-- All VTC fields are populated (goal, solution, user, driving forces, awareness)
-- User confirms this is the correct VTC for this content
-- VTC is documented for traceability
-
-### ❌ SYSTEM FAILURE:
-
-- Proceeding without a confirmed VTC
-- Generating content text in this step
-- Applying awareness strategy before VTC is loaded
-- Not offering VTC Workshop route when no VTC exists
-- Not waiting for user input at menu
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.