# Interface implementation brief

Blank working document. Replace placeholders with your own evidence; an empty field is unknown, not a passing result.

Owner: [fill in]
Source revision: [fill in]
Environment: [fill in]
Evidence date: [fill in]

## Task and evidence

Person/task: ___
Existing research or labelled hypothesis: ___
Source revision: ___
Authorised design frames: ___
Target devices: ___

## Design inventory

| Component or token | Source file/value | Design-frame counterpart | Mismatch |
| --- | --- | --- | --- |
| ___ | ___ | ___ | ___ |

## Interaction states

Entry and completion criteria: ___
Loading/empty/error/success: ___
Keyboard order and focus return: ___
Announcements and labels: ___

## Implementation acceptance

Assigned files and owner: ___
Viewport/theme test matrix: ___
Browser evidence: not run
Unresolved design decision: ___
Asset rights and attribution: ___

## Boundaries

- Choose a host for each stage and verify its tool mapping. Pass evidence explicitly between stages; the listed resources do not automatically configure or invoke one another.

- The extraction skill reads frontend source; Figma frames alone are not its documented input. The Copilot UX definition and Figma connection need separate host setup. This pairing is not a tested direct integration.

- Respect design-file permissions and asset licences. Do not overwrite shared designs or claim browser accessibility was tested until it was.

Workflow: https://undominated.ai/workflows/#plan-an-interface

Original worksheet: MIT. Linked resources retain their own licences and setup requirements.