---
name: 'step-06b-confirm-assessment'
description: 'Confirm assessment approach before running feature impact analysis'

# File References
nextStepFile: './step-06c-make-assessment.md'
activityWorkflowFile: '../workflow.md'
---

# Step 13: Confirm Assessment Approach

## STEP GOAL:

Confirm the user is ready for the initial impact assessment by explaining the scoring methodology and getting explicit approval to proceed.

## 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 - setting expectations clearly
- ✅ 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 explaining the assessment methodology clearly
- 🚫 FORBIDDEN to start assessment without user confirmation
- 💬 Approach: Set clear expectations about scoring and review process
- 📋 Explain that user will have opportunity to adjust scores after initial assessment

## EXECUTION PROTOCOLS:

- 🎯 Present scoring methodology transparently
- 💾 Confirm user ready to proceed
- 📖 Explain review opportunity after assessment
- 🚫 Do not proceed until user explicitly confirms

## CONTEXT BOUNDARIES:

- Available context: Confirmed feature list, personas with priorities
- Focus: Assessment methodology explanation and user confirmation
- Limits: Do not start assessing - only explain and confirm
- Dependencies: Requires confirmed feature list from step-06a

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

### 1. Explain Assessment Approach

Output:
"Perfect! I now have your confirmed feature list.

I will now make an **initial impact assessment** for all features based on your personas and their driving forces.

**Assessment approach:**

For each feature, I'll evaluate:
- **Impact on {{primary_persona.name}}** (Primary) - High/Medium/Low
- **Impact on {{secondary_persona.name}}** (Secondary) - High/Medium/Low
- **Impact on {{tertiary_persona.name}}** (Tertiary) - High/Medium/Low (if applicable)

**Scoring:**
- **Primary Persona:** High = 5 pts | Medium = 3 pts | Low = 1 pt
- **Other Personas:** High = 3 pts | Medium = 1 pt | Low = 0 pts

I'll base my assessment on the driving forces (wants and fears) we identified for each persona.

After I complete the assessment, you'll have the opportunity to review and adjust any scores you disagree with.

**Ready for me to proceed with the assessment?**"

### 2. Wait for User Confirmation

Wait for user to confirm readiness.

### 3. Present MENU OPTIONS

Display: "**Select an Option:** [C] Continue to Run Assessment | [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. User must explicitly confirm readiness for assessment.

---

## 🚨 SYSTEM SUCCESS/FAILURE METRICS

### ✅ SUCCESS:
- Assessment methodology explained clearly
- Scoring system presented (Primary weighted higher)
- User informed about review opportunity after assessment
- User explicitly confirmed readiness to proceed

### ❌ SYSTEM FAILURE:
- Starting assessment without explanation
- Not explaining scoring methodology
- Proceeding without user confirmation
- Not mentioning review opportunity

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