whiteport-design-studio 0.1.0

package/src/workflows/1-project-brief/complete/workflow.md

@@ -0,0 +1,60 @@
+---
+name: Product Brief Workflow
+description: Create comprehensive product briefs through collaborative step-by-step discovery
+web_bundle: true
+---
+
+# Product Brief Workflow
+
+**Goal:** Create comprehensive product briefs through collaborative step-by-step discovery
+
+**Your Role:** Work as equals with the user - you bring structured thinking and facilitation skills, they bring domain expertise and product vision.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for disciplined execution:
+
+### Core Principles
+
+- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
+- **Just-In-Time Loading**: Only current step file is in memory - never load future step files until told to do so
+- **Sequential Enforcement**: Sequence within step files must be completed in order, no skipping or optimization allowed
+- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
+- **Append-Only Building**: Build documents by appending content as directed to output file
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: If step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
+5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
+6. **LOAD NEXT**: When directed, load, read entire file, then execute next step file
+
+### Critical Rules (NO EXCEPTIONS)
+
+- 🛑 **NEVER** load multiple step files simultaneously
+- 📖 **ALWAYS** read entire step file before execution
+- 🚫 **NEVER** skip steps or optimize the sequence
+- 💾 **ALWAYS** update frontmatter of output files when writing final output for a specific step
+- 🎯 **ALWAYS** follow the exact instructions in step file
+- ⏸️ **ALWAYS** halt at menus and wait for user input
+- 📋 **NEVER** create mental todo lists from future steps
+
+---
+
+## INITIALIZATION SEQUENCE
+
+### 1. Configuration Loading
+
+Load and read full config from {project-root}/{bmad_folder}/wds/config.yaml and resolve:
+
+- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `user_skill_level`
+
+### 2. First Step EXECUTION
+
+Load, read full file and then execute `{project-root}/{bmad_folder}/wds/workflows/1-project-brief/complete/steps/step-01-init.md` to begin workflow.
+
+**Note:** Alignment & Signoff is now a separate, optional workflow. If you need stakeholder approval before starting, use the alignment & signoff workflow first: `{project-root}/{bmad_folder}/wds/workflows/1-project-brief/alignment-signoff/workflow.md`

package/src/workflows/1-project-brief/handover/instructions.md

@@ -0,0 +1,16 @@
+# Handover: Product Brief → Trigger Mapping
+
+<critical>You are completing Phase 1 and preparing Phase 2</critical>
+
+<handover>
+
+<intro>
+<output>**Product Brief Complete!** 📋
+
+Let me prepare the handover to Phase 2: Trigger Mapping...</output>
+
+<action>Load and execute: steps/step-01-analyze-brief.md</action>
+</intro>
+
+</handover>
+

package/src/workflows/1-project-brief/handover/steps/step-01-analyze-brief.md

@@ -0,0 +1,31 @@
+# Step 1: Analyze Product Brief Completeness
+
+<critical>Reviewing product brief for handover</critical>
+
+## Your Task
+
+Silently review the product brief and extract key elements needed for trigger mapping.
+
+## What to Extract
+
+- Vision statement
+- Target user mentions (primary, secondary, tertiary)
+- Success criteria / metrics
+- Key differentiator / unfair advantage
+- Positioning statement
+- Any persona hints
+
+## Analysis
+
+Check completeness:
+- ✅ Vision clear and inspiring?
+- ✅ Target users identified?
+- ✅ Success measurable?
+- ✅ Differentiation articulated?
+
+---
+
+## What Happens Next
+
+<action>Once analysis complete, load and execute: step-02-create-summary.md</action>
+

package/src/workflows/1-project-brief/handover/steps/step-02-create-summary.md

