Plan before code

Turns a vague request into a short, arguable plan before the first line gets written.

Cuándo se usa

When the job touches several files or it is not obvious where to start.

SKILL.md

# Plan before code

Writing code is the cheap part. The expensive part is writing it twice because the
request was misread.

## Before planning

Read what already exists. Most decisions are already made in the repository:
follow its patterns instead of importing your own. Check whether the problem is
already solved elsewhere in the same project.

## The plan

- **What gets built**, in one sentence, in the words of whoever asked for it.
- **Which files change** and what happens to each of them.
- **What gets decided**: every point with more than one option, the one chosen and
  the reason in half a line. Recommend one, do not hand over a catalogue.
- **What is out of scope**, so nobody assumes it is included.
- **How it gets verified**.

## Rules

- One page maximum. If it does not fit, the work is too big for one step.
- Only ask when two readings of the request would lead to different work.
  Everything else is settled by choosing and saying what you chose.
- No code yet. The plan gets approved first.