Wire an internal or admin screen from the existing template
An internal screen built from the existing template so operators stop asking somebody to run a query.
The ticket
Build an internal screen from the existing admin template.
Acceptance criteria
- The screen is built from the existing template and components
- Access is restricted and each role has a permission test
- Destructive actions require confirmation
- A screenshot is attached
What lands as proof
A permission test per role plus a screenshot, so both the access rules and the result are visible.
Why teams defer it
- Internal tools have no external customer, so they lose every prioritisation round.
- The manual workaround works, which is exactly why it survives for years.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: build an internal screen from the existing admin template. 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 screenshot plus the permission test for each role, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- The run stops once the plan is written. Somebody reads the approach and approves it before any code exists, which is the cheapest moment to redirect the work.