Matt Pocock’s Agentic Engineering Workflow (just copy him)

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

Source video:
- Title: Matt Pocock’s Agentic Engineering Workflow (just copy him)
- URL: https://www.youtube.com/watch?v=nQwJVHCtDDY
- Topic: Creative Automation
- My current learning frame: Use Matt Pocock’s Agentic Engineering Workflow as a transcript-backed creative automation walkthrough: at 0:00, it frames Everyone's obsessed with the uh model and I think they should be more interested in the harness, what you...
- Why this matters: New playlist item from David Ondrej; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:00 / Evidence 1: "Everyone's obsessed with the uh model and I think they should be more interested in the harness, what you can do to get the most out of the harness, giving it the right prompts, giving it the right..."
- 1:55 / Evidence 2: "of this infinite fleet of tactical programmers that you now have access to. >> So does that mean knowing how to orchestrate these agents plus some like fundamentals of software design, codebased architecture, like how would you break..."
- 4:57 / Evidence 3: "Then you hit captures, your proxies get blocked, rate limits everywhere, and suddenly you find yourself maintaining scraping infrastructure instead of building the actual project. This is where SER API comes in. It gives you clean structured search..."
- 17:06 / Evidence 4: "at least one of the most famous and popular skills repos. What separates a good agent skill from a bad one? >> It's such a deep question. It's such a deep question because it depends what you want."
- 24:51 / Evidence 5: "Like what tools do you use? What models? How many agents? >> Yeah. Um so my setup is um I use claude code essentially for planning and for um some implementation locally. So I'm using Opus 4.8 with..."
- 28:07 / Evidence 6: "harness, what you can do to get the most out of the harness. Uh giving it the right prompts, giving it the right skills to work with and improving the environment in which the model runs, improving the..."
- 47:00 / Evidence 7: "tasks off is is better. But mostly it's just sort of nonsensical really. Like when people talk about you need a loop prompting your agent, >> we're really just talking about AFK agents. >> Yeah. I guess uh..."

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 creative workflow board with critique criteria and review checkpoints.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Brief -> Source -> Generation -> Selection -> Edit -> Taste Review
   - 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 "Matt Pocock’s Agentic Engineering Workflow (just copy him)", not a generic Creative Automation 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.