whiteport-design-studio 0.2.2 → 0.3.0

package/src/workflows/1-project-brief/steps-v/{step-02-vtc-consistency.md → step-02-trigger-map-consistency.md}

@@ -1,6 +1,6 @@
 ---
-name: 'step-02-vtc-consistency'
-description: 'Verify Value Trigger Chain consistency and validity'
+name: 'step-02-trigger-map-consistency'
+description: 'Verify Trigger Map consistency and validity'
 
 # File References
 nextStepFile: './step-03-seo-strategy.md'
@@ -8,10 +8,10 @@ workflowFile: '../workflow.md'
 activityWorkflowFile: '../workflow-validate.md'
 ---
 
-# Validation Step 02: VTC Consistency
+# Validation Step 02: Trigger Map Consistency
 
 ## STEP GOAL:
-Verify the Value Trigger Chain(s) form a valid chain from business goals through personas to driving forces.
+Verify the Trigger Map(s) form a valid chain from business goals through personas to driving forces.
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
@@ -23,39 +23,39 @@ Verify the Value Trigger Chain(s) form a valid chain from business goals through
 - YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
-- You are a Strategic Business Analyst validating VTC chain integrity
+- You are a Strategic Business Analyst validating Trigger Map chain integrity
 - If you already have been given a name, communication_style and persona, continue to use those while playing this new role
 - We engage in collaborative dialogue, not command-response
 - You bring structured thinking and facilitation skills, user brings domain expertise and product vision
 - Maintain collaborative and strategic tone throughout
 
 ### Step-Specific Rules:
-- Focus: VTC completeness, chain validity, cross-VTC consistency
+- Focus: Trigger Map completeness, chain validity, cross-Trigger Map consistency
 - FORBIDDEN: Do not skip chain validity checks
-- Approach: Locate VTCs, check completeness, validate chains, check cross-VTC consistency
+- Approach: Locate Trigger Maps, check completeness, validate chains, check cross-Trigger Map consistency
 
 ## EXECUTION PROTOCOLS:
-- Primary goal: VTC consistency verified
+- Primary goal: Trigger Map consistency verified
 - Save/document outputs appropriately
 - Avoid generating content without user input
 
 ## CONTEXT BOUNDARIES:
-- Available context: VTC files and Product Brief
+- Available context: Trigger Map files and Product Brief
 - Focus: Chain validity and consistency
 - Limits: Validation only, not modification
 - Dependencies: Step 01 completed
 
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
 
-### 1. Locate VTC Files
+### 1. Locate Trigger Map Files
 
 Check for:
-- `{output_folder}/A-Product-Brief/vtc-primary.yaml` (Product Pitch VTC)
-- Any scenario-level VTCs in `{output_folder}/C-UX-Scenarios/`
+- `{output_folder}/B-Trigger-Map/00-trigger-map.md` (Trigger Map hub document)
+- Persona documents in `{output_folder}/B-Trigger-Map/`
 
-### 2. VTC Completeness
+### 2. Trigger Map Completeness
 
-For each VTC:
+For each Trigger Map:
 - [ ] `businessGoal` — specific and measurable
 - [ ] `solution` — describes how we help the user
 - [ ] `user` — identifies who we're helping
@@ -66,23 +66,23 @@ For each VTC:
 
 ### 3. Chain Validity
 
-- [ ] Business goal in VTC matches a goal in the Product Brief
-- [ ] User in VTC matches a target user in the Product Brief
+- [ ] Business goal in Trigger Map matches a goal in the Product Brief
+- [ ] User in Trigger Map matches a target user in the Product Brief
 - [ ] Driving forces are specific (not generic like "wants it to work")
 - [ ] Awareness journey makes logical sense (start ≠ end)
 
-### 4. Cross-VTC Consistency (if multiple)
+### 4. Cross-Trigger Map Consistency (if multiple)
 
-- [ ] No contradictory business goals across VTCs
+- [ ] No contradictory business goals across Trigger Maps
 - [ ] Users are distinct or represent different contexts
