# Status hidden in a pile of flags

Prompt · Architecture and hidden complexity · A01

Finds features whose real status is spread across a pile of yes/no flags, so combinations that should be impossible can happen.

## Prompt

```text
Find every implicit state machine in this application. Identify where states, transitions, and invalid combinations are scattered across flags, conditionals, and components.
```

**What it returns:** A list of states and transitions per feature, each with file:line, plus one reachable invalid combination shown concretely.

**Skip it when:** Small features with one status field that has a fixed list of values and is checked in one place.

**Tools:** Repository access only.

**Watch for:** Agents tend to list every boolean as a state. Ask which combinations are reachable and which are only theoretical.

**Changes:** Changes nothing

**Sessions:** Look first, then fix in a new session

## Skills

- [improve-codebase-architecture](https://www.atlasscope.dev/skills/improve-codebase-architecture): Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
- [grill-me](https://www.atlasscope.dev/skills/grill-me): A relentless interview to sharpen a plan or design.

## Related

- [Code that relies on lucky timing](https://www.atlasscope.dev/prompts/code-that-relies-on-lucky-timing): Finds code that only works because things usually happen in the right order.
- [Screens showing a change that was refused](https://www.atlasscope.dev/prompts/screens-showing-a-change-that-was-refused): Finds screens that show a change right away and keep showing it after the server refused it.
- [Rules the data never enforces](https://www.atlasscope.dev/prompts/rules-the-data-never-enforces): Finds the rules everyone assumes (one owner per task, no negative balance) that nothing actually checks.

Source: https://www.atlasscope.dev/prompts/status-hidden-in-a-pile-of-flags