# Consolidation and Reflection

This is the capstone skill. It consolidates everything the executive produced across the other skills in this collection into one personalized Agentic AI Strategic Playbook, then adds the reflection and board-readiness layers that turn analysis into a document they can lead with.

## The sibling skills to consolidate

Pull whatever the executive has from these. Ask them to paste the deliverable HTML files or the underlying data, or to recall the key outputs. For each, the fields worth carrying forward:

### AIDE Opportunities Audit
- Company profile: risk posture, AIDE Matrix quadrant, Leadership and Company scores, innovation readiness, cost-of-inertia numbers.
- Opportunity matrix: the high-priority opportunities, their four-metric scores, the Deep Economic Assessment results, and the icebox.
- The ranked roadmap of opportunities that passed deep assessment. This is the raw material for the phased deployment roadmap.

### AIDE Strategic Framework (three-pillar)
- The AI-term focus (AI / generative / agentic).
- Pillar rankings: application domains (opportunity vs. attention), the beachhead, capability rankings, the implementation spectrum, the strategy matrix (Domain x Capability x Implementation).
- The readiness key map: Literacy, Data, Cyber, Compliance, Change Management, Strategy scores, and the binding constraint.
- The sequenced moves (90 days, year).

### State of the Art Org Chart
- Company overview and 20-year history.
- The current human org chart, the single-agent deployment pattern (RACI plus budget/funding/launch-approval owners), the enriched multi-agent chart, and the greenfield AI-native vision.
- The node-mix projection, node economics (Human Time vs. System Time, bear/base/bull), and the latency stack.

### Corporate Entrepreneurship Audit (if run)
- The specific goal statement, the five system-friction scores, and the five problem-area scores with the binding area.
- The dual-operating-system and firewall design, the chosen implementation vehicle, and the buy-in plan. These slot directly into the playbook's roadmap and change-management sections.

## If they have not used the other skills

Do not require them. If a skill's output is missing, fill the gap with a focused mini-interview covering just what the playbook needs from that skill: risk posture and top opportunities (from the audit), the beachhead and readiness scores (from the three-pillar), and the current org shape plus agent-deployment intent (from the org chart). Keep it tight; this skill is consolidation and reflection, not a re-run of the others. Recommend they run the missing skill afterward for depth, and note in the playbook which sections are lighter because a source skill was not run.

## The reflection interview

This is unique to the capstone. After gathering the prior work, interview the executive on their own learning journey. Small batches, open-ended, let them talk:

1. **What have you learned?** Across all of this work, what shifted in how you think about AI in your organization? What is the one idea you will repeat to your team?
2. **What surprised you?** Where did the analysis contradict your going-in assumption? A quadrant you did not expect, a readiness score lower than you would have guessed, an opportunity you had dismissed.
3. **What do you wish you had known sooner?** What would have changed a decision you already made if you had understood it a year ago?
4. **What do you still need to learn, understand, or practice?** Be specific: a capability, a governance question, a technical concept, a leadership muscle. This becomes the personal development track in the playbook.

Capture their words closely. The reflection section is written in their voice, not yours. It is what makes the playbook personal rather than generic.

## Findings synthesis

After the reflection, present the high-level findings back to them: pull the through-lines across all the skills they used (and the gap-fill answers). Name the two or three things that are most true about where this organization stands and what it must do. Confirm these with the executive before writing the board narrative, because these findings become its spine.