EP.006 - The Orchestrator Method | Human in the Loop

Sash demos the five principles behind 'build the thing to build the thing' 0:00 Intro 2:23 The Orchestrator Method - what it is and why it exists 3:27 Principle 1: define the end state 5:54 Principle 2: plan it with AI (and use plan mode in Claude Code) 7:23 Principle 3: deconstruct and delegate 10:26 Principle 4: stay in the loop, with the 95% trust rule 13:35 Principle 5: build systems for reuse 18:08 Next week: Hermes Agent and agents talking to each other without us Sash walks through the Orchestrator Method - his five-principle framework for delegating real work to AI without losing the plot. The principles: define the end state, plan it with AI, deconstruct and delegate, stay in the loop, and build systems for reuse. None of it is technically novel - it is the same delegation muscle that any consultant, engineer, or manager already has - but Sash names it explicitly so you can run it as a checklist when you are wiring up agents instead of reinventing the wheel each time. The conversation moves between the meta (when to stay in the loop, when to step out) and the practical (a Sunday newsletter workflow Sash built with Nuro, a Google Ads skill he built with Claude for the laundry business he runs with his wife). Chris ties it back to his own Grove build - he started by modeling agents like a corporate org chart with a CTO and architect and found the management overhead was wasted, so he flattened it. The big shared insight is principle four: humans stay in the loop only until trust is earned. Chris's rule of thumb is 95% - if AI is right 95% of the time and he is not adding value in review, why is he still in the loop? The episode closes with a teaser for next week: Sash is bringing in Hermes Agent, an always-on AI Chris has been running for himself, his girlfriend, and the family. He logged in a few days ago to find his agents had been talking to each other without him. TAKEAWAYS - Use plan mode in Claude Code (Shift+Tab) before you let it write anything - it cannot touch files, so a misclick is harmless and the output is sharper. - If you do not know what good looks like for the end state, do not guess. Ask AI to draft the spec with you - 800-1,000 words, this geography, this time window - then start. - Pick a trust threshold for taking yourself out of the review loop. Sash and Chris both use 95%. Below it, stay in. Above it, step out and let the system run. - The third time you do something manually, turn it into a skill. Hermes Agent does this automatically; in Claude you have to remember to ask. - The orchestrator method is fractal - apply it to a single prompt, a single skill, an agent, or a multi-agent system. Same five steps, different scope. --- Human in the Loop - Real people. Real tools. Fifteen minutes. New episodes every Friday at 4:05 PM ET on LinkedIn Live. Website: https://humanintheloop.stream Episode page: https://humanintheloop.stream/episodes/006.html Hosts: Chris Shanku & Sash Mohapatra