whiteport-design-studio 0.2.2 → 0.3.0

package/src/workflows/0-project-setup/templates/folder-guides/00-design-system.template.md

@@ -87,9 +87,158 @@ D-Design-System/
 
 ---
 
+## Spacing Scale
+
+> **Bring your own or use ours.** If your project already has a design system with a spacing scale (Tailwind, Material, Carbon, your own tokens), use that. Map your token names below so page specs reference them consistently. If you don't have one yet, WDS provides a default 9-token scale to get started.
+
+### Option A: Use your existing design system
+
+Replace the table below with your system's spacing tokens. Any naming convention works — numbered (`spacing-4`), t-shirt (`sm`/`md`/`lg`), or your own. The only rule: page specs reference token names, never raw pixel values.
+
+### Option B: WDS default scale
+
+Nine tokens, symmetric around `space-md` (the baseline). Freya will propose pixel values during the first design session.
+
+`space-md` is to spacing what `text-md` is to typography — the default you reach for first. It's the gap between paragraphs, between form fields, between list items. Everything else is relative to it: `space-sm` is tighter, `space-lg` is more generous.
+
+| Token | Value | Use |
+|-------|-------|-----|
+| space-3xs | — | Hairline gaps (icon-to-label, inline elements) |
+| space-2xs | — | Minimal spacing (badge padding, tight lists) |
+| space-xs | — | Tight spacing (within compact groups) |
+| space-sm | — | Small gaps (between related elements) |
+| **space-md** | — | **Default element spacing (the baseline)** |
+| space-lg | — | Comfortable spacing (card padding, form fields) |
+| space-xl | — | Section padding |
+| space-2xl | — | Section gaps |
+| space-3xl | — | Page-level breathing room |
+
+### Optical adjustments
+
+Sometimes the math is right but the eye says it's wrong. A circular image leaves white corners, a light element on a light background looks more spaced than it is. When this happens, use token math — not raw pixels:
+
+```
+space-lg - space-3xs    → "standard spacing, pulled in by a hairline"
+space-xl + space-2xs    → "section padding, nudged out slightly"
+```
+
+In page specs, always annotate why:
+
+| Padding top | **space-lg - space-3xs** (optical: circular image adds perceived whitespace) |
+
+**Rules:**
+- Adjustments always use token math: `base ± correction`
+- Always annotate the reason — future readers need to know this wasn't a mistake
+- If adjusting by more than one step, the base token is probably wrong — reconsider
+
+In CSS: `calc(var(--space-lg) - var(--space-3xs))`
+
+<!--
+  space-md is typically 16px (on an 8px grid) or 12px (on a 4px grid) — the most common
+  default spacing on the web. Same ballpark as body text size, which is not a coincidence.
+
+  The pixel values are yours to define. Common starting points:
+  2/4/8/12/16/24/32/48/64 (8px grid) or 4/6/12/16/24/32/48/72.
+  You can adjust later — specs stay valid because they reference names, not numbers.
+-->
+
+---
+
+## Type Scale
+
+> **Bring your own or use ours.** Same principle as spacing — if your project has a type system, map it here. If not, use the WDS default.
+
+The type scale controls **visual size** — how big text looks. This is separate from semantic level (H1, H2, p) which controls **document structure**. An H2 in a sidebar might be `text-sm`. A tagline might be a `<p>` at `text-2xl`. The semantic level is for accessibility and SEO; the type token is for visual hierarchy.
+
+Headings can have different typefaces, weights, and styles on different pages. A landing page H1 might be a serif display font at `text-3xl` italic. An admin page H1 might be clean sans-serif at `text-lg` medium. Each page spec declares its own typographic treatment — the type scale provides the shared sizing vocabulary.
+
+### Option A: Use your existing type system
+
+Replace the table below with your system's type tokens.
+
+### Option B: WDS default scale
+
+Nine tokens, symmetric around `text-md` (body text). Freya will propose sizes during the first design session.
+
+| Token | Value | Use |
+|-------|-------|-----|
+| text-3xs | — | Fine print, legal text |
+| text-2xs | — | Metadata, timestamps |
+| text-xs | — | Captions, helper text |
+| text-sm | — | Labels, secondary text |
+| text-md | — | Body text (the baseline) |
+| text-lg | — | Emphasis, lead paragraphs |
+| text-xl | — | Subheadings |
+| text-2xl | — | Section titles, display text |
+| text-3xl | — | Hero headings, page titles |
+
+<!--
+  text-md (body text) is typically 16px or 14px — the most common baseline on the web.
+  Common starting points: 11/12/13/14/16/18/20/24/32 or 10/11/12/14/16/18/22/30/40.
+  Line heights should align to your spacing grid for vertical rhythm.
+-->
+
+---
+
 ## Tokens
 
