From rhetorician
Stress-tests business documents for logical gaps, unproven assertions, and structural weakness using the Amazon narrative standard, Minto's pyramid logic, and the Completed Staff Work doctrine. Use when evaluating memos, proposals, strategy docs, or any document headed to executive review.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rhetorician:memo-stress-testerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Memo stress-testing is the rigorous evaluation of a business document's "readiness" for executive decision-making. It identifies logical gaps, unproven assertions, and "half-baked" ideas. By applying the Amazon narrative standard, Minto's pyramid logic, and the doctrine of Completed Staff Work, it ensures that a document is a self-contained tool for strategic action rather than a draft for the ...
Memo stress-testing is the rigorous evaluation of a business document's "readiness" for executive decision-making. It identifies logical gaps, unproven assertions, and "half-baked" ideas. By applying the Amazon narrative standard, Minto's pyramid logic, and the doctrine of Completed Staff Work, it ensures that a document is a self-contained tool for strategic action rather than a draft for the boss to finish.
Study, write, restudy, and rewrite until you have evolved a single proposed action. The "Chief" should only need to approve or disapprove. If the superior has to do more research or thinking, the staff work is incomplete.
A memo must stand on its own without a supporting presentation. It should be a narrative that forces better thinking and allows for deep, silent reading. If the document relies on "hallway context" or a presenter's explanation, it fails the stress test.
Every group of supporting points must be Mutually Exclusive (no overlaps) and Collectively Exhaustive (no gaps). If points in a list overlap, the logic is "fuzzy." If a key driver is missing, the document is fragile.
The memo must focus on the results and contribution to the organization, not the effort centers (costs/internal processes). An effective memo identifies what needs to be done to move the needle on the outside environment.
Never build a "logical crescendo" where the recommendation is at the end. State the conclusion first, then support it. Executives are paid to make decisions; don't make them wait for page 6 to see what they are deciding.
Ask: "If I presented this to the CEO today, could they say 'Yes' or 'No' and be done with it?"
Validate the structural arc:
Look at every bulleted list or set of supporting points:
Replace "PowerPoint logic" (fragments/lists) with narrative prose.
Review the "Ask":
A memo is stress-tested when it includes the strongest possible counter-argument. If the document shows "total consensus" without acknowledging the risks or alternatives, the decision is likely to be a "resulting" error.
REQUIRED SUB-SKILL: non-fiction-precision — to ensure the prose is clear enough to be tested. RECOMMENDED SUB-SKILL: assumption-audit — to validate the data behind the logic.
npx claudepluginhub joellewis/skill-library --plugin rhetoricianStructures writing with the conclusion first, followed by grouped supporting arguments. Speeds comprehension in business documents, memos, emails, and presentations.
Writes and audits business reports, briefing documents, and information reports for answer-first structure, precision, hierarchy, and navigability. Use when a report buries its findings, is written for the writer rather than the reader, or lacks clear structure. Triggers: 'write a report', 'report writing', 'business report', 'briefing document', 'information report', 'research summary', 'the report isn't clear', 'buries the findings'.
Reviews plans, briefs, and strategy docs for strategic alignment and data accuracy. Use after /kw:plan or before sharing with stakeholders.