whiteport-design-studio 0.2.2 → 0.3.0

package/src/workflows/1-project-brief/vtc-workshop/steps-c/step-03b-select-user.md

@@ -1,142 +0,0 @@
----
-name: 'step-03b-select-user'
-description: 'Choose which user/target group from Trigger Map this VTC focuses on'
-
-# File References
-nextStepFile: './step-04b-select-driving-forces.md'
-workflowFile: '../../workflow.md'
-activityWorkflowFile: '../workflow.md'
----
-
-# Step 3: Select User
-
-## STEP GOAL:
-Choose which user/target group from the Trigger Map this VTC focuses on.
-
-## 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 facilitating VTC selection from an existing Trigger Map
-- 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: Present users connected to selected goal, guide selection, handle users not in map
-- FORBIDDEN: Do not select a user without user confirmation
-- Approach: Present users from map, user selects one primary, handle edge cases, capture
-
-## EXECUTION PROTOCOLS:
-- Primary goal: User/target group selected from Trigger Map
-- Save/document outputs appropriately
-- Avoid generating content without user input
-
-## CONTEXT BOUNDARIES:
-- Available context: Trigger Map and selected business goal from steps 1-2
-- Focus: User selection
-- Limits: One primary user per VTC
-- Dependencies: Step 02b completed
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Present Available Users
-
-Show users connected to selected business goal:
-
-> "For [selected goal], your Trigger Map has these target groups:
->
-> 1. [User 1 - brief description]
->    Priority: [score]
->    Key driving forces: [top 2-3]
->
-> 2. [User 2 - brief description]
->    Priority: [score]
->    Key driving forces: [top 2-3]
->
-> Which user is primary for this [solution/scenario]?"
-
-### 2. User Selects
-
-**One primary user** for this VTC
-
-**If multiple users important:**
-> "We can create additional VTCs for other users. For THIS VTC, let's focus on one."
-
-### 3. Handle User Not in Map
-
-**User:** "None of these users match. My scenario is for [different user type]."
-
-**Options:**
-
-**A) Add to Trigger Map now:**
-1. Pause VTC workshop
-2. Add new user/target group to Trigger Map
-3. Map their driving forces
-4. Resume with new user available
-
-**B) Switch to Creation Workshop:**
-1. If this is a one-off scenario
-2. Create VTC from scratch for this user
-3. Consider adding to Trigger Map later
-
-**C) Adapt existing user:**
-1. Pick closest match
-2. Note variations in VTC
-3. Consider if map needs new segment
-
-**Recommendation:** If this represents a significant new user segment, add to Trigger Map. Future scenarios will benefit.
-
-### 4. Capture Format
-
-```yaml
-user:
-  name: "[Selected user name from map]"
-  description: "[From Trigger Map]"
-  context: "[From Trigger Map]"
-  priority: "[Priority score from map]"
-```
-
-### 5. Validation
-
-- [ ] User selection makes sense for this solution/scenario?
-- [ ] User confirms this is primary target?
-
-### N. Present MENU OPTIONS
-Display: "**Select an Option:** [C] Continue to next step"
-
-#### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
-- 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
-ONLY WHEN step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
-
----
-
-## SYSTEM SUCCESS/FAILURE METRICS
-
-### SUCCESS:
-- Available users presented from Trigger Map with priorities
-- User selected primary target
-- User not in map handled appropriately (if applicable)
-- Selection captured with priority
-
-### FAILURE:
-- Selected user without confirmation
-- Did not present available options with context
-- Skipped handling user-not-in-map scenario
-
-**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/steps-c/step-04a-positive-driving-forces.md