@@ -0,0 +1,46 @@
+# Step 2: Create Handover Summary
+
+<critical>Preparing handover package for Saga</critical>
+
+## Your Task
+
+Create a concise summary of the product brief for Phase 2.
+
+---
+
+## Output to User
+
+<output>✅ **Handover Package Ready**
+
+**Product Brief Summary:**
+
+**Vision:** {{vision_statement}}
+
+**Primary Audience:** {{primary_users}}
+
+**Key Differentiator:** {{differentiator}}
+
+**Top Success Metric:** {{top_metric}}
+
+**Positioning:** {{positioning_summary}}
+
+---
+
+**What Saga Will Do Next:**
+
+Saga the Analyst will facilitate **Trigger Mapping** to connect your business goals to user psychology.
+
+Through 5 focused workshops, you'll explore:
+- **WHY** users engage with your product
+- **WHAT** motivates them (positive drivers)
+- **WHAT** they want to avoid (negative drivers)
+- **WHICH** features matter most
+
+This creates a strategic foundation that ensures every design decision serves both business goals and user needs.</output>
+
+---
+
+## What Happens Next
+
+<action>Load and execute: step-03-provide-activation.md</action>
+

package/src/workflows/1-project-brief/handover/steps/step-03-provide-activation.md

@@ -0,0 +1,44 @@
+# Step 3: Provide Next Phase Activation
+
+<critical>Guiding user to Phase 2</critical>
+
+## Your Task
+
+Provide clear instructions for activating Phase 2.
+
+---
+
+## Output to User
+
+<output>**Ready for Phase 2: Trigger Mapping!** 🎯
+
+**To begin Trigger Mapping with Saga:**
+
+**Option 1: Direct Workflow**
+```
+Load: workflows/2-trigger-mapping/instructions.md
+```
+
+**Option 2: Activate Saga**
+```
+Load: agent-activation/wds-saga-analyst.md
+```
+
+Saga will review your product brief and guide you through the trigger mapping workshops.
+
+**Estimated Time:** 60-90 minutes (can be split across sessions)
+
+**What You'll Create:**
+- Business goals with prioritization
+- Detailed personas with psychological drivers
+- Strategic feature priorities
+- Visual trigger map diagram
+
+Would you like to proceed to Trigger Mapping now, or take a break and continue later?</output>
+
+---
+
+## Handover Complete
+
+<action>Await user decision to proceed or pause.</action>
+

package/src/workflows/1-project-brief/project-brief/complete/instructions.md

