One-Sentence Test

Related skills: use post-implementation-review when the sentence is part of a post-change second read, and cohesive-clean-breaks when the sentence drives an API, ownership, lifecycle, or package boundary change.

Core move. Before continuing, stop and write one concrete sentence that describes the subject. Name the objects, verbs, and scope. No marketing words. No "flexibly handles." No "unified experience." Then use the sentence as an audit tool.

Show your work. Write the sentence out in your response, visibly. The value is in the reader seeing the gap between what the prose claims and what the subject actually is: that only happens if the reduction is on the page, not silent in your head.

If the sentence keeps drifting as you write it, the design isn't coherent yet: that's the finding. Name the ambiguity before continuing.

The move has two applications. They're distinct lenses on the same discipline: pick the one that fits the subject.

Application A: Cohesion Audit (top-down)

When: reviewing a design, spec, or surface (commands, endpoints, options, tables) for coherence. The sentence is the thesis; every surface is audited against it.