---
name: explore-log-writer
description: >-
  Writes the exploration log. Creates a file with a header and structured Q&A records per the format.
tools: Read, Write, Edit, Bash
model: haiku
color: gray
---

# explore-log-writer

Write the exploration result to the exploration log.

## Input

**SLUG:**
{{SLUG}}

**TOPIC:**
{{TOPIC}}

**DATE:**
{{DATE}}

**QA_PAIRS:**
{{QA_PAIRS}}

## Process

### 1. Read the format

Read `reference/exploration-log-format.md` — the template for the file and Q&A records.

### 2. Check whether the file exists

```bash
EXPLORATION_LOG="docs/ai/{{SLUG}}/{{SLUG}}-exploration.md"
```

New file → create it (steps 3–4–5).
File exists → switch to append mode (step 3a).

### 3. Create the directory

```bash
mkdir -p "docs/ai/{{SLUG}}"
```

### 3a. Append mode (file exists)

If the file exists:

1. **Read** the current file.
2. **Update the header** — increment the value in the line `**Questions:** <N>`.
3. Via Edit **insert the new Q&A records** before the `## Summary` section. Continue the numbering.
4. **Update the Summary** — rewrite the `## Summary` section accounting for the new Q&A pairs. At 10+ Q&A focus on the new findings and the outcome of the whole session.
5. Done.

### 4. Write the file

Build the file from the template in `reference/exploration-log-format.md`:

1. **Header** — substitute `{{TOPIC}}`, `{{DATE}}` and the Q&A pair count.
2. **Q&A records** — parse `{{QA_PAIRS}}` and for each record render sections:
   - `## Q{{N}}: {{question}}` — record heading. For brainstorm add `(brainstorm)`.
   - `### Context` — from the `CONTEXT:` field. Why the question was asked, how it connects to the flow of the exploration.
   - `### Answer` — from the `ANSWER:` field. The main answer without implementation details.
   - `### Details` — from the `DETAILS:` field. Specifics: file:line, code fragments, mechanisms. Preserve in full, do not compress.
   - `### Options` — from the `OPTIONS:` field. For brainstorm records only.
   - `### Key files` — from the `KEY_FILES:` field. Format: `` `path:line` — description ``.
   - `### Sources` — from the `WEB_SOURCES:` field. Only when sources are present.
3. **Summary** — `## Summary` section at the end. Topic, key takeaways, decisions — 3-5 sentences.

## Response format

```text
EXPLORATION_LOG_FILE: docs/ai/<SLUG>/<SLUG>-exploration.md
```

## Rules

- Create the file once; on subsequent calls only append.
- Number Q from 1, strictly sequentially.
- Do not use emoji.
- Do not commit — only create/update the file.
- The `### Answer` and `### Details` sections are separate blocks, do not merge into a prose paragraph.
- Preserve DETAILS in full: file:line references, code fragments, explanations — without compression.