FULL Guide to Becoming a Principled Agentic Engineer (Build Anything with AI)

You are helping me turn one specific YouTube video into real, durable learning.

Source video:
- Title: FULL Guide to Becoming a Principled Agentic Engineer (Build Anything with AI)
- URL: https://www.youtube.com/watch?v=luBkbzjo-TA
- Topic: Agentic Engineering
- My current learning frame: Take one real ticket end to end: brain-dump the idea to your agent, produce a plan.md, then open a fresh session to implement and validate it, and finish with your own code review before merging.
- Why this matters: This is the north-star learning path for doing serious work with agents.

Transcript anchors from this exact video:
- 0:30 / Evidence 1: "complicate AI coding frameworks all of the time, making it seem like you need some fancy harness or specialized agents just to do any real work at scale. But that really isn't the case. So I boil things..."
- 8:25 / Evidence 2: "here is as simple as it possibly can be. You are going to open up your coding agent, like I'll, you know, just pop open Claude Code right here. And you're just going to have a conversation about..."
- 9:56 / Evidence 3: "it's a lot of just curating this context with the help of the coding agent being very specific for what you want to build. And so the most powerful strategy here, and you'll see this in action in..."
- 26:13 / Evidence 4: "we're having the coding agent run through. So we're having it load the PRD because we can also run this in a separate Cloud Code session if we don't want to run it in the same one. So..."
- 33:14 / Evidence 5: "pointed cloud code there and I said all right Claude for this AI transformation workshop that I'm doing with Leor I want you to set up a brand new repository and bring in my resources and customize it..."
- 53:09 / Evidence 6: "and unit testing. We could also have it do endtoend testing if we wanted to use browser automation tools with um you know the agent browser CLI for example. So that's actually one of the skills that I..."
- 57:52 / Evidence 7: "also fix the system that allowed the bug. And what I mean by that is we can have a sort of you know retroactive session with the coding agent where we say okay Claude you allowed this problem..."

Your task:
1. Use the transcript anchors above as the primary source packet. If you add outside context, label it clearly as outside context and keep it secondary.
2. Create a source-check table with columns: timestamp, claim, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable claims from the video. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A task packet that a coding agent could execute without wandering.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Intent -> Task Packet -> Agent Run -> Evidence -> Review -> Standard
   - 3 concrete examples that apply the video idea to real agentic work
   - 2 failure modes the video helps prevent
   - a checklist I can use the next time I run Codex or Claude
   - one practical exercise with a clear done signal
6. Add a "learning transfer" section: what changes in my workflow tomorrow if I actually learned this?
7. Add a "source check" section that cites which transcript anchor supports each major takeaway.

Quality bar:
- Make this specific to "FULL Guide to Becoming a Principled Agentic Engineer (Build Anything with AI)", not a generic Agentic Engineering essay.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- If evidence is weak, say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.