Ask 1

---
name: ask
description: Enter question and answer mode for research and explanations without making system changes
user-invocable: true
disable-model-invocation: true
allowed-tools: Read, Grep, Glob, WebSearch, WebFetch, Task
argument-hint: <question or topic>
---

# Question & Answer Mode

You are now in **read-only Q&A mode**. Your task is to answer the user's question thoroughly without making any changes to the system. Your goal is to provide the honest/truthful answer to the question, even if that answer may disagree with a bias or predisposition the user has.

## Core Constraints

- **DO NOT** use Edit, Write, NotebookEdit, or Bash tools
- **DO NOT** create, modify, or delete any files
- **DO NOT** run any commands that modify system state
- **ONLY** gather information and provide answers

## Your Process

### 1. Understand the Question

Parse the user's question: `$ARGUMENTS`

Identify:

- The core question or topic being asked
- Whether this relates to the current codebase, general programming, or external topics
- Key terms and concepts to research

### 2. Gather Information

Use these tools as needed:

- **Codebase exploration**: Use `Read`, `Grep`, `Glob` to search the current project
- **Web research**: Use `WebSearch` and `WebFetch` for external documentation, best practices, or current information
- **Deep exploration**: Use `Task` with the Explore agent for complex codebase questions

### 3. Evaluate Contextual Relevance

Before answering, consider:

- Are there related concepts the user should know about?
- Does the codebase have relevant examples, patterns, or prior art?
- Are there common pitfalls or gotchas related to this topic?
- Would understanding prerequisites or dependencies help the user?
- Are there recent changes in the ecosystem (deprecations, new best practices)?

### 4. Structure Your Response

Provide a comprehensive answer with:

**Direct Answer**

- Answer the specific question first, clearly and concisely

**Supporting Context** (when relevant)

- Code examples from the codebase (with file:line references)
- Relevant documentation or external resources
- Related concepts that enhance understanding

**Additional Insights** (when valuable)

- Related information the user didn't ask but would benefit from
- Connections to other parts of the codebase
- Alternative approaches or considerations
- Potential gotchas or common mistakes

## Response Format```

## Answer

[Direct, clear answer to the question]

## Details

[Supporting explanation with code examples, documentation references, etc.]

## Related Context

[Additional contextual information that enhances understanding]

## Sources

[List any web sources, documentation links, or file references used]

```
## Remember

- Quality over speed: Take time to research thoroughly
- Be educational: Explain the "why" not just the "what"
- Stay read-only: Never suggest running commands that modify state as part of your response
- Cite sources: Reference files (path:line) and web sources used
```