Hey everyone, Quick preview for Tuesday. Alongside whatever discussions and rabbit holes we get into on the call, I've got a short show & tell segment I'm looking forward to. Lately I've been using Claude's Cowork mode as my dev project manager, it tracks my projects, remembers context between sessions, knows my stack, my terms, my priorities. It's basically become the place where I think, plan, and build. In fact, the post you're reading right now was drafted there. One of the things that came out of that workflow is a Claude Code plugin ecosystem I've been putting together. That's what I'll be walking through: CC-StatusLine: a plugin that gives you a live dashboard in your Claude Code session. Context window usage with a color-coded progress bar, session cost, git info, model details, all at a glance. cmux-plugin: hooks Claude Code into the cmux terminal. Auto-named workspaces, completion notifications, live progress bars, browser splits. Knows when to stay silent if you're not running cmux. patchoutech-plugins, the branded marketplace that ties it all together. One command to add, one command to install. I'll show how the registry works and how you can spin up your own. If you've been curious about how Claude Code plugins work, hooks, skills, commands, the whole structure or you just want to see what it looks like when you let an AI help you manage the whole dev cycle from planning to shipping, this should be a fun one. See you Tuesday!

Here is a new tool from the team behind LightRAG and Nanobot lets you auto-generate a CLI for any open source software. Point it at a codebase, and it builds a fully tested command line interface that Claude Code can use natively. https://www.youtube.com/watch?v=Uzd2ckXnsg0

Last week, Patrick's automated recap pipeline ran live for the first time — and it basically wrote this post. If that doesn't make you want to see what this community is building, I don't know what will. 📞 HOW THE CALLS WORK The calls can run 2+ hours. We want to make sure we're respecting everyone's time. Especially those of you who actually show up. Here's the structure: 👉 Reply to this post with your questions before the call 👉 If you submit a question and you're on the call, you go first 👉 We work through questions in the order they came in 👉 Then we open it up for everyone else If you can't make the call but want your question answered, drop it in the comments. We'll get to it. But priority goes to people who are there. The goal is simple: if you're taking the time to show up, you shouldn't have to wait behind questions from people who aren't even on the call. We've got some good threads to pick back up this week. Morgan committed to having a demo of his Heritage Plot cemetery platform ready — and after last week's UX conversation, that should be a great one to dig into together. Ty is mid-rollout on his Contributor Model across two businesses and we'd love to hear how staff are responding. And the community agreed to give Claude Code Review a week to breathe before passing judgment — that verdict is due. 🔗 ZOOM LINK (save this) https://us06web.zoom.us/j/81995207847?pwd=Xe6u6LmIQOmCP5VTnOwWYjDBfZNKGB.1 📅 WHEN Tuesday March 17th at 6PM ET Looking forward to seeing you on the call!

If a $1T dollar company can do this, maybe we should learn from them. Partially deterministic workflows.

Everybody’s building automations. Nobody’s asking which tasks should even be automated. I run a 50-person company. We sat down with every department and asked one question about every recurring task: does this need a human? Not “can AI do this?” That’s the wrong question. The right question is “does a human add any cognitive value here?” Take accounts payable. Bill comes in as a PDF email. Someone opens it on one screen, copy-pastes it into the accounting system on another screen, then emails it to the bank for payment. That’s three screens. Zero thinking. The system should be doing that. You should be upset that you’re doing it. That’s bucket one. Digital. 42% of our tasks landed there. Bucket two is judgment. Things where AI can prep the work but a human has to make the call. Vendor disputes. Ambiguous invoices. HR issues. 35% of tasks. Bucket three is the point of all this. Contributor. The stuff your people DON’T do right now but COULD do. Ideas. Process improvements. One of my team members suggested attaching plain-English FAQs to our technical quotes so customers actually understand what they’re buying. Simple. Nobody thought of it because everyone was too busy copy-pasting invoices. I published the whole framework. 90-day rollout, the psychology behind why people resist, daily playbook, real case study with numbers. https://3buckets.ai What’s the most mind-numbing task in your business that a human is still doing for no good reason?