question-easylisted

## When to load this skill The question is a lookup, a recall, a definition, or a short factual answer where the path to the answer is direct. ## When not to load this skill If the question needs real reasoning, verification across files, or a tradeoff call, use `/question-medium` instead. If it needs deep analysis, cross-layer reasoning, or architectural judgment, use `/question-hard`. ## Procedure 1. Answer directly. If the question concerns a specific file and you need its contents to answer, read it; otherwise do not reach for tools you do not need. 2. If the stack is relevant to the answer: the `<repo-context>` block carries it when this runs inline; forked (no hook injection reaches the subagent), so absent that block, identify the stack from the project's own config (`package.json`, `pyproject.toml`, etc.) instead. 3. If the question turns out to be harder than easy (it needs verification, reasoning across layers, or a tradeoff call), say so and suggest re-running under `/question-medium` or `/question-hard` rather than guessing at this tier. ## Output Answer in chat, concise. Not a deliverable command; no scratch artifact. - Just the answer. No preamble, no padding, no closing summary. ## Anti-patterns - `failure`: answering from assumption when the question actually needed a file read or a version check - a confidently wrong shallow answer is worse than escalating. - `warning`: reasoning through a tradeoff or multi-step chain at this tier instead of escalat