スキル一覧に戻る

one-on-ones

guia-matthieu
更新日 2 days ago
111
20
111
GitHubで表示
メタdesign

について

このClaudeスキルは、効果的な1対1ミーティングを実施するための構造化されたガイダンスを提供します。アジェンダの枠組み、質問集、困難な会話の進め方などを含み、リーダーシップを担う開発者が信頼関係を構築し、チームメンバーを育成し、問題を事前に対処することを目的としています。新しい1対1ミーティングの設定、非生産的なミーティングのリセット、あるいはパフォーマンスやキャリア開発に関する話し合いの準備時にご活用ください。

クイックインストール

Claude Code

推奨
メイン
npx skills add guia-matthieu/clawfu-skills -a claude-code
プラグインコマンド代替
/plugin add https://github.com/guia-matthieu/clawfu-skills
Git クローン代替
git clone https://github.com/guia-matthieu/clawfu-skills.git ~/.claude/skills/one-on-ones

このコマンドをClaude Codeにコピー&ペーストしてスキルをインストールします

ドキュメント

One-on-Ones

Design and run effective 1:1 meetings that build trust, develop people, and surface problems before they become crises.

When to Use This Skill

  • New manager setting up 1:1s for the first time
  • Resetting unproductive 1:1s that became status updates
  • Onboarding a new direct report with structured first conversations
  • Preparing for a difficult conversation (performance, conflict, change)
  • Career development coaching in 1:1 context
  • Scaling management as team grows

Methodology Foundation

AspectDetails
SourcesAndy Grove (High Output Management), Kim Scott (Radical Candor), Michael Lopp (Managing Humans)
Core PrincipleThe 1:1 is the direct report's meeting, not the manager's — their time to surface what matters to them
Key RatioManager talks 10-30% of the time; listens 70-90%

What Claude Does vs What You Decide

Claude DoesYou Decide
Designs 1:1 cadence and structure for your team sizePersonal relationship-building approach
Generates conversation frameworks and question banksWhich questions fit each person
Creates agenda templates and running-notes docsHow to adapt for individual personalities
Prepares scripts for difficult conversationsFinal wording and tone for sensitive topics
Suggests development discussion frameworksCareer advice based on your knowledge of the person

Instructions

Step 1: Set Up the Mechanics

Cadence by maturity:

Task-Relevant MaturityFrequencyDuration
New or struggling2x/week30-45 min
DevelopingWeekly30-45 min
Senior / independentBi-weekly45-60 min

Rules: Same time each week. Rarely cancel. They own the agenda (shared doc, they add topics first). Private space for sensitive topics.

30-minute structure:

TimeActivity
0-5 minCheck-in: "How are you, really?"
5-20 minTheir agenda items
20-25 minYour topics (feedback, context)
25-30 minCommitments and close

Step 2: Master the Conversation

Opening — Understand where they're at: "What's on your mind this week?" / "How's your energy level?"

Middle (their agenda) — Coach, don't solve:

  • "Tell me more about that."
  • "What have you tried?"
  • "What do you think you should do?"
  • "How can I help?"

Resist the urge to fix immediately. Ask → Listen → Ask more → Let them reach conclusions.

Middle (your topics) — Keep secondary. Feedback, context, observations.

Closing — Capture commitments: "What are you committing to? What am I committing to?" Document and review next time.

Step 3: Handle Different Conversation Types

Career Development (monthly/quarterly):

  • "Where do you want to be in 2-3 years?"
  • "What skills do you want to develop?"
  • "What would make this the best job you've ever had?"

Feedback:

  1. Context → 2. Specific observation → 3. Impact → 4. Their perspective → 5. What should change

Performance concern:

  1. State the pattern with specific examples
  2. Ask: "Help me understand — what's happening?"
  3. Explain the impact
  4. Agree on path forward with clear expectations and timeline
  5. Document

Validation checkpoint: After a performance conversation, check in at the next 1:1. If no improvement after 2-3 follow-ups, escalate to formal process.

Trust-building (new relationship):

  • "Tell me about your path to here."
  • "How do you like to receive feedback?"
  • "What do you need from me to do your best work?"

Step 4: Troubleshoot Common Problems

