One loop for clear knowledge work: check whether evidence is strong enough for the next action, shape the deliverable one useful question at a time, draft from an approved spec, review the result, and remember what you like.
Missing decisions, evidence limits, readiness, and required human approval stay visible.
Skills 6 in the Claude listing
calibrating Use after a knowledge-work deliverable ships or gets human edits. drafting Use when a mindpowers spec exists and the user wants the actual deliverable written, such as "draft it", "write the memo from the spec", or right after mindstorming locks a spec. Fact checking Use before a finished document ships, when the user asks "fact-check this", "is this ready to send", "check the numbers", or after drafting/review hand off a doc that carries checkable claims (numbers mindstorming Use before drafting any non-code knowledge-work deliverable, including strategic memos, business reviews, OKR defences, PRDs, decision docs, briefing docs, exec talking points, Slack messages to leade Reviewing docs Use when the user has a finished or near-finished document (memo, business review, PRD, decision doc, briefing, comms, framework, talking points, post-mortem) and wants it pressure-tested before it sh Validating problems Use when a user wants to test, sharpen, frame, or gather evidence for a customer or business problem before pitching a direction, prioritising work, or writing a PRD. 