reimagine-work

Reimagine work (v3.3 template: weekly Elon loop + continuous stream + escalation ladder + earned autonomy)

Template. Replace every <PLACEHOLDER> with your own values. Nothing in this skill sends, posts, spends or approves anything; it only proposes. The judge it refers to ships in shadow mode (log only) with hard gates on.

Find every place a human is what work waits on, remove that wait, and do it again next week. The deliverable is a short ranked list and exact yes lines, not a long report.

Asks that are already answered (never re-ask)

Before any yes line reaches the human, check these in order. If any one is true, the work proceeds with no new ask, and it gets logged with what authorized it:

1. The human already said it. If the owner's own words in this conversation asked for this exact action ("send these follow-ups, by email and chat"), that is the yes. A copy tweak they asked for ("keep it simple like the outbound") is still inside that yes. Do not send a confirm line for the same batch.
2. A lane owner approved it. If the person who owns the lane (for example, the content lead for publishing) approved, proceed under their conditions. Don't ask the top owner for a second yes.
3. A standing approval with a cap covers it. Check the approval ledger. A matching row with owner_bots, a cap and a scope is the yes.
4. It's reversible or read-only. No yes at all.

The human gets a yes line only for a new send, spend, publish, delete or gate change that none of the four covers. Each yes line that does reach them gets counted. If any lane sends more than 2 a day, flag it in the next pass as a defect to fix.

Where the idea comes from

These principles come from a public write-up by a ten-person company that runs a fleet of permanent agents. Its founder says they "found what work was waiting on and removed it, over and over." Use these principles to judge each redesign:

1. Own an area. Each agent is permanent and owns one part of the company. Two agents doing the same job is a SIMPLIFY finding.
2. Coordinate through the world, not through messages. Agents stop "telling each other what they were about to do." They read and change a shared record (queue, ledger, state file). A human relaying a message between agents is a finding.
3. Fix forward. A small reversible change goes in, a later check catches problems, and any break is fixed with a new change on top. Asking before a reversible internal fix is a finding.
4. Test on a clock, not per change. Run the full check on a schedule against the latest state. "It broke since the last run" is enough to find the cause.
5. Review by someone who didn't write it. Helper agents try to break a change before it lands.
6. Agents read production themselves. Errors, receipts and metrics go straight to the owning agent, and no human relays them.
7. A stall is an incident. A lane that ships nothing for a full working period pages its owner agent.
8. AI judges from recorded decisions. A judge either decides and cites where the owner already answered, sends back a wrong question, or holds the question for a human. "When a judge gets one wrong we say so, and the judges read that next time."
9. Nothing waits on the queue. Open asks that sit for days are the loop's main measure of failure.
10. Hard gates stay small and dumb. Anything that touches the outside world and can't be undone goes through "a small set of dumb, hard-coded gates."
11. Humans keep taste. That means saying no, deleting what the last model needed, and asking for 10x or 100x, which models do not ask for on their own.