# How to <accomplish a specific real-world goal>

<!-- GENRE: How-to guide (task-oriented)
     Goal: reader completes a specific, real-world task they already know they need.
     Voice: direct, imperative — assume competence, skip "what is X" explanations.
     Rule: one goal per guide; link to reference/explanation for the why. -->

## When to use this guide

<!-- One or two sentences: the concrete situation that brings someone here.
     If there are multiple variants of this task, state which one this covers. -->

## Prerequisites

<!-- What must be true BEFORE starting (tools installed, permissions, prior state).
     Do not explain these items; link to the source instead. -->

- Item one
- Item two

## Steps

<!-- Numbered list.  Each step is a single atomic action.
     Add a note (block-quote or inline) only when a step is non-obvious. -->

1. Do this first.

   ```shell
   # command
   ```

2. Do this second.

3. Do this third.

## Verify it worked

<!-- Describe the observable outcome that confirms success (output line, UI state,
     file diff, API response).  Include a code block if the output has a known shape. -->

## Troubleshooting

<!-- Two to four common failure modes, each as a sub-heading or bold label
     followed by the fix.  Remove this section if there are no known failure modes. -->

**Symptom:** description of what goes wrong.
Fix: what to do.

## Related

<!-- Links to the reference page for the main concept, the explanation for the
     reasoning behind this approach, or a related how-to. -->