-_Design tokens will be documented here as they emerge from page specifications._
+_Additional design tokens (colors, shadows, borders) will be documented here as they emerge from page specifications._
+
+---
+
+## Patterns
+
+<!--
+  Patterns are organized BY the spacing, not by object pairs.
+  Each spacing value/composition accumulates a list of where it's used.
+
+  When the designer says "more space here", the agent fixes it, reflects
+  what it learned, and adds the situation to the relevant pattern below.
+
+  The agent does NOT ask "why?" — it observes and reflects:
+  "Got it — large image above a card row needs extra room. I'll remember that."
+
+  EXTRACTION RULES — objects vs spacing:
+  - Objects: first use stays in the page spec. Second use → extract here.
+  - Spacing: first use → immediately extract here. No waiting.
+  Spacing is relational — a decision about two object types is universal from day one.
+
+  CONTEXT RULE: Entries are context-free by default (universal).
+  Add context only when the same object pair needs DIFFERENT spacing
+  in different situations. When that happens, BOTH entries get context
+  so you can tell them apart. Before the first violation, keep it clean.
+-->
+
+Spacing objects are first-class — they have IDs in page specs (e.g., `hem-v-space-xl`) and live here organized by value. Each spacing value accumulates the situations where it's used. The list grows from real design decisions.
+
+_Patterns will be documented here as spacing objects recur across pages._
+
+<!--
+  Example format (delete when real patterns emerge):
+
+  ### space-sm
+  | Above | Below | Why |
+  |-------|-------|-----|
+  | Heading | Subheading | Tight pair — always read together |
+  | Icon | Label (inside button) | Compact inline group |
+
+  ### space-lg
+  | Above | Below | Why |
+  |-------|-------|-----|
+  | Card | Card (grid gap) | Comfortable breathing room |
+  | Image | Caption | Standard image-to-text |
+
+  ### space-zero
+  | Above | Below | Why |
+  |-------|-------|-----|
+  | Header | Service menu | One continuous nav unit |
+  | Icon bar | Section below | Flush — belongs to the section above |
+
+  ### v-separator-2xl
+  | Above | Below | Why |
+  |-------|-------|-----|
+  | About preview | Trust cards | Gray line, equal space above/below |
+-->
 
 ---
 

package/src/workflows/0-project-setup/templates/folder-guides/00-trigger-map.template.md

@@ -23,7 +23,6 @@ This folder feeds directly into Phase 4 (UX Scenarios). Every page spec should t
 **Learn more:**
 - WDS Course Module 06: Trigger Mapping — Connect Business Goals to User Psychology
 - WDS Course Module 06, Lessons 4–8: The Five Workshops
-- WDS Course Tutorial 06b: Value Trigger Chain
 
 ---
 

package/src/workflows/0-project-setup/workflow.md

@@ -47,7 +47,7 @@ Phase 0: Project Setup
             ├─→ Tech stack (optional)
             ├─→ Component library (optional)
             ├─→ Brief level (complete/simplified)
-            ├─→ Strategic analysis (full/VTC/skip)
+            ├─→ Strategic analysis (full/simplified/skip)
             ├─→ Create folder structure
             └─→ Generate project outline
                     │
@@ -102,4 +102,4 @@ Phase 0: Project Setup
 | Tech Stack | react / vue / wordpress / etc. | Delivery format guidance |
 | Component Library | shadcn / tailwind / custom | Skip or enable Phase 5 |
 | Brief Level | complete / simplified | Depth of Phase 1 |
