bi-agents/_bmad/wds/workflows/4-ux-design/steps-s/step-05-shortest-path.md

name, description, nextStepFile, workflowFile, activityWorkflowFile

name	description	nextStepFile	workflowFile	activityWorkflowFile
step-05-shortest-path	Map the shortest possible journey from entry point to mutual success	./step-06-scenario-name.md	../workflow.md	../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

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.

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:

Parse pages from user input Store pages_list pages_list

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

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.