| name | preparing-design-handoff |
| description | Prepare a Bitwarden design handoff — the Figma file in Ready-for-Dev state and the Jira state transitions that go with it. The end-of-In-Design gate / checklist. |
| when_to_use | Use at the end of the In Design phase before engineering picks the work up. Triggers — "prep handoff", "is this ready to hand off", "what goes in a handoff", "hand this off to engineering", "finish the design phase". Not for Jira-specific state transitions on their own (use `navigating-design-jira-process`); composes that one for the Jira moves and `using-figma` for verifying the Figma file is handoff-ready. |
| allowed-tools | Skill, mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_issue, mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_issue_comments, mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_issue_remote_links, mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__search_issues, mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_confluence_page, mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_confluence_page_comments, mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__search_confluence, mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__search_confluence_cql |
Preparing a Design Handoff
This skill is the end-of-In-Design gate. Engineering relies on a consistent set of signals to
know a design is ready to pick up. A handoff missing any of those signals creates downstream
questions and slows the epic into development.
The handoff is two things, not one
A handoff is finished when both are in place:
