whiteport-design-studio 0.2.2 → 0.3.0

package/src/workflows/0-project-setup/templates/folder-guides/00-progress.template.md

@@ -1,56 +0,0 @@
-# Design Process Log
-
-> Track progress, decisions, and agent handoffs across the design process.
-
-**Project:** {{project_name}}
-**Started:** {{date}}
-**Method:** Whiteport Design Studio (WDS)
-
----
-
-## About This Folder
-
-The `_progress` folder is the memory of your design process. It tracks what happened, when, and why — so any agent or human can pick up where you left off.
-
-**Contents:**
-- **This file** — Design log with phase progress and key decisions
-- **agent-dialogs/** — Conversation records between agents and humans, persisted across sessions
-- **wds-project-outline.yaml** — Project configuration from Phase 0 setup
-
-**Learn more:** WDS Course Module 02 (Installation & Setup), Lesson 4: WDS Initialization
-
----
-
-## For Agents
-
-**Your dialog files go in `agent-dialogs/`.** Name them: `YYYY-MM-DD-agent-topic.md`
-
-When you complete a phase milestone, add an entry to the Progress section below. When the user makes a key decision, record it in Key Decisions.
-
-**Do not modify `wds-project-outline.yaml`** — it is the source of truth for project configuration.
-
----
-
-## Progress
-
-### {{date}} — Project Initialized (Phase 0)
-
-**Configuration:**
-- Type: {{greenfield/brownfield}}
-- Complexity: {{product_complexity}}
-- Tech Stack: {{tech_stack}}
-- Brief Level: {{brief_level}}
-
-**Next:** Phase 1 — Product Brief
-
----
-
-## Key Decisions
-
-| Date | Decision | Context | Made By |
-|------|----------|---------|---------|
-| {{date}} | Project initialized | Phase 0 setup | {{agent}} |
-
----
-
-_Updated using Whiteport Design Studio (WDS) methodology_

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

@@ -1,120 +0,0 @@
----
-name: 'step-04-create-vtc'
-description: 'Create a simplified Value Trigger Chain to crystallize strategic thinking early'
-
-# File References
-nextStepFile: './step-05-business-model.md'
-workflowFile: '../workflow.md'
----
-
-# Step 4: Create Value Trigger Chain
-
-## STEP GOAL:
-Create a simplified Value Trigger Chain (VTC) to crystallize strategic thinking early and guide all subsequent discovery. The VTC serves as a strategic benchmark — capturing Business Goal, Solution, User, Driving Forces, and Customer Awareness.
-
-## 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 Saga, a strategic facilitator helping create VTC based on available context
-- ✅ 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 strategic thinking, user brings domain expertise
-- ✅ Maintain focused, strategic tone throughout
-
-### Step-Specific Rules:
-- 🎯 Focus on creating VTC leveraging existing Vision and Positioning context
-- 🚫 FORBIDDEN to start from zero — use the strategic work already completed
-- 💬 Approach: Leverage existing context, fill gaps collaboratively
-- 📋 VTC is saved separately, NOT added to brief document yet (that happens at Step 12)
-
-## EXECUTION PROTOCOLS:
-- 🎯 Produce a complete VTC (Business Goal, Solution, User, Driving Forces, Customer Awareness)
-- 💾 Save VTC to `{output_folder}/A-Product-Brief/vtc-primary.yaml`
-- 📖 Route to VTC Workshop at `../vtc-workshop/workflow.md` if user agrees
-- 🚫 Avoid starting from zero — leverage Vision and Positioning
-
-## CONTEXT BOUNDARIES:
-- Available context: Vision from Step 2, Positioning from Step 3
-- Focus: VTC creation as strategic benchmark
-- Limits: At this stage, estimates are fine — VTC will be refined later
-- Dependencies: Steps 1-3 completed
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Explain VTC to User
-Explain VTC components and purpose:
-- Business Goal — What measurable outcome we want
-- Solution — What we are building
-- User — Who the primary user is
-- Driving Forces — What motivates them (positive + negative)
-- Customer Awareness — Where they start and where we move them
-
-Explain this takes 20-30 minutes and is incredibly valuable for strategic clarity. Ask: "Shall we create the VTC now?"
-
-### 2. Route to VTC Workshop
-**If user agrees:** Load and execute the VTC Workshop Router at `../vtc-workshop/workflow.md`. Since Product Brief stage typically has NO Trigger Map yet, the router will likely send to the Creation Workshop.
-
-### 3. Leverage Vision and Positioning Context
-Use existing strategic work:
-- Solution: From vision (what we are 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)
-
-### 4. Save VTC
-Save to `{output_folder}/A-Product-Brief/vtc-primary.yaml`. VTC is saved but NOT yet added to brief document — that happens during final synthesis.
-
-### 5. Confirm Completion
-Explain that VTC will serve as strategic benchmark. As discovery continues, we use this VTC to ensure everything aligns. If contradictions arise, either VTC needs adjustment or the discovery finding does not serve strategy.
-
-### 6. Agent Dialog Update
-**Mandatory:** Append to `dialog/decisions.md` if key decisions were made.
-
-Record: Value/Transformation/Cost framework decisions, how value and transformation connect, key insights about user journey.
-
-Mark Step 4 complete in `dialog/progress-tracker.md` progress tracker.
-
-### 7. If User Declines VTC
-If user says "Let's skip the VTC for now," explain they can create it later using `_bmad/wds/workflows/1-project-brief/vtc-workshop/workflow.md`. Recommend creating it before pitching to stakeholders or starting Phase 4. Then proceed to next step.
-
-### 8. Present MENU OPTIONS
-Display: "**Select an Option:** [C] Continue to Business Model"
-
-#### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
-- IF M: Return to {workflowFile}
-- 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 VTC is created (or user declines) and completion is confirmed will you then load and read fully `{nextStepFile}`.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-- VTC created with all components or user explicitly declined
-- Existing Vision and Positioning context leveraged (not starting from zero)
-- VTC saved to correct output location
-- User understands VTC purpose as strategic benchmark
-- Agent dialog updated
-
-### ❌ SYSTEM FAILURE:
-- Started VTC from zero without using existing context
-- Generated VTC components without user input
-- Did not save VTC to correct location
-- Skipped confirmation with user
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

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

@@ -1,181 +0,0 @@
----
-name: 'step-11a-create-vtc'
-description: 'Create simplified Value Trigger Chain for strategic summary'
-
-# File References
-nextStepFile: './step-12-synthesize.md'
-workflowFile: '../workflow.md'
-activityWorkflowFile: '../workflow.md'
----
-
-# Step 11A: Create Value Trigger Chain
-
-## STEP GOAL:
-Create a simplified Value Trigger Chain (VTC) to capture strategic essence for stakeholder communication.
-
-## 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 helping distill the Product Brief into a focused VTC
-- 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: VTC creation from Product Brief context - Business Goal, Solution, User, Driving Forces, Customer Awareness
-- FORBIDDEN: Do not start from zero - use the strategic work already completed
-- Approach: Leverage existing Product Brief context, route to VTC Workshop
-
-## EXECUTION PROTOCOLS:
-- Primary goal: VTC created and added to Product Brief
-- Save/document outputs appropriately
-- Avoid generating content without user input
-
-## CONTEXT BOUNDARIES:
-- Available context: Complete Product Brief content from steps 1-11
-- Focus: Strategic VTC summarizing the product's value chain
-- Limits: This is a simplified strategic summary, not detailed scenario VTCs
-- Dependencies: Steps 1-11 completed
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 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:
-`../vtc-workshop/workflow.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!"
-
-### 7. If User Declines VTC
-
-**If user says:** "Let's skip the VTC for now"
-
-**Response:**
-> "No problem! You can create a VTC later using:
-> `../vtc-workshop/workflow.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.
-
-### 8. Agent Dialog Update
-**Mandatory:** Append to `dialog/decisions.md` if key decisions were made.
-
-**Record:**
-- VTC framework decisions
-- Value/Transformation/Cost mapping
-- Strategic insights from framework
-
-**Then:** Mark Step 11a complete in `dialog/progress-tracker.md` progress tracker
-
-### 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:
-- VTC created or user explicitly deferred
-- Product Brief context leveraged (not starting from zero)
-- VTC saved to correct location
-- VTC summary added to Product Brief document
-- User confirmed
-
-### FAILURE:
-- Started VTC from zero ignoring existing Product Brief context
-- Skipped VTC without offering
-- Generated VTC without user collaboration
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/workflows/1-project-brief/templates/vtc-template.yaml

@@ -1,210 +0,0 @@
-# Value Trigger Chain Template
-# See: docs/method/value-trigger-chain-guide.md
-
-vtc:
-  # ==========================================
-  # BUSINESS GOAL
-  # What measurable outcome do we want?
-  # ==========================================
-  business_goal:
-    primary: "500 newsletter signups in Q1"
-    secondary: "" # Optional: Secondary goal this also supports
-
-  # ==========================================
-  # SOLUTION
-  # What are we building to achieve this goal?
-  # ==========================================
-  solution: "Landing page with trend insights lead magnet"
-
-  # ==========================================
-  # USER
-  # Who is the primary user for this solution?
-  # ==========================================
-  user:
-    name: "Harriet"
-    description: "Hairdresser, ambitious, small-town salon owner"
-    context: "Late evening, researching industry trends online"
-    current_state: "Wants to stay ahead of local competitors"
-    priority: "" # Optional: Priority score from Trigger Map
-
-  # ==========================================
-  # DRIVING FORCES
-  # What motivates this user?
-  # ==========================================
-  driving_forces:
-    # Positive: Wishes, aspirations, what they want to achieve
-    positive:
-      - "Wish to be the local beauty authority"
-      - "Wish to attract premium clients"
-      - "Wish to be seen as cutting-edge"
-
-    # Negative: Fears, frustrations, what they want to avoid
-    negative:
-      - "Fear of missing industry trends"
-      - "Fear of losing clients to trendier salons"
-      - "Avoid appearing outdated"
-
-  # ==========================================
-  # CUSTOMER AWARENESS
-  # Where user starts → where we move them
-  # ==========================================
-  customer_awareness:
-    start: "Problem Aware" # Knows: Need to stay current
-    end: "Product Aware" # Knows: Our newsletter helps
-
-  # Awareness stages:
-  # - Unaware: Doesn't know problem exists
-  # - Problem Aware: Knows problem, doesn't know solutions
-  # - Solution Aware: Knows solutions exist, doesn't know yours
-  # - Product Aware: Knows your solution exists
-  # - Most Aware: Has used, loved, advocates
-
-# ==========================================
-# METADATA (Optional but recommended)
-# ==========================================
-metadata:
-  # Creation information
-  created_date: "2025-12-31"
-  created_by: "Product Team"
-  version: "1.0"
-
-  # Source tracking
-  source: "creation" # "creation" (from scratch) or "trigger_map" (extracted)
-  trigger_map_path: "" # If extracted from Trigger Map, path to source
-
-  # Priorities (if from Trigger Map)
-  business_goal_priority: "" # e.g., "1" or "High"
-  user_priority: "" # e.g., "1" or "High"
-
-  # Usage context
-  purpose: "product_pitch" # "product_pitch", "scenario", "prototype", etc.
-  phase: "Phase 1" # WDS phase where this VTC is used
-
-  # Related files
-  related_documents:
-    - "" # Path to Product Brief, Scenario, etc.
-
-# ==========================================
-# NOTES & RATIONALE
-# ==========================================
-notes: |
-  Creation context:
-  - Why this VTC was created
-  - Key decisions made during workshop
-  - Important insights captured
-
-  Selection rationale (if from Trigger Map):
-  - Why these specific driving forces were chosen
-  - Why this user/goal combination
-  - Any refinements made from original map
-
-  Usage guidance:
-  - How this VTC should inform design
-  - What questions it should answer
-  - Where it applies
-
-  ALPHA FEEDBACK (please document):
-  - Actual workshop duration: [X minutes]
-  - Steps that were unclear: [which steps?]
-  - What was missing: [gaps?]
-  - What worked well: [successes?]
-  - Suggestions: [improvements?]
-
-# ==========================================
-# REFINEMENTS (Optional)
-# Track changes from Trigger Map if applicable
-# ==========================================
-refinements:
-  - type: "" # "added", "modified", "clarified"
-    element: "" # What was changed
-    original: "" # Original from Trigger Map
-    updated: "" # Updated version in this VTC
-    reason: "" # Why the change was made
-
-# ==========================================
-# VALIDATION CHECKLIST
-# ==========================================
-validation:
-  coherence: false # Does this tell a coherent story?
-  actionable: false # Can designers make decisions from this?
-  specific: false # Are driving forces specific enough?
-  realistic: false # Does awareness progression make sense?
-  measurable: false # Is business goal measurable?
-  focused: false # Is this focused (not trying to serve everyone)?
-
-# ==========================================
-# EXAMPLE APPLICATIONS
-# How this VTC informs design decisions
-# ==========================================
-applications:
-  # Examples of how this VTC guides design
-  # Remove this section in actual VTC files
-
-  content_examples:
-    - element: "Hero headline"
-      vtc_reasoning: "Addresses 'fear of missing trends' directly"
-      result: "'Never Miss a Trend: Weekly Insights for Ambitious Stylists'"
-
-    - element: "CTA button"
-      vtc_reasoning: "Aspirational language matching 'wish to be authority'"
-      result: "'Join the Authority Circle' (not just 'Subscribe')"
-
-  design_examples:
-    - element: "Visual style"
-      vtc_reasoning: "User wants to be seen as cutting-edge"
-      result: "Modern, premium aesthetic (not traditional salon look)"
-
-    - element: "Social proof"
-      vtc_reasoning: "Reduces 'fear of appearing outdated'"
-      result: "Testimonials from successful salon owners"
-
-# ==========================================
-# USAGE INSTRUCTIONS
-# ==========================================
-
-# HOW TO USE THIS TEMPLATE:
-#
-# 1. Copy this file to your project location:
-#    - Product Pitch: docs/A-Product-Brief/vtc-primary.yaml
-#    - Scenario: docs/C-UX-Scenarios/[scenario-name]/vtc.yaml
-#
-# 2. Fill in all sections with your VTC data
-#
-# 3. Remove example applications section (it's just for reference)
-#
-# 4. Complete validation checklist - all should be true
-#
-# 5. Use this VTC to inform ALL design decisions for this scope:
-#    - Content creation (what to say, how to say it)
-#    - Interaction design (what actions to enable)
-#    - Visual design (what aesthetic matches user psychology)
-#    - Microcopy (what tone builds confidence)
-#
-# 6. When making design decisions, ask:
-#    "Does this serve the business goal by triggering these driving forces
-#     while moving the user forward in customer awareness?"
-#
-#    If yes → Good design decision
-#    If no → Reconsider
-
-# ==========================================
-# MAINTENANCE
-# ==========================================
-
-# WHEN TO UPDATE VTC:
-# - Business goal changes
-# - Learn new insights about user
-# - Discover additional driving forces
-# - Awareness progression needs adjustment
-# - Solution scope changes
-#
-# VERSION CONTROL:
-# - Keep old versions (vtc-v1.yaml, vtc-v2.yaml)
-# - Document what changed and why
-# - Update related documents (scenarios, pitch, etc.)
-#
-# CONSISTENCY:
-# - If extracted from Trigger Map, periodically check alignment
-# - If Trigger Map updates significantly, review VTC
-# - Multiple VTCs from same map should be consistent in priorities
-