# Feature map file shape

`features/README.md` indexes one file per user-facing feature. Each file:

```markdown
# <Feature name>

## Sub-features

## How to get to it (user POV)

## Driving it with <harness>

## Gotchas
```

Write from the user's point of view. Name the observable end state that
proves it works. Aim for the top 3–5 features from routes, commands, menus,
or docs. A proof that drives one convenient entry point is incomplete when
the map lists others.