---
name: 'step-00f-gap-analysis'
description: 'Analyze gaps and validate strategic alignment of documentation synthesis'

# File References
nextStepFile: './step-01-overview.md'
activityWorkflowFile: '../workflow.md'
---

# Step 6: Gap Analysis & Validation

## STEP GOAL:

Analyze what was strong vs. weak in the documentation, validate strategic alignment between documentation and plans, and prepare a comprehensive summary of what has been built from the existing documentation.

## 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 - validating strategic alignment and identifying gaps
- ✅ 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 identifying strengths, gaps, and strategic alignment
- 🚫 FORBIDDEN to skip alignment validation or ignore contradictions
- 💬 Approach: Honest assessment of documentation quality with constructive recommendations
- 📋 Identify what was strong vs. weak in documentation
- 📋 Validate strategic alignment between stated vision and actual plans

## EXECUTION PROTOCOLS:

- 🎯 Compare original documentation to synthesized Trigger Map
- 💾 Store gap_analysis and alignment_check results
- 📖 Present clear summary of strengths, gaps, and alignment
- 🚫 Do not proceed until user decides how to handle gaps

## CONTEXT BOUNDARIES:

- Available context: Original documentation, all synthesized outputs (vision, objectives, personas, forces, priorities)
- Focus: Gap analysis, strategic alignment validation, summary
- Limits: Be honest about gaps - do not gloss over weaknesses
- Dependencies: Requires all previous extraction steps completed

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

### 1. Analyze Documentation Strengths

Compare original documentation to synthesized Trigger Map. Identify what was clear and strong.

Present documentation strengths.

### 2. Identify Gaps

Determine what was vague or missing, what was filled through conversation, and any contradictions or misalignments.

Present gaps identified with their impact and how they were filled.

### 3. Handle Critical Gaps (If Any)

If critical gaps exist, present them and ask:
"These gaps could affect your strategy. Would you like to:
a. **Address now** - Fill these gaps through focused conversation
b. **Note for later** - Document as areas for future research
c. **Accept as-is** - Work with what we have"

If address now: Run targeted mini-workshops for critical gaps.
If note for later: Document gaps in handover notes.

### 4. Strategic Alignment Check

Reverse engineer alignment: Does the plan match the vision?
- Compare stated vision to implied vision from plans
- Check if objectives align with vision
- Verify target groups serve objectives
- Validate features address drivers

**If alignment good:** Confirm strong alignment and explain how objectives, groups, and forces connect to support the vision.

**If alignment issues:** Present potential misalignments with what documentation says vs. what plan implies. Ask if these should be addressed before finalizing.

Discuss and resolve misalignments if needed.

### 5. Present Accomplishment Summary

Output what was accomplished:
- Clear Vision (statement)
- Strategic Objectives (count and SMART status)
- Prioritized Target Groups (count with behavioral profiles)
- Driving Forces (count, both positive and negative)
- Strategic Focus (statement)
- Gap Analysis (areas identified for future research)

Explain what they now have (single-slide reference instead of extensive docs) and what they can do with it (reference in design work, share in AI chats, team alignment, feature prioritization, design decisions).

Ask: "Ready to proceed to documentation generation and handover?"

Store gap_analysis and alignment_check.

### 6. Present MENU OPTIONS

Display: "**Select an Option:** [C] Continue to Overview | [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. Gap analysis and alignment check must be complete and user must confirm readiness to proceed.

---

## 🚨 SYSTEM SUCCESS/FAILURE METRICS

### ✅ SUCCESS:
- Documentation strengths clearly identified
- Gaps identified with impact assessment
- Critical gaps addressed or documented for later
- Strategic alignment validated (vision vs. plan vs. groups vs. forces)
- Misalignments surfaced and discussed
- Comprehensive summary presented
- User confirmed readiness to proceed
- gap_analysis and alignment_check stored

### ❌ SYSTEM FAILURE:
- Skipping gap analysis
- Not checking strategic alignment
- Glossing over contradictions in documentation
- Not giving user choice on how to handle gaps
- Missing critical gaps that could affect strategy
- Not presenting accomplishment summary
- Proceeding without user confirmation

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