-- [ ] Driving forces don't duplicate across VTCs without reason
+- [ ] Driving forces don't duplicate across Trigger Maps without reason
 
 ### 5. Report
 
 ```
-## VTC Consistency Report
+## Trigger Map Consistency Report
 
-**VTCs found:** [N]
+**Trigger Maps found:** [N]
 **All complete:** [Yes/No]
 **Chain issues:** [N]
 
@@ -93,7 +93,7 @@ For each VTC:
 Display: "**Select an Option:** [C] Continue to next step"
 
 #### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
+- IF C: Load, read entire file, then execute {nextStepFile}
 - IF M: Return to {workflowFile} or {activityWorkflowFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
@@ -109,15 +109,15 @@ ONLY WHEN step objectives are met and user confirms will you then load and read
 ## SYSTEM SUCCESS/FAILURE METRICS
 
 ### SUCCESS:
-- All VTCs located and checked
-- Completeness verified for each VTC
+- All Trigger Maps located and checked
+- Completeness verified for each Trigger Map
 - Chain validity confirmed
-- Cross-VTC consistency checked (if multiple)
+- Cross-Trigger Map consistency checked (if multiple)
 - Consistency report generated
 
 ### FAILURE:
 - Skipped chain validity checks
-- Missed VTC files
-- Did not check cross-VTC consistency
+- Missed Trigger Map files
+- Did not check cross-Trigger Map consistency
 
 **Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/workflows/1-project-brief/steps-v/step-03-seo-strategy.md

@@ -67,7 +67,7 @@ Check if SEO/keyword content exists in the Content & Language document. If not,
 ### 3. Cross-Phase Readiness
 
 - [ ] Keyword map is in a format Phase 3 (Scenarios) can reference
-- [ ] SEO priorities align with user priorities from VTC
+- [ ] SEO priorities align with user priorities from Trigger Map
 - [ ] Content structure supports keyword targeting
 
 ### 4. Report
@@ -87,7 +87,7 @@ Check if SEO/keyword content exists in the Content & Language document. If not,
 Display: "**Select an Option:** [C] Continue to next step"
 
 #### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
+- IF C: Load, read entire file, then execute {nextStepFile}
 - IF M: Return to {workflowFile} or {activityWorkflowFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 

package/src/workflows/1-project-brief/steps-v/step-04-content-language.md

@@ -93,7 +93,7 @@ Check if Content & Language document exists at `{output_folder}/A-Product-Brief/
 Display: "**Select an Option:** [C] Continue to next step"
 
 #### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
