initial commit

_bmad/wds/workflows/0-alignment-signoff/steps-c/step-01a-understand-situation.md

@@ -0,0 +1,102 @@
+---
+name: 'step-01a-understand-situation'
+description: 'Clarify the users situation before proceeding with the alignment workflow'
+
+# File References
+nextStepFile: './step-01b-determine-if-needed.md'
+workflowFile: '../workflow.md'
+---
+
+# Step 1: Understand Situation
+
+## STEP GOAL:
+
+Clarify the user's situation so you can guide them through the correct alignment path efficiently.
+
+## 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 understanding the user's situation and role
+- 🚫 FORBIDDEN to skip situation assessment or assume the user's role
+- 💬 Approach: Ask clarifying questions, listen carefully
+- 📋 Do not proceed to next step until the user's situation is clearly understood
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Determine the user's role and relationship to the project
+- 💾 Note the user's situation for routing in the next step
+- 📖 Reference the alignment workflow purpose from workflow.md
+- 🚫 Do not start building any alignment content yet
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Workflow initialization, config loaded
+- Focus: Understanding who the user is and what they need
+- Limits: Do not explore alignment sections or build documents yet
+- Dependencies: Config must be loaded from workflow initialization
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Ask the User to Clarify Their Situation
+
+Ask the user to clarify their situation:
+
+"I'd like to understand your situation first. This will help me guide you efficiently.
+
+**Are you:**
+- A consultant proposing a solution to a client?
+- A business owner hiring consultants/suppliers to build software?
+- A manager or employee seeking approval for an internal project?
+- Or doing this yourself and don't need stakeholder alignment?
+
+Let's get clear on what you need so we can move forward."
+
+### 2. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to step-01b-determine-if-needed"
+
+#### 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's situation is clearly understood will you then load and read fully `{nextStepFile}` to execute and begin the next step.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- User's situation and role are clearly identified
+- User feels heard and understood before moving forward
+
+### ❌ SYSTEM FAILURE:
+- Skipping situation assessment and assuming the user's role
+- Proceeding without user input
+- Generating alignment content prematurely
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.