Build the missing empty, loading, and error states for one screen
A screen designed only for the case where everything works, given the states users meet first.
The ticket
Build the empty, loading, and error states for one screen.
Acceptance criteria
- Each state is implemented and reachable
- A screenshot of each is attached
- The empty state says what to do next rather than only that there is nothing
- Errors explain what went wrong and offer a way forward
What lands as proof
A screenshot per state, which is also the first time anybody has seen them rendered.
Why teams defer it
- The design file usually shows one populated state, so the others were never specified.
- They are hard to reach by hand during development, which is why they ship unfinished.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: build the empty, loading, and error states for one screen. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means a screenshot of each state attached to the pull request, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- None is required before the run starts. Every claim this ticket makes can be checked by machine, so the agent works straight through and a person reviews the finished pull request like any other.