メニュー
Use when coaching technical leaders on conflict, burnout, cofounders, CTO transitions, or growth.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | executive-coaching |
| description | Use when coaching technical leaders on conflict, burnout, cofounders, CTO transitions, or growth. |
| allowed-tools | Read,Write,Edit,Bash,Glob,Grep,WebSearch,WebFetch |
Use for coaching technical leaders through conflict, growth, burnout, cofounder dynamics, and CTO transition planning.
Coach when the person has context and can solve the problem. Advise when urgent, when they lack context, or when you have a specific answer. Ask: "Do you want advice, or space to think it through?"
Listen for content, emotion, and context. Use GROW questions: goal, reality, options, way forward. Keep ownership with the coachee and end with a concrete next step.
Use NVC for conflict: observation, feeling, need, request. Stay factual, avoid blame, and ask how the person may be contributing to the pattern.
Look for chronic depletion, not just workload. Track energizing and draining work, name strengths, and redesign toward more high-energy work.
Load CTO, stakeholder, goal, cofounder, or assessment references only when the user asks for that specific depth.
Use when copy editing, proofreading, polishing, or removing AI-sounding prose.
Use when creating Data/AI strategy, principles, roadmaps, MLOps plans, or executive docs.
Use when writing Manning-style technical chapters, Chapter 1s, examples, callouts, or summaries.
Use when drafting ML/AI papers, verifying citations, framing evidence, using LaTeX, or preparing submissions.
Use when writing strategic tech posts, engineering narratives, opinion pieces, or industry analysis.
