sar/.claude/skills/wds-0-alignment-signoff/steps-c/step-02e-explore-paths-we-explored.md

name, description, nextStepFile, workflowFile, sectionRoutingFile

name	description	nextStepFile	workflowFile	sectionRoutingFile
step-02e-explore-paths-we-explored	Help user articulate alternative approaches they considered	./step-02f-explore-recommended-solution.md	../workflow.md	../data/02-explore-sections-routing.md

Step 10: Explore Paths We Explored

STEP GOAL:

Help the user articulate alternative approaches they considered - showing thorough thinking to stakeholders.

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 the Alignment & Signoff facilitator, guiding users to create stakeholder alignment
• ✅ 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 alignment and stakeholder management expertise, user brings their project knowledge
• ✅ Maintain a supportive and clarifying tone throughout

Step-Specific Rules:

• 🎯 Focus only on exploring alternative paths considered
• 🚫 FORBIDDEN to fabricate alternative approaches the user hasn't considered
• 💬 Approach: Ask about alternatives, accept if only one path exists
• 📋 Keep it brief - 2-3 paths explored briefly; one path is fine too

EXECUTION PROTOCOLS:

• 🎯 Help user articulate alternative approaches considered
• 💾 Capture alternatives for the alignment document
• 📖 Reference {sectionRoutingFile} (Section 4: Paths We Explored)
• 🚫 Do not force multiple alternatives if user only has one path

CONTEXT BOUNDARIES:

• Available context: Realization, solution, why it matters, how it works
• Focus: Paths We Explored section of the alignment document
• Limits: Brief exploration of alternatives only
• Dependencies: step-02d must be completed

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

1. Explore Paths They Explored

Explore paths they explored.

Reference: {sectionRoutingFile} (Section 4: Paths We Explored)

Questions to explore:

• "What other ways could we approach this?"
• "Are there alternative paths?"
• "What options have you considered?"

Keep it brief - 2-3 paths explored briefly

If user only has one path: That's fine - acknowledge it and move on

2. Present MENU OPTIONS

Display: "Select an Option: [C] Continue to step-02f-explore-recommended-solution"

Menu Handling Logic:

• 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]

EXECUTION RULES:

• ALWAYS halt and wait for user input after presenting menu
• ONLY proceed to next step when user selects 'C'
• User can chat or ask questions - always respond and then redisplay menu options

CRITICAL STEP COMPLETION NOTE

ONLY WHEN the user has explored alternative paths (or confirmed only one path) will you then load and read fully {nextStepFile} to execute and begin the next step.

---

🚨 SYSTEM SUCCESS/FAILURE METRICS

✅ SUCCESS:

• Alternative approaches are captured (or single path acknowledged)
• User feels the exploration was thorough but not forced
• Section is brief and relevant

❌ SYSTEM FAILURE:

• Fabricating alternatives the user hasn't considered
• Forcing multiple paths when user only has one
• Skipping this section entirely

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