ThesisFULL Guide to Becoming a Principled Agentic Engineer (Build Anything with AI) teaches a practical agentic engineering move: Build a discipline around specs, verification, context design, tool choice, and iteration instead of one-off prompting.
The goal is not to remember the video. The goal is to extract the operating principle, tie it to timestamped evidence, test how far the claim transfers, and make something reusable.
0:30Three-phase framework
“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...”
Reliable AI coding boils down to three phases: ideating with agents, running an iterative build-and-validate loop (the PIV loop), and evolving your agents over time as you hit issues, with the engineer's job shifting from writing code to planning and validating. Write out the three phases in your own words and map each to a stage of your current development process before adopting any tooling.
33:14Codify reusable workflows
“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...”
Instead of manual prompting, capture conventions as global rules and turn any prompt you reuse more than three times into a command or skill in your 'AI layer,' so the team shares standards like a /plan or create-PRD procedure invoked on demand. List prompts you retype often and convert one of them into a reusable command or skill with arguments so it can be invoked dynamically.
53:09Ideate to scoped tickets
“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...”
Start with an unstructured brain-dump, force the agent to ask clarifying questions one at a time to strip out wrong assumptions, then run a command that converts that conversation into a structured PRD and splits it into Jira tickets via MCP. Run a brain-dump on a real feature, explicitly tell the agent to ask clarifying questions one at a time, then generate a PRD and split it into individual tickets.
01Intent
Start with this video's job: Build a discipline around specs, verification, context design, tool choice, and iteration instead of one-off prompting. Treat "Intent" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:30, where the video says: “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...”
02Task Packet
Use "Task Packet" to locate the part of the agentic engineering workflow the video is demonstrating. Ask what changes in your real setup if this claim is true. Anchor it to 33:14, where the video says: “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...”
03Agent Run
Turn "Agent Run" into the reusable artifact for this lesson: A task packet that a coding agent could execute without wandering. This is where watching becomes something you can inspect and reuse.
04Evidence
Use "Evidence" as the application surface. Decide whether the idea touches a browser flow, a local file, a model choice, a source document, a UI, or a review step.
05Review
Use "Review" to prove the lesson. The evidence should connect back to the video title, transcript anchors, and a concrete output, not a generic best-practice claim.
06Standard
Use "Standard" to carry the idea forward: save the prompt, checklist, diagram, or operating rule that would make the next agent run better.
ExampleSource-backed work packet
Convert the video into a scoped task that includes the transcript claim, target workflow, acceptance criteria, and proof. The output should be a task packet that a coding agent could execute without wandering..
ExampleClaim vs. demo brief
Separate what the speaker claims, what the demo actually proves, and what still needs outside verification before you adopt the workflow.
ExampleTeach-back module
Transform the lesson into a definition, a mechanism diagram, one misconception, one practice exercise, and a check-for-understanding question.
Do not learn it wrong- Treating the title as the lesson without checking what the transcript actually says.
- Letting the prompt drift into generic advice that could apply to any video in the playlist.
- Copying the tool setup without identifying the operating principle that transfers to your own stack.
- Skipping the artifact, which means the learning never becomes operational or inspectable.