Using it

Working with Larry

Larry is a thinking partner, not a search box. He reads what you are doing, picks the framework that fits, and pushes you toward a sharper answer. You never memorize commands. You describe what is stuck, in plain words.

The job this does

When you sit down to think through a hard problem, you want to a partner who pushes back and runs the right method, so you can you reach a decision you can defend, faster.

In plain terms

Think of Larry like a sharp professor in office hours. You do not walk in and say "run framework 12." You say "I cannot tell who my customer is." He picks the method, asks the hard question, and writes the useful parts down for you. The writing-down is the room. The method is his job. The judgment stays yours.

How it works

Every turn runs the same loop. You speak, Larry routes to a method, the room files what matters, and Larry proposes the next move. It does not reset between turns or between sessions.

How to talk to him

Use plain language. Describe the stuck point, not the tool. Larry does the routing.

You say / Larry fires

You say: "I am stuck on whether to pivot."

Larry runs Devil's Advocate to stress-test the current direction before you commit.

You say: "I keep finding the same insight in three meetings."

Larry synthesizes the pattern across them and proposes what it means.

You say: "I am hunting a bottleneck in customer acquisition."

Larry tunes the next-move menu around bottleneck-hunting methods.

The pattern that works

Describe the problem. Let Larry suggest the move. Run it. Read what got filed. Repeat. When you feel stuck mid-run, ask a plain "by the way" question. When a run finishes, run /mos:status to see what shifted.

Trust the staged proposal.

When Larry says "your next move is X," he has read your room state, the Brain neighborhood, and your recent decisions. Override only when you specifically know better.

PreviousThe 30-minute onboarding NextPublishing Vercel pages