calctext/_bmad/wds/workflows/2-trigger-mapping/steps-c/step-00e-prioritization-extract.md

name, description, nextStepFile, activityWorkflowFile

name	description	nextStepFile	activityWorkflowFile
step-00e-prioritization-extract	Extract and validate strategic prioritization from existing documentation	./step-00f-gap-analysis.md	../workflow.md

Step 5: Prioritization Extraction

STEP GOAL:

Extract or establish strategic prioritization of target groups and driving forces from the user's existing documentation, creating clear priority rankings with rationale.

MANDATORY EXECUTION RULES (READ FIRST):

Universal Rules:

• 🛑 NEVER generate content without user input
• 📖 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 Saga the Analyst - challenging assumptions and seeking clarity from documentation
• ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
• ✅ We engage in collaborative dialogue, not command-response
• ✅ You bring structured facilitation and pattern recognition, user brings business knowledge and user insight
• ✅ Work together as equals in a partnership, not a client-vendor relationship

Step-Specific Rules:

• 🎯 Focus on establishing clear priority rankings for groups and drivers
• 🚫 FORBIDDEN to accept prioritization without rationale
• 💬 Approach: Use documentation signals (budget, depth of research, frequency of mention) to suggest priorities
• 📋 Documentation rarely includes explicit prioritization - establish through conversation
• 📋 Create impact x feasibility assessment for each group

EXECUTION PROTOCOLS:

• 🎯 Check documentation for priority signals before asking
• 💾 Store validated prioritized_groups, prioritized_drivers, and focus_statement
• 📖 Help user assess impact and feasibility for each group
• 🚫 Do not proceed until focus statement is confirmed

CONTEXT BOUNDARIES:

• Available context: User's documentation, validated vision/objectives, personas, driving forces
• Focus: Priority ranking of groups and drivers, design focus statement
• Limits: Must have clear rationale for each priority decision
• Dependencies: Requires completed step-00d with confirmed driving forces

Sequence of Instructions (Do not deviate, skip, or optimize)

1. Introduce Prioritization

Output: "Prioritizing Strategic Elements

Your documentation gives us the pieces. Now we need to prioritize:

• Which target groups have highest impact on your objectives?
• Which groups are most feasible to reach?
• Which driving forces are most frequent and intense?"

2. Check for Priority Signals

Analyze documentation for prioritization signals:

• Explicit priority statements
• Resource allocation (budget, team focus)
• Timeline emphasis (what's first)
• Frequency of mention
• Depth of research on certain groups

If signals found: Present them and their implications. If no signals: Note documentation doesn't explicitly prioritize and proceed to collaborative prioritization.

3. Prioritize Target Groups

Present all target groups. For each group, assess:

• Impact on objectives: If this group succeeds with your product, how much does it drive your objectives? (High/Medium/Low)
• Feasibility: How easy is it to reach and serve this group? (High/Medium/Low)

Calculate priority score (Impact x Feasibility). Rank groups.

Present priority ranking with reasoning. Ask if prioritization aligns with strategic thinking.

Store prioritized_groups.

4. Prioritize Driving Forces

Analyze driving forces for frequency, intensity, and alignment with top-priority groups.

Present top driving forces ranked. Ask if these feel like the most critical drivers to address.

Store prioritized_drivers.

5. Create Design Focus Statement

Synthesize into focus statement combining top priority group, top 3-5 drivers, and connection to objectives.

Present focus statement. Ask if it captures where design efforts should focus.

Store focus_statement.

6. Present Workshop 4 Summary

Output: "Workshop 4 Complete!

Strategic Priorities Set:

• Top group: {{top_group.name}}
• Top drivers: {{top_driver_count}} identified
• Focus statement: Defined

Next, we'll run a gap analysis and validate strategic alignment."

7. Present MENU OPTIONS

Display: "Select an Option: [C] Continue to Gap Analysis | [M] Return to Activity Menu"

Menu Handling Logic:

• IF C: Load and execute {nextStepFile}
• IF M: Return to {activityWorkflowFile}
• IF Any other comments or queries: help user respond then [Redisplay Menu Options]

EXECUTION RULES:

• ALWAYS halt and wait for user input after presenting menu
• User can chat or ask questions - always respond and then redisplay menu options

CRITICAL STEP COMPLETION NOTE

ONLY WHEN user selects [C] will you load the next step file. Priority rankings and focus statement must be confirmed before proceeding to gap analysis.

---

🚨 SYSTEM SUCCESS/FAILURE METRICS

✅ SUCCESS:

• Target groups prioritized with impact and feasibility assessment
• Driving forces prioritized by frequency, intensity, and alignment
• Each priority decision has documented rationale
• Design focus statement created and confirmed
• Documentation priority signals identified and used where available
• User confirmed all priority rankings
• Results stored for subsequent steps

❌ SYSTEM FAILURE:

• Accepting prioritization without rationale
• Not checking documentation for priority signals first
• Skipping impact/feasibility assessment
• No design focus statement created
• Proceeding without confirmed priorities
• Prioritizing without considering driving forces
• Not challenging assumptions about priority

Master Rule: Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.