Exasol Developer Guide New

Use WebSearch and WebFetch to gather information from all of the following:

• Search: site:docs.exasol.com [topic] — official Exasol documentation
• Search: site:github.com/exasol [topic] — Exasol GitHub repositories
• Search: site:pypi.org [topic] exasol — Python packages (if applicable)
• Search: [topic] exasol tutorial getting started
• Search: [topic] exasol example

Fetch the most relevant pages found. Extract:

• What the feature/tool does and why it exists
• Key concepts and terminology
• Official API / configuration parameters
• Code examples and usage patterns
• Prerequisites and system requirements
• Common real-world use cases
• Links to authoritative external documentation

Step 3 — Read the Existing Project

Detect the project root:

git rev-parse --show-toplevel

Then read the following (relative to that root) to ensure the new section fits project conventions:

• doc/index.rst — current top-level toctree structure
• doc/connect_to_exasol/index.rst and one content file from it
• doc/gen_ai/ai_text_summary/index.rst

Step 4 — Ask Clarifying Questions

Before sketching the plan, ask:

1. Is this a connector, a feature, a tool, or a tutorial/example?
2. Who is the primary user — data engineers, analysts, data scientists, or all?
3. Are there existing code examples or GitHub repos to reference?
4. Any specific aspects to emphasize — performance, ease of setup, integrations?
5. Should this be a top-level section in doc/ or a subsection of an existing one?
6. Any topics to exclude or keep minimal?

Wait for responses before sketching the plan.

Step 5 — Sketch the Plan

Proposed Folder Structure

doc/[section-folder-name]/
├── index.rst          — Section landing page with toctree
├── overview.rst       — What: definition, key concepts, system requirements
├── installation.rst   — (if applicable) setup, dependencies, pip commands
├── [descriptive].rst  — How: step-by-step with working code examples
└── [examples].rst     — Real-world use cases and complete end-to-end examples

Adjust files based on complexity and content type.

Per-File Content Plan

For each file state:

• Title
• Sections/headings to include
• Key content points (bullet list — not full RST)
• Code examples to include (language + what the example shows)
• External links to reference (from Step 2 research — real URLs only)

Toctree Update

State exactly:

• Which position in doc/index.rst to insert the new entry
• The exact toctree entry string (e.g., [folder]/index)

Cross-References

Note any :ref: links to/from existing sections that should be added.

Do NOT write any files. This skill produces a plan only. The user will run /exasol-developer-guide:implement to write the files once the plan is approved.