Session 2

Session Agenda

Session 1 Recap

In Session 1 you built the foundation:

• Three Approaches Framework — ADRs vs Structured Files vs Tool-assisted
• Tier Evaluation — proven vs emerging vs experimental
• Four Foundational Patterns — Persona, Few-shot, Template, Chain-of-Thought
• Real application — Priority Builder with actual deliverables and CSV output

Session 2 evolves each of those: simple patterns become orchestrated workflows, single-step tasks become multi-phase reasoning, and the same methodology scales from priorities to interviews to code.

Advanced Patterns

When a single prompt with four foundational patterns isn't enough for complex, multi-step tasks, two research-backed patterns handle the gap:

ReAct Pattern

From Yao et al. (2022). Designed for tasks that require validation checkpoints between steps — where you can't know the next action until you observe the result of the current one.

When to use: Multi-step tasks where each step depends on the previous result. Code migration, gap analysis, systematic positioning strategy.

Tree of Thoughts

From Yao et al. (2023). Designed for decision points where multiple valid approaches exist and the right choice requires explicit evaluation of tradeoffs.

1. Generate 3 genuinely different approaches to the problem
2. Evaluate pros/cons/risks of each approach explicitly
3. Choose the best approach with clear rationale
4. Proceed with that choice

When to use: Any decision point with real tradeoffs. Interview positioning strategy, architecture choices, migration approach selection.

When Simple Patterns Are Enough

Decision rule: Use the simplest approach that handles the complexity. Don't reach for ReAct when a good Persona + Template covers it.

Spec-Kit 4-File Workflow

The spec-kit pattern separates concerns across files so each piece can be reused, updated independently, and understood by teammates without context from your head.

Key advantage: Separation of concerns. knowledge-base.md stays reusable; specification.md is the only file that changes per task; execution.md is throwaway.

Exercise: Build Interview Strategy

Phase 1 — Create specification.md (8 minutes)

1. Start with the provided knowledge-base.md (interview fundamentals, STAR method, positioning options)
2. Select a job from the participant materials (Senior Manager AI Strategy, Principal Consultant Banking, Director Digital Transformation)
3. Pick the same demo persona you used in Session 1 for continuity
4. Document: target role details, your persona's background, key gaps and key strengths

Phase 2 — Execute implementation-plan.md (7 minutes)

THINK: What is the biggest gap between my background and this role?
ACT: Map my specific experience to each key requirement
OBSERVE: What positioning angle emerges from this mapping?
THINK: How do I turn gaps into learning narratives?
ACT: Develop core connecting story: past experience → role requirements

Option A: Technical Expert
  Pros: Deep credibility, clear differentiation
  Cons: May undersell business acumen, narrow appeal
  Risk: Medium

Option B: Strategic Leader
  Pros: Broad appeal, executive positioning
  Cons: May lack specificity, needs strong evidence
  Risk: Medium

Option C: Balanced Bridge
  Pros: Technical depth + business growth story
  Cons: Harder to articulate concisely
  Risk: Low

Selected: [Your choice with rationale]

Success criteria: Clear positioning strategy with documented rationale, not just a chosen answer.

Live Java Demo: Spring Boot Migration

Same patterns, technical domain. Spring Boot 2→3 migration involves three types of changes: namespace updates (javax → jakarta), annotation modernization, and security configuration updates.

The three approaches from Session 1 apply directly:

"Following .github/copilot-instructions.md migration standards,
migrate UserController to Spring Boot 3"

THINK: Dependencies must be updated before annotations
ACT: Update javax → jakarta imports first
OBSERVE: mvn compile — success, proceed to annotations
THINK: Security config needs modernization next
ACT: Migrate to SecurityFilterChain pattern

Cross-Domain Pattern Recognition

The same cognitive patterns appear across all three domains in this workshop:

The domain changes. The systematic thinking doesn't.

What You Now Have

This Week

1. Apply ReAct pattern to one complex work decision
2. Use Tree of Thoughts for your next strategic choice — write out the three options explicitly
3. Create a spec-kit workflow for one task you do repeatedly

Longer Term

• Evaluate new AI tools using the Three Approaches and Tier frameworks before adopting
• Build team templates using proven foundational patterns — document what works
• Apply systematic thinking across your domain — same patterns, different problems