@@ -1,163 +0,0 @@
----
-name: 'step-04a-positive-driving-forces'
-description: 'Discover what the user WANTS to achieve - aspirations and wishes'
-
-# File References
-nextStepFile: './step-05a-negative-driving-forces.md'
-workflowFile: '../../workflow.md'
-activityWorkflowFile: '../workflow.md'
----
-
-# Step 4: Identify Positive Driving Forces
-
-## STEP GOAL:
-Discover what the user WANTS to achieve - their aspirations, wishes, and what makes them want to engage with the solution.
-
-## 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 facilitating VTC creation from scratch
-- 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: Aspirations, not just functional needs - emotionally resonant wishes
-- FORBIDDEN: Do not accept only functional needs without probing for emotional aspirations
-- Approach: Ask, probe for emotions, capture 2-3 strong wishes, validate
-
-## EXECUTION PROTOCOLS:
-- Primary goal: 2-3 positive driving forces captured
-- Save/document outputs appropriately
-- Avoid generating content without user input
-
-## CONTEXT BOUNDARIES:
-- Available context: Business goal, solution, user description from steps 1-3
-- Focus: Positive driving forces (wishes, aspirations)
-- Limits: 2-3 forces, quality over quantity
-- Dependencies: Step 03a completed
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Ask for Positive Forces
-
-> "What does [user name] WANT to achieve? What would make them feel successful?"
-
-**Probing questions:**
-- "What would 'winning' look like for them?"
-- "What outcome would they be proud of?"
-- "What would they brag about to colleagues/friends?"
-- "What capability would transform their work/life?"
-
-### 2. Apply Guidelines
-
-**Think aspirations, not just functional needs:**
-- Not: "Upload files"
-- Yes: "Wish to feel organized and in control"
-
-**What would they feel:**
-- Proud of?
-- Excited about?
-- Validated by?
-- Transformed by?
-
-**Aim for 2-3 strong wishes:**
-- Quality over quantity
-- Specific enough to inform design
-- Emotionally resonant
-
-### 3. Reference Examples
-
-**Hairdresser (Harriet):**
-- "Wish to be the local beauty authority"
-- "Wish to attract premium clients"
-- "Wish to be seen as cutting-edge"
-
-**Developer (reviewing code):**
-- "Wish to be helpful to teammates"
-- "Wish to catch critical bugs"
-- "Wish to be recognized for thorough reviews"
-
-**Small business owner:**
-- "Wish to understand finances clearly"
-- "Wish to make confident decisions"
-- "Wish to prove business is growing"
-
-### 4. Capture Format
-
-```yaml
-driving_forces:
-  positive:
-    - "Wish to [aspiration]"
-    - "Wish to [aspiration]"
-    - "Wish to [aspiration]"
-```
-
-### 5. Validation Checklist
-
-Before proceeding, confirm:
-
-- [ ] Forces feel true for this user?
-- [ ] Specific enough to inform design?
-- [ ] Emotionally resonant (not just functional)?
-- [ ] 2-3 forces captured (not too many)?
-- [ ] User agrees these motivate their target?
-
-### 6. Handle Common Issues
-
-**Issue:** Forces too generic ("want to save time")
-> "Save time doing WHAT specifically? WHY does saving that time matter to them? What would they do with that time?"
-
-**Issue:** Too many wishes listed (7+)
-> "Which 2-3 matter MOST? If we could only address three, which would transform their experience?"
-
-**Issue:** Only functional needs ("need to upload files")
-> "Why do they need that? What would having that enable them to achieve? What would they feel?"
-
-### 7. Design Hint
-
-These positive forces should inform:
-- Success messaging
-- Aspirational content
-- Celebration moments
-- Value proposition
-
-### N. Present MENU OPTIONS
-Display: "**Select an Option:** [C] Continue to next step"
-
-#### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
-- 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
-ONLY WHEN step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
-
----
-
-## SYSTEM SUCCESS/FAILURE METRICS
-
-### SUCCESS:
-- 2-3 emotionally resonant positive forces captured
-- Forces are specific enough to inform design
-- Validation checklist passed
-- User confirmed the aspirations
-
-### FAILURE:
-- Accepted only functional needs without emotional depth
-- Captured too many or too few forces
-- Generated forces without user input
-
-**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/steps-c/step-04b-select-driving-forces.md

