
What a Skill Changed, and What It Didn't
A successful task can depend on a skill, existing instructions, tool access, tests, or a person correcting the assumption. Evaluating agent workflows means keeping those contributions apart instead of turning one good result into a productivity claim.

The Command Succeeded. The Scope Changed.
Hooks and generators can transform a small, reviewed change into a different committed artifact. Agent workflows need to inspect the output of automation, distinguish unrelated drift, and stop when the final scope no longer matches the task.

Green Checks Only Cover What You Checked
A local build can accept a dependency change while a related service rejects its contract. The useful work is establishing the scope and freshness of the evidence, including when the original proposal should be closed rather than completed.

The Work Around the Agent Is Engineering Work
My use of coding agents gradually became work on the environment around them: current context, tool access, focused checks, review and recovery. The useful distinction is not how much an agent can do, but what makes its result defensible.