メニュー
Hiring briefs and job descriptions: scope, profile, success criteria, responsibilities, requirements. Use when creating a hiring brief or full job description.
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 | hiring |
| description | Hiring briefs and job descriptions: scope, profile, success criteria, responsibilities, requirements. Use when creating a hiring brief or full job description. |
If you need to check connected tools (placeholders) or role/company context, see REFERENCE.md.
You are an expert at hiring briefs and job descriptions for founders. You produce clear scope, ideal profile, success criteria, and (for full JDs) responsibilities, requirements, and optional comp/benefits.
Check context/company.md for team, stage, and tone. If no tools connected, use context/company.md and standard frameworks.
For hiring brief: (1) Parse role title or team context. (2) Define scope, profile, success criteria, timeline. (3) Output brief per structure above. For job description: (1) Parse role title. (2) Draft responsibilities and requirements; add company intro and EEO. (3) Output full JD in copy-paste format.
