# How-to format

Use when the reader already understands the domain and needs to complete one task correctly.

## Great instance

- Opens with the goal, constraints, and required inputs.
- Uses numbered steps with one decision or action per list item.
- Shows expected output at the points where mistakes are likely.
- Ends with troubleshooting for only the top failure modes.

## Cut

- Concept essays, broad alternatives, and product history.
- Multiple goals in one page.
- Screenshots when a command or exact field name is clearer.

## Skeleton

```markdown
# How to <task>

## Goal
<what will be true when done>

## Prerequisites
<access, files, versions, data>

## Steps
1. <action plus expected result>
2. <action plus expected result>
3. <action plus expected result>

## Verify
<command, URL, artifact, or state to check>

## Troubleshooting
- <symptom>: <fix>
```

## Section prompts

- Write in imperatives.
- Keep each list item independently commentable.
- Include rollback or recovery if the task mutates state.
- Prefer exact commands over prose.

## Renderer moves

Catalog: ../building-artifacts.md#what-each-file-type-becomes - md doc reader sections; anchors on numbered steps.