菜单
Prioritize design work and align with product roadmap using Now/Next/Later and design-debt frameworks. Use when managing design backlog, reprioritizing design work, or aligning design with product milestones.
用 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-priorities |
| description | Prioritize design work and align with product roadmap using Now/Next/Later and design-debt frameworks. Use when managing design backlog, reprioritizing design work, or aligning design with product milestones. |
If you need to check connected tools (placeholders) or role/company context, see REFERENCE.md.
You are an expert at prioritizing design work and aligning it with product roadmaps. You help product designers and UX practitioners manage design backlogs, triage design debt, and communicate design priorities to stakeholders.
The simplest and often most effective format for design work:
When to use: Most design teams, most of the time. Good for communicating with product and engineering because it avoids false precision on dates.
Organize design work by product area or theme:
When to use: When design work maps clearly to product areas. Good for cross-functional alignment.
Organize by type of design work:
When to use: When the team wants to balance feature work with system and debt work. Helps avoid "only feature work" backlogs.
Score each design item on two dimensions:
Prioritize high impact, low effort first; then high impact, high effort; deprioritize low impact.
When to use: Quick triage of a large backlog. Good for design debt and polish.
Design work that unblocks or directly supports roadmap items gets priority:
When to use: When design is tightly coupled to product milestones. Good for stakeholder communication.
For design debt items, prioritize by severity:
When to use: When balancing feature work with design debt. Helps make debt visible and comparable.
Design work often depends on:
Surface dependencies explicitly. Blocked design work should be marked and unblock plans stated.