+- IF C: Load, read entire file, then execute {nextStepFile}
 - IF M: Return to {workflowFile} or {activityWorkflowFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 

package/src/workflows/1-project-brief/steps-v/step-05-visual-direction.md

@@ -93,7 +93,7 @@ Check if Visual Direction document exists at `{output_folder}/A-Product-Brief/`.
 Display: "**Select an Option:** [C] Continue to next step"
 
 #### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
+- IF C: Load, read entire file, then execute {nextStepFile}
 - IF M: Return to {workflowFile} or {activityWorkflowFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 

package/src/workflows/1-project-brief/steps-v/step-06-platform-requirements.md

@@ -102,7 +102,7 @@ Compile results from all 6 validation steps:
 | Check | Status | Issues |
 |-------|--------|--------|
 | Brief Completeness | pass/warn/fail | [summary] |
-| VTC Consistency | pass/warn/fail | [summary] |
+| Trigger Map Consistency | pass/warn/fail | [summary] |
 | SEO Strategy | pass/warn/fail | [summary] |
 | Content & Language | pass/warn/fail | [summary] |
 | Visual Direction | pass/warn/fail | [summary] |

package/src/workflows/1-project-brief/templates/00-project-info.template.md

@@ -75,8 +75,7 @@ Read and activate the agent in `{{wds_folder}}/agents/[agent-name].md`
 ```
 
 **Available:**
-- **Mimir** — Orchestrator & Guide
-- **Saga** — Product Brief & Trigger Mapping
+- **Saga** — Product Brief, Trigger Mapping & Scenarios
 - **Idunn** — Platform Requirements & Design Deliveries
 - **Freya** — UX Design, Design System & Testing
 

package/src/workflows/1-project-brief/templates/pitch.template.md

@@ -68,22 +68,14 @@
 
 ---
 
-## Value Trigger Chain
-
-**Strategic Summary** - [View full VTC](./vtc-primary.yaml)
+## Business Context
 
 This project serves:
-- **Business Goal:** {{vtc_business_goal}}
-- **Solution:** {{vtc_solution}}
-- **Primary User:** {{vtc_user}}
-
-**What drives them:**
-- *Wants to:* {{vtc_positive_forces}}
-- *Wants to avoid:* {{vtc_negative_forces}}
-
-**Awareness Journey:** {{vtc_awareness_start}} → {{vtc_awareness_end}}
+- **Primary Goal:** {{business_goal}}
+- **Solution:** {{solution}}
+- **Target Users:** {{target_users}}
 
-This strategic chain ensures every design decision serves the user's psychology while achieving business goals.
+*Detailed strategic analysis (personas, driving forces, prioritization) is developed in Phase 2: Trigger Mapping.*
 
 ---
 

package/src/workflows/1-project-brief/templates/project-brief-dialog/USAGE.md

@@ -45,7 +45,7 @@ cp -r workflows/1-project-brief/templates/project-brief-dialog projects/{{slug}}
 **Each step file should mandate:**
 
 ```markdown
-## Agent Dialog Update
+## Design Log Update
 
 Before marking complete:
 1. Update `dialog/{{step}}-{{name}}.md`
@@ -62,105 +62,20 @@ All dialog files: 65-86 lines (well under 100-line target)
 
 ---
 
-## Agent Session Dialogs (Meta-Level)
+## Design Log (Meta-Level)
 
-**For multi-session work**, agents should maintain their own session dialog separate from project dialogs.
+**For multi-session work**, agents should use the design log for state tracking and `_progress/agent-experiences/` for session insights.
 
-**Location:** `{{root_folder}}/_progress/agent-dialogs/{{session-date}}-{{agent-name}}-{{task}}.md`
-
-**Structure Pattern:**
-
-```markdown
-# Agent Dialog: {{Task Name}}
-
-**Date:** {{date}}
-**Agent:** {{agent name}}
-**Project:** {{project name}}
-
----
-
-## CURRENT PLAN
-
-**{{Overall objective}}**
-
-1. ✅ Task 1 name
-2. ✅ Task 2 name
-3. ⏳ Task 3 name (in progress)
-4. ⬜ Task 4 name
-5. ⬜ Task 5 name
-
-**Ultimate Goal:** {{End state description}}
-
----
-
-## ⏳ CURRENT WORK
-
-### Task 3: {{Task name}}
-
-**Objective:** {{What you're doing now}}
-
-**Sub-tasks:**
-- {{Specific thing 1}}
-- {{Specific thing 2}}
-- {{Specific thing 3}}
-
-**Status:** {{Current status}}
-
----
-
-## 🎯 UPCOMING WORK
-
-### Task 4: {{Next task}}
-
-**Purpose:** {{Why this matters}}
-
-**Implementation:** {{How you'll do it}}
-
----
-
-## ✅ COMPLETED WORK
-
-*(Reverse chronological order - latest first)*
-
----
-
-### Task 2: {{Task name}} ({{date}})
-
-**Objective:** {{What was done}}
-
-**Key achievements:**
-- {{Achievement 1}}
-- {{Achievement 2}}
-
-**Files modified:** {{File count and names}}
-
-**Status:** Complete
-
----
-
-### Task 1: {{Task name}} ({{date}})
-
-**Objective:** {{What was done}}
-
-[Details...]
-```
-
-**Navigation Benefits:**
-- Easy to see progress at a glance
-- Clear separation: current vs upcoming vs completed
-- Latest work always at top of completed section
-- Ultimate goal always visible
+**Location:** `{{root_folder}}/_progress/00-design-log.md`
 
 **Update Protocol:**
 1. Complete current task
-2. Update agent dialog with changes
+2. Update design log with changes
 3. Show git diff to user
-4. Move task from CURRENT WORK to top of COMPLETED WORK
-5. Move next task from UPCOMING WORK to CURRENT WORK
-6. Update CURRENT PLAN checkboxes (✅/⏳/⬜)
+4. Record session insights in `_progress/agent-experiences/` if needed
 
 ---
 
 ## Purpose
 
-Create transparent record of discovery conversations so future agents (and humans) understand WHY decisions were made, not just WHAT was decided.
+Create transparent record of discovery conversations so future agents (and humans) understand WHY decisions were made, not just WHAT was decided. The design log provides this continuity across sessions.

package/src/workflows/1-project-brief/templates/project-brief.template.md

@@ -162,19 +162,13 @@
 
 ---
 
-## Value Trigger Chain
+## Business Context
 
-**Strategic Summary** - [View full VTC](./vtc-primary.yaml)
+- **Primary Goal:** {{business_goal}}
+- **Solution:** {{solution}}
+- **Target Users:** {{target_users}}
 
-- **Business Goal:** {{vtc_business_goal}}
-- **Solution:** {{vtc_solution}}
-- **User:** {{vtc_user}}
-- **Driving Forces:**
-  - *Wants to:* {{vtc_positive_forces}}
-  - *Wants to avoid:* {{vtc_negative_forces}}
-- **Awareness Journey:** {{vtc_awareness_start}} → {{vtc_awareness_end}}
-
-This VTC provides quick strategic reference and will inform all design decisions.
+*Full strategic analysis (business goals, personas, driving forces) is developed in [Phase 2: Trigger Mapping](../B-Trigger-Map/).*
 
 ---
 

package/src/workflows/1-project-brief/workflow-validate.md

@@ -11,11 +11,9 @@ description: 'Verify all Product Brief artifacts are complete, consistent, and r
 
 ## INITIALIZATION
 
-### Agent Dialog Gate
+### Design Log
 
-1. Check for pending activity dialogs
-2. If none, suggest creating one
-3. Load dialog context
+Read `{output_folder}/_progress/00-design-log.md` before starting.
 
 ### Configuration Loading
 
@@ -32,7 +30,7 @@ Execute each step in order. Each step produces a section of the final validation
 | Step | Name | Validates |
 |------|------|-----------|
 | 01 | Brief Completeness | All required sections present and filled |
-| 02 | VTC Consistency | Goals → personas → forces chain is valid |
+| 02 | Trigger Map Consistency | Goals → personas → forces chain is valid |
 | 03 | SEO Strategy | Keyword map complete, page assignments clear |
 | 04 | Content & Language | Tone, personality, guidelines coherent |
 | 05 | Visual Direction | Brand, style, references documented |

package/src/workflows/1-project-brief/workflow.md

@@ -34,11 +34,9 @@ Load and read full config from `{project-root}/_bmad/wds/config.yaml` and resolv
 - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
 - `brief_level` from `{output_folder}/wds-workflow-status.yaml:config.brief_level`
 
-### 2. Agent Dialog Gate
+### 2. Design Log
 
-1. Check `{output_folder}/_progress/agent-dialogs/` for pending project brief dialogs
-2. If pending, present with status
-3. If none, suggest creating one
+Read `{output_folder}/_progress/00-design-log.md`. Check Current and Backlog for context.
 
 ### 3. Mode Determination
 
@@ -64,7 +62,6 @@ Based on `brief_level`:
 | 01 | Init | Load context, confirm readiness |
 | 02 | Vision | Explore and document project vision |
 | 03 | Positioning | Define market positioning |
-| 04 | Create VTC | Value Trigger Chain (refs `vtc-workshop/`) |
 | 05 | Business Model | Define revenue/business model |
 | 06 | Business Customers | Identify B2B customers (if applicable) |
 | 07 | Target Users | Define end users |
@@ -74,15 +71,14 @@ Based on `brief_level`:
 | 10 | Constraints | Document project constraints |
 | 10a | Platform Strategy | Define platform approach |
 | 11 | Tone of Voice | Establish brand voice |
-| 11a | Create VTC | Second VTC opportunity (refs `vtc-workshop/`) |
-| 12 | Synthesize | Create the Product Brief document |
+| 12 | Create Product Brief | Generate the Product Brief document |
 | 13 | Content Init | Initialize content & language strategy |
 | 14 | Personality | Define brand personality |
 | 15 | Tone | Refine tone guidelines |
 | 16 | Languages | Language strategy |
 | 17 | SEO Keywords | Define keyword map |
 | 17a | Content Structure | Content architecture |
-| 18 | Content Synthesize | Create Content & Language document |
+| 18 | Create Content Document | Generate Content & Language document |
 | 19 | Inspiration Workshop | Analyze reference sites |
 | 20 | Visual Init | Initialize visual direction |
 | 21 | Existing Brand | Document existing brand assets |
@@ -90,13 +86,13 @@ Based on `brief_level`:
 | 23 | Design Style | Define design style |
 | 24 | Layout & Effects | Layout patterns and effects |
 | 25 | Imagery | Photography and illustration direction |
-| 26 | Visual Synthesize | Create Visual Direction document |
+| 26 | Create Visual Document | Generate Visual Direction document |
 | 27 | Platform Init | Initialize platform requirements |
 | 28 | Tech Stack | Define technology choices |
 | 29 | Integrations | Third-party integrations |
 | 30 | Contact Strategy | Contact forms and communication |
 | 31 | Multilingual | Multi-language setup |
-| 32 | Platform Synthesize | Create Platform Requirements document |
+| 32 | Create Platform Document | Generate Platform Requirements document |
 | 33 | Analyze Brief | Review all Phase 1 artifacts |
 | 34 | Create Summary | Generate handover summary |
 | 35 | Update Design Log | Record Phase 1 decisions |

package/src/workflows/2-trigger-mapping/steps-c/step-01-overview.md

@@ -37,7 +37,7 @@ Present Phase 2: Trigger Mapping overview, offer engagement mode selection (Work
 - 🚫 FORBIDDEN to skip mode selection or auto-choose for user
 - 💬 Approach: Clear presentation of three modes with time estimates
 - 📋 Workshop mode proceeds through step-by-step facilitation
-- 📋 Suggest and Dream modes use the dream-up-approach with agent dialog tracking
+- 📋 Suggest and Dream modes use the dream-up-approach with design log tracking
 
 ## EXECUTION PROTOCOLS:
 
@@ -88,9 +88,9 @@ If One at a time: Run Workshop 1, then offer to save and continue later.
 **If Suggest (S) or Dream (D):**
 Output: "{{mode}} selected. I'll generate the Trigger Map using WDS methodology + Product Brief + domain research."
 
-Inform user: "I'm creating an agent dialog to track my learning, research, generation, and self-review process."
+Inform user: "I'm creating a design log to track my learning, research, generation, and self-review process."
 
-Create agent dialog using ../../_agent-dialogs/templates/dream-up-agent-dialog.template.md at {output_folder}/_progress/agent-dialogs/{date}-trigger-map-{{mode}}.md
+Create session log at {output_folder}/_progress/agent-experiences/{date}-trigger-map-{{mode}}.md
 
 Execute Layer 1: Learn WDS Form (Static - loaded once)
 - Read docs/method/phase-2-trigger-mapping-guide.md
@@ -99,7 +99,7 @@ Execute Layer 1: Learn WDS Form (Static - loaded once)
 - Read docs/models/impact-effect-mapping.md
 - Read docs/method/dream-up-rubric-phase-2.md
 - Internalize: Structure, quality criteria, common mistakes, best practices
-- Document in agent dialog "Layer 1: WDS Form Learned" section
+- Document in design log "Layer 1: WDS Form Learned" section
 
 Execute Layer 2: Project Context (Initial load, grows with each step)
 - Read {output_folder}/A-Product-Brief/product-brief.md
@@ -107,7 +107,7 @@ Execute Layer 2: Project Context (Initial load, grows with each step)
 - Read {output_folder}/A-Product-Brief/platform-requirements.md
 - Read {output_folder}/A-Product-Brief/visual-direction.md
 - Extract: business context, user archetypes, constraints, strategic direction
-- Document in agent dialog "Layer 2: Project Context (Initial)" section
+- Document in design log "Layer 2: Project Context (Initial)" section
 - NOTE: Layer 2 grows cumulatively - add Business Goals, Target Groups, Driving Forces, Prioritization as created
 
 For EACH step (Business Goals, Target Groups, Driving Forces, Prioritization):
@@ -115,7 +115,7 @@ For EACH step (Business Goals, Target Groups, Driving Forces, Prioritization):
   Execute Layer 3: Domain Research (per step)
   - WebSearch relevant to current step
   - Look for industry insights, user reviews, behavioral patterns
-  - Document findings in agent dialog
+  - Document findings in design log
 
   Execute Layer 4: Generate
   - Apply WDS Form (Layer 1) with ALL Project Context (Layer 2 cumulative)
@@ -125,7 +125,7 @@ For EACH step (Business Goals, Target Groups, Driving Forces, Prioritization):
   Execute Layer 5: Self-Review
   - Check against rubric (completeness, quality, mistakes, practices)
   - Calculate quality score, identify gaps
-  - Document in agent dialog
+  - Document in design log
 
   If gaps exist: Create refinement plan, regenerate (max 5 iterations per step)
 
@@ -140,7 +140,7 @@ When all steps complete:
 - Create persona documents if needed
 - Create mermaid diagram if generated
 - Present final output to user
-- Update agent dialog with final output section
+- Update design log with final output section
 
 Skip to handover after generation complete.
 
@@ -171,7 +171,7 @@ ONLY WHEN user selects [C] will you load the next step file. Mode must be select
 - User explicitly selected a mode
 - Correct path activated based on selection
 - Workshop sub-choice (All/One) offered if Workshop mode selected
-- Suggest/Dream modes properly initialize agent dialog and layered approach
+- Suggest/Dream modes properly initialize design log and layered approach
 - User confirmed and ready to proceed
 
 ### ❌ SYSTEM FAILURE:
@@ -179,7 +179,7 @@ ONLY WHEN user selects [C] will you load the next step file. Mode must be select
 - Not presenting all three mode options
 - Not explaining what each mode involves
 - Proceeding without explicit user selection
-- Not initializing agent dialog for Suggest/Dream modes
+- Not initializing design log for Suggest/Dream modes
 - Skipping the layered approach for autonomous modes
 
 **Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/workflows/2-trigger-mapping/steps-c/step-07a-generate-hub.md

@@ -55,6 +55,32 @@ Create the main entry point document (00-trigger-map.md) with Mermaid diagram, o
 
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
 
+### 0. Data Extraction (MANDATORY BEFORE GENERATION)
+
+Before generating ANY content, extract structured data from all workshop outputs:
+
+**Read and extract from workshop data:**
+
+1. **From Business Goals workshop:**
+   - `vision_statement` = exact vision text (character-for-character)
+   - `objectives[]` = each SMART objective with metric, target, timeline
+
+2. **From Target Groups workshop:**
+   - `target_groups[]` = each group with name, priority, persona summary
+   - `positive_drivers[]` per group (specific wants)
+   - `negative_drivers[]` per group (specific fears)
+
+3. **From Prioritization workshop:**
+   - `focus_statement` = strategic focus
+   - `top_group` = primary design target
+   - `must_address_drivers[]` and `should_address_drivers[]`
+
+**Store these as variables. When filling the hub document, use EXACT values from these variables. Do NOT paraphrase or summarize workshop outputs.**
+
+**Validation rule:** Vision statement in the hub MUST be character-for-character identical to the vision from Business Goals workshop. If you cannot find the exact text, ask the user rather than inventing a paraphrase.
+
+---
+
 ### 1. Generate Header Section
 
 Create header with project name, date, author, and methodology credit.
@@ -97,6 +123,16 @@ Explain diagram reading: left-to-right flow, top-to-bottom priority, driving for
 
 Include WDS framework credit and Effect Mapping methodology credits.
 
+### 6b. Cross-Validation Check
+
+Before saving, verify data consistency:
+- [ ] Vision in hub matches vision from Business Goals workshop exactly
+- [ ] Persona names in hub match names used in individual persona documents
+- [ ] Driver count in Mermaid diagram matches drivers in per-persona workshop outputs
+- [ ] Priority ordering in hub matches prioritization workshop output
+
+If any mismatch found: correct the hub document to match the source workshop data.
+
 ### 7. Save and Confirm
 
 Store as: 00-trigger-map.md in trigger map folder.

package/src/workflows/2-trigger-mapping/steps-c/step-09a-finalize-hub.md

@@ -66,9 +66,25 @@ This will create all documents following the standard trigger map structure:
 - `05-Key-Insights.md`
 - `06-Feature-Impact.md` (if workshop was run)
 
-### 2. Confirm Generation Complete
+### 2. Confirm Generation Complete (Completeness Gate)
 
-Verify all documents have been generated and saved.
+Verify ALL required documents have been generated:
+
+**Mandatory files in `{output_folder}/B-Trigger-Map/`:**
+- [ ] `00-trigger-map.md` — Hub document with Mermaid diagram
+- [ ] `01-Business-Goals.md` — Vision + SMART objectives
+- [ ] One persona document per target group (`02-XX.md`, `03-XX.md`, etc.)
+- [ ] `05-Key-Insights.md` — Strategic insights summary
+
+**Conditional files:**
+- [ ] `06-Feature-Impact.md` — Only if feature impact workshop was completed
+
+**Validation rules:**
+- Each file must be non-empty (contains actual content, not just headers)
+- Hub document must contain a Mermaid code block
+- Persona count must match the number of target groups from workshops
+
+**If any file is missing:** Generate the missing file before proceeding. Do NOT skip.
 
 ### 3. Present MENU OPTIONS
 

package/src/workflows/2-trigger-mapping/steps-c/step-09e-update-design-log.md

@@ -42,7 +42,7 @@ Document Phase 2: Trigger Mapping completion in the project design log, listing
 ## EXECUTION PROTOCOLS:
 
 - 🎯 Read current design log and append progress entry
-- 💾 Update {output_folder}/_progress/00-progress.md
+- 💾 Update {output_folder}/_progress/00-design-log.md
 - 📖 List all artifacts and key decisions specifically
 - 🚫 Do not overwrite existing entries
 
@@ -57,7 +57,7 @@ Document Phase 2: Trigger Mapping completion in the project design log, listing
 
 ### 1. Read Current Log
 
-Read `{output_folder}/_progress/00-progress.md` to understand existing entries and format.
+Read `{output_folder}/_progress/00-design-log.md` to understand existing entries and format.
 
 ### 2. Append Progress Entry
 
@@ -106,7 +106,7 @@ If no significant decisions were made, skip this section.
 - Summary is specific, not generic
 - Key decisions recorded (if any)
 
-Output: "Design log updated. Phase 2: Trigger Mapping documented in _progress/00-progress.md"
+Output: "Design log updated. Phase 2: Trigger Mapping documented in _progress/00-design-log.md"
 
 ### 5. Present MENU OPTIONS
 

package/src/workflows/2-trigger-mapping/workflow-validate.md

@@ -15,11 +15,8 @@ validateWorkflow: './steps-v/step-01-target-group-coverage.md'
 
 ## INITIALIZATION
 
-### Agent Dialog Gate
-
-1. Check for pending activity dialogs
-2. If none, suggest creating one
-3. Load dialog context
+### Design Log
+Read `{output_folder}/_progress/00-design-log.md`. Check Current and Backlog for context.
 
 ### Configuration Loading