whiteport-design-studio 0.2.2 → 0.3.0

package/src/workflows/_agent-dialogs/project-analysis/analysis-types/unknown-structure-response.md

@@ -1,216 +0,0 @@
-# Unknown Structure Analysis
-
-**You were routed here because**: Docs folder exists but doesn't match WDS v6 or WPS2C v4 patterns  
-**Analysis type**: Complete project scan with structure analysis
-
----
-
-## What to Do
-
-Analyze the custom documentation structure and provide complete project assessment.
-
----
-
-## 1. Scan Attached Repos
-
-**Check ALL repos attached to IDE** (exclude WDS, BMAD, WPS2C):
-
-For each project repo:
-
-- **Project name**: Extract from package.json, folder name, or README
-- **Tech stack**: Check package.json dependencies, frameworks
-- **Documentation structure**: Analyze docs/ folder pattern
-- **Implementation status**: Check code directories
-
----
-
-## 2. Analyze Custom Docs Structure
-
-**Examine docs/ folder**:
-
-- **Pattern**: Numbered? Lettered? Date-based? Topic-based?
-- **Content**: What types of files? (specs, designs, planning)
-- **Completeness**: How much documentation exists?
-- **Methodology hints**: Can you identify what system they're using?
-
-**Common patterns**:
-
-- Agile/Scrum: sprints/, backlog/, retrospectives/
-- Feature-based: features/, requirements/, designs/
-- Date-based: 2024-01-project-plan/
-- Custom: Unique naming convention
-
----
-
-## 3. Map to WDS Phases (If Possible)
-
-**Try to map existing docs to WDS phases**:
-
-| Custom Folder  | Possible WDS Phase                     |
-| -------------- | -------------------------------------- |
-| requirements/  | Phase 1: Project Brief or Phase 3: PRD |
-| user-research/ | Phase 2: Trigger Mapping               |
-| wireframes/    | Phase 4: UX Design                     |
-| design-system/ | Phase 5: Design System                 |
-| handoff/       | Phase 6: Design Deliveries             |
-
----
-
-## 4. Assess Your Domain
-
-**Filter by YOUR agent's domain**:
-
-- **Saga**: Look for business strategy, user research, requirements
-- **Freya**: Look for design files, prototypes, UI specs, wireframes
-- **Idunn**: Look for technical specs, architecture, API docs
-
----
-
-## 5. Present Complete Status Report
-
-**Format**:
-
-```
-🎨 [Your Agent Name]
-
-Complete Project Analysis:
-
-📁 Project: [Name]
-🔧 Tech Stack: [List]
-📂 Structure: Custom documentation methodology
-
-Documentation Structure Detected:
-├─ docs/
-│   ├─ [folder 1]/ - [X] files
-│   ├─ [folder 2]/ - [Y] files
-│   └─ [folder 3]/ - [Z] files
-└─ Pattern: [Describe: topic-based, feature-based, etc.]
-
-Mapping to WDS Phases:
-├─ Phase 1 (Project Brief): [Folder name or "Not found"]
-├─ Phase 2 (Trigger Map): [Folder name or "Not found"]
-├─ Phase 4 (UX Design): [Folder name or "Not found"]
-└─ [Other relevant phases]
-
-Content Analysis (Your Domain):
-[Focus on content relevant to YOUR agent]
-├─ [What exists in your domain]
-├─ [Quality/completeness assessment]
-└─ [What's missing]
-
-Implementation Status:
-├─ Code: [X] files in [directory]
-├─ Features: [List implemented features]
-└─ Alignment: [Does code match docs?]
-
-💡 Observation:
-This project uses a [custom/agile/feature-based] methodology instead of
-standard WDS structure. [Your assessment of effectiveness]
-
-Recommended Options:
-
-1. **Continue with current structure**
-   - I'll adapt to your methodology
-   - You keep your current organization
-   - Tell me more about your approach
-
-2. **Migrate to WDS v6 structure**
-   - Modern numbered phases (1-8)
-   - Better agent integration
-   - Systematic workflow
-   - Saga WDS Analyst Agent can help migrate
-
-3. **Hybrid approach**
-   - Keep your structure
-   - Add WDS project outline for agent tracking
-   - Best of both worlds
-
-Which approach would you prefer?
-
-[If they choose "continue", ask]:
-Please describe your documentation structure so I can adapt:
-- What do your folders represent?
-- What's your workflow?
-- What are you trying to achieve?
-```
-
----
-
-## 6. Example Output (Freya analyzing Agile project)
-
-```
-🎨 Freya WDS Designer Agent
-
-Complete Project Analysis:
-
-📁 Project: E-commerce Platform
-🔧 Tech Stack: Vue 3, Nuxt, TypeScript, Vuetify
-📂 Structure: Agile sprint-based methodology
-
-Documentation Structure Detected:
-├─ docs/
-│   ├─ sprint-01/ - 8 user stories
-│   ├─ sprint-02/ - 12 user stories
-│   ├─ backlog/ - 24 items
-│   ├─ design-assets/ - 15 Figma links
-│   └─ api-specs/ - 6 OpenAPI files
-└─ Pattern: Sprint-based Agile workflow
-
-Mapping to WDS Phases:
-├─ Phase 1 (Project Brief): Found in /backlog/project-vision.md
-├─ Phase 2 (Trigger Map): Not found (user personas scattered in stories)
-├─ Phase 4 (UX Design): Found in /design-assets/ and story attachments
-├─ Phase 5 (Design System): Found in /design-assets/component-library.fig
-└─ Phase 3 (PRD): Found in /api-specs/
-
-Content Analysis (Design Domain):
-├─ Wireframes: 12 Figma files linked in design-assets/
-├─ User flows: Embedded in individual user stories
-├─ Design system: Figma component library exists
-└─ Consistency: Good, but scattered across sprints
-
-Implementation Status:
-├─ Code: 89 Vue component files
-├─ Features: E-commerce core (cart, checkout, product catalog)
-└─ Alignment: Design files match sprint implementation well
-
-💡 Observation:
-You're running a healthy Agile process with good design documentation,
-but design specs are scattered across multiple sprints, making it hard
-to get an overview.
-
-Recommended Options:
-
-1. **Continue with Agile structure**
-   - I'll work within your sprint model
-   - Help create design specs per user story
-   - Maintain your current process
-
-2. **Migrate to WDS v6 structure**
-   - Consolidate design docs into Phase 4/5
-   - Keep sprint planning separate
-   - Better design overview
-   - **Saga WDS Analyst Agent** can help migrate
-
-3. **Hybrid approach** (Recommended)
-   - Keep sprint planning
-   - Add docs/4-ux-design/ for consolidated specs
-   - Add project outline for agent tracking
-   - Best of both: Agile + systematic design docs
-
-Which approach would you prefer?
-```
-
----
-
-## After User Responds
-
-**If "continue with current"**: Ask for explanation of their structure  
-**If "migrate to WDS"**: Hand over to Saga WDS Analyst Agent  
-**If "hybrid"**: Offer to help set up hybrid structure  
-**If task in YOUR domain**: Continue helping  
-**If task in ANOTHER domain**: Use `../05-agent-handoff-guide.md`
-
----
-
-**Total time: 20-35 seconds** (depends on docs complexity)

