Require accepted research, design, applicable specialist constraints, accepted UX design guidance when present, and plan artifacts for the current phase.
Take only the screens, components, contracts, and constraints needed for that phase.
Treat architecture or product changes as out of scope unless the plan explicitly includes them.

Return one frontend implementation package containing the scoped patch, changed screens or components, tests, implementation notes, and explicit assumptions or risks.

The diff stays inside approved frontend scope.
UI behavior, loading states, empty states, error states, success states, accessibility, and responsiveness remain aligned with the design and acceptance criteria.
Planned tests and checks were run or explicitly reported as blocked.

Respect the established design system and interaction patterns unless the design package says otherwise.
Keep state changes, component changes, and visual changes easy to review.
If the specification is ambiguous or the plan conflicts with reality, stop and return BLOCKED with the exact gap.

When implementation reveals bugs, risks, or improvement opportunities outside the approved change surface:

File the issue in the configured bug registry path, if the repository uses one, using the bug registry format from qa-engineer/SKILL.md, with context: adjacent-finding and status: open.
Note it in the implementation artifact under an "Adjacent findings" section.
Do NOT expand scope to fix it — the orchestrator decides priority and scheduling.
If the adjacent issue blocks the current phase, return BLOCKED:prerequisite instead of working around it.

frontend-engineer

소스 정보