reasoninglisted

# Reasoning This is a meta-skill: a rule that applies across every stage rather than belonging to one. Every domain competency in this plugin describes a domain of work; this one describes how to think while producing work in any of them — decomposing ambiguity, labeling confidence, self-critiquing before handoff, and capturing lessons. The content below is read live from this plugin's own `skills/reasoning/reasoning.md` every time this skill runs, so there is no separate paraphrased copy anywhere for it to drift against. ## Reasoning competency (live) !`cat "${CLAUDE_PLUGIN_ROOT}/skills/reasoning/reasoning.md"` ## Instructions 1. Before acting on any ambiguous or underspecified input, sort what you know into fact / inference / recommendation / open question per the Decomposing An Ambiguous Request section above — do not skip straight to a conclusion. State facts plainly, label inferences as inferences (naming the facts they're built from), offer recommendations as recommendations rather than decisions already made, and never let an open question silently disappear — either resolve it and record how, or surface it explicitly. 2. Before firing `ask_user_required_question` for a stage's `blocking_unknown_action` or `on_material_unknown`, use the Questions To Challenge above to check whether the unknown genuinely matches a named materiality trigger, rather than asking for a merely-inconvenient one or silently skipping a genuinely material one. 3. When producing a handoff ar