package/src/workflows/_agent-dialogs/project-analysis/validation/deep-validation-before-work.md

@@ -1,235 +0,0 @@
-# Deep Validation Before Work (Tier 2)
-
-**Purpose**: Thoroughly validate selected section before starting work  
-**When**: User has selected a task, before agent begins working  
-**Time**: 5-10 seconds  
-**Scope**: ONLY the selected phase/scenario
-
----
-
-## Why Deep Validation?
-
-**Problem**: User selects "Continue Scenario 03" but:
-
-- Outline says 8 pages, reality has 6
-- 2 pages deleted since outline update
-- Files modified recently, outline outdated
-- Dependencies changed
-
-**Solution**: Deep check ensures agent has accurate context before work starts.
-
----
-
-## What to Check
-
-### 1. File Existence & Completeness
-
-**Check ALL files** claimed by outline for this section:
-
-```
-Outline claims for Scenario 03:
-  - 00-Scenario-Overview.md
-  - 3.1-Landing-Page.md
-  - 3.2-Feature-List.md
-  - 3.3-Pricing.md
-  - 3.4-FAQ.md
-  - Prototypes/sketch-landing.html
-
-Reality check:
-✅ 00-Scenario-Overview.md exists (2.3 KB)
-✅ 3.1-Landing-Page.md exists (15 KB)
-⚠️  3.2-Feature-List.md MISSING
-✅ 3.3-Pricing.md exists (8 KB)
-❌ 3.4-FAQ.md exists but EMPTY (0 KB)
-✅ Prototypes/ folder exists
-❌ sketch-landing.html MISSING from Prototypes/
-```
-
-### 2. File Count & Unexpected Files
-
-**Check for NEW files** not in outline:
-
-```
-Scanning docs/4-ux-design/03-pricing-page/...
-
-Found 7 files, outline claims 6:
-✅ Expected: 6 files
-⚠️  Found: 7 files
-📄 NEW: 3.5-Contact-Form.md (not in outline)
-```
-
-### 3. Modification Dates
-
-**Compare outline update vs file changes**:
-
-```
-Outline last updated: 2024-11-15
-Files modified:
-  - 3.1-Landing-Page.md: 2024-12-01 (AFTER outline)
-  - 3.3-Pricing.md: 2024-12-08 (AFTER outline)
-
-⚠️  Files changed since outline updated
-```
-
-### 4. Dependencies
-
-**For scenarios, check**:
-
-- Related scenarios referenced
-- Shared components mentioned
-- Design system dependencies
-
-```
-Scenario 03 references:
-  - Component: PricingCard (from Design System)
-  - Dependency: Scenario 01 (User auth flow)
-
-Checking dependencies:
-✅ docs/7-design-system/components/PricingCard.md exists
-⚠️  Scenario 01 shows "in_progress" but outline claims "complete"
-```
-
----
-
-## Report Format
-
-```
-🎨 Freya WDS Designer Agent
-
-You selected: "Continue Scenario 03"
-
-Deep validation of Scenario 03... ⚠️ Issues found
-
-Validation Results:
-
-📁 Folder: docs/4-ux-design/03-pricing-page/
-✅ Folder exists and accessible
-
-📄 Files (Outline claims 6, found 7):
-✅ 00-Scenario-Overview.md (complete, 2.3 KB)
-✅ 3.1-Landing-Page.md (complete, 15 KB)
-❌ 3.2-Feature-List.md MISSING
-✅ 3.3-Pricing.md (complete, 8 KB, modified after outline)
-⚠️  3.4-FAQ.md exists but EMPTY (0 KB)
-📄 3.5-Contact-Form.md NEW (not in outline)
-
-🔗 Dependencies:
-✅ PricingCard component (Design System)
-⚠️  Scenario 01 dependency shows mismatch
-
-🕒 Timeline:
-Outline updated: 2024-11-15
-Files modified: 2024-12-01, 2024-12-08 (2 files changed after)
-
-💡 Before we continue, would you like to:
-
-1. **Update outline first** (recommended)
-   - Add 3.5-Contact-Form.md to outline
-   - Mark 3.2-Feature-List.md as missing/deleted
-   - Update page count (6 → 5 existing + 1 new)
-   - Refresh last_updated date
-
-2. **Fix missing/empty files**
-   - Recreate 3.2-Feature-List.md
-   - Complete 3.4-FAQ.md content
-   - Then continue work
-
-3. **Proceed anyway**
-   - I'll work with current state
-   - Update outline after work complete
-
-Which approach would you prefer?
-```
-
----
-
-## Decision Tree
-
-```
-After deep validation:
-
-All valid? ✅
-    ↓
-Start work immediately
-
-Minor issues? ⚠️
-    ↓
-Ask user:
-  - Update outline?
-  - Proceed anyway?
-    ↓
-User chooses → Continue
-
-Major issues? ❌
-    ↓
-Strongly recommend:
-  - Fix missing files
-  - Update outline
-  - Review dependencies
-    ↓
-Don't start work until resolved
-```
-
----
-
-## After Validation
-
-**If user chooses "Update outline first"**:
-
-1. Agent updates `.wds-project-outline.yaml`
-2. Reflects current reality
-3. Then starts work
-
-**If user chooses "Fix missing files"**:
-
-1. Agent helps recreate/complete files
-2. Updates outline
-3. Then continues with original task
-
-**If user chooses "Proceed anyway"**:
-
-1. Agent works with current state
-2. Updates outline AFTER work complete
-3. Documents what was found vs expected
-
----
-
-## Example: Freya Deep Validation
-
-```
-User: "Continue Scenario 03"
-
-Freya: "Let me validate Scenario 03 before we start..."
-
-[5 seconds of checking]
-
-Freya: "I found the scenario folder with 5 pages:
-- Landing page (complete)
-- Pricing tiers (complete)
-- FAQ (in progress)
-- Contact form (not in outline - did you add this recently?)
-- Missing: Feature comparison page
-
-The outline expected 6 pages but I found 5 (one missing, one new).
-
-Before designing more pages, shall I:
-1. Update the outline to reflect these 5 pages?
-2. Recreate the missing feature comparison page?
-3. Continue with existing pages as-is?
-
-What would work best for you?"
-```
-
----
-
-## Benefits
-
-✅ **Prevents wasted work** - Agent knows true state  
-✅ **Catches drift early** - Before it compounds  
-✅ **Keeps outline accurate** - Forces sync with reality  
-✅ **User stays informed** - Knows what's actually there  
-✅ **Reduces confusion** - No surprises mid-work
-
----
-
-**This is the second safety net after Tier 1 fast check!** 🛡️