ProblemLikely CauseFix
"Everything is fine" every weekLack of trust or wrong questionsWait in silence longer; share your own challenges first; ask "What would you change if you could?"
Turns into status updateHabit, no agenda ownership"I can read status — what do you need from me?"; use shared doc for status, meeting for discussion
Same complaints, no actionVenting without ownership"We've discussed this for weeks. Are you ready to address it?"
Surface-level onlyTrust not established yetWalk-and-talks, share about yourself, be patient
Too busy to hold 1:1sToo many reports or not delegating1:1s are core management work, not optional — restructure

Examples

Example: Onboarding a New Report

Week 1 (60 min): Getting to know each other — their story, working preferences, how they like feedback, your context and priorities.

Weeks 2-4 (30 min, 2x/week): Frequent check-ins — "What's surprising? What's confusing? What do you need?"

Week 4+: Transition to weekly cadence with shared running doc. Add development topics monthly.

90-day check-in: "How's it going overall? What's working? What's not? What do you want to focus on next quarter?"

Example: Resetting Stale 1:1s

The reset conversation: "I've noticed our 1:1s have become mostly status updates. I want to use this time for things you can't get elsewhere — challenges, development, feedback. What would make these more valuable for you?"

Then: implement shared agenda doc, change opening from "What's your update?" to "What's on your mind?", add 10 minutes for development each week, experiment with format (walks, coffee).

See QUESTIONS.md for a complete question bank organized by category (opening, work, development, relationship, closing).

Skill Boundaries

What This Skill Does Well

  • Designing 1:1 systems and cadence for different team sizes
  • Generating conversation frameworks and question banks
  • Preparing scripts for difficult management conversations
  • Diagnosing and fixing unproductive 1:1 patterns

What This Skill Cannot Do

  • Replace real human judgment about individual personalities
  • Handle legally sensitive HR situations (consult HR/legal)
  • Know your team members — you provide the context
  • Substitute for building genuine relationships over time

References

  • Grove, Andy. High Output Management — 1:1 fundamentals
  • Scott, Kim. Radical Candor — Caring personally + challenging directly
  • Lopp, Michael. Managing Humans — Practical 1:1 advice
  • Horowitz, Ben. The Hard Thing About Hard Things — Difficult conversations

Related Skills

GitHub リポジトリ

guia-matthieu/clawfu-skills
パス: skills/leadership/one-on-ones
0
ai-skillsanthropicclaude-codeclaude-skillsmarketingmcp-server

関連スキル

content-collections

メタ

このスキルは、Content Collections(Markdown/MDXファイルを型安全なデータコレクションに変換するTypeScriptファーストのツール)の本番環境でテストされた設定を提供します。Zodバリデーションによる型安全性を実現し、ブログ、ドキュメントサイト、コンテンツ重視のVite + Reactアプリケーション構築時にご利用ください。Viteプラグインの設定、MDXコンパイルから、デプロイ最適化、スキーマバリデーションまで、すべてを網羅しています。

スキルを見る

polymarket

メタ

このスキルは、開発者がPolymarket予測市場プラットフォームを活用したアプリケーション構築を可能にします。API統合による取引や市場データの取得に加え、WebSocketを介したリアルタイムデータストリーミングにより、ライブ取引や市場活動を監視できます。取引戦略の実装や、ライブ市場更新を処理するツールの作成にご利用ください。

スキルを見る

creating-opencode-plugins

メタ

このスキルは、開発者がコマンド、ファイル、LSP操作など25種類以上のイベントタイプにフックするOpenCodeプラグインを作成することを支援します。JavaScript/TypeScriptモジュール向けに、プラグイン構造、イベントAPI仕様、および実装パターンを提供します。カスタムイベント駆動ロジックでOpenCode AIアシスタントのライフサイクルをインターセプト、監視、または拡張する必要がある場合にご利用ください。

スキルを見る

sglang

メタ

SGLangは、高性能なLLMサービングフレームワークであり、RadixAttentionプレフィックスキャッシュを活用したJSON、正規表現、エージェントワークフロー向けの高速で構造化された生成を特長とします。特にプレフィックスが繰り返されるタスクにおいて、大幅に高速な推論を実現し、複雑な構造化出力やマルチターン対話に最適です。制約付きデコードが必要な場合や、広範なプレフィックス共有を伴うアプリケーションを構築する場合は、vLLMなどの代替案ではなくSGLangを選択してください。

スキルを見る