Part 1: Intro to Claude Code

Two Workflows in Agentic Coding

Choosing the right approach for your task

Ad-hoc Prompting

Best for: isolated, one-off tasks (aka "vibe coding")

Prompt

↓

AI generates code

↓

Fix / adjust

↺

repeat

○

Context: Limited to current conversation

○

Process: Reactive, fix-as-you-go

○

Best when: Quick script, single function, Q&A about codebase

Spec-Driven Development

Best for: anything you'll iterate on

Plan & brainstorm with AI

↓

Create spec document

↓

AI implements from spec

↓

Review & evolve spec

✓

Context: Centralized in spec documents

✓

Process: Architect upfront, fewer surprises

✓

Best when: Multi-file, evolving projects, prototypes

Both approaches have their place. Ad-hoc is fast for small tasks.
Spec-driven scales better, and that's what we'll focus on today.

IDEs with native spec-driven support: Kiro (new!)