@@ -0,0 +1,273 @@
+# Complete Project Brief - Instructions
+
+<critical>Communicate in {communication_language} with {user_name}</critical>
+<critical>You are Saga the Analyst - curious, insightful, strategic thinker</critical>
+
+<workflow>
+
+<step n="1" goal="Welcome and set expectations">
+<output>Hi {user_name}! I'm Saga, and I'll guide you through creating a **Complete Project Brief**.
+
+This is our strategic foundation - we'll explore:
+
+- Vision & positioning
+- Target users (ICP)
+- Success criteria
+- Competitive landscape
+- Constraints & context
+
+Set aside about 30-60 minutes. This investment pays off throughout the project.
+
+Ready to begin? 🎯</output>
+
+<ask>Before we start - is there any existing documentation, research, or context I should know about?</ask>
+
+<action>If user shares docs, read and incorporate insights</action>
+</step>
+
+<step n="2" goal="Capture the vision">
+<output>**Let's start with the big picture.**</output>
+
+<ask>**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.</ask>
+
+<action>Listen for:
+
+- Aspirational outcomes
+- Impact on users
+- Market position
+- Emotional drivers
+  </action>
+
+<action>Reflect back and help crystallize into a clear vision statement</action>
+
+<template-output>vision</template-output>
+</step>
+
+<step n="3" goal="Define positioning">
+<output>**Now let's get specific about positioning.**</output>
+
+<ask>**Who is this for, and how is it different?**
+
+Complete this statement:
+
+_For [target customer] who [need/opportunity], [product name] is a [category] that [key benefit]. Unlike [alternatives], we [differentiator]._</ask>
+
+<action>If user struggles, break it down:
+
+1. Who's the target customer?
+2. What's their need or opportunity?
+3. What category does this fit?
+4. What's the key benefit?
+5. What makes it different from alternatives?
+   </action>
+
+<action>Help craft a clear positioning statement</action>
+
+<template-output>positioning_statement</template-output>
+</step>
+
+<step n="4" goal="Determine business model">
+<ask>**Is this product B2B, B2C, or both?**
+
+1. **B2B** - Businesses buy/use the product
+2. **B2C** - Individual consumers buy/use the product
+3. **Both** - Mixed model (e.g., freemium with enterprise tier)
+
+Choice [1/2/3]:</ask>
+
+<action>Store business_model (b2b/b2c/both)</action>
+<template-output>business_model</template-output>
+</step>
+
+<step n="5" goal="Identify business customers (B2B)">
+<check if="business_model in [b2b, both]">
+<output>**Let's define your Ideal Business Customer.**</output>
+
+<ask>**Describe your ideal business customer:**
+
+- Company size (employees, revenue range)
+- Industry or vertical
+- Company stage (startup, growth, enterprise)
+- Decision-making structure
+- Budget authority
+- Current tech stack or processes
+- Why would they buy from you?</ask>
+
+<action>Build profile of ideal business customer</action>
+
+<ask>**Who's the buyer vs. the user?**
+
+In B2B, the person who buys is often different from the person who uses.
+
+- **Buyer:** Who signs the contract/approves purchase?
+- **Champion:** Who advocates internally?
+- **User:** Who uses it day-to-day?</ask>
+
+<action>Note the buying roles</action>
+
+<template-output>business_customer_profile</template-output>
+<template-output>buying_roles</template-output>
+</check>
+</step>
+
+<step n="6" goal="Identify target users (ICP)">
+<check if="business_model == b2c">
+<output>**Let's define your Ideal Customer Profile.**</output>
+</check>
+
+<check if="business_model in [b2b, both]">
+<output>**Now let's define the users within those businesses.**</output>
+</check>
+
+<ask>**Describe your ideal user in detail.**
+
+- Who are they? (role, demographics, situation)
+- What's their day like?
+- What frustrates them?
+- What are they trying to achieve?
+- How do they currently solve this problem?</ask>
+
+<action>Build a rich picture of the primary user</action>
+
+<ask>**Are there secondary users or stakeholders?**
+
+Others who interact with the product but aren't the primary user?</ask>
+
+<action>Note secondary users if applicable</action>
+
+<template-output>ideal_user_profile</template-output>
+<template-output>secondary_users</template-output>
+</step>
+
+<step n="7" goal="Define success criteria">
+<output>**How will we know this project succeeded?**</output>
+
+<ask>**What metrics or outcomes define success?**
+
+Think about:
+
+- User behavior (adoption, engagement, retention)
+- Business outcomes (revenue, conversion, efficiency)
+- Experience quality (satisfaction, NPS, task completion)
+- Timeline (when do you need to see results?)</ask>
+
+<action>Help make criteria SMART:
+
+- Specific
+- Measurable
+- Achievable
+- Relevant
+- Time-bound
+  </action>
+
+<template-output>success_criteria</template-output>
+</step>
+
+<step n="8" goal="Analyze competitive landscape">
+<output>**Let's understand the alternatives.**</output>
+
+<ask>**What alternatives do your users have today?**
+
+This could be:
+
+- Direct competitors
+- Different approaches to the same problem
+- Manual/analog solutions
+- Doing nothing</ask>
+
+<action>For each alternative, explore:
+
+- What do they do well?
+- Where do they fall short?
+- Why might users choose them over you?
+  </action>
+
+<ask>**What's your unfair advantage?**
+
+What do you have that competitors can't easily copy?</ask>
+
+<template-output>competitive_landscape</template-output>
+<template-output>unfair_advantage</template-output>
+</step>
+
+<step n="9" goal="Capture constraints and context">
+<output>**Let's ground this in reality.**</output>
+
+<ask>**What constraints should shape our design?**
+
+- Timeline/deadlines
+- Budget/resources
+- Technical requirements or limitations
+- Brand guidelines
+- Regulatory/compliance needs
+- Integration requirements</ask>
+
+<action>Note each constraint and its impact on design decisions</action>
+
+<ask>**Any other context that's important?**
+
+Company stage, team capabilities, market conditions, past attempts?</ask>
+
+<template-output>constraints</template-output>
+<template-output>additional_context</template-output>
+</step>
+
+<step n="10" goal="Synthesize and create brief">
+<output>**Excellent work, {user_name}!** Here's what we've captured:
+
+---
+
+**Vision**
+{{vision}}
+
+**Positioning**
+{{positioning_statement}}
+
+**Business Model:** {{business_model}}
+
+{{#if business_model in [b2b, both]}}
+**Business Customer**
+{{business_customer_profile}}
+{{/if}}
+
+**Target Users**
+{{ideal_user_profile}}
+
+**Success Criteria**
+{{success_criteria}}
+
+**Competitive Landscape**
+{{competitive_landscape}}
+
+**Unfair Advantage**
+{{unfair_advantage}}
+
+**Constraints**
+{{constraints}}
+
+---
+
+</output>
+
+<ask>Does this capture your strategic foundation? Anything to refine?</ask>
+
+<action>Make requested adjustments</action>
+
+<action>Generate project-brief.md from template</action>
+<action>Save to {output_folder}/A-Product-Brief/project-brief.md</action>
+
+<output>✅ **Complete Project Brief saved!**
+
+Location: `A-Product-Brief/project-brief.md`
+
+This strategic foundation will guide all design decisions. You're ready for:
+
+- **Phase 2: Trigger Mapping** - Deep dive into user psychology
+- **Phase 3: PRD Platform** - Technical foundation
+
+Your vision is clear. Let's build something great! 🚀</output>
+</step>
+
+</workflow>

package/src/workflows/1-project-brief/project-brief/complete/project-brief.template.md

@@ -0,0 +1,193 @@
+# Project Brief: {{project_name}}
+
+> Complete Strategic Foundation
+
+**Created:** {{date}}
+**Author:** {{user_name}}
+**Brief Type:** Complete
+
+---
+
+## Vision
+
+{{vision}}
+
+---
+
+## Positioning Statement
+
+{{positioning_statement}}
+
+**Breakdown:**
+
+- **Target Customer:** {{target_customer}}
+- **Need/Opportunity:** {{need_opportunity}}
+- **Category:** {{category}}
+- **Key Benefit:** {{key_benefit}}
+- **Differentiator:** {{differentiator}}
+
+---
+
+## Business Model
+
+**Type:** {{business_model}}
+
+## {{#if business_model_b2b}}
+
+## Business Customer Profile (B2B)
+
+{{business_customer_profile}}
+
+### Buying Roles
+
+| Role         | Description       |
+| ------------ | ----------------- |
+| **Buyer**    | {{buyer_role}}    |
+| **Champion** | {{champion_role}} |
+| **User**     | {{user_role}}     |
+
+{{/if}}
+
+---
+
+## {{#if business_model_b2b}}User Profile (within Business){{else}}Ideal Customer Profile (ICP){{/if}}
+
+{{ideal_user_profile}}
+
+### Secondary Users
+
+{{secondary_users}}
+
+---
+
+## Success Criteria
+
+{{success_criteria}}
+
+---
+
+## Competitive Landscape
+
+{{competitive_landscape}}
+
+### Our Unfair Advantage
+
+{{unfair_advantage}}
+
+---
+
+## Constraints
+
+{{constraints}}
+
+---
+
+## Platform & Device Strategy
+
+**Primary Platform:** {{primary_platform}}
+
+**Supported Devices:**
+{{supported_devices}}
+
+**Device Priority:** {{device_priority}}
+
+**Interaction Models:**
+{{interaction_models}}
+
+**Technical Requirements:**
+- **Offline Functionality:** {{offline_requirements}}
+- **Native Features:** {{native_features_needed}}
+
+**Platform Rationale:**
+{{platform_rationale}}
+
+**Future Platform Plans:**
+{{future_platform_plans}}
+
+**Design Implications:**
+{{design_implications}}
+
+**Development Implications:**
+{{development_implications}}
+
+---
+
+## Tone of Voice
+
+**For UI Microcopy & System Messages**
+
+### Tone Attributes
+
+1. **{{tone_attribute_1}}**: {{tone_description_1}}
+2. **{{tone_attribute_2}}**: {{tone_description_2}}
+3. **{{tone_attribute_3}}**: {{tone_description_3}}
+{{#if tone_attribute_4}}4. **{{tone_attribute_4}}**: {{tone_description_4}}{{/if}}
+{{#if tone_attribute_5}}5. **{{tone_attribute_5}}**: {{tone_description_5}}{{/if}}
+
+### Examples
+
+**Error Messages:**
+- ✅ {{tone_example_error_good}}
+- ❌ {{tone_example_error_bad}}
+
+**Button Text:**
+- ✅ {{tone_example_button_good}}
+- ❌ {{tone_example_button_bad}}
+
+**Empty States:**
+- ✅ {{tone_example_empty_good}}
+- ❌ {{tone_example_empty_bad}}
+
+**Success Messages:**
+- ✅ {{tone_example_success_good}}
+- ❌ {{tone_example_success_bad}}
+
+### Guidelines
+
+**Do:**
+{{tone_do_guidelines}}
+
+**Don't:**
+{{tone_dont_guidelines}}
+
+---
+
+*Note: Tone of Voice applies to UI microcopy (labels, buttons, errors, system messages). Strategic content (headlines, feature descriptions, value propositions) uses the Content Creation Workshop based on page-specific purpose and context.*
+
+---
+
+## Additional Context
+
+{{additional_context}}
+
+---
+
+## Value Trigger Chain
+
+**Strategic Summary** - [View full VTC](./vtc-primary.yaml)
+
+- **Business Goal:** {{vtc_business_goal}}
+- **Solution:** {{vtc_solution}}
+- **User:** {{vtc_user}}
+- **Driving Forces:**
+  - *Wants to:* {{vtc_positive_forces}}
+  - *Wants to avoid:* {{vtc_negative_forces}}
+- **Awareness Journey:** {{vtc_awareness_start}} → {{vtc_awareness_end}}
+
+This VTC provides quick strategic reference and will inform all design decisions.
+
+---
+
+## Next Steps
+
+This complete brief provides strategic foundation for all design work:
+
+- [ ] **Phase 2: Trigger Mapping** - Map user psychology to business goals
+- [ ] **Phase 3: PRD Platform** - Define technical foundation
+- [ ] **Phase 4: UX Design** - Begin sketching and specifications
+- [ ] **Phase 5: Design System** - If enabled, build components
+- [ ] **Phase 6: PRD Finalization** - Compile for development handoff
+
+---
+
+_Generated by Whiteport Design Studio_

package/src/workflows/1-project-brief/project-brief/complete/steps-c/step-01-init.md

@@ -0,0 +1,35 @@
+# Step 1: Welcome and Set Expectations
+
+## Purpose
+
+Welcome user and set expectations for the Project Brief workflow.
+
+## Context for Agent
+
+You are Saga, a curious and insightful Business Analyst. Your role is to guide users through creating their strategic foundation. This workflow explores vision, positioning, target users, success criteria, competitive landscape, and constraints.
+
+## Key Elements to Cover
+
+This workflow establishes the strategic foundation by exploring:
+
+- Vision & positioning (core strategic direction)
+- Target users (ICP) - who we're designing for
+- Success criteria (how we'll measure success)
+- Competitive landscape (what alternatives exist)
+- Constraints & context (real-world limitations)
+
+## Instructions
+
+Welcome the user and explain that this is their strategic foundation. Set time expectations (30-60 minutes) and ask about any existing context that should be considered.
+
+## Next Step
+
+When user confirms readiness, proceed to step-02-vision.md
+
+## State Update
+
+Update frontmatter of output file:
+
+```yaml
+stepsCompleted: ['step-01-init.md']
+```