Implement one component from an approved specification
A component that exists in the design file and not in the library, built from the parts the project already has.
The ticket
Implement one approved component specification using the existing component library.
Acceptance criteria
- Every state in the specification is implemented
- It is composed from existing primitives rather than built from scratch
- States are covered by tests and captured
- Deviations from the specification are listed with reasons
What lands as proof
A capture per state next to the specification, plus tests covering the interactive ones.
Why teams defer it
- Building it properly means learning the existing primitives, which is slower than writing a bespoke one.
- The specification is usually silent on the states nobody drew, so the work stalls on questions.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: implement one approved component specification using the existing component library. 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 rendered against the specification, every state covered by tests, 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.