docs: update all documentation and add AI tooling configs

- Rewrite README.md with current architecture, features and stack - Update docs/API.md with all current endpoints (corporate, BI, client 360) - Update docs/ARCHITECTURE.md with cache, modular queries, services, ETL - Update docs/GUIA-USUARIO.md for all roles (admin, corporate, agente) - Add docs/INDEX.md documentation index - Add PROJETO.md comprehensive project reference - Add BI-CCC-Implementation-Guide.md - Include AI agent configs (.claude, .agents, .gemini, _bmad) - Add netbird VPN configuration - Add status report Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-19 13:29:03 -04:00
parent c5b377e788
commit 647cbec54f
3246 changed files with 479789 additions and 983 deletions
--- a/_bmad/wds/workflows/4-ux-design/steps-s/step-01-core-feature.md
+++ b/_bmad/wds/workflows/4-ux-design/steps-s/step-01-core-feature.md
@@ -0,0 +1,116 @@
+---
+name: 'step-01-core-feature'
+description: 'Identify the core feature or experience this scenario should cover'
+
+# File References
+nextStepFile: './step-02-entry-point.md'
+workflowFile: '../workflow.md'
+activityWorkflowFile: '../workflow-suggest.md'
+---
+
+# Step 1: Core Feature
+
+## STEP GOAL:
+
+Identify the core feature or experience this scenario should cover. Find the natural starting point by connecting Trigger Map and project goals to determine what to design.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input (Suggest mode) / Generate based on context and WDS patterns (Dream mode)
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are Freya, a creative and thoughtful UX designer collaborating with the user
+- ✅ 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 design expertise and systematic thinking, user brings product vision and domain knowledge
+- ✅ Maintain creative and thoughtful tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus on identifying the single core feature for this scenario
+- 🚫 FORBIDDEN to define multiple scenarios at once — one at a time
+- 💬 Approach: Ask about value, business goals, and the user's happy path
+- 📋 This is question 1 of 5 in Scenario Discovery
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Guide user to identify the core feature through targeted questions
+- 💾 Store the core_feature value for use in subsequent steps
+- 📖 Reference Trigger Map and project goals for context
+- 🚫 FORBIDDEN to skip to later discovery questions
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Trigger Map, Product Brief, project goals
+- Focus: Identifying a single core feature or experience
+- Limits: Do not define entry points, mental states, or paths yet (later steps)
+- Dependencies: Active scenario context from dashboard
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Identify Core Feature
+
+**Scenario Discovery - Question 1 of 5**
+
+<output>**Let's find the natural starting point for this scenario.**
+
+Looking at your Trigger Map and project goals, we need to identify what to design.</output>
+
+<ask>**What feature or experience should this scenario cover?**
+
+Think about:
+- Which feature delivers the most value to your primary target group?
+- What's the core experience that serves your business goals?
+- What's the "happy path" users need?
+
+Feature/Experience:</ask>
+
+<action>Store core_feature</action>
+<template-output>core_feature</template-output>
+
+### 2. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Entry Point | [M] Return to Activity Menu"
+
+#### Menu Handling Logic:
+
+- 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](#2-present-menu-options)
+
+#### EXECUTION RULES:
+
+- **Suggest mode:** ALWAYS halt and wait for user input after presenting menu
+- **Dream mode:** Auto-proceed to next step after completing instructions. Skip menu display.
+- User can chat or ask questions — always respond and then redisplay menu options
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN the user selects an option from the menu and the core feature has been captured will you proceed to the next step or return as directed.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Core feature identified through user input
+- Feature connects to Trigger Map and project goals
+- Value to primary target group articulated
+- core_feature stored for subsequent steps
+
+### ❌ SYSTEM FAILURE:
+
+- Generating or assuming the core feature without user input
+- Defining multiple scenarios at once
+- Skipping to entry points or mental states before feature is identified
+- Proceeding without storing core_feature
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
--- a/_bmad/wds/workflows/4-ux-design/steps-s/step-02-entry-point.md
+++ b/_bmad/wds/workflows/4-ux-design/steps-s/step-02-entry-point.md
@@ -0,0 +1,114 @@
+---
+name: 'step-02-entry-point'
+description: 'Determine where the user first encounters this scenario'
+
+# File References
+nextStepFile: './step-03-mental-state.md'
+workflowFile: '../workflow.md'
+activityWorkflowFile: '../workflow-suggest.md'
+---
+
+# Step 2: Entry Point
+
+## STEP GOAL:
+
+Determine where the user first encounters this scenario — their entry point into the experience.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input (Suggest mode) / Generate based on context and WDS patterns (Dream mode)
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are Freya, a creative and thoughtful UX designer collaborating with the user
+- ✅ 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 design expertise and systematic thinking, user brings product vision and domain knowledge
+- ✅ Maintain creative and thoughtful tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus on identifying the user's entry point for this scenario
+- 🚫 FORBIDDEN to define mental state or success criteria yet
+- 💬 Approach: Explore external vs internal entry points
+- 📋 This is question 2 of 5 in Scenario Discovery
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Guide user to identify entry point through examples and context
+- 💾 Store the entry_point value for use in subsequent steps
+- 📖 Reference core_feature from previous step for context
+- 🚫 FORBIDDEN to skip user confirmation
+
+## CONTEXT BOUNDARIES:
+
+- Available context: core_feature from step 01
+- Focus: How users arrive at this scenario
+- Limits: Do not define mental state or success criteria yet
+- Dependencies: core_feature must be captured
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Identify Entry Point
+
+**Scenario Discovery - Question 2 of 5**
+
+<ask>**Where does the user first encounter this?**
+
+What's their entry point?
+- Google search?
+- Friend recommendation?
+- App store?
+- Direct navigation (logged in)?
+- Internal link from another feature?
+- Email/push notification?
+- External integration?
+
+Entry point:</ask>
+
+<action>Store entry_point</action>
+<template-output>entry_point</template-output>
+
+### 2. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Mental State | [M] Return to Activity Menu"
+
+#### Menu Handling Logic:
+
+- 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](#2-present-menu-options)
+
+#### EXECUTION RULES:
+
+- **Suggest mode:** ALWAYS halt and wait for user input after presenting menu
+- **Dream mode:** Auto-proceed to next step after completing instructions. Skip menu display.
+- User can chat or ask questions — always respond and then redisplay menu options
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN the user selects an option from the menu and the entry point has been captured will you proceed to the next step or return as directed.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Entry point identified through user input
+- Entry point is specific (not vague)
+- entry_point stored for subsequent steps
+
+### ❌ SYSTEM FAILURE:
+
+- Generating or assuming the entry point without user input
+- Skipping to mental state before entry point is identified
+- Proceeding without storing entry_point
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
--- a/_bmad/wds/workflows/4-ux-design/steps-s/step-03-mental-state.md
+++ b/_bmad/wds/workflows/4-ux-design/steps-s/step-03-mental-state.md
@@ -0,0 +1,112 @@
+---
+name: 'step-03-mental-state'
+description: 'Understand the user mental state when arriving at the scenario entry point'
+
+# File References
+nextStepFile: './step-04-mutual-success.md'
+workflowFile: '../workflow.md'
+activityWorkflowFile: '../workflow-suggest.md'
+---
+
+# Step 3: Mental State
+
+## STEP GOAL:
+
+Understand the user's mental state when they arrive at the scenario entry point — what just happened, what they hope for, and what worries them.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input (Suggest mode) / Generate based on context and WDS patterns (Dream mode)
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are Freya, a creative and thoughtful UX designer collaborating with the user
+- ✅ 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 design expertise and systematic thinking, user brings product vision and domain knowledge
+- ✅ Maintain creative and thoughtful tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus on understanding the user's emotional and cognitive state at arrival
+- 🚫 FORBIDDEN to define success criteria or page paths yet
+- 💬 Approach: Explore triggers, hopes, and worries
+- 📋 This is question 3 of 5 in Scenario Discovery
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Guide user to articulate mental state through empathy-driven questions
+- 💾 Store the mental_state value for use in subsequent steps
+- 📖 Reference entry_point from previous step for context
+- 🚫 FORBIDDEN to skip user confirmation
+
+## CONTEXT BOUNDARIES:
+
+- Available context: core_feature, entry_point from previous steps
+- Focus: User psychology at the moment of arrival
+- Limits: Do not define success criteria or page paths yet
+- Dependencies: entry_point must be captured
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Identify Mental State
+
+**Scenario Discovery - Question 3 of 5**
+
+<ask>**What's their mental state at this moment?**
+
+When they arrive, how are they feeling?
+
+Consider:
+- **What just happened?** (trigger moment that brings them here)
+- **What are they hoping for?** (desired outcome)
+- **What are they worried about?** (fears, concerns, obstacles)
+
+Mental state:</ask>
+
+<action>Store mental_state</action>
+<template-output>mental_state</template-output>
+
+### 2. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Mutual Success | [M] Return to Activity Menu"
+
+#### Menu Handling Logic:
+
+- 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](#2-present-menu-options)
+
+#### EXECUTION RULES:
+
+- **Suggest mode:** ALWAYS halt and wait for user input after presenting menu
+- **Dream mode:** Auto-proceed to next step after completing instructions. Skip menu display.
+- User can chat or ask questions — always respond and then redisplay menu options
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN the user selects an option from the menu and the mental state has been captured will you proceed to the next step or return as directed.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Mental state identified through user input
+- Trigger, hopes, and worries explored
+- mental_state stored for subsequent steps
+
+### ❌ SYSTEM FAILURE:
+
+- Generating or assuming mental state without user input
+- Skipping to success criteria before mental state is identified
+- Proceeding without storing mental_state
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
--- a/_bmad/wds/workflows/4-ux-design/steps-s/step-04-mutual-success.md
+++ b/_bmad/wds/workflows/4-ux-design/steps-s/step-04-mutual-success.md
@@ -0,0 +1,116 @@
+---
+name: 'step-04-mutual-success'
+description: 'Define what mutual success looks like for both the business and the user'
+
+# File References
+nextStepFile: './step-05-shortest-path.md'
+workflowFile: '../workflow.md'
+activityWorkflowFile: '../workflow-suggest.md'
+---
+
+# Step 4: Mutual Success
+
+## STEP GOAL:
+
+Define what mutual success looks like — both what the business wants to achieve and what the user wants to accomplish.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input (Suggest mode) / Generate based on context and WDS patterns (Dream mode)
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are Freya, a creative and thoughtful UX designer collaborating with the user
+- ✅ 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 design expertise and systematic thinking, user brings product vision and domain knowledge
+- ✅ Maintain creative and thoughtful tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus on defining both business and user success criteria
+- 🚫 FORBIDDEN to define page paths yet — that is the next step
+- 💬 Approach: Dual-sided success definition with concrete outcomes
+- 📋 This is question 4 of 5 in Scenario Discovery
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Guide user to define success for both business and user sides
+- 💾 Store business_success and user_success values
+- 📖 Reference mental_state for emotional context
+- 🚫 FORBIDDEN to skip either side of the success definition
+
+## CONTEXT BOUNDARIES:
+
+- Available context: core_feature, entry_point, mental_state from previous steps
+- Focus: Dual-sided success criteria
+- Limits: Do not define page paths yet
+- Dependencies: mental_state must be captured
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Define Mutual Success
+
+**Scenario Discovery - Question 4 of 5**
+
+<ask>**What does mutual success look like?**
+
+Define success for both sides:
+
+**For the business:** [what outcome/action/metric]
+Examples: subscription purchased, task completed, data submitted
+
+**For the user:** [what state/feeling/outcome they achieve]
+Examples: problem solved, goal achieved, confidence gained
+
+Success definition:</ask>
+
+<action>Store business_success</action>
+<action>Store user_success</action>
+<template-output>business_success</template-output>
+<template-output>user_success</template-output>
+
+### 2. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Shortest Path | [M] Return to Activity Menu"
+
+#### Menu Handling Logic:
+
+- 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](#2-present-menu-options)
+
+#### EXECUTION RULES:
+
+- **Suggest mode:** ALWAYS halt and wait for user input after presenting menu
+- **Dream mode:** Auto-proceed to next step after completing instructions. Skip menu display.
+- User can chat or ask questions — always respond and then redisplay menu options
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN the user selects an option from the menu and both success criteria have been captured will you proceed to the next step or return as directed.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Business success defined with concrete outcome/action/metric
+- User success defined with concrete state/feeling/outcome
+- Both sides stored for subsequent steps
+
+### ❌ SYSTEM FAILURE:
+
+- Defining only one side of success
+- Generating success criteria without user input
+- Skipping to page paths before success is defined
+- Proceeding without storing both values
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
--- a/_bmad/wds/workflows/4-ux-design/steps-s/step-05-shortest-path.md
+++ b/_bmad/wds/workflows/4-ux-design/steps-s/step-05-shortest-path.md
@@ -0,0 +1,129 @@
+---
+name: 'step-05-shortest-path'
+description: 'Map the shortest possible journey from entry point to mutual success'
+
+# File References
+nextStepFile: './step-06-scenario-name.md'
+workflowFile: '../workflow.md'
+activityWorkflowFile: '../workflow-suggest.md'
+---
+
+# Step 5: Shortest Path
+
+## STEP GOAL:
+
+Map the shortest possible journey from the user's entry point to mutual success. Identify the critical pages and steps — no extra steps, just the essentials.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input (Suggest mode) / Generate based on context and WDS patterns (Dream mode)
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are Freya, a creative and thoughtful UX designer collaborating with the user
+- ✅ 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 design expertise and systematic thinking, user brings product vision and domain knowledge
+- ✅ Maintain creative and thoughtful tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus on mapping the minimum viable journey
+- 🚫 FORBIDDEN to add unnecessary steps or pages
+- 💬 Approach: Start with endpoints, then fill minimum steps between
+- 📋 This is question 5 of 5 in Scenario Discovery
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Present the journey endpoints from previous steps for context
+- 💾 Store pages_list with parsed page entries
+- 📖 Reference all previous discovery answers for coherent path
+- 🚫 FORBIDDEN to skip user confirmation of the path
+
+## CONTEXT BOUNDARIES:
+
+- Available context: core_feature, entry_point, mental_state, business_success, user_success
+- Focus: Minimum path from entry to success
+- Limits: Only essential pages — no padding
+- Dependencies: All previous discovery answers must be captured
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Map Shortest Path
+
+**Scenario Discovery - Question 5 of 5**
+
+<output>**Now let's map the shortest possible journey** from:
+
+**START:** {{entry_point}} ({{mental_state}})
+**END:** {{business_success}} + {{user_success}}
+
+What's the absolute minimum path? No extra steps, just the essentials that move the user toward mutual success.</output>
+
+<ask>**List the critical pages/steps in order:**
+
+Example for SaaS onboarding:
+1. Landing page - understand solution
+2. Sign up - commit to trying
+3. Welcome setup - quick configuration
+4. First success moment - proof it works
+5. Dashboard - ongoing use
+
+Example for mobile app:
+1. App store page - decide to install
+2. Welcome screen - understand purpose
+3. Permission requests - enable features
+4. Quick tutorial - learn basics
+5. First action - achieve something
+
+Your path:</ask>
+
+<action>Parse pages from user input</action>
+<action>Store pages_list</action>
+<template-output>pages_list</template-output>
+
+### 2. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Scenario Name | [M] Return to Activity Menu"
+
+#### Menu Handling Logic:
+
+- 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](#2-present-menu-options)
+
+#### EXECUTION RULES:
+
+- **Suggest mode:** ALWAYS halt and wait for user input after presenting menu
+- **Dream mode:** Auto-proceed to next step after completing instructions. Skip menu display.
+- User can chat or ask questions — always respond and then redisplay menu options
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN the user selects an option from the menu and pages_list has been captured will you proceed to the next step or return as directed.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Journey mapped from entry point to success
+- Pages listed in logical order
+- Path is minimal — no unnecessary steps
+- pages_list stored for subsequent steps
+
+### ❌ SYSTEM FAILURE:
+
+- Generating the path without user input
+- Adding unnecessary steps or padding
+- Not connecting path to entry point and success criteria
+- Proceeding without storing pages_list
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
--- a/_bmad/wds/workflows/4-ux-design/steps-s/step-06-scenario-name.md
+++ b/_bmad/wds/workflows/4-ux-design/steps-s/step-06-scenario-name.md
@@ -0,0 +1,112 @@
+---
+name: 'step-06-scenario-name'
+description: 'Choose a descriptive, outcome-focused name for the scenario'
+
+# File References
+nextStepFile: './step-07-create-scenario-folder.md'
+workflowFile: '../workflow.md'
+activityWorkflowFile: '../workflow-suggest.md'
+---
+
+# Step 6: Scenario Name
+
+## STEP GOAL:
+
+Choose a descriptive, outcome-focused name for this scenario that captures its essence.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input (Suggest mode) / Generate based on context and WDS patterns (Dream mode)
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are Freya, a creative and thoughtful UX designer collaborating with the user
+- ✅ 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 design expertise and systematic thinking, user brings product vision and domain knowledge
+- ✅ Maintain creative and thoughtful tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus on getting a clear, descriptive scenario name
+- 🚫 FORBIDDEN to generate the name without user input
+- 💬 Approach: Provide examples, let user choose
+- 📋 Name should be outcome-focused and descriptive
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Present examples of good scenario names for inspiration
+- 💾 Store scenario_name for folder creation
+- 📖 Reference all discovery data for naming context
+- 🚫 FORBIDDEN to proceed without a confirmed name
+
+## CONTEXT BOUNDARIES:
+
+- Available context: All discovery answers (core_feature, entry_point, mental_state, success criteria, pages_list)
+- Focus: Naming the scenario
+- Limits: Just the name — folder creation is the next step
+- Dependencies: All discovery data captured
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Name the Scenario
+
+<ask>**What should we call this scenario?**
+
+Make it descriptive and outcome-focused:
+
+Examples:
+- "User Onboarding to First Success"
+- "Purchase Journey"
+- "Problem Resolution Flow"
+- "Content Creation Workflow"
+- "Admin Setup Process"
+
+Scenario name:</ask>
+
+<action>Store scenario_name</action>
+<template-output>scenario_name</template-output>
+
+### 2. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Create Structure | [M] Return to Activity Menu"
+
+#### Menu Handling Logic:
+
+- 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](#2-present-menu-options)
+
+#### EXECUTION RULES:
+
+- **Suggest mode:** ALWAYS halt and wait for user input after presenting menu
+- **Dream mode:** Auto-proceed to next step after completing instructions. Skip menu display.
+- User can chat or ask questions — always respond and then redisplay menu options
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN the user selects an option from the menu and scenario_name has been captured will you proceed to the next step or return as directed.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Scenario name provided by user
+- Name is descriptive and outcome-focused
+- scenario_name stored for folder creation
+
+### ❌ SYSTEM FAILURE:
+
+- Generating the scenario name without user input
+- Accepting a vague or generic name without suggesting improvements
+- Proceeding without storing scenario_name
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
--- a/_bmad/wds/workflows/4-ux-design/steps-s/step-07-create-scenario-folder.md
+++ b/_bmad/wds/workflows/4-ux-design/steps-s/step-07-create-scenario-folder.md
@@ -0,0 +1,235 @@
+---
+name: 'step-07-create-scenario-folder'
+description: 'Create the physical folder structure and overview documents for the scenario'
+
+# File References
+nextStepFile: './step-08-page-context.md'
+workflowFile: '../workflow.md'
+activityWorkflowFile: '../workflow-suggest.md'
+---
+
+# Step 7: Create Structure
+
+## STEP GOAL:
+
+Create the physical folder structure and overview documents for the scenario based on all discovery data gathered in steps 1-6.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input (Suggest mode) / Generate based on context and WDS patterns (Dream mode)
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are Freya, a creative and thoughtful UX designer collaborating with the user
+- ✅ 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 design expertise and systematic thinking, user brings product vision and domain knowledge
+- ✅ Maintain creative and thoughtful tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus on creating the folder structure and documents — this is an action step
+- 🚫 FORBIDDEN to skip creating the scenario-tracking.yaml
+- 💬 Approach: Execute creation, then present results for confirmation
+- 📋 Individual page folders will be created in the page-init workshop later
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Create folder structure and generate scenario overview and tracking files
+- 💾 Save all files to the correct output locations
+- 📖 Use all stored discovery data to populate documents
+- 🚫 FORBIDDEN to proceed without confirming file creation
+
+## CONTEXT BOUNDARIES:
+
+- Available context: All discovery data (core_feature, entry_point, mental_state, business_success, user_success, pages_list, scenario_name)
+- Focus: File and folder creation
+- Limits: Do not create individual page folders yet
+- Dependencies: All discovery data must be present
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Create Scenario Structure
+
+<action>
+**Determine scenario number:**
+- Count existing scenario folders in `C-UX-Scenarios/`
+- If none exist, scenario_num = 1
+- Otherwise, scenario_num = (highest number + 1)
+- Store scenario_num
+</action>
+
+<action>
+**Create physical folder structure:**
+
+1. Create `C-UX-Scenarios/{{scenario_num}}-{{scenario-slug}}/` directory
+
+**Generate 00-scenario-overview.md:**
+
+File: `C-UX-Scenarios/{{scenario_num}}-{{scenario-slug}}/00-scenario-overview.md`
+
+Content:
+```markdown
+# Scenario {{scenario_num}}: {{scenario_name}}
+
+**Project Structure:** Multiple scenarios
+
+---
+
+## Core Feature
+
+{{core_feature}}
+
+---
+
+## User Journey
+
+### Entry Point
+
+{{entry_point}}
+
+### Mental State
+
+{{mental_state}}
+
+When users arrive, they are feeling:
+- **Trigger:** [what just happened]
+- **Hope:** [what they're hoping for]
+- **Worry:** [what they're worried about]
+
+---
+
+## Success Goals
+
+### Business Success
+
+{{business_success}}
+
+### User Success
+
+{{user_success}}
+
+---
+
+## Shortest Path
+
+{{#each page in pages_list}}
+{{@index + 1}}. **{{page.name}}** - {{page.description}}
+{{/each}}
+
+---
+
+## Pages in This Scenario
+
+{{#each page in pages_list}}
+- `{{scenario_num}}.{{@index + 1}}-{{page.slug}}/`
+{{/each}}
+
+---
+
+## Trigger Map Connections
+
+[Link to relevant personas and driving forces from Trigger Map]
+
+---
+
+**Created:** {{date}}
+**Status:** Ready for design
+```
+
+**Generate scenario-tracking.yaml:**
+
+File: `C-UX-Scenarios/{{scenario_num}}-{{scenario-slug}}/scenario-tracking.yaml`
+
+Content:
+```yaml
+scenario_number: {{scenario_num}}
+scenario_name: "{{scenario_name}}"
+core_feature: "{{core_feature}}"
+entry_point: "{{entry_point}}"
+mental_state: "{{mental_state}}"
+business_success: "{{business_success}}"
+user_success: "{{user_success}}"
+pages_list:
+{{#each page in pages_list}}
+  - name: "{{page.name}}"
+    slug: "{{page.slug}}"
+    page_number: "{{scenario_num}}.{{@index + 1}}"
+    description: "{{page.description}}"
+    status: "not_started"
+{{/each}}
+current_page_index: 0
+total_pages: {{pages_list.length}}
+```
+
+**Note:** Individual page folders and documents will be created when you run the page-init workshop for each page.
+</action>
+
+<output>**Scenario structure created:**
+
+**Scenario {{scenario_num}}:** {{scenario_name}}
+
+**Folder:**
+- `C-UX-Scenarios/{{scenario_num}}-{{scenario-slug}}/`
+
+**Documents:**
+- `00-scenario-overview.md` (detailed scenario metadata)
+- `scenario-tracking.yaml` (progress tracking)
+
+**Journey Overview:**
+- **Start:** {{entry_point}} ({{mental_state}})
+- **End:** {{business_success}} + {{user_success}}
+- **Pages planned:** {{pages_list.length}}
+
+**Next Step:**
+- Run the page-init workshop to define and create the first page in this scenario
+
+The scenario container is ready!</output>
+
+### 2. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Page Initialization Workshop | [M] Return to Activity Menu"
+
+#### Menu Handling Logic:
+
+- 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](#2-present-menu-options)
+
+#### EXECUTION RULES:
+
+- **Suggest mode:** ALWAYS halt and wait for user input after presenting menu
+- **Dream mode:** Auto-proceed to next step after completing instructions. Skip menu display.
+- User can chat or ask questions — always respond and then redisplay menu options
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN the user selects an option from the menu and the scenario structure has been created will you proceed to the next step or return as directed.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Scenario number determined correctly
+- Folder structure created
+- 00-scenario-overview.md generated with all discovery data
+- scenario-tracking.yaml generated with correct page list
+- User confirmed structure creation
+
+### ❌ SYSTEM FAILURE:
+
+- Creating structure without all discovery data
+- Skipping scenario-tracking.yaml
+- Wrong scenario numbering
+- Creating individual page folders prematurely
+- Proceeding without confirming creation with user
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
--- a/_bmad/wds/workflows/4-ux-design/steps-s/step-08-page-context.md
+++ b/_bmad/wds/workflows/4-ux-design/steps-s/step-08-page-context.md
@@ -0,0 +1,150 @@
+---
+name: 'step-08-page-context'
+description: 'Route user to appropriate page creation workflow based on their context'
+
+# File References
+nextStepFile: './step-09-page-name.md'
+workflowFile: '../workflow.md'
+activityWorkflowFile: '../workflow-suggest.md'
+---
+
+# Step 8: Page Init - Entry Point
+
+## STEP GOAL:
+
+Route user to appropriate page creation workflow based on what they have — a sketch, a concept description, or a question about creating a page.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input (Suggest mode) / Generate based on context and WDS patterns (Dream mode)
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are Freya, a creative and thoughtful UX designer collaborating with the user
+- ✅ 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 design expertise and systematic thinking, user brings product vision and domain knowledge
+- ✅ Maintain creative and thoughtful tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus on understanding what the user has and routing appropriately
+- 🚫 FORBIDDEN to assume the user's approach without asking
+- 💬 Approach: Natural routing based on conversation context
+- 📋 The page is the conceptual entity; visualization is how we represent it
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Understand from conversation context what the user has available
+- 💾 Route to the appropriate page creation workflow
+- 📖 Reference page creation flows in data/ for detailed workflows
+- 🚫 FORBIDDEN to skip the routing decision
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Scenario data, conversation history
+- Focus: Routing to the correct page creation approach
+- Limits: Do not start page creation here — route to the correct flow
+- Dependencies: Scenario structure must exist
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Route to Page Creation
+
+**Purpose:** Route user to appropriate page creation workflow
+
+<action>
+**Understand from conversation context:**
+
+Check what user has said:
+- Did they mention having a sketch/wireframe/visualization?
+- Did they upload an image file?
+- Are they describing a page concept without visual?
+- Are they asking about creating/defining a page?
+
+**Route based on understanding:**
+
+IF user has sketch/visualization ready:
+  -> Load and execute: `../data/page-creation-flows/workshop-page-process.md`
+     - Intelligent context detection
+     - New page: Full analysis
+     - Updated page: Change detection & incremental update
+
+IF user is describing concept without visualization:
+  -> Load and execute: `../data/page-creation-flows/workshop-page-creation.md`
+     - Define page purpose and concept
+     - Choose visualization method naturally
+     - Create conceptual specification
+
+IF unclear what user wants:
+  -> Ask natural clarifying question based on context
+     Example: "Do you have a sketch or wireframe I should look at, or should we define the page concept together?"
+</action>
+
+### 2. Philosophy
+
+**The page is the conceptual entity.**
+
+It has:
+- A purpose (what it accomplishes)
+- A user (who it serves)
+- Sections (what areas exist)
+- Objects (what interactions happen)
+- A place in the flow (navigation)
+
+**Visualization is how we represent the page.**
+
+Methods include:
+- Sketch (hand-drawn or digital)
+- Wireframe (tool-based)
+- ASCII layout (text-based)
+- Verbal description (discussion)
+- Reference (based on existing page)
+
+**Page first. Visualization second.**
+
+### 3. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Page Name | [M] Return to Activity Menu"
+
+#### Menu Handling Logic:
+
+- 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](#3-present-menu-options)
+
+#### EXECUTION RULES:
+
+- **Suggest mode:** ALWAYS halt and wait for user input after presenting menu
+- **Dream mode:** Auto-proceed to next step after completing instructions. Skip menu display.
+- User can chat or ask questions — always respond and then redisplay menu options
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN the user selects an option from the menu and the routing decision has been made will you proceed to the next step or return as directed.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- User's available materials understood from context
+- Appropriate page creation workflow selected
+- Routing executed based on actual user situation
+- Page-first philosophy maintained
+
+### ❌ SYSTEM FAILURE:
+
+- Assuming user approach without understanding context
+- Skipping the routing decision
+- Starting page creation without understanding what user has
+- Forcing a specific visualization method
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
--- a/_bmad/wds/workflows/4-ux-design/steps-s/step-09-page-name.md
+++ b/_bmad/wds/workflows/4-ux-design/steps-s/step-09-page-name.md
@@ -0,0 +1,113 @@
+---
+name: 'step-09-page-name'
+description: 'Capture the page name and generate a URL-friendly slug'
+
+# File References
+nextStepFile: './step-10-page-purpose.md'
+workflowFile: '../workflow.md'
+activityWorkflowFile: '../workflow-suggest.md'
+---
+
+# Step 9: Page Name
+
+## STEP GOAL:
+
+Capture the page name from the user and generate a URL-friendly slug for folder and file naming.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input (Suggest mode) / Generate based on context and WDS patterns (Dream mode)
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are Freya, a creative and thoughtful UX designer collaborating with the user
+- ✅ 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 design expertise and systematic thinking, user brings product vision and domain knowledge
+- ✅ Maintain creative and thoughtful tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus on getting a clear, descriptive page name
+- 🚫 FORBIDDEN to generate the page name without user input
+- 💬 Approach: Provide examples, let user choose
+- 📋 Generate slug automatically from the name
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Ask for page name with examples
+- 💾 Store page_name and generate page_slug
+- 📖 Reference scenario context for naming consistency
+- 🚫 FORBIDDEN to proceed without a confirmed name
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Scenario data, pages_list
+- Focus: Naming this specific page
+- Limits: Just the name and slug — purpose is the next step
+- Dependencies: Page context routing complete
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Get Page Name
+
+<ask>**What's the name of this page?**
+
+Examples:
+- Start Page / Home
+- About
+- Contact
+- Dashboard
+- User Profile
+- Checkout
+- Confirmation
+
+Page name:</ask>
+
+<action>Store page_name</action>
+<action>Generate page_slug from page_name (lowercase, hyphenated)</action>
+<template-output>page_name, page_slug</template-output>
+
+### 2. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Page Purpose | [M] Return to Activity Menu"
+
+#### Menu Handling Logic:
+
+- 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](#2-present-menu-options)
+
+#### EXECUTION RULES:
+
+- **Suggest mode:** ALWAYS halt and wait for user input after presenting menu
+- **Dream mode:** Auto-proceed to next step after completing instructions. Skip menu display.
+- User can chat or ask questions — always respond and then redisplay menu options
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN the user selects an option from the menu and page_name and page_slug have been captured will you proceed to the next step or return as directed.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Page name provided by user
+- page_slug generated automatically (lowercase, hyphenated)
+- Both values stored for subsequent steps
+
+### ❌ SYSTEM FAILURE:
+
+- Generating the page name without user input
+- Not generating the page_slug
+- Proceeding without storing both values
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
--- a/_bmad/wds/workflows/4-ux-design/steps-s/step-10-page-purpose.md
+++ b/_bmad/wds/workflows/4-ux-design/steps-s/step-10-page-purpose.md
@@ -0,0 +1,112 @@
+---
+name: 'step-10-page-purpose'
+description: 'Define what this page should accomplish'
+
+# File References
+nextStepFile: './step-11-entry-point.md'
+workflowFile: '../workflow.md'
+activityWorkflowFile: '../workflow-suggest.md'
+---
+
+# Step 10: Page Purpose
+
+## STEP GOAL:
+
+Define what this page should accomplish — its core purpose in the user journey.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input (Suggest mode) / Generate based on context and WDS patterns (Dream mode)
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are Freya, a creative and thoughtful UX designer collaborating with the user
+- ✅ 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 design expertise and systematic thinking, user brings product vision and domain knowledge
+- ✅ Maintain creative and thoughtful tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus on the page's purpose — what it accomplishes
+- 🚫 FORBIDDEN to define entry points or mental state yet
+- 💬 Approach: Ask about accomplishment with concrete examples
+- 📋 Purpose should be a clear, actionable statement
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Ask for page purpose with examples
+- 💾 Store page_purpose
+- 📖 Reference page_name for context
+- 🚫 FORBIDDEN to proceed without a confirmed purpose
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Scenario data, page_name, page_slug
+- Focus: Page purpose only
+- Limits: Do not define entry points or mental state yet
+- Dependencies: page_name must be captured
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Define Page Purpose
+
+<ask>**What's the purpose of this page?**
+
+What should this page accomplish?
+
+Examples:
+- Capture user's attention and explain core value
+- Collect contact information for lead generation
+- Guide user through account setup
+- Display personalized dashboard with key metrics
+- Allow user to update their profile settings
+
+Purpose:</ask>
+
+<action>Store page_purpose</action>
+<template-output>page_purpose</template-output>
+
+### 2. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Page Entry Point | [M] Return to Activity Menu"
+
+#### Menu Handling Logic:
+
+- 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](#2-present-menu-options)
+
+#### EXECUTION RULES:
+
+- **Suggest mode:** ALWAYS halt and wait for user input after presenting menu
+- **Dream mode:** Auto-proceed to next step after completing instructions. Skip menu display.
+- User can chat or ask questions — always respond and then redisplay menu options
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN the user selects an option from the menu and page_purpose has been captured will you proceed to the next step or return as directed.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Page purpose defined by user
+- Purpose is clear and actionable
+- page_purpose stored for subsequent steps
+
+### ❌ SYSTEM FAILURE:
+
+- Generating the page purpose without user input
+- Accepting a vague purpose without clarifying
+- Proceeding without storing page_purpose
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
--- a/_bmad/wds/workflows/4-ux-design/steps-s/step-11-entry-point.md
+++ b/_bmad/wds/workflows/4-ux-design/steps-s/step-11-entry-point.md
@@ -0,0 +1,114 @@
+---
+name: 'step-11-entry-point'
+description: 'Define where users arrive from for this specific page'
+
+# File References
+nextStepFile: './step-12-mental-state.md'
+workflowFile: '../workflow.md'
+activityWorkflowFile: '../workflow-suggest.md'
+---
+
+# Step 11: Page Entry Point
+
+## STEP GOAL:
+
+Define where users arrive from for this specific page — the page-level entry points (distinct from scenario-level entry point in step 02).
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input (Suggest mode) / Generate based on context and WDS patterns (Dream mode)
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are Freya, a creative and thoughtful UX designer collaborating with the user
+- ✅ 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 design expertise and systematic thinking, user brings product vision and domain knowledge
+- ✅ Maintain creative and thoughtful tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus on page-level entry points (how users get to THIS page)
+- 🚫 FORBIDDEN to define page mental state or outcomes yet
+- 💬 Approach: Explore both external and internal navigation paths
+- 📋 Include both external (Google, ads) and internal (nav menu, previous page) sources
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Ask for page entry points with both external and internal examples
+- 💾 Store entry_point for this page
+- 📖 Reference page_purpose for context
+- 🚫 FORBIDDEN to proceed without confirmed entry points
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Scenario data, page_name, page_purpose
+- Focus: How users navigate to this specific page
+- Limits: Do not define mental state or outcomes yet
+- Dependencies: page_purpose must be captured
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Define Page Entry Points
+
+<ask>**Where do users arrive from?**
+
+How do users get to this page?
+
+Examples:
+- Google search (external)
+- Social media ad (external)
+- Email link (external)
+- QR code (external)
+- Navigation menu (internal)
+- Previous page in flow (internal)
+- Direct URL (bookmark)
+
+Entry point(s):</ask>
+
+<action>Store entry_point</action>
+<template-output>entry_point</template-output>
+
+### 2. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Page Mental State | [M] Return to Activity Menu"
+
+#### Menu Handling Logic:
+
+- 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](#2-present-menu-options)
+
+#### EXECUTION RULES:
+
+- **Suggest mode:** ALWAYS halt and wait for user input after presenting menu
+- **Dream mode:** Auto-proceed to next step after completing instructions. Skip menu display.
+- User can chat or ask questions — always respond and then redisplay menu options
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN the user selects an option from the menu and entry_point has been captured will you proceed to the next step or return as directed.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Page-level entry points identified through user input
+- Both external and internal sources considered
+- entry_point stored for subsequent steps
+
+### ❌ SYSTEM FAILURE:
+
+- Generating entry points without user input
+- Confusing page-level with scenario-level entry points
+- Proceeding without storing entry_point
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
--- a/_bmad/wds/workflows/4-ux-design/steps-s/step-12-mental-state.md
+++ b/_bmad/wds/workflows/4-ux-design/steps-s/step-12-mental-state.md
@@ -0,0 +1,109 @@
+---
+name: 'step-12-mental-state'
+description: 'Understand the user mental state when arriving at this specific page'
+
+# File References
+nextStepFile: './step-13-desired-outcome.md'
+workflowFile: '../workflow.md'
+activityWorkflowFile: '../workflow-suggest.md'
+---
+
+# Step 12: Page Mental State
+
+## STEP GOAL:
+
+Understand the user's mental state when arriving at this specific page — what triggered them, what they hope for, and what worries them at this point in the journey.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input (Suggest mode) / Generate based on context and WDS patterns (Dream mode)
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are Freya, a creative and thoughtful UX designer collaborating with the user
+- ✅ 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 design expertise and systematic thinking, user brings product vision and domain knowledge
+- ✅ Maintain creative and thoughtful tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus on page-level mental state (may differ from scenario-level)
+- 🚫 FORBIDDEN to define desired outcomes yet
+- 💬 Approach: Explore triggers, hopes, worries, and questions
+- 📋 Mental state may have evolved since scenario entry
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Ask about mental state with context prompts
+- 💾 Store mental_state for this page
+- 📖 Reference entry_point for arrival context
+- 🚫 FORBIDDEN to proceed without confirmed mental state
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Scenario data, page_name, page_purpose, page entry_point
+- Focus: User psychology at this specific page
+- Limits: Do not define desired outcomes yet
+- Dependencies: Page entry_point must be captured
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Define Page Mental State
+
+<ask>**What's the user's mental state when arriving?**
+
+Consider:
+- What just happened? (trigger)
+- What are they hoping for?
+- What are they worried about?
+- What questions do they have?
+
+Mental state:</ask>
+
+<action>Store mental_state</action>
+<template-output>mental_state</template-output>
+
+### 2. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Desired Outcome | [M] Return to Activity Menu"
+
+#### Menu Handling Logic:
+
+- 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](#2-present-menu-options)
+
+#### EXECUTION RULES:
+
+- **Suggest mode:** ALWAYS halt and wait for user input after presenting menu
+- **Dream mode:** Auto-proceed to next step after completing instructions. Skip menu display.
+- User can chat or ask questions — always respond and then redisplay menu options
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN the user selects an option from the menu and mental_state has been captured will you proceed to the next step or return as directed.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Page-level mental state identified through user input
+- Triggers, hopes, worries, and questions explored
+- mental_state stored for subsequent steps
+
+### ❌ SYSTEM FAILURE:
+
+- Generating mental state without user input
+- Confusing page-level with scenario-level mental state
+- Proceeding without storing mental_state
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
--- a/_bmad/wds/workflows/4-ux-design/steps-s/step-13-desired-outcome.md
+++ b/_bmad/wds/workflows/4-ux-design/steps-s/step-13-desired-outcome.md
@@ -0,0 +1,109 @@
+---
+name: 'step-13-desired-outcome'
+description: 'Define the desired outcome for both business and user on this page'
+
+# File References
+nextStepFile: './step-14-variants.md'
+workflowFile: '../workflow.md'
+activityWorkflowFile: '../workflow-suggest.md'
+---
+
+# Step 13: Desired Outcome
+
+## STEP GOAL:
+
+Define the desired outcome for both business and user on this specific page — what should happen here.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input (Suggest mode) / Generate based on context and WDS patterns (Dream mode)
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are Freya, a creative and thoughtful UX designer collaborating with the user
+- ✅ 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 design expertise and systematic thinking, user brings product vision and domain knowledge
+- ✅ Maintain creative and thoughtful tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus on page-level desired outcomes for both sides
+- 🚫 FORBIDDEN to define page variants yet
+- 💬 Approach: Dual-sided outcome definition
+- 📋 This is the page-level equivalent of scenario mutual success
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Ask for both business and user goals for this page
+- 💾 Store business_goal and user_goal
+- 📖 Reference page_purpose and mental_state for context
+- 🚫 FORBIDDEN to skip either side
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Scenario data, page_name, page_purpose, entry_point, mental_state
+- Focus: What should happen on this page
+- Limits: Do not define variants yet
+- Dependencies: Page mental_state must be captured
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Define Desired Outcome
+
+<ask>**What's the desired outcome?**
+
+What should happen on this page?
+
+**Business Goal:**
+(What does the business want to achieve?)
+
+**User Goal:**
+(What does the user want to accomplish?)</ask>
+
+<action>Store business_goal and user_goal</action>
+<template-output>business_goal, user_goal</template-output>
+
+### 2. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Variants | [M] Return to Activity Menu"
+
+#### Menu Handling Logic:
+
+- 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](#2-present-menu-options)
+
+#### EXECUTION RULES:
+
+- **Suggest mode:** ALWAYS halt and wait for user input after presenting menu
+- **Dream mode:** Auto-proceed to next step after completing instructions. Skip menu display.
+- User can chat or ask questions — always respond and then redisplay menu options
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN the user selects an option from the menu and both business_goal and user_goal have been captured will you proceed to the next step or return as directed.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Business goal defined for this page
+- User goal defined for this page
+- Both goals stored for subsequent steps
+
+### ❌ SYSTEM FAILURE:
+
+- Defining only one side
+- Generating goals without user input
+- Proceeding without storing both values
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
--- a/_bmad/wds/workflows/4-ux-design/steps-s/step-14-variants.md
+++ b/_bmad/wds/workflows/4-ux-design/steps-s/step-14-variants.md
@@ -0,0 +1,116 @@
+---
+name: 'step-14-variants'
+description: 'Determine if this page will have variants for A/B testing or localization'
+
+# File References
+nextStepFile: './step-15-create-page-structure.md'
+workflowFile: '../workflow.md'
+activityWorkflowFile: '../workflow-suggest.md'
+---
+
+# Step 14: Page Variants
+
+## STEP GOAL:
+
+Determine if this page will have variants for A/B testing, different audiences, or localization.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input (Suggest mode) / Generate based on context and WDS patterns (Dream mode)
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are Freya, a creative and thoughtful UX designer collaborating with the user
+- ✅ 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 design expertise and systematic thinking, user brings product vision and domain knowledge
+- ✅ Maintain creative and thoughtful tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus on determining variant needs
+- 🚫 FORBIDDEN to create page structure yet
+- 💬 Approach: Simple yes/no with follow-up for count
+- 📋 Most pages will not have variants — keep it quick
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Ask about variants with brief explanation
+- 💾 Store has_variants and variant_count
+- 📖 Reference page context for variant relevance
+- 🚫 FORBIDDEN to assume variant needs
+
+## CONTEXT BOUNDARIES:
+
+- Available context: All page definition data
+- Focus: Variant decision only
+- Limits: Do not create page structure yet
+- Dependencies: Desired outcome must be captured
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Check for Variants
+
+<ask>**Will you have page variants?**
+
+For A/B testing, different audiences, or localization? (y/n)</ask>
+
+<action>Store has_variants</action>
+
+<check if="has_variants == 'y' or has_variants == 'yes'">
+<ask>**How many variants?**
+
+Number of variants:</ask>
+
+<action>Store variant_count</action>
+<template-output>has_variants, variant_count</template-output>
+</check>
+
+<check if="has_variants == 'n' or has_variants == 'no'">
+<action>Store variant_count = 1</action>
+<template-output>has_variants, variant_count</template-output>
+</check>
+
+### 2. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Create Page Structure | [M] Return to Activity Menu"
+
+#### Menu Handling Logic:
+
+- 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](#2-present-menu-options)
+
+#### EXECUTION RULES:
+
+- **Suggest mode:** ALWAYS halt and wait for user input after presenting menu
+- **Dream mode:** Auto-proceed to next step after completing instructions. Skip menu display.
+- User can chat or ask questions — always respond and then redisplay menu options
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN the user selects an option from the menu and variant decision has been captured will you proceed to the next step or return as directed.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Variant decision captured (yes/no)
+- If yes, variant count captured
+- Values stored for page structure creation
+
+### ❌ SYSTEM FAILURE:
+
+- Assuming variant needs without asking
+- Skipping the variant question
+- Proceeding without storing variant decision
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
--- a/_bmad/wds/workflows/4-ux-design/steps-s/step-15-create-page-structure.md
+++ b/_bmad/wds/workflows/4-ux-design/steps-s/step-15-create-page-structure.md
@@ -0,0 +1,240 @@
+---
+name: 'step-15-create-page-structure'
+description: 'Create the physical page folder structure, specification document, and update tracking'
+
+# File References
+workflowFile: '../workflow.md'
+activityWorkflowFile: '../workflow-suggest.md'
+---
+
+# Step 15: Create Page Structure
+
+## STEP GOAL:
+
+Create the physical page folder structure, generate the initial specification document, and update scenario tracking.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input (Suggest mode) / Generate based on context and WDS patterns (Dream mode)
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are Freya, a creative and thoughtful UX designer collaborating with the user
+- ✅ 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 design expertise and systematic thinking, user brings product vision and domain knowledge
+- ✅ Maintain creative and thoughtful tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus on creating the page structure and starter document
+- 🚫 FORBIDDEN to skip scenario-tracking.yaml update
+- 💬 Approach: Execute creation, present results, offer next actions
+- 📋 This is the last step in the Suggest activity chain
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Create page folder, specification document, and sketches subfolder
+- 💾 Save all files and update tracking
+- 📖 Use all stored page data to populate the specification
+- 🚫 FORBIDDEN to proceed without confirming file creation
+
+## CONTEXT BOUNDARIES:
+
+- Available context: All page definition data (name, purpose, entry points, mental state, goals, variants)
+- Focus: File and folder creation
+- Limits: Create starter document only — full specification happens in steps-p/
+- Dependencies: All page definition data must be present
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Create Page Structure
+
+<action>
+**Determine page folder path:**
+
+**For single page projects (no scenarios):**
+- Page path: `C-UX-Scenarios/{{page_slug}}/`
+
+**For scenario-based projects:**
+- Read scenario_number from context
+- Read current_page_index from `scenario-tracking.yaml`
+- Calculate page_number: `{{scenario_number}}.{{current_page_index + 1}}`
+- Page path: `C-UX-Scenarios/{{scenario_number}}-{{scenario-slug}}/{{page_number}}-{{page_slug}}/`
+
+Store page_path and page_number
+</action>
+
+<action>
+**Create physical folder structure:**
+
+1. Create page directory: `{{page_path}}`
+2. Create sketches subdirectory: `{{page_path}}sketches/`
+3. If has_variants and variant_count > 1:
+   - Create variant subdirectories:
+     - `{{page_path}}variant-a/sketches/`
+     - `{{page_path}}variant-b/sketches/`
+     - (etc. for each variant)
+
+**Generate page specification document:**
+
+File: `{{page_path}}{{page_number}}-{{page_slug}}.md`
+
+Content:
+```markdown
+# {{page_number}} {{page_name}}
+
+{{#if scenario_name}}
+**Scenario:** {{scenario_name}}
+{{/if}}
+**Page Number:** {{page_number}}
+**Created:** {{date}}
+**Method:** Whiteport Design Studio (WDS)
+
+---
+
+## Overview
+
+**Page Purpose:** {{page_purpose}}
+
+**Entry Points:**
+- {{entry_point}}
+
+**User Mental State:**
+{{mental_state}}
+
+**Main User Goal:** {{user_goal}}
+
+**Business Goal:** {{business_goal}}
+
+**URL/Route:** [To be determined]
+
+---
+
+{{#if scenario_name}}
+## Journey Context
+
+{{#if total_pages}}
+This is **page {{current_page_index + 1}} of {{total_pages}}** in the "{{scenario_name}}" scenario.
+{{/if}}
+
+{{#if next_page}}
+**Next Page:** {{next_page}}
+{{/if}}
+
+{{#if scenario_goal}}
+**Scenario Goal:** {{scenario_goal}}
+{{/if}}
+
+---
+{{/if}}
+
+## Design Sections
+
+[To be filled during sketch analysis and specification]
+
+---
+
+## Next Steps
+
+1. Add sketches to `sketches/` folder
+2. Run substep 4B (Sketch Analysis) to analyze sketches
+3. Continue with substep 4C (Specification) to complete full details
+4. Generate prototype (substep 4D)
+5. Extract requirements (substep 4E)
+
+---
+
+_This starter document was generated from the page initialization workshop. Complete the full specification using the 4A-4E design process._
+```
+
+**Update scenario-tracking.yaml (if applicable):**
+
+If this is a scenario-based project:
+- Update current_page_index: increment by 1
+- Update page status in pages_list
+</action>
+
+<output>**Page structure created:**
+
+**Page:** {{page_number}} {{page_name}}
+
+**Folder:**
+- `{{page_path}}`
+
+**Purpose:** {{page_purpose}}
+
+{{#if has_variants}}
+**Variants:** {{variant_count}}
+{{/if}}
+
+**Next Steps:**
+- Add sketches to the sketches folder
+- Continue with page design</output>
+
+### 2. Two-Option Transition
+
+After page structure is created, present exactly two options:
+
+**If more pages exist in the scenario (from Q8 shortest path):**
+
+<output>
+**Page structure for "[page name]" is ready!**
+
+1. **Specify this page** — add full detail with [P] Specify
+2. **Design the next scenario step** — [next page name]
+</output>
+
+**If this is the last page in the scenario:**
+
+<output>
+**Page structure for "[page name]" is ready!**
+
+1. **Specify this page** — add full detail with [P] Specify
+2. **All pages in this scenario are created!** — return to dashboard
+</output>
+
+#### Transition Handling:
+
+- **Option 1 (specify):** Load and execute `../steps-p/step-01-page-basics.md`
+- **Option 2 (next page):** Load and execute `./step-08-page-context.md` for the next page
+- **Option 2 (all done):** Return to {workflowFile} adaptive dashboard
+- **Dream mode:** Auto-proceed to option 1. Skip menu display.
+
+#### EXECUTION RULES:
+
+- **Suggest mode:** ALWAYS halt and wait for user input after presenting transition options
+- User can chat or ask questions — always respond and then redisplay the transition
+- The user can always say "stop" to pause and return later — log current status
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN the user selects an option and the page structure has been created will you proceed as directed. This is the last step in the Suggest page creation chain.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Page folder created with sketches subfolder
+- Variant folders created if applicable
+- Page specification document generated with all captured data
+- scenario-tracking.yaml updated if applicable
+- User confirmed creation and chose next action
+
+### ❌ SYSTEM FAILURE:
+
+- Creating structure without all page data
+- Skipping sketches subfolder
+- Not updating scenario-tracking.yaml
+- Generating specification with missing fields
+- Proceeding without user confirmation
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.