whiteport-design-studio 0.1.0

package/src/workflows/8-ongoing-development/workflow.md

@@ -0,0 +1,302 @@
+# Phase 8: Ongoing Development (Kaizen) Workflow
+
+**Continuous improvement through strategic, incremental changes**
+
+---
+
+## Purpose
+
+Phase 8 is about **Kaizen (改善)** - the Japanese philosophy of continuous improvement.
+
+**Two contexts for Phase 8:**
+
+1. **Entry Point for Existing Products** - Jump into an existing product as a linchpin designer
+2. **Continuous Improvement** - After initial launch, keep improving through small, strategic changes
+
+---
+
+## Lean Manufacturing Philosophy
+
+### Kaizen (改善) vs Kaikaku (改革)
+
+**Two approaches to improvement from Lean manufacturing:**
+
+---
+
+### Kaizen (改善) - Continuous Improvement
+
+**改善 = Change (改) + Good (善)**
+
+**Definition:** Small, incremental, continuous improvements over time.
+
+**Characteristics:**
+
+- Small changes (1-2 weeks each)
+- Low cost, low risk
+- Everyone participates
+- Continuous, never stops
+- Gradual improvement
+- Process-focused
+- Bottom-up approach
+
+**In product design:**
+
+- Ship → Learn → Improve → Ship → Repeat
+- Small updates beat big redesigns
+- User feedback drives improvements
+- Data informs decisions
+- Quality improves gradually
+- Team learns continuously
+
+**Example:**
+
+- Add onboarding tooltip to improve feature usage
+- Optimize button color for better conversion
+- Improve error message clarity
+
+**Phase 8 uses Kaizen approach!**
+
+---
+
+### Kaikaku (改革) - Revolutionary Change
+
+**改革 = Change (改) + Reform (革)**
+
+**Definition:** Radical, revolutionary transformation in a short period.
+
+**Characteristics:**
+
+- Large changes (months)
+- High cost, high risk
+- Leadership-driven
+- One-time event
+- Dramatic improvement
+- Result-focused
+- Top-down approach
+
+**In product design:**
+
+- Complete redesign
+- Platform migration
+- Architecture overhaul
+- Brand transformation
+- Business model pivot
+
+**Example:**
+
+- Complete product redesign
+- Migrate from web to mobile-first
+- Rebrand entire product
+- Change business model
+
+**Phases 1-7 can be Kaikaku (greenfield projects)!**
+
+---
+
+### When to Use Each
+
+**Use Kaizen (改善) when:**
+
+- ✅ Product is live and working
+- ✅ Need continuous improvement
+- ✅ Want low-risk changes
+- ✅ Team capacity is limited
+- ✅ Learning is important
+- ✅ **Phase 8: Ongoing Development**
+
+**Use Kaikaku (改革) when:**
+
+- ✅ Starting from scratch (greenfield)
+- ✅ Product needs complete overhaul
+- ✅ Market demands radical change
+- ✅ Current approach is fundamentally broken
+- ✅ Have resources for big change
+- ✅ **Phases 1-7: New Product Development**
+
+---
+
+### The Balance
+
+**Best practice:** Kaikaku to establish, Kaizen to improve.
+
+```
+Kaikaku (改革): Build product v1.0 (Phases 1-7)
+    ↓
+Launch
+    ↓
+Kaizen (改善): Continuous improvement (Phase 8)
+    ↓
+Kaizen cycle 1, 2, 3, 4, 5... (ongoing)
+    ↓
+(If needed) Kaikaku: Major redesign v2.0
+    ↓
+Kaizen: Continuous improvement again
+```
+
+**Phase 8 embodies Kaizen philosophy!**
+
+---
+
+## Workflow Architecture
+
+This uses **micro-file architecture** for disciplined execution:
+
+- Each step is a self-contained file with embedded rules
+- Sequential progression with user control at each step
+- Iterative improvement cycles
+
+---
+
+## Phase 8 Micro-Steps
+
+### Context 1: Existing Product Entry Point
+
+```
+Phase 8.1: Identify Strategic Challenge
+    ↓ (What problem are we solving?)
+Phase 8.2: Gather Existing Context
+    ↓ (Understand current state)
+Phase 8.3: Design Critical Updates
+    ↓ (Targeted improvements, not complete redesign)
+Phase 8.4: Create Design Delivery
+    ↓ (Package changes as DD-XXX for BMad)
+Phase 8.5: Hand Off to BMad
+    ↓ (Touch Point 2: WDS → BMad)
+Phase 8.6: Validate Implementation
+    ↓ (Touch Point 3: BMad → WDS)
+Phase 8.7: Monitor and Learn
+    ↓ (Gather data, identify next improvement)
+Phase 8.8: Iterate
+    ↓ (Repeat cycle for next challenge)
+```
+
+---
+
+### Context 2: Continuous Improvement (Post-Launch)
+
+```
+Phase 8.1: Monitor Product Performance
+    ↓ (Analytics, feedback, issues)
+Phase 8.2: Identify Improvement Opportunity
+    ↓ (What's the next most valuable change?)
+Phase 8.3: Design Incremental Update
+    ↓ (Small, focused improvement)
+Phase 8.4: Create Design Delivery
+    ↓ (Package changes as DD-XXX for BMad)
+Phase 8.5: Hand Off to BMad
+    ↓ (Touch Point 2: WDS → BMad)
+Phase 8.6: Validate Implementation
+    ↓ (Touch Point 3: BMad → WDS)
+Phase 8.7: Monitor Impact
+    ↓ (Did it improve the metric?)
+Phase 8.8: Iterate
+    ↓ (Repeat cycle - Kaizen never stops!)
+```
+
+---
+
+## When to Enter Phase 8
+
+### Scenario 1: Existing Product Entry Point
+
+**You're brought in as a linchpin designer to improve an existing product:**
+
+```
+Product Manager: "We have a product with 60% onboarding drop-off.
+                  We need a designer to fix this critical issue."
+
+You: "I'll use WDS Phase 8 to make strategic improvements."
+```
+
+**Start with:** `steps/step-8.1-identify-challenge.md`
+
+---
+
+### Scenario 2: Post-Launch Continuous Improvement
+
+**Your product is live and you're iterating based on data:**
+
+```
+Analytics: "Feature X has low engagement (15% usage)"
+User Feedback: "Users don't understand how to use Feature X"
+
+You: "Time for a Kaizen cycle to improve Feature X."
+```
+
+**Start with:** `steps/step-8.1-monitor-performance.md`
+
+---
+
+## Execution
+
+Load and execute the appropriate step file based on your context:
+
+**Existing Product Entry Point:**
+
+- `steps/step-8.1-identify-challenge.md`
+
+**Continuous Improvement:**
+
+- `steps/step-8.1-monitor-performance.md`
+
+**Note:** Each step will guide you to the next step when ready.
+
+---
+
+## Resources
+
+- Limited Project Brief: `A-Project-Brief/limited-brief.md`
+- Existing Context: `A-Project-Brief/existing-context/`
+- Design Deliveries: `deliveries/DD-XXX.yaml` (all improvements use DD-XXX)
+- Test Scenarios: `test-scenarios/TS-XXX.yaml`
+- Analytics: `analytics/`
+- User Feedback: `feedback/`
+
+---
+
+## Key Differences from Phases 1-7
+
+**Phase 8 is NOT about:**
+
+- ❌ Complete redesigns
+- ❌ Designing full user flows from scratch
+- ❌ Starting with blank canvas
+- ❌ Defining tech stack (already decided)
+
+**Phase 8 IS about:**
+
+- ✅ Strategic, targeted improvements
+- ✅ Updating existing screens and features
+- ✅ Incremental changes that compound
+- ✅ Working within existing constraints
+- ✅ Continuous improvement (Kaizen)
+
+---
+
+## The Kaizen Cycle
+
+```
+Ship → Monitor → Learn → Improve → Ship → Monitor → Learn → Improve...
+
+This cycle never stops!
+```
+
+**Each cycle:**
+
+- Takes 1-2 weeks (small changes)
+- Focuses on one improvement
+- Ships to production
+- Measures impact
+- Informs next cycle
+
+**Over time:**
+
+- Small improvements compound
+- Product quality increases
+- User satisfaction grows
+- Team learns continuously
+- Competitive advantage builds
+
+---
+
+**Phase 8 is where products become great - through continuous, disciplined improvement!** 🎯✨

