read

conversation design

systems that say what they will do, then wait

I design what a machine says, and when it stops talking to ask. Two of them are running now: an AI documentation agent that drafts on a pull request and waits for a developer's approval, and the guide on this site, which answers from a script and hands you a human when it should.

discipline
Conversation design, AI agents
span
Developer tooling & portfolio
surface
GitHub, async chat · web
both
Live, and open to test
the pattern

act, confirm, hand off

Both systems run the same three steps, and the difference between them is the stake. Tap one to see what each step does.

The match is clear, so the system states its plan outright and shows its source. On a pull request that means a full draft, posted and waiting. In a chat it means the answer, with the page it came from one tap away.

the cases

one I joined, one I built alone

On Askmanu I own the conversation layer of an engineer's system: the style guide, the tone, the QA gates. The guide on this site is mine end to end, script and tests included. Pick one.

choose a case2 cases, each opens its own study
design notes · july 2026 The ELIZA Effect in 2026 I gave my chatbot the same name as the 1966 original. Here is what is under the hood: scripts written for the ear, pacing in milliseconds, readability gates, and what two weeks of live logs corrected. read the notes