whiteport-design-studio 0.1.0

package/src/workflows/workflow-init/methodology-instructions/methodology-guide.md

@@ -0,0 +1,252 @@
+# Methodology Instructions
+
+This folder contains micro-instruction files for different WDS methodologies.
+
+## Available Methodologies
+
+### 1. WDS v6 (Default)
+
+**File**: `wds-v6-instructions.md`  
+**Structure**: Numbered phases (1-8)  
+**Use for**: New projects, modern workflow
+
+```yaml
+methodology:
+  type: 'wds-v6'
+```
+
+**Phases**:
+
+- 1-project-brief
+- 2-trigger-mapping
+- 3-prd-platform
+- 4-ux-design
+- 5-design-system
+- 6-design-deliveries
+- 7-testing
+- 8-ongoing-development
+
+---
+
+### 2. WPS2C v4 (Legacy)
+
+**File**: `wps2c-v4-instructions.md`  
+**Structure**: Letter-based phases (A-G)  
+**Use for**: Existing v4 projects, backward compatibility
+
+```yaml
+methodology:
+  type: 'wps2c-v4'
+```
+
+**Phases**:
+
+- A-Product-Brief
+- B-Trigger-Map
+- C-Scenarios
+- D-Design-System
+- E-PRD (or D-PRD)
+- F-Testing (optional)
+- G-Product-Development (optional)
+
+---
+
+### 3. Custom Methodology
+
+**File**: `custom-methodology-template.md` (copy and adapt)  
+**Structure**: Your own!  
+**Use for**: Specialized workflows, team preferences
+
+```yaml
+methodology:
+  type: 'custom'
+  instructions_file: 'docs/.custom-methodology.md'
+```
+
+**Examples**:
+
+- Lean Startup (Build-Measure-Learn)
+- Design Sprint (Mon-Fri)
+- Shape Up (Pitch-Bet-Shape-Build-Cool down)
+- JTBD (Jobs-to-Be-Done)
+
+---
+
+## How Agents Use These Files
+
+### On Project Initiation (Saga)
+
+1. Ask user which methodology they want
+2. Set `methodology.type` in project outline
+3. Link to appropriate instructions file
+4. Walk through phases asking user intentions
+
+### On Agent Activation (All Agents)
+
+1. Read project outline
+2. Check `methodology.type`
+3. Load appropriate instructions
+4. Follow methodology-specific behavior:
+   - Folder naming conventions
+   - Phase structure
+   - Deliverable expectations
+
+### Example Flow
+
+**User starts new project:**
+
+```
+Saga: "Which methodology would you like to use?
+1. WDS v6 (recommended for new projects)
+2. WPS2C v4 (if you prefer the legacy structure)
+3. Custom (define your own workflow)
+
+User: "WDS v6"
+
+Saga: ✅ Setting up WDS v6 methodology
+      Creating project outline with numbered phases (1-8)...
+```
+
+---
+
+## Creating a Custom Methodology
+
+### Step 1: Copy Template
+
+```bash
+cp custom-methodology-template.md /path/to/your/project/docs/.custom-methodology.md
+```
+
+### Step 2: Define Your Phases
+
+Edit `.custom-methodology.md`:
+
+- List all phases
+- Assign agents
+- Define deliverables
+- Specify folder names
+
+### Step 3: Update Project Outline
+
+```yaml
+methodology:
+  type: 'custom'
+  instructions_file: 'docs/.custom-methodology.md'
+
+phases:
+  phase_1_product_brief:
+    folder: '{{YOUR_PHASE_1_FOLDER}}'
+    name: '{{YOUR_PHASE_1_NAME}}'
+```
+
+### Step 4: Agents Adapt Automatically
+
+WDS agents will:
+
+- Read your custom instructions
+- Follow your folder naming
+- Adapt their behavior
+- Ask clarifying questions if needed
+
+---
+
+## Methodology Comparison
+
+| Feature            | WDS v6         | WPS2C v4        | Custom          |
+| ------------------ | -------------- | --------------- | --------------- |
+| **Folder Naming**  | Numbered (1-8) | Letter (A-G)    | Your choice     |
+| **Flexibility**    | High           | Medium          | Unlimited       |
+| **Legacy Support** | N/A            | Full v4 support | Varies          |
+| **Phase Count**    | 8 (flexible)   | 5-7 (fixed)     | Unlimited       |
+| **Learning Curve** | Low            | Low (familiar)  | Depends         |
+| **Agent Support**  | Full           | Full            | Adapt as needed |
+
+---
+
+## Best Practices
+
+### For New Projects
+
+✅ **Use WDS v6** - modern, flexible, full featured
+
+### For Existing v4 Projects
+
+✅ **Use WPS2C v4** - no migration needed, agents support it fully
+
+### For Specialized Workflows
+
+✅ **Use Custom** - if you have specific team processes or industry requirements
+
+### Don't
+
+❌ Switch methodologies mid-project (unless you have a good reason)  
+❌ Create custom methodology without documenting thoroughly  
+❌ Mix naming conventions within a single project
+
+---
+
+## Migration Paths
+
+### v4 → v6
+
+If you want to migrate an existing WPS2C v4 project to WDS v6:
+
+1. **Update project outline**:
+
+```yaml
+methodology:
+  type: 'wds-v6'
+```
+
+2. **Rename folders**:
+
+```bash
+A-Product-Brief → 1-project-brief
+B-Trigger-Map → 2-trigger-mapping
+C-Scenarios → 4-ux-design
+D-Design-System → 5-design-system
+E-PRD → 6-design-deliveries
+```
+
+3. **Consolidate** (optional):
+
+```bash
+C-Platform-Requirements → merge into 3-prd-platform
+```
+
+**Note**: Migration is optional. Agents work with v4 structure indefinitely.
+
+---
+
+## Files in This Folder
+
+```
+methodology-instructions/
+├── README.md                      ← You are here
+├── wds-v6-instructions.md         ← WDS v6 methodology
+├── wps2c-v4-instructions.md       ← WPS2C v4 backward compatibility
+└── custom-methodology-template.md ← Template for custom workflows
+```
+
+---
+
+## Support
+
+### Questions About Methodologies?
+
+- Ask **Saga WDS Analyst Agent** during project initiation
+- Reference methodology instructions file during any phase
+- Agents adapt automatically based on `methodology.type`
+
+### Custom Methodology Help?
+
+- Start with `custom-methodology-template.md`
+- Base it on WDS v6 or WPS2C v4
+- Document thoroughly for your team
+- Test with one project first
+
+---
+
+**Last Updated**: 2024-12-10  
+**Part of**: WDS v6 (Whiteport Design Studio)  
+**Folder**: `src/modules/wds/workflows/workflow-init/methodology-instructions/`

