This Coding Tool Kills AI Code Slop

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

Source video:
- Title: This Coding Tool Kills AI Code Slop
- URL: https://www.youtube.com/watch?v=XLtuSy1opW4
- Topic: Agentic Engineering
- My current learning frame: On a small AI-assisted TypeScript project, run the dead-code, dupes, and health commands, fix one validated finding from each, then add a boundary rule and a post-commit hook so the scan runs automatically.
- Why this matters: This directly addresses the gap between "agent did something" and "agent made something excellent."

Transcript anchors from this exact video:
- 1:09 / Evidence 1: "It actually is very fast all things uh considered. The benchmarks do be benchmarking. Now, using FOW is dead simple. You just run npxow and then there's a number of different tools like dead code, dupes, health and..."
- 3:27 / Evidence 2: "presets here that you can use. Uh or you can easily write your own with your individually tuned preset or just folder structure. So that way when AI is working, it can run your boundary violations code and..."
- 5:22 / Evidence 3: "also in the same file as uh 328 to 338. That's a prime target for something that is going to be refactored. And this is one of those tools that you will want to when you're first getting..."
- 7:01 / Evidence 4: "absolutely love about this tool is how fast it is. Meaning that you can just keep running it. You can have agents run it. You can run it personally, put in your CI, any of that sort of..."
- 8:37 / Evidence 5: "I'm talking about spelt kit, Gatsby, Astro, Angular, Expo, NextJS, NestJS, Nitro, Capacitor, Sel, uh, Vess, and the bundlers. V, Webpack, RS pack, RS build, roll up, roll down, TS up, TS down, uh, linting. It works with..."

Video-aware target:
- Prompt lane: Agentic engineering
- Mechanism to extract: Extract the engineering loop that converts an agent demo into controlled, inspectable work.
- Artifact to produce: A task packet and review rubric that a coding agent could execute without wandering.
- Artifact must include: scope; context inputs; acceptance criteria; verification command; review rubric

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, transcript support, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable mechanism from the video: Extract the engineering loop that converts an agent demo into controlled, inspectable work. 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 and review rubric 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 -> Context -> Agent run -> Evidence -> Review -> Reusable standard
   - answers to these source questions: What work packet is implied? | Which context does the agent need before editing? | How does the video define proof or quality?
   - 3 concrete examples that apply the video idea to real agentic work, such as a feature patch packet; a test-fix packet; a learning-page improvement packet
   - 2 failure modes the video helps prevent, chosen from the transcript evidence and these likely risks: delegating vague intent; accepting output without evidence; turning taste into loose preference instead of a rubric
   - a checklist for the next real workflow, focused on: scope, files/context, tests, review criteria
   - one practical exercise with a clear done signal: Rewrite one vague request into a bounded agent packet with explicit proof of done.
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 "This Coding Tool Kills AI Code Slop", not a generic Agentic Engineering essay.
- Cite the transcript wherever the prompt names a task boundary, review habit, context move, or verification standard.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- Avoid these generic drifts: generic productivity advice; unsupported claims about autonomy; summaries without implementation criteria.
- If evidence is weak or missing, stop and say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.