-| Strategic Analysis | full / simplified / skip | Full Trigger Map or VTC in brief |
+| Strategic Analysis | full / simplified / skip | Full Trigger Map or simplified in brief |

package/src/workflows/1-project-brief/data/positioning-reflect-confirm.md

@@ -40,7 +40,7 @@ Present the positioning components you captured:
 
 ### 3. Document What Was Misunderstood
 
-**For agent dialog `07-positioning.md`:**
+**For design log `07-positioning.md`:**
 
 In the Reflection Checkpoint section, record:
 - Your synthesis (what you presented)
@@ -72,7 +72,7 @@ Am I capturing this right?"
 
 **Agent:** [Updates understanding, proceeds to Substep 4]
 
-**Agent Dialog Update (`dialog/07-positioning.md`):**
+**Design Log Update (`dialog/07-positioning.md`):**
 ```markdown
 ### Reflection Checkpoint
 

package/src/workflows/1-project-brief/data/positioning-synthesize.md

@@ -56,7 +56,7 @@ Show them the positioning statement:
 [1-2 sentences explaining why this positioning makes sense - reference specific context from conversation]
 ```
 
-### 4. Update Agent Dialog
+### 4. Update Design Log
 
 **In `dialog/07-positioning.md`:**
 
@@ -108,7 +108,7 @@ Northern Öland's geography creates a natural monopoly during summer season, but
 
 ---
 
-## Agent Dialog Update
+## Design Log Update
 
 **Mandatory:** Update `dialog/07-positioning.md` with:
 - Full conversation flow