@@ -1,154 +0,0 @@
----
-name: 'step-04b-select-driving-forces'
-description: 'Choose 2-5 most relevant driving forces from Trigger Map for this VTC'
-
-# File References
-nextStepFile: './step-05b-define-solution.md'
-workflowFile: '../../workflow.md'
-activityWorkflowFile: '../workflow.md'
----
-
-# Step 4: Select Driving Forces
-
-## STEP GOAL:
-Choose 2-5 most relevant driving forces from the Trigger Map for this VTC.
-
-## 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 facilitating VTC selection from an existing Trigger Map
-- 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: Present available forces, guide selection of 2-5, handle forces not in map
-- FORBIDDEN: Do not select forces without user confirmation; do not include all forces (lose focus)
-- Approach: Present forces with priorities, guide selection criteria, handle missing forces, capture
-
-## EXECUTION PROTOCOLS:
-- Primary goal: 2-5 relevant driving forces selected from Trigger Map
-- Save/document outputs appropriately
-- Avoid generating content without user input
-
-## CONTEXT BOUNDARIES:
-- Available context: Trigger Map, selected goal, selected user from steps 1-3
-- Focus: Driving forces selection
-- Limits: 2-5 total, mix of positive and negative
-- Dependencies: Step 03b completed
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Present Available Forces
-
-Show all driving forces for selected user:
-
-> "For [selected user], your Trigger Map shows:
->
-> **Positive (Wishes):**
-> 1. [Force 1] - Priority: [score]
-> 2. [Force 2] - Priority: [score]
-> 3. [Force 3] - Priority: [score]
->
-> **Negative (Fears/Avoid):**
-> 1. [Force 1] - Priority: [score]
-> 2. [Force 2] - Priority: [score]
-> 3. [Force 3] - Priority: [score]"
-
-### 2. Guide Selection
-
-> "Which of these driving forces does [this solution/scenario] directly address?
->
-> Pick 2-5 total (mix of positive and negative) that are most relevant here."
-
-**Selection criteria:**
-- Does THIS solution actually address this force?
-- Balance positive and negative
-- Don't include everything (lose focus)
-- Higher priority forces are good candidates
-
-### 3. Handle Driving Force Missing
-
-**User:** "None of these capture [specific driving force]. But that's critical for this scenario!"
-
-**This is valuable discovery!** Using the map reveals gaps.
-
-**Options:**
-
-**A) Add to Trigger Map now:**
-1. Pause VTC workshop
-2. Add new driving force to Trigger Map
-3. Assign priority
-4. Resume and select it
-
-**B) Add to VTC and note for map:**
-1. Use new force in this VTC
-2. Note: "Add to Trigger Map: [new force]"
-3. Update map after workshop
-
-**C) Reword existing force:**
-1. Take closest match from map
-2. Refine wording in VTC
-3. Consider updating map
-
-**Recommendation:** If you discovered this force is critical, add it to the map. Other scenarios likely need it too.
-
-### 4. Capture Format
-
-```yaml
-driving_forces:
-  positive:
-    - "[Selected wish 1 from map]"
-    - "[Selected wish 2 from map]"
-  negative:
-    - "[Selected fear 1 from map]"
-    - "[Selected fear 2 from map]"
-```
-
-### 5. Validation
-
-- [ ] Selected forces directly addressed by this solution?
-- [ ] Focused enough (not too many)?
-- [ ] Includes both positive and negative?
-- [ ] User confirms these are the right ones?
-- [ ] If adding new forces, documented for map update?
-
-### N. Present MENU OPTIONS
-Display: "**Select an Option:** [C] Continue to next step"
-
-#### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
-- 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
-ONLY WHEN step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
-
----
-
-## SYSTEM SUCCESS/FAILURE METRICS
-
-### SUCCESS:
-- Available forces presented with priorities
-- 2-5 forces selected with balance of positive and negative
-- Missing forces handled and documented (if applicable)
-- User confirmed selection
-
-### FAILURE:
-- Selected forces without user confirmation
-- Included all forces without focus
-- Did not handle missing force scenario
-
-**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/steps-c/step-05a-negative-driving-forces.md

