whiteport-design-studio 0.1.0

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

@@ -0,0 +1,216 @@
+# 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 `../agent-handoff-guide.md`
+
+---
+
+**Total time: 20-35 seconds** (depends on docs complexity)

package/src/workflows/project-analysis/context-aware-activation.md

@@ -0,0 +1,99 @@
+# Context-Aware Activation
+
+**Purpose**: Instructions for agents receiving a handoff with specific task context
+
+---
+
+## Detect Handoff Context
+
+**Check the conversation** for these signals:
+
+1. **Another agent just handed over** - Look for phrases like "Let me hand over to..."
+2. **Specific task mentioned** - "User wants to work on: [Task]"
+3. **Project status already shown** - "Current Project Status:" exists in recent messages
+
+---
+
+## If Handoff Context Detected
+
+**Your activation should be**:
+
+### Step 1: Show Your Presentation ✅
+
+**Always show**: Your full presentation (personality, expertise, philosophy)  
+**Why**: Human connection is important, even in handoffs
+
+### Step 2: Skip Project Analysis ❌
+
+**Don't show**: Full project status (already shown)  
+**Why**: User already saw it, would be redundant
+
+### Step 3: Acknowledge Specific Task ✅
+
+**Do say**: "You want to work on [specific task]. Great!"  
+**Why**: Shows you understand the context
+
+### Step 4: Ask Task-Specific Question ✅
+
+**Do ask**: Direct question about the specific work  
+**Example**: "What would you like to change in the Product Brief?"  
+**Why**: Gets straight to productive work
+
+---
+
+## Example: Saga Receiving Handoff
+
+**Previous agent said**: "User wants to work on: Product Brief"
+
+**Saga's activation**:
+
+```
+📚 Hello! I'm Saga, Your Strategic Business Analyst!
+
+[...Full presentation shown...]
+
+---
+
+You want to work on the **Product Brief** - great choice!
+
+What would you like to change in the Product Brief?
+
+- **Vision and positioning** - Refine the core message?
+- **Competitive landscape** - Update market analysis?
+- **Success metrics** - Adjust how we measure success?
+- **Target users** - Sharpen our user understanding?
+- **Something else** - Tell me what you're thinking!
+
+Tell me what you'd like to explore!
+```
+
+---
+
+## If No Handoff Context
+
+**Your activation should be**:
+
+### Step 1: Show Your Presentation ✅
+
+### Step 2: Show Full Project Analysis ✅
+
+### Step 3: Ask What They Want to Work On ✅
+
+(Standard activation flow)
+
+---
+
+## How to Detect
+
+**Simple check**: Look in conversation history for:
+
+- "Let me hand over to [Your Name]"
+- "User wants to work on: [Task]"
+- "[Previous Agent] specializes in..."
+
+**If found**: Context-aware activation (skip analysis)  
+**If not found**: Standard activation (full analysis)
+
+---
+
+**This makes handoffs seamless and efficient!**

package/src/workflows/project-analysis/conversation-persistence/check-conversations.md

