Skip to content

borghei/Claude-Skills / project-management/career/pm-1on1s

pm-1on1s

Verified

Builds 1:1 agendas and kickoff scripts for a PM's manager, EM, designer, reports and cross-functional partners. Use when starting a new 1:1, a 1:1 has turned into status updates, or you need to give a partner hard feedback.

assets/kickoff_template.md

View on GitHub
# 1:1 Kickoff Conversation

**You:** ___________  **Partner:** ___________
**Partner type:** [ ] Manager  [ ] EM partner  [ ] Design partner  [ ] Direct report  [ ] Cross-functional
**Kickoff date:** ___________

---

## Purpose statement (1 sentence, share aloud)

> "Our 1:1 is for ___________________________________________________."

Examples by type:

- Manager: "Our 1:1 is for me to bring you the judgment calls and feedback that don't fit in writing, and for you to give me direction and growth feedback."
- EM partner: "Our 1:1 is for coordinating on the team's operating cadence, surfacing tension early, and growing our partnership."
- Direct report: "Our 1:1 is for you -- your topics, your growth, your blockers -- with feedback flowing both ways."
- Cross-functional: "Our 1:1 is for mutual context, alignment on priorities, and early-warning signals from each side."

---

## Cadence and format

| Question | Agreement |
|----------|-----------|
| How often? | [ ] Weekly  [ ] Bi-weekly  [ ] Monthly |
| How long? | [ ] 30 min  [ ] 45 min  [ ] 60 min |
| What time slot? | |
| Live or async-first? | |
| In person, video, or hybrid? | |
| Cancel policy (when is it OK to skip vs. reschedule)? | |

---

## Agenda ownership

- Default: ____________ owns the agenda
- Pre-meeting agenda shared by: ____________ (time before meeting)
- Format: [ ] Shared doc  [ ] Bullet list in calendar invite  [ ] Async write-up

---

## Feedback agreement

How will we give each other feedback?

- Frequency: ___________________________________________________
- Format: ____________________________________________________
- Examples of what "good" feedback looks like for each of us: __________________

**One thing we each find hard about feedback:**

- You: _________________________________________________________
- Them: ________________________________________________________

---

## How will we know this is working?

Set explicit success criteria for the partnership in 6 months.

- _________________________________________________________________
- _________________________________________________________________
- _________________________________________________________________

---

## What do we each need from each other right now?

- I need from you: ____________________________________________
- You need from me: __________________________________________

---

## Working style preferences

| Dimension | Yours | Theirs |
|-----------|-------|--------|
| Comms preference (sync / async, Slack / email) | | |
| When you're "in flow" and don't want to be interrupted | | |
| Decision style (consensus / authority / advise) | | |
| Feedback style (in-the-moment / structured / written) | | |
| Conflict style | | |

---

## First 1:1 follow-up

What's the first thing each of us will do based on this conversation?

- I will: _____________________________________________________
- You will: ___________________________________________________

---

## Check-in cadence on the partnership itself

- [ ] Quick partnership health check at month 3 (5 min in 1:1)
- [ ] Full partnership reset at month 6 (60 min separate meeting)

---

## Notes

> _________________________________________________________________
> _________________________________________________________________
> _________________________________________________________________
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall