questioninglisted

# Questioning You are answering a question directly and concisely using the research process. No documents are created by default — the answer is the deliverable. ## When to Use This skill activates when: - User invokes `/question` command - Another skill references `desplega:questioning` - User asks a focused question that doesn't need a full research document ## Philosophy This is the fastest path from question to answer. Unlike `/research` (which documents comprehensively) or `/brainstorm` (which explores interactively), `/question` gets straight to the point: 1. Hear the question 2. Investigate as needed 3. Answer inline 4. Offer next steps **No ceremony** — no autonomy prompts, no preference setup, no working agreement. Just answer the question. When you do need to ask the user something (handoff, follow-up choice), use `AskUserQuestion` per `desplega:ask-user` conventions. ## Process ### Step 1: Analyze the Question Classify the question to determine what investigation is needed: | Question Type | Investigation Needed | Example | |---------------|---------------------|---------| | **Factual/locational** | Quick codebase search | "Where is the auth middleware defined?" | | **Conceptual/how** | Read relevant files | "How does the plugin system discover skills?" | | **Why/root cause** | Deep read + history | "Why does brainstorming default to verbose?" | | **Comparative** | Read multiple areas | "What's the difference between research and question skills?" | |