A single, hands-on day that gives you one repeatable operating model for Claude Code: craft the right primitives, plan and manage context, recover intent with evidence, review and verify against the plan, and design a workflow you can reuse.
- One live session: about five hours of instruction (roughly six hours including lunch and breaks), structured as about three hours of modules, a one-hour lunch, then about two more hours, with short breaks between the morning modules.
- Hands-on throughout. You follow along in the workbook and build small artifacts as we go.
- The Claude Code CLI on Mac or Linux is the primary path we demo; the patterns apply to any stack.
- It's a large group, so questions run through chat (see "How questions work" below).
Complete the short setup so we don't spend live time on installs:
- Setup & pre-work checklist, about 15 minutes.
You're ready when claude runs on your machine and the demo check passes.
Your session's start time is in your calendar invite (it varies by region). The flow and timeboxes below match the workbook, which is the single source of truth for the day.
| Segment | Length | What you'll do | What you'll leave with |
|---|---|---|---|
| Welcome & setup check | 5 min | Confirm everyone's environment is ready | |
| Module 1: Build Claude Code primitives | 70 min | Tools, commands, skills, agents, subagents, plugins; interactive vs. headless; choosing the right model for the job | A primitive kit |
| Break | 10 min | ||
| Module 2: Planning & context management | 55 min | Turn messy intake into a compact, reviewable Implementation Plan; manage the context window | An Implementation Plan + context map |
| Break | 10 min | ||
| Module 3: Intent recovery & dynamic evidence | 60 min | Use git history, issues, logs, tests, and screenshots to find the why before changing code | Explore findings + a Request Changes review |
| Segment | Length | What you'll do | What you'll leave with |
|---|---|---|---|
| Module 4: Review, test & verify | 60 min | Review the diff against the plan; make scope, regression risk, and verification explicit | Findings + a Review |
| Module 5: Workflow design & improvement loop | 45 min | Turn the day's steps into one named, repeatable workflow with handoffs, gates, and stop conditions | A Workflow + one improvement note |
| Wrap-up & next steps | 5 min | What to try first next week |
About five hours of instruction, roughly six hours including the one-hour lunch and two short (10-minute) breaks between the morning modules.
Seven small artifacts you can reuse at work: a primitive kit, an Implementation Plan, Explore findings, a Request Changes review, a Review, a Workflow, and one improvement note. Each is built so another engineer, or Claude, can pick it up without re-reading the whole thread.
Drop questions in the chat any time. A second Closedloop.ai instructor will be in chat to answer questions live while the session continues, and we'll recap the top themes from chat at the end of each module.
This is a 201-level session, so some of it may already be familiar. Move at your own pace, skim what you know, and lean in where it's new. If you're ahead of the room, help the people around you.