返回技能列表

one-on-ones

guia-matthieu
更新于 2 days ago
5 次查看
111
20
111
在 GitHub 上查看
design

关于

This Claude Skill provides structured guidance for conducting effective one-on-one meetings, including agenda frameworks, question banks, and handling difficult conversations. It's designed for developers in leadership roles to build trust, develop team members, and proactively address issues. Use it when setting up new 1:1s, resetting unproductive meetings, or preparing for performance and career development discussions.

快速安装

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 是一个 TypeScript 优先的构建工具,可将本地 Markdown/MDX 文件转换为类型安全的数据集合。它专为构建博客、文档站和内容密集型 Vite+React 应用而设计,提供基于 Zod 的自动模式验证。该工具涵盖从 Vite 插件配置、MDX 编译到生产环境部署的完整工作流。

查看技能

polymarket

这个Claude Skill为开发者提供完整的Polymarket预测市场开发支持,涵盖API调用、交易执行和市场数据分析。关键特性包括实时WebSocket数据流,可监控实时交易、订单和市场动态。开发者可用它构建预测市场应用、实施交易策略并集成实时市场预测功能。

查看技能

creating-opencode-plugins

该Skill帮助开发者创建OpenCode插件,用于接入命令、文件、LSP等25+种事件。它提供了插件结构、事件API规范和JavaScript/TypeScript实现模式,适合需要拦截操作、扩展功能或自定义事件处理的场景。开发者可通过它快速构建响应式模块来增强OpenCode AI助手的能力。

查看技能

sglang

SGLang是一个专为LLM设计的高性能推理框架,特别适用于需要结构化输出的场景。它通过RadixAttention前缀缓存技术,在处理JSON、正则表达式、工具调用等具有重复前缀的复杂工作流时,能实现极速生成。如果你正在构建智能体或多轮对话系统,并追求远超vLLM的推理性能,SGLang是理想选择。

查看技能