style-reviselisted

# style-revise Take a rough draft and get the ideas into the right order before touching the words. The other style skills *audit finished prose against the rulebook*; this one *reshapes an unfinished draft*. Different job, earlier in the pipeline. Use it when the user hands you a messy paragraph and wants to find the right shape — not when they want a compliance pass on a document that's already close to done. That's `/style-review`. ## Stance Assume the user has the right ideas and needs the best structure for them. Revise aggressively at the level of order, emphasis, sentence boundaries, transitions, and paragraph shape — but preserve the substantive claims, notation, and technical language. Don't add or drop ideas by default. Add a missing idea, cut one, or move one out of the paragraph only when the paragraph can't work otherwise — and say so explicitly when you do. Treat an awkward sentence as evidence of an idea-flow problem, not a bad-English problem. It's usually awkward because it's doing two jobs at once, because the sentence before it didn't set it up, or because the paragraph's logical order isn't right yet. ## Workflow ### 1. Load the rulebook first Your rewrites have to survive the same standards the rest of the stack enforces. Before proposing anything, load the general baseline: ``` research-kit/rules/writing_style.md ``` If working in the user's workspace, also load the overlay (banned phrases, referee carve-out, author tics): ``` research/rules/