package/src/workflows/workflow-init/methodology-instructions/wds-v6-instructions.md

@@ -0,0 +1,221 @@
+# WDS v6 Methodology Instructions
+
+# Numbered workflow phases with modern structure
+
+## Phase Structure
+
+WDS v6 uses **numbered phases** for clarity and flexibility:
+
+```
+1-project-brief/       → Phase 1: Product Brief
+2-trigger-mapping/     → Phase 2: Trigger Mapping
+3-prd-platform/        → Phase 3: PRD Platform
+4-ux-design/           → Phase 4: UX Design (Scenarios)
+5-design-system/       → Phase 5: Design System
+6-design-deliveries/   → Phase 6: Design Deliveries
+7-testing/             → Phase 7: Testing
+8-ongoing-development/ → Phase 8: Ongoing Development
+```
+
+---
+
+## Phase Details
+
+### Phase 1: Project Brief (Required)
+
+**Agent**: Saga WDS Analyst Agent  
+**Folder**: `docs/1-project-brief/`  
+**Deliverables**:
+
+- Product vision and positioning
+- Goals and success criteria
+- Project constraints and assumptions
+- Project outline (`.wds-project-outline.yaml`)
+
+**Brief Levels**:
+
+- `complete`: Full brief with stakeholder interviews
+- `simplified`: 5-10 minute brief for simple projects
+
+---
+
+### Phase 2: Trigger Mapping (Optional)
+
+**Agent**: Saga WDS Analyst Agent  
+**Folder**: `docs/2-trigger-mapping/`  
+**Deliverables**:
+
+- Target groups
+- User personas
+- Business goals
+- Trigger map
+- Feature impact analysis
+
+**Skip if**: Internal tools, technical products with no end users
+
+---
+
+### Phase 3: PRD Platform (Required)
+
+**Agent**: Idunn WDS PM Agent  
+**Folder**: `docs/3-prd-platform/`  
+**Deliverables**:
+
+- Technical architecture
+- Data model
+- Platform requirements
+- Integration specifications
+- Infrastructure needs
+
+---
+
+### Phase 4: UX Design (Required)
+
+**Agent**: Freya WDS Designer Agent  
+**Folder**: `docs/4-ux-design/`  
+**Deliverables**:
+
+- Scenario overview documents
+- Page specifications with object IDs
+- Interactive prototypes (Excalidraw/HTML)
+- User flow diagrams
+- Content in multiple languages
+
+**Structure**:
+
+```
+4-ux-design/
+├── 01-scenario-name/
+│   ├── 00-scenario-overview.md
+│   ├── 1.1-page-name.md
+│   ├── 1.2-page-name.md
+│   └── sketches/
+│       ├── 1.1-page-name.excalidraw
+│       └── 1.1-page-name-prototype.html
+```
+
+**Scenario Tracking**: Each scenario tracked in project outline with status
+
+---
+
+### Phase 5: Design System (Optional)
+
+**Agent**: Freya WDS Designer Agent  
+**Folder**: `docs/5-design-system/`  
+**Deliverables**:
+
+- Design tokens (colors, typography, spacing)
+- Component documentation (atoms, molecules, organisms)
+- HTML showcases
+- Figma integration (if applicable)
+
+**Skip if**:
+
+- Using existing library (shadcn/ui, MUI, Radix)
+- Single-product MVP
+- One-off pages/simple projects
+
+---
+
+### Phase 6: Design Deliveries (Optional)
+
+**Agent**: Idunn WDS PM Agent  
+**Folder**: `docs/6-design-deliveries/`  
+**Deliverables**:
+
+- Complete PRD
+- Implementation roadmap
+- Handoff package for development
+- Epic and story breakdowns
+
+**Skip if**: Direct implementation from specs (no handoff needed)
+
+---
+
+### Phase 7: Testing (Optional)
+
+**Agent**: Freya WDS Designer Agent  
+**Folder**: `docs/7-testing/`  
+**Deliverables**:
+
+- Test scenarios
+- Visual regression tests
+- Implementation validation reports
+- Comparison: specs vs. built product
+
+---
+
+### Phase 8: Ongoing Development (Optional)
+
+**Agent**: Idunn WDS PM Agent  
+**Folder**: `docs/8-ongoing-development/`  
+**Deliverables**:
+
+- Feature enhancement requests
+- Optimization recommendations
+- Evolution roadmap
+
+**Active only for**: Existing products in maintenance phase
+
+---
+
+## Folder Naming Convention
+
+WDS v6 uses **numbered prefixes** for phases:
+
+- `1-project-brief/`
+- `2-trigger-mapping/`
+- `4-ux-design/` (scenarios go here)
+
+Benefits:
+
+- Clear ordering
+- Flexible (can add phases)
+- Modern structure
+- Aligns with workflow numbering
+
+---
+
+## Project Outline Fields
+
+For WDS v6 projects, use these folder names in the outline:
+
+```yaml
+methodology:
+  type: 'wds-v6'
+
+phases:
+  phase_1_project_brief:
+    folder: '1-project-brief'
+  phase_2_trigger_mapping:
+    folder: '2-trigger-mapping'
+  phase_3_prd_platform:
+    folder: '3-prd-platform'
+  phase_4_ux_design:
+    folder: '4-ux-design'
+  phase_5_design_system:
+    folder: '5-design-system'
+  phase_6_design_deliveries:
+    folder: '6-design-deliveries'
+  phase_7_testing:
+    folder: '7-testing'
+  phase_8_ongoing_development:
+    folder: '8-ongoing-development'
+```
+
+---
+
+## Agent Behavior
+
+When agents detect `methodology.type: "wds-v6"`:
+
+- Use numbered folder names
+- Follow 8-phase structure
+- Apply modern WDS v6 workflows
+- Use scenario-based UX design in Phase 4
+
+---
+
+**Version**: 1.0  
+**Last Updated**: 2024-12-10  
+**Part of**: WDS v6 (Whiteport Design Studio)