@@ -0,0 +1,162 @@
+# Check Conversations - Instructions
+
+**When**: On agent wake-up/activation
+
+**Purpose**: Discover if there are active conversations to resume
+
+---
+
+## When to Check
+
+**Always check** when:
+- Agent is activated/awakened
+- Starting a new conversation
+- User asks "what were we working on?"
+
+**Don't check**:
+- Mid-conversation (unless user asks)
+- When conversation is clearly continuing
+
+---
+
+## How to Check
+
+### Step 1: Look in Conversations Folder
+
+**Location**: `docs/.conversations/`
+
+**Look for**: Files with `status: active` in frontmatter
+
+### Step 2: Filter by Relevance
+
+**Consider relevant if**:
+- Topic matches what user is asking about
+- Recent timestamp (within last few days/weeks)
+- Same agent (if user was working with you before)
+- Related domain/phase
+
+**Don't show**:
+- Very old conversations (unless explicitly relevant)
+- Conversations marked `archived`
+- Conversations already `picked-up` (unless user asks)
+
+### Step 3: Present Options
+
+If relevant conversations found:
+
+```
+"I see there's an active conversation about [topic] from [time]. 
+Should I pick up from there, or start fresh?"
+```
+
+**If multiple conversations**:
+```
+"I found a few active conversations:
+1. [Topic 1] from [time]
+2. [Topic 2] from [time]
+3. [Topic 3] from [time]
+
+Which would you like to continue, or start something new?"
+```
+
+### Step 4: Load Context if Resuming
+
+**If user says yes**:
+1. Read the conversation file
+2. Update status to `picked-up`
+3. Update `last_updated` timestamp
+4. Summarize: "We were discussing [topic]. [Brief summary]. Where would you like to continue?"
+
+**If user says no**:
+- Acknowledge and start fresh
+- Keep the file available (don't delete)
+
+---
+
+## Conversation File Format
+
+Check frontmatter for:
+- `status: active` (what to look for)
+- `topic` (to match relevance)
+- `created` (to check recency)
+- `context_summary` (quick preview)
+
+---
+
+## Relevance Matching
+
+**High relevance**:
+- Exact topic match
+- Same agent
+- Recent (within 1-2 days)
+- Related to current request
+
+**Medium relevance**:
+- Related topic/domain
+- Same phase/work type
+- Recent (within a week)
+
+**Low relevance**:
+- Different topic
+- Old (weeks/months old)
+- Different domain
+
+**Show high/medium relevance conversations, skip low relevance unless user asks**
+
+---
+
+## Status Updates
+
+**When resuming conversation**:
+- Update `status: active` → `status: picked-up`
+- Update `last_updated: [current timestamp]`
+- Optionally add note: "Resumed on [date]"
+
+**Don't delete files** - Keep for history/backup
+
+---
+
+## Example Flow
+
+**Agent wakes up**:
+```
+[Agent checks docs/.conversations/]
+
+"I see there's an active conversation about 'pitch module' from yesterday. 
+Should I pick up from there, or are we starting something new?"
+```
+
+**User says "pick it up"**:
+```
+[Agent reads file, updates status]
+
+"Perfect! We were discussing adding a pitch module to the Project Brief workflow. 
+You wanted it to be a prerequisite step that establishes why the project matters 
+before diving into strategy.
+
+Where would you like to continue? We had started designing the step structure..."
+```
+
+**User says "start fresh"**:
+```
+"Got it! Starting fresh. What would you like to work on?"
+```
+
+---
+
+## Multi-User Scenarios
+
+- All users can see all conversations
+- Anyone can pick up any active conversation
+- Status helps track what's been resumed
+- Useful for team collaboration on same repo
+
+---
+
+## Cleanup (Optional)
+
+**Old conversations** can be marked `archived`:
+- After being picked up and completed
+- After being inactive for extended period
+- But keep them - don't delete (valuable history)
+

package/src/workflows/project-analysis/conversation-persistence/conversation-template.md

@@ -0,0 +1,70 @@
+# Conversation Template
+
+**File naming format**: `[timestamp]-[agent]-[topic].md`
+
+**Example**: `2025-01-15-1430-saga-pitch-module.md`
+
+**Location**: `docs/.conversations/`
+
+---
+
+## File Structure
+
+```markdown
+---
+status: active | picked-up | archived
+agent: [agent-name]
+topic: [brief-topic-description]
+created: [YYYY-MM-DD HH:MM]
+last_updated: [YYYY-MM-DD HH:MM]
+context_summary: [one-line summary]
+---
+
+# Conversation: [Topic]
+
+## Context Summary
+
+[Brief 2-3 sentence summary of what was discussed]
+
+## Key Decisions & Understandings
+
+- [Decision/understanding 1]
+- [Decision/understanding 2]
+- [Decision/understanding 3]
+
+## Where We Left Off
+
+[What was the last thing discussed? What was the state of the conversation?]
+
+## Next Steps
+
+- [What needs to happen next?]
+- [What was the user planning to do?]
+
+## Important Details
+
+[Any specific details, constraints, preferences, or context that would be valuable to know]
+
+## Conversation Thread
+
+[Optional: Key parts of the conversation that provide context]
+```
+
+---
+
+## Status Values
+
+- **active** - Conversation is waiting to be picked up
+- **picked-up** - Conversation has been resumed
+- **archived** - Old conversation, kept for history/backup
+
+---
+
+## Usage Notes
+
+- Timestamp format: `YYYY-MM-DD-HHMM` (24-hour format)
+- Topic should be brief and descriptive (2-4 words)
+- Keep summaries concise but informative
+- Update `last_updated` whenever file is modified
+- Update `status` when conversation is picked up
+

package/src/workflows/project-analysis/conversation-persistence/persistence-guide.md

@@ -0,0 +1,81 @@
+# Conversation Persistence System
+
+**Purpose**: Preserve valuable conversation context across sessions and enable multi-user collaboration
+
+---
+
+## Overview
+
+This system allows agents to:
+- Save valuable conversations when context gets full or sessions close
+- Resume conversations later without losing context
+- Enable multiple users to see and continue discussions on the same repo
+
+---
+
+## Components
+
+1. **conversation-template.md** - File format and structure
+2. **save-conversation.md** - Instructions for saving conversations
+3. **check-conversations.md** - Instructions for checking/resuming on wake-up
+
+---
+
+## File Structure
+
+**Location**: `docs/.conversations/`
+
+**Naming**: `[timestamp]-[agent]-[topic].md`
+
+**Example**: `2025-01-15-1430-saga-pitch-module.md`
+
+---
+
+## Status Values
+
+- **active** - Waiting to be picked up
+- **picked-up** - Conversation has been resumed
+- **archived** - Old conversation, kept for history
+
+---
+
+## Usage Flow
+
+### Saving a Conversation
+
+1. Agent detects need to save (context full, user closing session, etc.)
+2. Creates file using template
+3. Fills in context summary, key decisions, where left off
+4. Sets status to `active`
+5. Informs user where file is saved
+
+### Resuming a Conversation
+
+1. Agent wakes up
+2. Checks `docs/.conversations/` for `status: active` files
+3. Filters by relevance (topic, recency, agent)
+4. Presents options to user
+5. If resuming: loads file, updates status to `picked-up`, continues
+
+---
+
+## Integration Points
+
+**Agents should**:
+- Check conversations on wake-up (reference `check-conversations.md`)
+- Save conversations when needed (reference `save-conversation.md`)
+- Use template format (reference `conversation-template.md`)
+
+**Agent definitions should include**:
+- Reference to check conversations on activation
+- Reference to save conversations when context full
+
+---
+
+## Benefits
+
+- **No lost context** - Valuable discussions preserved
+- **Session continuity** - Pick up where you left off
+- **Multi-user collaboration** - Team members can see and continue discussions
+- **History** - All conversations kept for reference/backup
+