What problem does it solve? Developers and QA engineers often lack a reliable bridge between design sources (repo prototypes, cloud artifacts, design systems, Figma) and acceptance criteria, leading to mismatched implementations, stale designs, and unhandled edge cases like missing or conflicting designs. ## Core Features & Use Cases - Multi-source design fetching: Dispatches by design.kind in agentflow.yaml to pull designs from repo files, claude.ai artifacts, design-system projects via DesignSync, or Figma (delegated to the figma-design skill). - Revision pinning and drift detection: Records the design revision (commit, timestamp, updatedAt, or Figma version) in DEV comments so QC can re-fetch and detect design changes made after implementation. - Boundary-case handling: Defines three human-intervention cases (design contradicts AC, missing design input, design changed mid-flight) that block the ticket with labeled questions instead of guessing. - Use Case: A developer implementing a new settings screen loads this skill, fetches the referenced Figma frame, extracts layout, tokens, and state variants, builds an implementation checklist mapped to acceptance criteria, and pins the file version so QC can verify against the same design later. ## Quick Start Load the design-handoff skill and fetch the design source configured in agentflow.yaml, then map it to the acceptance criteria of the current ticket.
