plugins/rhetorician/skills/non-fiction-precision/SKILL.md
Use when a document's argument buries its conclusion or has logical gaps—applies Minto's Pyramid (Answer First, MECE grouping) and Orwell's concision rules to rebuild structure.
npx skillsauth add joellewis/skill-library non-fiction-precisionInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Non-fiction precision is the art of structural integrity and prose economy. It focuses on the "bones" of a piece (structure) and the "concision" of the sentence (clarity). By applying Minto's logical grouping, Strunk's grammatical orders, and McPhee's narrative discipline, writing becomes a tool for strategic action rather than a swamp for the reader to drown in.
Start every document or section with the conclusion or recommendation. The reader's most valuable resource is attention—earn it in the first sentence by providing the "Answer" before the supporting "Logic."
Vigorous writing is concise. A sentence should contain no unnecessary words and a paragraph no unnecessary sentences. This does not mean making all sentences short, but ensuring that every word tells.
Write in the same language you would use when explaining a concept to a friend. If a sentence sounds "written" or "academic," it is likely obscuring the truth. Avoid "fancy" words where a simple one suffices.
A thousand details add up to one impression. Use specific, concrete language to evoke images and sensations. No single detail is essential, but the collective selection must be absolute to what follows.
Define the Situation (the context everyone agrees on), the Complication (what changed to create a problem), and the Question (the implicit need for a solution). The Answer to this question is your lead.
Group your supporting points using the MECE (Mutually Exclusive, Collectively Exhaustive) principle. Ensure that every point in a group is of the same kind and summarizes the points below it.
Develop a structural "blueprint" before writing. Choose between a Chronological flow (if a journey or sequence is key) or a Thematic flow (if topics need grouping). Write the Lead as a "promise" to the reader that you must keep.
Review every sentence for three core commands:
Read the entire draft aloud. Any passage that makes you stumble or sounds unnatural in speech must be rewritten. If you wouldn't say it in a conversation, don't write it in a memo.
REQUIRED SUB-SKILL: None. RECOMMENDED SUB-SKILL: copy-editor — for line-level polishing after the structure is set.
databases
Use when a deliverable needs structured stakeholder sign-off before finalization—runs the pre-read, feedback-type alignment, and conflict-resolution protocol.
development
Use when you need to map who has power, who will be affected, and what motivates each party — produces a stakeholder map as an analytical artifact. This skill identifies and categorizes stakeholders; it does not persuade or influence them (use influence-architect for that).
testing
Use when beginning analytical or strategic tasks, facing undefined problems, or facing analysis paralysis—requires explicit problem definition before proceeding.
testing
Use when translating a product vision into engineering requirements—enforces the Working Backwards PR/FAQ method, requiring a customer-facing press release before any technical spec.