@@ -1,195 +0,0 @@
----
-name: 'step-05a-negative-driving-forces'
-description: 'Discover what the user FEARS or wants to avoid - anxieties and frustrations'
-
-# File References
-nextStepFile: './step-06a-customer-awareness.md'
-workflowFile: '../../workflow.md'
-activityWorkflowFile: '../workflow.md'
----
-
-# Step 5: Identify Negative Driving Forces
-
-## STEP GOAL:
-Discover what the user FEARS or wants to avoid - their anxieties, frustrations, and what pushes them away from failure.
-
-## 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 facilitating VTC creation from scratch
-- 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: Anxieties and frustrations, not just functional dislikes
-- FORBIDDEN: Do not accept mild or generic fears without probing deeper
-- Approach: Ask, probe for real fears, capture 2-3 strong forces, validate, review combined forces
-
-## EXECUTION PROTOCOLS:
-- Primary goal: 2-3 negative driving forces captured and combined forces reviewed
-- Save/document outputs appropriately
-- Avoid generating content without user input
-
-## CONTEXT BOUNDARIES:
-- Available context: Business goal, solution, user, positive forces from steps 1-4
-- Focus: Negative driving forces (fears, anxieties, frustrations)
-- Limits: 2-3 forces, total 4-6 combined with positive
-- Dependencies: Step 04a completed
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Ask for Negative Forces
-
-> "What does [user name] FEAR or want to avoid? What keeps them up at night?"
-
-**Probing questions:**
-- "What are they worried about?"
-- "What would be embarrassing or costly?"
-- "What would feel like failure?"
-- "What friction do they currently experience?"
-- "What do they NOT want to happen?"
-
-### 2. Apply Guidelines
-
-**Think anxieties and frustrations:**
-- Not: "Don't want slow system"
-- Yes: "Fear of wasting hours on complex tools"
-
-**What do they fear:**
-- Losing?
-- Missing?
-- Being seen as?
-- Experiencing?
-
-**Aim for 2-3 strong fears:**
-- Often opposite side of positive forces
-- Specific and emotionally real
-- Inform risk reduction in design
-
-### 3. Reference Examples
-
-**Hairdresser (Harriet):**
-- "Fear of missing industry trends"
-- "Fear of losing clients to trendier salons"
-- "Avoid appearing outdated to clients"
-
-**Developer (reviewing code):**
-- "Fear of missing critical bugs"
-- "Fear of slowing down teammates"
-- "Avoid looking careless or rushed"
-
-**Small business owner:**
-- "Fear of making wrong financial decisions"
-- "Fear of tax compliance issues"
-- "Avoid feeling stupid about numbers"
-
-### 4. Note Connection to Positive Forces
-
-**Notice patterns:**
-- Positive: "Wish to be authority" <-> Negative: "Fear of appearing outdated"
-- Positive: "Wish to catch bugs" <-> Negative: "Fear of missing bugs"
-
-**Both sides of same coin** - this is good! Shows coherent psychology.
-
-### 5. Capture Format
-
-```yaml
-driving_forces:
-  positive:
-    - "[from previous step]"
-  negative:
-    - "Fear of [anxiety]"
-    - "Fear of [frustration]"
-    - "Avoid [problem]"
-```
-
-### 6. Validation Checklist
-
-Before proceeding, confirm:
-
-- [ ] Forces feel true for this user?
-- [ ] Specific enough to inform design?
-- [ ] Connect to positive forces (opposite sides)?
-- [ ] 2-3 forces captured (total 4-6 positive + negative)?
-- [ ] User agrees these are real anxieties?
-
-### 7. Handle Common Issues
-
-**Issue:** Forces too mild ("don't like complexity")
-> "What's the REAL fear behind that? What happens if they encounter complexity? What cost do they pay?"
-
-**Issue:** Only negative stated as positive inverse ("want to not fail")
-> "What ARE they afraid of specifically? What would failure look like?"
-
-**Issue:** Too many fears (overwhelming)
-> "Which 2-3 fears are strongest? Which would prevent them from using this solution?"
-
-### 8. Review Combined Forces
-
-**At this point, review ALL driving forces together:**
-
-```yaml
-driving_forces:
-  positive:
-    - "[wish 1]"
-    - "[wish 2]"
-    - "[wish 3]"
-  negative:
-    - "[fear 1]"
-    - "[fear 2]"
-```
-
-**Ask:** "Do these forces tell a coherent story about what drives [user name]?"
-
-If yes -> Proceed
-If no -> Refine before moving forward
-
-### 9. Design Hint
-
-These negative forces should inform:
-- Risk reduction features
-- Reassurance messaging
-- Error prevention
-- Trust signals
-- Recovery paths
-
-### N. Present MENU OPTIONS
-Display: "**Select an Option:** [C] Continue to next step"
-
-#### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
-- 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
-ONLY WHEN step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
-
----
-
-## SYSTEM SUCCESS/FAILURE METRICS
-
-### SUCCESS:
-- 2-3 emotionally real negative forces captured
-- Forces connect to positive forces (coherent psychology)
-- Combined forces reviewed and validated
-- User confirmed the anxieties
-
-### FAILURE:
-- Accepted mild or generic fears without depth
-- Skipped combined forces review
-- Generated forces without user input
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.