whiteport-design-studio 0.2.2 → 0.3.0

package/src/workflows/_agent-dialogs/conversation-persistence/check-conversations.md

@@ -1,162 +0,0 @@
-# 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/_agent-dialogs/conversation-persistence/conversation-template.md

@@ -1,70 +0,0 @@
-# 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/_agent-dialogs/conversation-persistence/persistence-guide.md

@@ -1,81 +0,0 @@
-# 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
-

package/src/workflows/_agent-dialogs/conversation-persistence/save-conversation.md

@@ -1,146 +0,0 @@
-# Save Conversation - Instructions
-
-**When to save**: When valuable context needs to be preserved
-
-**Purpose**: Capture important discussions so they can be resumed later
-
----
-
-## When to Save Conversations
-
-Save a conversation when:
-
-1. **Context window getting full** - User mentions context is crowded or you detect it's getting long
-2. **User explicitly requests** - "Let me pick this up later", "I need to close this session"
-3. **Natural break point** - After completing a significant discussion/task
-4. **Switching to different work** - Before starting something completely different
-5. **Multi-user scenario** - When another user might need to pick up the work
-
-**Don't save**:
-- Very brief exchanges
-- Conversations that are clearly complete/finished
-- Trivial discussions with no valuable context
-
----
-
-## How to Save
-
-### Step 1: Create Conversation File
-
-**File location**: `docs/.conversations/`
-
-**File name**: `[timestamp]-[agent]-[topic].md`
-
-**Timestamp format**: `YYYY-MM-DD-HHMM` (current date/time)
-
-**Example**: `2025-01-15-1430-saga-pitch-module.md`
-
-### Step 2: Fill in Template
-
-Use the template from `conversation-template.md`:
-
-```markdown
----
-status: active
-agent: [your-agent-name]
-topic: [brief-topic]
-created: [YYYY-MM-DD HH:MM]
-last_updated: [YYYY-MM-DD HH:MM]
-context_summary: [one-line summary]
----
-
-# Conversation: [Topic]
-
-## Context Summary
-
-[What was discussed - 2-3 sentences]
-
-## Key Decisions & Understandings
-
-- [Important decision 1]
-- [Important understanding 2]
-- [Key insight 3]
-
-## Where We Left Off
-
-[Last thing discussed, current state]
-
-## Next Steps
-
-- [What needs to happen next]
-- [User's intent]
-
-## Important Details
-
-[Specific context, constraints, preferences]
-
-## Conversation Thread
-
-[Key parts of conversation if needed for context]
-```
-
-### Step 3: Inform User
-
-After saving, let the user know:
-
-"I've saved our conversation about [topic] so you can pick it up later. The file is at `docs/.conversations/[filename].md`"
-
----
-
-## What to Include
-
-**Essential**:
-- What was discussed (summary)
-- Key decisions made
-- Where conversation left off
-- What needs to happen next
-
-**Valuable**:
-- User's preferences or constraints
-- Important context that might be forgotten
-- Specific details about approach or direction
-
-**Skip**:
-- Full conversation transcript (unless critical)
-- Trivial back-and-forth
-- Information already documented elsewhere
-
----
-
-## File Naming Guidelines
-
-- **Timestamp first** - For chronological sorting
-- **Agent name** - Who was having the conversation
-- **Topic** - Brief, descriptive (2-4 words)
-- **Use hyphens** - No spaces in filename
-- **Lowercase** - Keep it simple
-
-**Good examples**:
-- `2025-01-15-1430-saga-pitch-module.md`
-- `2025-01-15-1500-freya-login-wireframes.md`
-- `2025-01-15-1600-idunn-api-architecture.md`
-
-**Bad examples**:
-- `pitch-module.md` (no timestamp)
-- `Saga Pitch Module.md` (spaces, uppercase)
-- `2025-01-15-saga-discussion.md` (too vague)
-
----
-
-## Status Management
-
-**When creating**: Set `status: active`
-
-**When resuming**: Update to `status: picked-up` and update `last_updated`
-
-**When archiving**: Update to `status: archived` (for old conversations)
-
----
-
-## Multi-User Considerations
-
-- Files are visible to all users working on the repo
-- Anyone can pick up any active conversation
-- Status field helps track what's been resumed
-- Timestamp helps identify most recent discussions
-

package/src/workflows/_agent-dialogs/project-analysis/01-instructions.md

