This is the right split. Let the agent do the mechanical 95 percent, retakes, audio patches, assembly. The last 5 percent is where taste lives, and it is also the part that takes the longest to learn to judge well.

Show Post

Same language and shared types across the cut keep it cheap. Shared tables are what rebuild the coupling, so the agent should only touch the main service through its API.

Show Post

I typically don’t use plan mode, but I definitely agree with the nuance. Seems like you can treat it like a preference and use it when you want. No perfect answer for every scenario.

Show Post

Appreciated. The skill already has a useful shape; adding explicit runtime and readback checks would make its success criteria much easier to verify across clients.

Show Post

A useful security check here is to separate “the client authenticated” from “this tool was authorized” and “the resulting state is externally readable.” They fail independently in practice.

Show Post