package/src/workflows/_agent-dialogs/project-analysis/work-types/strategy-work.md

@@ -1,88 +0,0 @@
-# Strategy & Research Work
-
-**You were routed here because**: User selected strategy/research work (Product Brief or Trigger Map)
-
----
-
-## What This Work Involves
-
-**Strategy and research work** includes:
-
-- Product vision and positioning
-- Market and competitive analysis
-- User research and personas
-- Business goals and success metrics
-- Trigger mapping and user journeys
-
----
-
-## Recommended Agent
-
-**Saga WDS Analyst Agent** specializes in this type of work (Phases 1-2).
-
-**If you're NOT Saga**, here's how to hand over:
-
----
-
-## Seamless Handoff to Saga
-
-"I can see you want to work on **[Product Brief/Trigger Map]** - strategic foundation work.
-
-**Saga WDS Analyst Agent** specializes in strategy and research. She's brilliant at:
-
-- Defining product vision and positioning
-- Market intelligence and competitive analysis
-- User research and persona development
-- Business strategy and success metrics
-
-Let me hand over to Saga who can help you best with this..."
-
-**Then activate Saga** but skip project analysis:
-
-→ Load: `getting-started/agent-activation/wds-saga-analyst.md`  
-→ Saga shows: Full presentation ✅  
-→ Saga skips: Project analysis (already shown)  
-→ Saga continues: Directly to the specific work
-
-**Task context to pass**: "User wants to work on: [Product Brief/Trigger Map]"
-
----
-
-## If You ARE Saga
-
-**Context aware handoff**: The user already selected a specific task, so you don't need to re-analyze the project.
-
-Continue directly with the work:
-
-"Great! Let's work on the **[specific task user selected]** together.
-
-[Ask clarifying questions specific to their selection]
-[Engage directly with the work]
-[Offer specific next steps]"
-
-**For Product Brief review**:
-"Let's review the Product Brief together.
-
-What aspect would you like to focus on?
-
-- Vision and positioning - Is it still aligned with where you're heading?
-- Competitive landscape - Has anything changed in the market?
-- Success metrics - Are we measuring the right things?
-- Target users - Do we need to refine our understanding?
-
-Tell me what you'd like to explore!"
-
-**For Trigger Map work**:
-"Let's dive into the Trigger Map!
-
-What would you like to work on?
-
-- Refining user personas - Add depth or new segments?
-- Updating journey maps - Has user behavior changed?
-- Feature prioritization - What should we focus on?
-
-Tell me what you'd like to explore!"
-
----
-
-**The goal**: Get the right agent working on the right work, seamlessly.