@@ -1,79 +0,0 @@
-# Project Analysis - Entry Point
-
-**Your role**: WDS Agent (Freya, Saga, or Idunn)
-
----
-
-## What to Do
-
-### Step 1: Check for Project Outline
-
-**Look for**: `_progress/wds-project-outline.yaml`
-
-**If FOUND** → Fast path:
-- Read outline for project type and status
-- Route to `02-project-analysis-router.md`
-- Skip Phase 0 (already set up)
-
-**If NOT FOUND** → New project:
-- Continue to Step 2
-
----
-
-### Step 2: Show Your Presentation
-
-Present your complete agent introduction:
-
-- **Freya**: Load and present `{project-root}/_bmad/wds/data/presentations/freya-presentation.md`
-- **Saga**: Load and present `{project-root}/_bmad/wds/data/presentations/saga-presentation.md`
-- **Idunn**: Load and present `{project-root}/_bmad/wds/data/presentations/idunn-presentation.md`
-
-**Why**: This establishes who you are before analyzing their project.
-
----
-
-### Step 3: Route to Phase 0
-
-**After presentation, go to Phase 0: Project Setup**
-
-Route to: `../0-project-setup/steps/step-01-welcome.md`
-
-**Why Phase 0 first?**
-- Introduces WDS to new users
-- Asks the critical question: Greenfield vs Brownfield?
-- Prevents wrong-path work (existing code going through Phase 1-3)
-- Sets up proper project structure
-
----
-
-## Flow Summary
-
-```
-New User Arrives
-    │
-    ├─→ Check for project outline
-    │       │
-    │       ├─→ FOUND → 02-project-analysis-router.md (fast path)
-    │       │
-    │       └─→ NOT FOUND
-    │               │
-    │               ├─→ Show agent presentation
-    │               │
-    │               └─→ Phase 0: Project Setup
-    │                       │
-    │                       ├─→ WDS Introduction
-    │                       ├─→ Project Type Question
-    │                       ├─→ Create Structure
-    │                       │
-    │                       └─→ Route to correct phase
-    │                               │
-    │                               ├─→ Greenfield → Phase 1
-    │                               └─→ Brownfield → Phase 8
-```
-
----
-
-## Alternative: If You Can't Find Presentation
-
-If the presentation file is missing, go directly to:
-`../0-project-setup/steps/step-01-welcome.md`

package/src/workflows/_agent-dialogs/project-analysis/02-project-analysis-router.md

@@ -1,99 +0,0 @@
-# Project Analysis Router
-
-**Purpose**: Route to appropriate analysis file based on project state
-**When**: Called AFTER agent presentation is complete
-
----
-
-## FIRST: Check for Agent Dialog Files (Context Loading)
-
-**Before routing, check for ongoing work:**
-
-1. **Look for dialog files:**
-   - Check: `docs/progress/dialog/README.md`
-   - Check: `design-process/progress/dialog/README.md`
-   - Check: `{{custom_root}}/progress/dialog/README.md`
-
-2. **If dialog files exist:**
-   - Read `dialog/progress-tracker.md` for progress overview
-   - Check which steps are complete
-   - Read relevant dialog files (00-context.md, decisions.md) for conversation history
-   - **Context loaded:** You now understand what's been done and where user left off
-
-3. **If dialog files don't exist:**
-   - Fresh start, no prior context
-   - Proceed with routing as normal
-
-**Why this matters:** Dialog files contain conversation history, decisions made, and progress status. Loading them first ensures you continue work seamlessly rather than starting over.
-
----
-
-## Check Conditions & Route
-
-**Check these conditions IN ORDER and route to first match:**
-
-### Condition A: Project Outline Exists?
-
-**Check for**: `docs/.wds-project-outline.yaml` OR `.wds-project-outline.yaml`
-
-**If EXISTS** → Route to:  
-`analysis-types/outline-based-analysis.md`
-
-**STOP CHECKING. Jump to that file now.**
-
----
-
-### Condition B: Docs Folder with WDS/WPS2C Structure?
-
-**Check for**: `docs/` folder exists AND has numbered (1-_, 2-_) or letter folders (A-_, B-_)
-
-**If EXISTS** → Route to:  
-`analysis-types/folder-based-analysis.md`
-
-**STOP CHECKING. Jump to that file now.**
-
----
-
-### Condition C: Empty Docs Folder?
-
-**Check for**: `docs/` folder exists BUT is empty
-
-**If EMPTY** → Route to:  
-`analysis-types/empty-project-response.md`
-
-**STOP CHECKING. Jump to that file now.**
-
----
-
-### Condition D: No Docs Folder?
-
-**Check for**: NO `docs/` folder at all
-
-**If NO DOCS** → Route to:  
-`analysis-types/new-project-response.md`
-
-**STOP CHECKING. Jump to that file now.**
-
----
-
-### Condition E: Unknown Structure?
-
-**If**: `docs/` exists but no recognizable pattern
-
-**Route to**:  
-`analysis-types/unknown-structure-response.md`
-
-**STOP CHECKING. Jump to that file now.**
-
----
-
-## Rules
-
-- ✅ Check conditions in order (A → B → C → D → E)
-- ✅ Route to FIRST matching condition
-- ✅ STOP checking after first match
-- ✅ Follow instructions in routed file ONLY
-
----
-
-**This is a ROUTER. Check → Route → Stop.**