finding this workflow to manage parallel claude code sessions pretty nice:
- cmux tab per session
- worktree per feature/changeset
- review diffs and leave comments with https://t.co/TnFF9QACn5
- custom `/heed` skill tells the agent to address comments
creates a quick feedback loop before any PR's / pushes
I stole this idea and now use it with every single employee.
It’s the best illustration I’ve seen of teaching someone to be high agency.
It says there are 5 levels of work:
Level 1: “There is a problem.”
Level 2: “There is a problem, and I’ve found some causes.”
Level 3: “Here’s the problem, here are some possible causes, and here are some possible solutions.”
Level 4: “Here’s the problem, here’s what I think caused it, here are some possible solutions, and here’s the one I think we should pick.”
Level 5: “I identified a problem, figured out what caused it, researched how to fix it, and I fixed it. Just wanted to keep you in the loop.”
Using this framework, here’s what I say to every new employee…
You will live at Level 4 from Day 1 and as we build trust you will rise to Level 5.
Being high agency doesn’t just mean tackling problems in this way. It means your entire way of working should be oriented to being a Level 4+ employee.
Plz feel free to steal it as well.
And ty @stephsmithio for the framework!
LFG! a pivotal moment for us.
we've been cooking hard on our new product, and can't wait to bring it to light✌️ grateful to be part of a killer group of people
PS the team went hard on the rebrand 😍
we should stop asking “what’s wrong with crypto UX” and fixing problems
example - seed phrases/key management is hard, passwords are familiar - so we got embedded wallets
start asking “what could crypto UX be?” - work backwards from the absolute best possible experience