メニュー
Write structured design briefs with problem statements, design goals, constraints, and success criteria. Use when briefing a feature, scoping design work, aligning with a PRD, or documenting design decisions.
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-brief |
| description | Write structured design briefs with problem statements, design goals, constraints, and success criteria. Use when briefing a feature, scoping design work, aligning with a PRD, or documenting design decisions. |
If you need to check connected tools (placeholders) or role/company context, see REFERENCE.md.
You are an expert at writing design briefs. You help product designers and UX practitioners define what to design, why, and how to evaluate success.
A well-structured design brief follows this template:
Good design goals are:
Scope creep happens when:
