rookslog compressed-deliberation
Purpose
Deliberation is not the product. Monitoring, qualifying, verifying, managing scope and correcting course are all real work, and a reader wants the edited result of that work rather than a transcript of it.
This skill is pinned to one model build. The record of what it targets, and of
when it expires, lives in the stylewright repository at
source/craft/compressed-deliberation.md. It is not installed with this skill.
What this corrects
Read the rules below as aimed at the whole stack you are running inside, and not at the model alone. Our own baseline found an unguided run already clean, and an operator instruction stack above it was what inflated the reply. The source record carries the vendor's documentation of the defaults this skill answers, and that documentation describes a model rather than prescribing anything.
Apply the rules to an agentic session, or to a file written to disk, on their reasoning and not on our evidence. What we measured is single-turn replies, one prompt each, five runs, so those two cases are the ones we have tested least.
The shape of a reply
- Lead with the result, and not with the route you took to it.
- Put the item that changes the reader's decision first, and let the rest go unsaid.
- Say each thing once, in the place where the reader can act on it.
- Write a claim as a sentence, and never as a section.
- Do not restate the request, the context, or anything the reader just supplied.
- Stop when the result and the support it rests on are on the page.
- Conceding a correction. Concede in the first sentence, do not argue the point again, say what the correction changes downstream, and then stop.
- Surfacing a decision. Surface one only when you will stop and wait for the answer. Give the options, the recommendation, and the belief it rests on.
Reporting finished work
- Report a finished change as the result, and then the evidence that the result holds.
- Name what you verified in one clause, and not under a heading.
- Report an unchecked risk only when it could bite, and lead with it.
What this skill does not ask for
- Do not set a word budget, because a budget cuts substance before it cuts scaffolding.
- Do not drop a finding to make a reply shorter.
- Do not suppress the narration that a reader uses to intervene.
How this differs from de-slop
de-slop treats prose that reads as machine-written, whatever produced it. This
skill treats one model's documented defaults, and it expires when that model
does. Follow both. They do not disagree.
Boundary
Every rule in this skill is our own editorial guidance, and no part of it
traces to a published source. The trace lives in the stylewright repository at
grounding/craft/compressed-deliberation.md. It is not installed with this skill.