メニュー
Create design handoff docs and status updates for engineering and stakeholders. Use when handing off a feature, documenting specs and assets, writing acceptance criteria, or communicating design status.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Churn signals, at-risk criteria, and suggested actions for customer accounts. Use when finding at-risk customers, when building an at-risk list, or when assessing churn risk from CRM, support, or product analytics.
Structure customer feedback for any internal team (Product, Design, Engineering, Leadership): themes, severity, source, suggested action. Use when summarizing feedback from tickets, email, calls, or surveys for internal stakeholders.
Research customer questions by searching across documentation, knowledge bases, and connected sources, then synthesize a confidence-scored answer. Use when a customer asks a question you need to investigate, when building background on a customer situation, or when you need account context.
Structure and package support escalations for engineering, product, or leadership with full context, reproduction steps, and business impact. Use when an issue needs to go beyond support, when writing an escalation brief, or when assessing whether an issue warrants escalation.
Usage vs entitlement, expansion opportunity by account or segment. Use when finding expansion or upsell opportunities, when comparing usage to plan limits, or when identifying expansion opportunity from CRM or product analytics.
Repeatable expansion motions — who, when, how, and assets for upsell, cross-sell, and seat expansion. Use when getting an expansion playbook from knowledge base or when structuring expansion motions for CX.
| name | design-handoff |
| description | Create design handoff docs and status updates for engineering and stakeholders. Use when handing off a feature, documenting specs and assets, writing acceptance criteria, or communicating design status. |
If you need to check connected tools (placeholders) or role/company context, see REFERENCE.md.
You are an expert at design handoff — turning design work into clear, actionable specs for engineering and stakeholders. You help product designers communicate what to build, how to build it, and how to verify it.
For each screen or key state:
Write acceptance criteria in Given/When/Then format or as a checklist:
Given/When/Then:
Checklist format:
color.action.primary and matches height 44px on touch targets."Keep format scannable. Use tables for specs. Link to single source of truth (Figma, design system) where possible.
Keep it brief. Product cares about "what ships when" and "what we need from you."
Keep it high-level. No pixel-level detail.