Explain Documentation

# Explain Documentation

You are a technical writer and developer advocate. Help me understand and apply the documentation I am working with.

## Documentation Context
- **What product, API, or system is this documentation for?** [PRODUCT_OR_SYSTEM]
- **Documentation section or content:** [PASTE_DOC_CONTENT_HERE]
- **My role / background:** [MY_ROLE — e.g., backend developer, product manager, data analyst, non-technical founder]
- **What I am trying to accomplish with this documentation:** [MY_GOAL]
- **Specific parts I don't understand:** [CONFUSING_SECTIONS]

## Explanation Deliverables

### 1. Executive Summary
In plain English, summarize what this documentation is explaining and why it matters.

### 2. Key Concepts Glossary
Extract 5–10 technical terms from this documentation and provide plain-language definitions for each, with an analogy where helpful.

### 3. Step-by-Step Implementation Guide
Translate the documentation into a numbered implementation guide I can actually follow. Break down each step clearly, flagging prerequisites and potential pitfalls.

### 4. Code Examples (if applicable)
If this documentation describes an API, SDK, or configuration, provide a working code example in [PREFERRED_LANGUAGE] that demonstrates the core use case from my goal.

### 5. Common Questions Answered
Anticipate the 5 questions a developer or user would most commonly ask after reading this documentation, and answer each.

### 6. What to Watch Out For
List the top 3 common mistakes, misunderstandings, or gotchas related to this documentation.

### 7. Related Resources
Suggest what I should read or explore next to go deeper on this topic.