메뉴
Use when coaching technical leaders on conflict, burnout, cofounders, CTO transitions, or growth.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
| 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.