package/src/workflows/9-agent-dialogs/steps/step-01-initialize-dialog.md

@@ -0,0 +1,244 @@
+# Step 1: Initialize Dialog
+
+## CONTEXT
+
+This is the first step of the Agent Dialog Workflow. Before creating a new dialog, we first check for any existing pending dialogs.
+
+---
+
+## CHECK FOR EXISTING DIALOGS
+
+⚠️ **IMPORTANT: Always check for pending dialogs before creating a new one.**
+
+<action>
+**Scan for existing dialogs:**
+
+1. Check if `docs/F-Agent-Dialogs/` exists
+2. If it exists, scan all subdirectories for dialog files (*-dialog.md)
+3. Read the Meta section of each dialog file
+4. Identify dialogs where:
+   - Status = "Not Started" OR "In Progress"
+   - Agent matches the current agent (if known)
+</action>
+
+<conditional>
+**If pending dialogs found:**
+
+Present them to the user:
+
+```
+📋 **Found {N} pending dialog(s):**
+
+| # | Date | Agent | Feature | Status |
+|---|------|-------|---------|--------|
+| 1 | {date} | {agent} | {feature} | {status} |
+
+**Options:**
+[A] Continue existing dialog #{N}
+[B] Create a new dialog (existing ones remain pending)
+
+Choice:
+```
+
+If user chooses an existing dialog:
+- Load that dialog file
+- Check the Steps Overview table for next incomplete step
+- Continue from there
+
+If user chooses to create new:
+- Continue to SELECT DIALOG TYPE below
+</conditional>
+
+<conditional>
+**If no pending dialogs found OR docs/F-Agent-Dialogs/ doesn't exist:**
+
+Continue to SELECT DIALOG TYPE below.
+</conditional>
+
+---
+
+## SELECT DIALOG TYPE
+
+<ask>**What type of work is this?**
+
+| Type | Icon | Use When |
+|------|------|----------|
+| **[A] Prototype Implementation** | 🔧 | Building UI from specifications |
+| **[B] Bug Fix** | 🐛 | Fixing issues and defects |
+| **[C] Design Exploration** | 🎨 | Exploring visual/UX directions |
+| **[D] Capture** | 💾 | Saving ideas for later |
+| **[E] Generic** | 📋 | Anything else |
+
+Type:</ask>
+
+<action>
+Store dialog_type and select appropriate template:
+- A → templates/dialog-types/prototype-implementation.template.md
+- B → templates/dialog-types/bug-fix.template.md
+- C → templates/dialog-types/design-exploration.template.md
+- D → templates/dialog-capture.template.md
+- E → templates/dialog.template.md
+</action>
+
+---
+
+## GATHER INFORMATION
+
+<ask>**What feature or implementation are we working on?**
+
+Examples:
+- "Booking details drawer"
+- "User authentication refactor"
+- "Calendar scroll fix"
+
+Feature name:</ask>
+
+<action>Store feature_name and generate feature_slug (lowercase, hyphenated)</action>
+
+<ask>**Which specification(s) are relevant?**
+
+Provide the path to the specification file(s) this implementation is based on.
+
+Specification path:</ask>
+
+<action>Store spec_path</action>
+
+<ask>**What agent persona should execute this work?**
+
+Examples:
+- "Freya (UX Designer)" — For UI implementation
+- "Dev Agent" — For backend work
+- "Full Stack" — For end-to-end features
+
+Agent:</ask>
+
+<action>Store agent_name</action>
+
+---
+
+## CREATE FOLDER STRUCTURE
+
+<action>
+**Create dialog folder:**
+
+Path: `docs/F-Agent-Dialogs/{date}-{agent_slug}-{feature_slug}/`
+
+Where:
+- `{date}` = Today's date in YYYY-MM-DD format
+- `{agent_slug}` = Agent name, lowercase (e.g., "freya", "saga", "dev")
+- `{feature_slug}` = Feature name, lowercase, hyphenated
+
+**Examples:**
+- `2026-01-23-freya-booking-details-overlay/`
+- `2026-01-23-saga-course-workflow-integration/`
+- `2026-01-23-dev-calendar-scroll-fix/`
+
+**Create subfolders:**
+- `steps/` — For step instruction files
+</action>
+
+---
+
+## CREATE DIALOG FILE
+
+<action>
+**Create main dialog file:**
+
+File: `docs/F-Agent-Dialogs/{date}-{agent_slug}-{feature_slug}/{date}-{agent_slug}-{feature_slug}-dialog.md`
+
+**Use template from:** Selected dialog type template (see SELECT DIALOG TYPE step above)
+
+**Fill in:**
+- Date: Today's date
+- Agent: {agent_name}
+- Feature: {feature_name}
+- Specification: Link to {spec_path}
+- Status: "In Progress"
+</action>
+
+---
+
+## GATHER SETUP CONTEXT
+
+<action>
+**Read the specification file(s)** to understand:
+- What needs to be implemented
+- What already exists
+- Technical requirements
+</action>
+
+<ask>**What's the tech stack for this project?**
+
+Example: "React 19, Next.js 15, TypeScript, Tailwind CSS, Supabase"
+
+Tech stack:</ask>
+
+<action>Store tech_stack</action>
+
+<ask>**What files are relevant to this implementation?**
+
+List the key files that will be modified or referenced.
+
+Relevant files:</ask>
+
+<action>Store relevant_files</action>
+
+<ask>**Are there any existing patterns to follow?**
+
+Describe component structure, styling approach, state management, etc.
+
+Patterns:</ask>
+
+<action>Store patterns</action>
+
+---
+
+## UPDATE DIALOG FILE
+
+<action>
+**Fill in Setup Context section:**
+
+- Project Context (tech stack)
+- Relevant Files (table)
+- Existing Patterns
+- Current State (what exists)
+
+**Fill in Purpose:**
+- 1-3 sentences describing what this dialog accomplishes
+</action>
+
+---
+
+## COMPLETION
+
+<output>
+✅ **Dialog initialized!**
+
+**Created:**
+- Folder: `docs/F-Agent-Dialogs/{date}-{agent_slug}-{feature_slug}/`
+- Dialog file: `{date}-{agent_slug}-{feature_slug}-dialog.md`
+- Steps folder: `steps/`
+
+**Next:** Proceed to Step 2 to analyze scope and create step breakdown.
+
+[A] Continue to Step 2: Analyze Scope
+[B] Review the dialog file first
+[C] Add more setup context
+
+Choice:
+</output>
+
+---
+
+## ROUTING
+
+<action>
+Based on user choice:
+- [A] → Load and execute step-02-analyze-scope.md
+- [B] → Show the dialog file contents
+- [C] → Ask for additional context to add
+</action>
+
+---
+
+_Agent Dialog Workflow — Step 1: Initialize Dialog_