@@ -129,4 +129,4 @@ stepsCompleted: ['step-01-init.md', 'step-02-vision.md', 'step-03-positioning.md
 positioning: '[final positioning statement]'
 ```
 
-Load, read full file, and execute: `step-04-create-vtc.md`
+Load, read full file, and execute: `step-05-business-model.md` (Business Model)

package/src/workflows/1-project-brief/data/vision-synthesize.md

@@ -33,7 +33,7 @@ Add to `product-brief.md`:
 - [Insight 3 - unique angle]
 ```
 
-### 3. Update Agent Dialog
+### 3. Update Design Log
 
 **Mandatory:** Update `dialog/02-vision.md` before marking this step complete.
 

package/src/workflows/1-project-brief/steps-c/step-00-simplified-brief.md

@@ -42,7 +42,7 @@ Guide the user through a quick, focused session to capture the essential project
 ## CONTEXT BOUNDARIES:
 - Available context: Project configuration, user name, communication language
 - Focus: Essential project context in minimal time
-- Limits: No deep competitive analysis, no VTC, no detailed positioning
+- Limits: No deep competitive analysis, no Trigger Map, no detailed positioning
 - Dependencies: Config loaded from `{project-root}/_bmad/wds/config.yaml`
 
 ## Sequence of Instructions (Do not deviate, skip, or optimize)

package/src/workflows/1-project-brief/steps-c/step-01-init.md

@@ -58,7 +58,7 @@ Welcome the user and explain that this is their strategic foundation. This workf
 
 Set time expectations (30-60 minutes) and ask about any existing context that should be considered.
 
-### 2. Agent Dialog Update
+### 2. Design Log Update
 **Mandatory:** Update `dialog/00-context.md` before marking this step complete.
 
 Fill in:
@@ -72,7 +72,7 @@ Mark Phase 0 / Step 1 complete in `dialog/progress-tracker.md` progress tracker.
 Display: "**Select an Option:** [C] Continue to Vision"
 
 #### 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}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
@@ -91,13 +91,13 @@ ONLY WHEN user confirms readiness will you then load and read fully `{nextStepFi
 - User welcomed and expectations set
 - Time estimate communicated (30-60 minutes)
 - Existing context gathered (or noted as none)
-- Agent dialog updated with project metadata
+- Design log updated with project metadata
 - User confirms readiness to proceed
 
 ### ❌ SYSTEM FAILURE:
 - Started exploring vision or strategic topics
 - Generated content without user input
-- Skipped agent dialog update
+- Skipped design log update
 - Did not wait for user confirmation before proceeding
 
 **Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/workflows/1-project-brief/steps-c/step-02-vision.md

@@ -71,7 +71,7 @@ vision: '[synthesized vision statement]'
 Display: "**Select an Option:** [C] Continue to Positioning"
 
 #### 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}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 

package/src/workflows/1-project-brief/steps-c/step-03-positioning.md

@@ -3,7 +3,7 @@ name: 'step-03-positioning'
 description: 'Help user explore and articulate their positioning through natural conversation'
 
 # File References
-nextStepFile: './step-04-create-vtc.md'
+nextStepFile: './step-05-business-model.md'
 workflowFile: '../workflow.md'
 ---
 
@@ -60,7 +60,7 @@ Load and reference `../data/positioning-reflect-confirm.md`. Synthesize position
 ### 4. Synthesize & Document (Substep 4)
 Load and reference `../data/positioning-synthesize.md`. Create positioning statement, document with components and rationale.
 
-### 5. Agent Dialog Update
+### 5. Design Log Update
 **Mandatory:** Update `dialog/07-positioning.md` before marking this step complete.
 
 The dialog should capture:
@@ -73,10 +73,10 @@ The dialog should capture:
 Mark Step 3 complete in `dialog/progress-tracker.md` progress tracker.
 
 ### 6. Present MENU OPTIONS
-Display: "**Select an Option:** [C] Continue to Create VTC"
+Display: "**Select an Option:** [C] Continue to Create Trigger Map"
 
 #### 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}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
@@ -96,7 +96,7 @@ ONLY WHEN positioning is synthesized and user confirms will you then load and re
 - All components captured (target, need, category, benefit, differentiator)
 - Positioning statement synthesized by agent from user input
 - User confirmed the synthesis
-- Agent dialog updated
+- Design log updated
 
 ### ❌ SYSTEM FAILURE:
 - Asked user to write a positioning statement directly

package/src/workflows/1-project-brief/steps-c/step-05-business-model.md

@@ -41,7 +41,7 @@ Help the user identify and understand their business model (B2B, B2C, or both) t
 - 🚫 Avoid generic questions — adapt to context
 
 ## CONTEXT BOUNDARIES:
-- Available context: Vision, Positioning, VTC from previous steps
+- Available context: Vision, Positioning, Trigger Map from previous steps
 - Focus: Business model determination and implications
 - Limits: Not detailed customer profiles yet — that is next steps
 - Dependencies: Steps 1-4 completed
@@ -62,7 +62,7 @@ Reflect back what you heard. If user corrects, update understanding and confirm
 ### 4. Document Decision
 Add Business Model section to product brief with Model, Rationale, and Implications.
 
-### 5. Agent Dialog Update
+### 5. Design Log Update
 **Mandatory:** In `dialog/decisions.md`, append Business Model decision with opening question, user response, key discussion points, final decision, rationale, and implications.
 
 Mark Step 5 complete in `dialog/progress-tracker.md` progress tracker.
@@ -75,7 +75,7 @@ Mark Step 5 complete in `dialog/progress-tracker.md` progress tracker.
 Display: "**Select an Option:** [C] Continue to Business Customers" (or "Continue to Target Users" if B2C)
 
 #### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile} (or step-07 if B2C)
+- IF C: Load, read entire file, then execute {nextStepFile} (or step-07 if B2C)
 - IF M: Return to {workflowFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
@@ -94,7 +94,7 @@ ONLY WHEN business model is determined and user confirms will you then load and
 - Business model determined through natural conversation
 - Rationale and implications documented
 - User confirmed the business model assessment
-- Agent dialog updated with decision
+- Design log updated with decision
 - Correct conditional routing applied
 
 ### ❌ SYSTEM FAILURE:

package/src/workflows/1-project-brief/steps-c/step-06-business-customers.md

@@ -46,12 +46,18 @@ Help the user define their ideal business customer profile, including company ch
 - Limits: Not end users — that is next step
 - Dependencies: Step 5 determined B2B or Both
 
+## CONTEXT CARRY-FORWARD (READ BEFORE ASKING QUESTIONS):
+- From Step 3 (Positioning): You already know the target segment and market positioning. DO NOT re-ask "who is this for?" — instead reference: "In positioning, we identified [target segment]. Now let's go deeper into the business customer profile."
+- From Trigger Map Workshop (if completed): You may already have Trigger Maps with user archetypes. Reference those rather than starting from scratch.
+- BUILD ON prior answers. If the user already described their customers during positioning, acknowledge that: "You mentioned [X] earlier. Let's build on that — tell me more about the decision-making structure."
+- RULE: If the user says "I already told you this," immediately acknowledge, reference the earlier answer, and ask only for NEW information.
+
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
 
 ### 1. Guide Business Customer Definition
 Ask about company size, industry, decision-making structure, and budget authority. Also identify buying roles (buyer vs. user).
 
-### 2. Agent Dialog Update
+### 2. Design Log Update
 **Mandatory:** Append to `dialog/decisions.md` if key decisions were made.
 
 Record: Business customer definition, buyer vs end-user distinction, business customer needs and decision criteria.
@@ -62,7 +68,7 @@ Mark Step 6 complete in `dialog/progress-tracker.md` progress tracker.
 Display: "**Select an Option:** [C] Continue to Target Users"
 
 #### 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}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 

package/src/workflows/1-project-brief/steps-c/step-07-target-users.md

@@ -41,17 +41,23 @@ Help the user define their ideal customer profile by exploring who we are design
 - 🚫 Avoid superficial user descriptions
 
 ## CONTEXT BOUNDARIES:
-- Available context: Vision, positioning, business model, VTC from previous steps
+- Available context: Vision, positioning, business model, Trigger Map from previous steps
 - Focus: User identification and behavioral profiling
 - Limits: Not detailed personas (that comes in Phase 2) — focus on who and why
 - Dependencies: Steps 1-5 (or 1-6 if B2B) completed
 
+## CONTEXT CARRY-FORWARD (READ BEFORE ASKING QUESTIONS):
+- From Step 3 (Positioning): Target segment already defined. DO NOT re-ask "who are your users?" — instead reference: "We've established your positioning targets [segment]. Now let's build behavioral profiles."
+- From Step 6 (Business Customers, if B2B): Buyer vs end-user distinction already captured. Reference it: "We defined the business buyers in the last step. Now let's focus on the end users who actually interact with the product."
+- From Trigger Map Workshop (if completed): User archetypes may exist. Use them as starting points rather than re-discovering.
+- RULE: If the user says "I already told you this," immediately acknowledge, reference the earlier answer, and ask only for NEW information not yet captured.
+
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
 
 ### 1. Guide User Description
 Guide user to describe their ideal users in detail. Ask about their role, demographics, daily experience, frustrations, goals, and current solutions. Also identify any secondary users or stakeholders.
 
-### 2. Agent Dialog Update
+### 2. Design Log Update
 **Mandatory:** Update `dialog/03-users.md` before marking this step complete.
 
 Fill in: Opening question about users + user's initial response, key exchanges exploring who they are, frustrations, goals, current solutions, user scenarios captured, reflection checkpoint, primary user definition + secondary users.
@@ -62,7 +68,7 @@ Mark Step 7 complete in `dialog/progress-tracker.md` progress tracker.
 Display: "**Select an Option:** [C] Continue to Product Concept"
 
 #### 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}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
@@ -81,7 +87,7 @@ ONLY WHEN target users are defined and user confirms will you then load and read
 - Primary user profile defined with behavioral depth
 - Secondary users identified if applicable
 - User confirmed the profiles match their target
-- Agent dialog updated
+- Design log updated
 
 ### ❌ SYSTEM FAILURE:
 - Accepted demographics-only user description

package/src/workflows/1-project-brief/steps-c/step-07a-product-concept.md

@@ -46,6 +46,12 @@ Capture the designer's STRUCTURAL vision — the founding idea, key concept, or
 - Limits: Not detailed features or specifications — the founding principle
 - Dependencies: Steps 1-7 completed
 
+## CONTEXT CARRY-FORWARD (READ BEFORE ASKING QUESTIONS):
+- From Step 2 (Vision): The high-level vision is already captured. Product concept is the STRUCTURAL realization of that vision — do not re-ask about vision.
+- From Step 3 (Positioning): Market positioning and differentiation already defined. Product concept is how the structural design delivers on that positioning.
+- From Step 7 (Target Users): User needs and behavioral profiles exist. Product concept should serve those users — reference them rather than re-exploring user needs.
+- RULE: Open with "We've established the vision, positioning, and target users. Now I want to understand the structural idea — the founding principle that makes this product WORK differently."
+
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
 
 ### 1. Open the Concept Conversation
@@ -67,7 +73,7 @@ Synthesize what you heard and confirm understanding with: Core Structural Idea,
 ### 5. Document the Concept
 Record: Core Structural Idea, Implementation Principle, Rationale, Concrete Example, Features That Stem From Concept.
 
-### 6. Agent Dialog Update
+### 6. Design Log Update
 **Mandatory:** Update `dialog/04-concept.md` before marking this step complete.
 
 Fill in: Opening question, user's initial description, key exchanges, rationale discussion, reflection checkpoint, final concept documentation. Mark Step 7a complete in `dialog/progress-tracker.md`.
@@ -76,7 +82,7 @@ Fill in: Opening question, user's initial description, key exchanges, rationale
 Display: "**Select an Option:** [C] Continue to Success Criteria"
 
 #### 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}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
@@ -96,7 +102,7 @@ ONLY WHEN product concept is articulated and user confirms will you then load an
 - Rationale explored and documented
 - Concrete example provided
 - User confirmed the concept captures their vision
-- Agent dialog updated
+- Design log updated
 
 ### ❌ SYSTEM FAILURE:
 - Accepted a feature list as the product concept

package/src/workflows/1-project-brief/steps-c/step-08-success-criteria.md

@@ -40,7 +40,7 @@ Help the user explore and define what success looks like through conversational
 - Avoid generating content without user input
 
 ## CONTEXT BOUNDARIES:
-- Available context: Vision, positioning, VTC, business model, target users, product concept
+- Available context: Vision, positioning, Trigger Map, business model, target users, product concept
 - Focus: Measurable success criteria with primary/secondary metrics and timeline
 - Limits: Not business model changes, not competitive analysis
 - Dependencies: Steps 1-7a completed
@@ -62,14 +62,14 @@ Ask which is most important.
 ### 5. Confirm and Document
 Reflect back. Get confirmation. Document in product brief.
 
-### 6. Agent Dialog Update
+### 6. Design Log Update
 Mandatory: Append to dialog/decisions.md. Mark Step 8 complete.
 
 ### N. Present MENU OPTIONS
 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-c/step-09-competitive-landscape.md

@@ -40,7 +40,7 @@ Help user explore alternatives and discover their unfair advantage. Explore what
 - Avoid generating content without user input
 
 ## CONTEXT BOUNDARIES:
-- Available context: Vision, positioning, VTC, business model, users, success criteria
+- Available context: Vision, positioning, Trigger Map, business model, users, success criteria
 - Focus: Competitive landscape and unfair advantage
 - Limits: Not detailed feature comparison - strategic positioning
 - Dependencies: Steps 1-8 completed
@@ -65,14 +65,14 @@ What if the main alternative just adds your key feature?
 ### 6. Synthesize and Document
 Reflect back. Get confirmation. Document in product brief.
 
-### 7. Agent Dialog Update
+### 7. Design Log Update
 Append to dialog/decisions.md. Mark Step 9 complete.
 
 ### N. Present MENU OPTIONS
 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-c/step-10-constraints.md

@@ -63,7 +63,7 @@ Brief and dialog.
 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-c/step-10a-platform-strategy.md

@@ -40,7 +40,7 @@ Establish the technical platform strategy and device support requirements that w
 - Avoid generating content without user input
 
 ## CONTEXT BOUNDARIES:
-- Available context: All previous steps (vision, positioning, VTC, business model, users, success criteria, competitive landscape, constraints)
+- Available context: All previous steps (vision, positioning, Trigger Map, business model, users, success criteria, competitive landscape, constraints)
 - Focus: Platform and device strategy
 - Limits: Not detailed technical specs - strategic platform direction
 - Dependencies: Steps 1-10 completed
@@ -76,7 +76,7 @@ Help user define their platform strategy by asking about primary platform choice
 ### 2. Capture and Validate
 Capture platform strategy, validate alignment with vision and constraints, and document in Product Brief under "Platform & Device Strategy" section including primary platform, supported devices, device priority with rationale, interaction models, technical requirements (offline, native features), platform rationale, constraints considered, future plans, and design/development implications.
 
-### 3. Agent Dialog Update
+### 3. Design Log Update
 **Mandatory:** Append to `dialog/decisions.md` if key decisions were made.
 
 **Record:**
@@ -90,7 +90,7 @@ Capture platform strategy, validate alignment with vision and constraints, and d
 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-c/step-11-tone-of-voice.md

@@ -3,7 +3,7 @@ name: 'step-11-tone-of-voice'
 description: 'Establish the product communication personality and style'
 
 # File References
-nextStepFile: './step-11a-create-vtc.md'
+nextStepFile: './step-12-create-product-brief.md'
 workflowFile: '../workflow.md'
 activityWorkflowFile: '../workflow.md'
 ---
@@ -40,7 +40,7 @@ Establish the product's communication personality and style for consistent UI mi
 - Avoid generating content without user input
 
 ## CONTEXT BOUNDARIES:
-- Available context: Vision, positioning, VTC, business model, users, success criteria, competitive landscape, constraints, platform strategy
+- Available context: Vision, positioning, Trigger Map, business model, users, success criteria, competitive landscape, constraints, platform strategy
 - Focus: Communication personality and microcopy style
 - Limits: Tone of Voice is for UI microcopy (buttons, labels, errors, system messages), NOT strategic content (headlines, feature descriptions, value propositions)
 - Dependencies: Steps 1-10a completed
@@ -122,7 +122,7 @@ Once confirmed, document:
 4. **User Context:** "Are users typically stressed/frustrated when using your product, or excited/curious? How should tone respond to their state?"
 5. **Differentiation:** "How do competitors communicate? Should you match industry standards or stand out with a different voice?"
 
-### 7. Agent Dialog Update
+### 7. Design Log Update
 **Mandatory:** Append to `dialog/decisions.md` if key decisions were made.
 
 **Record:**
@@ -136,7 +136,7 @@ Once confirmed, document:
 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-c/{step-12-synthesize.md → step-12-create-product-brief.md}

@@ -1,6 +1,6 @@
 ---
-name: 'step-12-synthesize'
-description: 'Synthesize all captured information and generate the complete Product Brief document'
+name: 'step-12-create-product-brief'
+description: 'Compile all captured information and generate the complete Product Brief document'
 
 # File References
 nextStepFile: './step-13-content-init.md'
@@ -8,10 +8,10 @@ workflowFile: '../workflow.md'
 activityWorkflowFile: '../workflow.md'
 ---
 
-# Step 12: Synthesize and Create Brief
+# Step 12: Create Product Brief
 
 ## STEP GOAL:
-Present a cohesive synthesis of everything captured, get final confirmation, and generate the complete Product Brief document.
+Present a cohesive summary of everything captured, get final confirmation, and generate the complete Product Brief document.
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
@@ -177,7 +177,7 @@ Present a cohesive synthesis of everything captured, get final confirmation, and
 
 ### 5. Update All Dialog Files
 
-**Finalize agent dialogs:**
+**Finalize design log:**
 
 **In `dialog/progress-tracker.md`:**
 - Mark ALL steps complete
@@ -205,7 +205,7 @@ Present a cohesive synthesis of everything captured, get final confirmation, and
 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]