package/src/workflows/_agent-dialogs/step-completion-protocol.md

@@ -1,175 +0,0 @@
-# Step Completion Protocol
-
-**Purpose:** Standard protocol for completing workflow steps and communicating progress to users.
-
----
-
-## When to Use
-
-Apply this protocol whenever you:
-- Complete a Product Brief step
-- Finish a major task or milestone
-- Update agent dialog files
-- Make significant changes to project files
-
----
-
-## Protocol Steps
-
-### 1. Complete the Work
-
-- Finish all tasks required for the step
-- Ensure all artifacts are generated and validated
-- Verify step requirements are met
-
-### 2. Update Agent Dialog Files
-
-**If project has agent dialog structure:**
-
-1. Update the relevant dialog file (e.g., `dialog/02-vision.md`, `dialog/decisions.md`)
-2. Document reflection checkpoint (synthesis + confirmation/correction)
-3. Record final outputs and key insights
-4. Mark step complete in `dialog/README.md` progress tracker
-
-**If this is a meta-level agent dialog** (like ongoing session work):
-
-1. Move completed task from CURRENT WORK to top of COMPLETED WORK
-2. Update CURRENT PLAN checkboxes (⏳ → ✅)
-3. Move next task from UPCOMING WORK to CURRENT WORK
-4. Update CURRENT WORK section with new task details
-
-### 3. Show Git Diff (MANDATORY)
-
-**ALWAYS show git diff of changes made.**
-
-**For single file changes:**
-```bash
-git diff path/to/file.md
-```
-
-**For multiple files:**
-```bash
-git diff --stat path/to/directory/
-```
-
-**For all changes in session:**
-```bash
-git diff --stat
-```
-
-**Why this matters:**
-- Transparency: User sees exactly what changed
-- Validation: User can review changes before committing
-- Context: Clear record of progress made
-- Accountability: Agent and user stay aligned
-
-**When NOT to show diff:**
-- Files too large (>50KB) - show `--stat` only
-- Binary files (images, PDFs) - mention they were created/modified
-- Sensitive information - describe changes verbally instead
-
-### 4. Present Summary
-
-**Tell the user what was accomplished:**
-
-```markdown
-✅ **[Task/Step Name] Complete**
-
-[Brief summary of what was done - 1-3 sentences]
-
-**Changes made:**
-- [Key change 1]
-- [Key change 2]
-- [Key change 3]
-
-**Files modified:** [count] files, [+insertions]/-[deletions] lines
-
-[If applicable: What's next or what to review]
-```
-
-### 5. Update State
-
-**Update project state files if needed:**
-- Update `.wds-project-outline.yaml` if phase/step status changed
-- Update frontmatter in step files if using state tracking
-- Update any progress trackers
-
----
-
-## Example Execution
-
-**Scenario:** Just completed Step 3 (Positioning) in Product Brief
-
-**Agent actions:**
-
-1. ✅ **Completed work:** Generated positioning statement with components
-2. ✅ **Updated dialog:** Added to `dialog/07-positioning.md` and `dialog/README.md`
-3. ✅ **Show diff:**
-
-```bash
-git diff --stat src/workflows/.../dialog/
-```
-
-Output:
-```
-dialog/07-positioning.md | 45 ++++++++++++++++++++
-dialog/README.md         |  2 +-
-2 files changed, 46 insertions(+), 1 deletion(-)
-```
-
-4. ✅ **Present to user:**
-
-```markdown
-✅ **Step 3: Positioning Complete**
-
-Created positioning statement synthesized from conversation about target customers, alternatives, and differentiation.
-
-**Key outputs:**
-- Positioning statement for vehicle owners in northern Öland
-- Component breakdown (target, need, category, benefit, alternatives, differentiator)
-- Strategic rationale documenting why this positioning makes sense
-
-**Files modified:** 2 files, 46 insertions(+), 1 deletion(-)
-
-**Next:** Step 4 - Business Model (B2B/B2C/Both)
-```
-
-5. ✅ **Updated state:** Marked Step 3 complete in progress tracking
-
----
-
-## Common Mistakes to Avoid
-
-❌ **DON'T:**
-- Skip showing git diff (transparency matters!)
-- Batch multiple steps without showing individual diffs
-- Present diff without explaining what changed
-- Show diff of unrelated files from previous work
-- Forget to update agent dialog files
-
-✅ **DO:**
-- Show diff immediately after making changes
-- Explain what the diff represents
-- Update dialog files before showing diff
-- Keep diffs focused on current work
-- Use `--stat` for high-level overview when many files changed
-
----
-
-## Integration with Workflows
-
-**This protocol is referenced by:**
-- All Product Brief step files (steps-c/*.md)
-- Agent dialog templates (workflows/1-project-brief/templates/project-brief-dialog/USAGE.md)
-- Workflow orchestration files (workflow.md)
-
-**Agents should:**
-- Internalize this protocol
-- Apply it consistently
-- Adapt language to user's working relationship context
-- Use git diff tools fluently
-
----
-
-**Status:** Active protocol for all WDS workflow steps
-**Last Updated:** 2026-02-12