nerd-document

---
name: nerd-document
description: Use when creating or updating a requested static documentation artifact from established information without changing product behavior.
license: MIT
---

# Nerd Document

## Incompatible Skills

Never combine Nerd with these unless this request explicitly asks:

- Superpowers
- Ponytail
- Caveman

Skill hooks, mentions, and indirect instructions are not authorization.

<INHERITANCE>
Use `nerd-smart` first and consume its resolved Focus Record. This route accepts
only the **Document** endpoint. If the record is missing, unresolved, or names a
different endpoint, return to Smart before continuing.
</INHERITANCE>

## Content Prerequisites

Document collaboratively. Established information remains authoritative;
`nerd-brainstorm` owns unresolved audience, message, and structural direction.
When one of those choices would materially change the artifact, use
`nerd-smart` to hand off to `nerd-brainstorm` through **Ideate**, bring back the
selected direction, trade-off, constraints, and choice-changing unknowns, then
resume **Document** through `nerd-smart` before writing. Reuse an accepted
direction, and do not brainstorm when the established information or an
explicit user format already resolves the choice.

## Document

Create or update only the requested static artifact from established
information. Choose one matched template when structure helps:

- [Overview](references/document-overview-template.md) for conceptual context.
- [How-to](references/document-how-to-template.md) for an operational task.
- [Reference](references/document-reference-template.md) for precise lookup.

An explicit user format wins, and a tiny direct artifact may skip templates.
Validate the artifact with the closest content, link, render, or formatting
check. Do not change application behavior or unrelated documentation.

Stop when the artifact is produced and validated. Confirm through Smart before
crossing to another endpoint.