package/src/workflows/workflow-init/methodology-instructions/wps2c-v4-instructions.md

@@ -0,0 +1,231 @@
+# WPS2C v4 Methodology Instructions
+
+# Letter-based phases from Whiteport Sketch-to-Code v4
+
+## Phase Structure
+
+WPS2C v4 uses **letter-based phases** (alphabetical ordering):
+
+```
+A-Product-Brief/         → Phase A: Product Brief
+B-Trigger-Map/           → Phase B: Trigger Map
+C-Scenarios/             → Phase C: Scenarios (UX Design)
+D-Design-System/         → Phase D: Design System
+D-PRD/ or E-PRD/         → Phase E: PRD (optional)
+F-Testing/               → Phase F: Testing (if exists)
+G-Product-Development/   → Phase G: Ongoing Development (if exists)
+```
+
+**Note**: Original WPS2C v4 had some projects with `D-PRD/` and others with `E-PRD/`. This is a known variation in v4 structure.
+
+---
+
+## Phase Details
+
+### Phase A: Product Brief (Required)
+
+**Agent**: Saga WDS Analyst Agent  
+**Folder**: `docs/A-Product-Brief/`  
+**Deliverables**:
+
+- `00-Product-Brief.md` or `01-Product-Brief.md`
+- Product vision and positioning
+- Goals and success criteria
+
+**Note**: v4 typically uses simpler brief structure than v6
+
+---
+
+### Phase B: Trigger Map (Optional)
+
+**Agent**: Saga WDS Analyst Agent  
+**Folder**: `docs/B-Trigger-Map/`  
+**Deliverables**:
+
+- Target groups
+- User personas (alliterative names)
+- Trigger map with business goals
+- Feature impact analysis
+
+**Skip if**: Internal tools
+
+---
+
+### Phase C: Scenarios (Required)
+
+**Agent**: Freya WDS Designer Agent  
+**Folder**: `docs/C-Scenarios/`  
+**Deliverables**:
+
+- Scenario folders (01-_, 02-_, etc.)
+- Page specifications with object IDs
+- Sketches (Excalidraw or paper)
+- Interactive prototypes
+
+**Structure** (same as WDS v6):
+
+```
+C-Scenarios/
+├── 01-scenario-name/
+│   ├── 00-scenario-overview.md
+│   ├── 1.1-page-name.md
+│   └── Sketches/
+│       └── 1.1-page-name.excalidraw
+```
+
+**Key Difference from v6**: Folder is `C-Scenarios/` instead of `4-ux-design/`
+
+---
+
+### Phase D: Design System (Optional)
+
+**Agent**: Freya WDS Designer Agent  
+**Folder**: `docs/D-Design-System/`  
+**Deliverables**:
+
+- Design tokens
+- Component library
+- HTML showcases
+
+**Skip if**: Using component library
+
+---
+
+### Phase E: PRD (Optional)
+
+**Agent**: Idunn WDS PM Agent  
+**Folder**: `docs/E-PRD/` or `docs/D-PRD/` (varies by project)  
+**Deliverables**:
+
+- Complete PRD document
+- Epic and story breakdowns
+- Implementation roadmap
+
+**Note**: Some v4 projects use `D-PRD/`, others `E-PRD/`. Check existing structure.
+
+---
+
+### Phase F: Testing (Optional)
+
+**Agent**: Freya WDS Designer Agent  
+**Folder**: `docs/F-Testing/` (if exists)  
+**Deliverables**:
+
+- Test scenarios
+- Implementation validation
+
+---
+
+### Phase G: Product Development (Optional)
+
+**Agent**: Idunn WDS PM Agent  
+**Folder**: `docs/G-Product-Development/` (if exists)  
+**Deliverables**:
+
+- Ongoing enhancement tracking
+
+---
+
+## Platform Requirements
+
+**WPS2C v4** often includes:
+
+- `C-Platform-Requirements/` - Technical foundation separate from scenarios
+
+In some projects, this exists alongside `C-Scenarios/`. Agents should check for both.
+
+---
+
+## Folder Naming Convention
+
+WPS2C v4 uses **letter prefixes**:
+
+- `A-Product-Brief/`
+- `B-Trigger-Map/`
+- `C-Scenarios/`
+- `D-Design-System/`
+
+Benefits:
+
+- Clear alphabetical progression
+- Established pattern (many existing projects)
+- Compatible with legacy WPS2C workflows
+
+Limitations:
+
+- Less flexible (A-Z limit)
+- Some confusion with D-PRD vs E-PRD
+
+---
+
+## Project Outline Fields
+
+For WPS2C v4 projects, use these folder names:
+
+```yaml
+methodology:
+  type: 'wps2c-v4'
+
+phases:
+  phase_1_product_brief:
+    folder: 'A-Product-Brief'
+  phase_2_trigger_mapping:
+    folder: 'B-Trigger-Map'
+  phase_3_prd_platform:
+    folder: 'C-Platform-Requirements' # If exists
+  phase_4_ux_design:
+    folder: 'C-Scenarios'
+  phase_5_design_system:
+    folder: 'D-Design-System'
+  phase_6_design_deliveries:
+    folder: 'E-PRD' # or "D-PRD" - check existing structure
+  phase_7_testing:
+    folder: 'F-Testing' # if exists
+  phase_8_ongoing_development:
+    folder: 'G-Product-Development' # if exists
+```
+
+---
+
+## Agent Behavior
+
+When agents detect `methodology.type: "wps2c-v4"`:
+
+- Use letter-based folder names
+- Look for both `C-Platform-Requirements/` and `C-Scenarios/`
+- Check for `D-PRD/` vs `E-PRD/` variation
+- Follow WPS2C v4 workflows
+- Fetch additional instructions from WPS2C GitHub if needed
+
+---
+
+## Migration to WDS v6
+
+To migrate a WPS2C v4 project to WDS v6:
+
+1. Update project outline: `methodology.type: "wds-v6"`
+2. Rename folders (A→1, B→2, C-Scenarios→4-ux-design)
+3. Consolidate `C-Platform-Requirements/` into `3-prd-platform/`
+4. Standardize PRD folder naming
+
+Agents can work with v4 structure without migration.
+
+---
+
+## Legacy Support
+
+WDS v6 agents fully support WPS2C v4 projects:
+
+- ✅ Read v4 folder structure
+- ✅ Apply v4 naming conventions
+- ✅ Fetch v4-specific instructions when needed
+- ✅ No migration required
+
+Users can continue using v4 methodology indefinitely.
+
+---
+
+**Version**: 1.0  
+**Last Updated**: 2024-12-10  
+**Based on**: Whiteport Sketch-to-Code BMAD v4  
+**Part of**: WDS v6 backward compatibility