https://video.ut0pia.org/videos/watch/44ee79c1-5608-4a73-a2c0-1df3f6883256 Leave agent adoption to individuals and the engineer shipping two PRs a day ends up reviewing the ten that the early adopter ships. They fall further behind, the code they are reading is worse, and they conclude the agents are the problem. Aditya Khandelwal's argument, from leading a team of ten through this, is that adoption is therefore a leadership problem and not an IC one, because the changes that actually work, restructuring a codebase for progressive disclosure and converging on a shared setup, are not changes one engineer can make alone. The symptoms of a bad setup are specific. Engineers babysit runs. A simple task burns through 500k of context and hits auto compaction. Someone says the model got dumb today, when the model did not change and the harness did. Their fix centered on one high value skill, called ship it, that carries a change from code done to PR ready, handling the description, the review comments, and CI failures, and often runs for over an hour. That duration scared people until they saw what it bought them. Around it they wired issues and boards into the repo, agentic reviews, and a code gardener that runs nightly. It was not clean: agents filing against each other took the repo to roughly 4,500 open issues in a couple of weeks. Stay for the Q&A, which lands a hard limit near 100 lines in a skill file and offers first prompt context burn as the test of whether progressive disclosure is actually working. Speaker info: https://www.linkedin.com/in/aditya-khandelwal/, https://github.com/adityak6798, https://adityak6798.github.io/, Timestamps: 0:00 - Why solo agent advice breaks on a team 1:30 - The adoption journey, from mandates to slop 2:10 - Fear against confidence, the two axes 4:02 - Is a CLAUDE.md and some skills enough 4:38 - Symptoms that your setup is wrong 5:52 - Why this is leadership's job, not an IC's 6:31 - The review burden trap 7:09 - Harness engineering principles 7:45 - Smart prompt injection 8:25 - Close the loop and keep iterating 9:08 - The playbook: start with the basics 9:47 - Ship it, the one high value skill 11:02 - Winning over the skeptics 12:18 - What went wrong along the way 12:57 - Let prototypes opt out of the standards 13:34 - Stop saying the model is dumb 14:10 - Commit to the turn 14:47 - Q&A: strategies for progressive disclosure 16:03 - Measuring context burn on the first prompt Tue, 11 Aug 2026 20:24:51 GMT https://validator.w3.org/feed/docs/rss2.html PeerTube - https://video.ut0pia.org https://video.ut0pia.org/lazy-static/avatars/0287a09a-aae7-4840-9843-b416426e7046.webp https://video.ut0pia.org/videos/watch/44ee79c1-5608-4a73-a2c0-1df3f6883256 All rights reserved, unless otherwise specified in the terms specified at https://video.ut0pia.org/about and potential licenses granted by each content's rightholder.