Gap State Inventory

Use this skill to find the undesigned interface. Real users often experience products while loading, empty, failed, blocked, offline, unauthorized, or partially complete.

Process

1. Identify the screen, component, or flow being reviewed.
2. List data dependencies, user permissions, network dependencies, and mutation points.
3. Inventory states: loading, empty, populated, partial, error, retry, offline, permission denied, expired session, validation, disabled, success, destructive confirmation, localization, and responsive edge cases.
4. For each state, define user-visible behavior, copy needs, recovery path, and implementation owner if known.
5. Prioritize states as must-have for v1, should-have, or later.
6. Recommend tests or acceptance criteria for critical states.

Output format

## Gap state inventory