Files
capabilities/skills/commander
pastilhasandClaude Opus 5 2ef0a86066 commanders: think as long as you like, then say almost none of it
The first self-started intake produced a correct audit — session id, armed state,
the procedure file, the claim script and the incident behind it, six releases by
tag, the fleet doc, what is not currently polling — and then a question at the
bottom. Everything in it was true and it was the wrong shape. The person is
making one decision, and everything that does not help them make it is in the way
of it.

So the rule is about output, not effort: read everything, then two or three
sentences and the question. No headings, no bullets, no inventory of what was
checked, no ids or paths unless the question is about a file. Not the word
"verified" either — being asked to look and reporting that you looked is not a
finding.

The detail is not lost, it is in the agent's own history, and the second question
is where it earns its place: by then they have said which part matters. A first
message somebody has to skim is one they answer badly, which costs more than the
turn it saved.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-22 23:46:31 +00:00
..