one-to-one-agenda

$npx mdskill add Significant-Gravitas/skills-catalog/one-to-one-agenda

Use this before a manager's regular meeting with one person.

SKILL.md

.github/skills/one-to-one-agendaView on GitHub ↗
---
name: "one-to-one-agenda"
description: "Prepare a one-to-one agenda from prior notes, goals, and open actions."
triggers: ["1:1 agenda", "one to one", "manager meeting", "check-in agenda", "1-1 prep"]
version: "1"
---

# One-to-one agenda

Use this before a manager's regular meeting with one person.

## Review what is open

Read the last two or three sets of notes, the person's current goals, and
open actions for both sides. Note what was promised, by whom, and whether it
happened. Use items the manager or employee supplied for this agenda. Leave
out private notes that neither person approved for the meeting.

## Build the agenda

Keep it to 30 minutes and put the person's items first:

1. Their topics.
2. Progress on goals, with one fact for each.
3. Open actions from last time.
4. One question about support, workload, or growth.
5. Agreed actions, owners, and dates.

Suggest open questions such as "what is getting in your way?" rather than
yes or no ones.

## Note template

Give a short template: date, topics, decisions, actions with owners and
dates, and anything to follow up. Keep notes factual and about work.

If a sensitive matter comes up, such as health, pay, a complaint, or
discipline, suggest the manager pause and bring in HR.

Never record guesses about someone's health, family, or personal life. Do not
send the agenda, file the notes, or advise on a sensitive matter; hand it to
HR.

More from Significant-Gravitas/skills-catalog

SkillDescription
account-health-and-qbrsUse when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
accounts-receivable-follow-upReview open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
ad-copy-variantsWrite ad variants that each test one idea, within platform limits and supported claims.
alex-getting-startedUse on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
alliance-co-commercializationUse when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
anika-getting-startedUse on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
assure-partner-led-deliveryUse when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
automate-finance-reportingUse to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
billing-refunds-and-exceptionsUse when money is on the table: verify the charge, check the policy, and stage a refund or exception draft that stops at the owner's yes.
board-and-investor-metrics-briefPrepare a concise board or investor metrics brief with definitions, sources, comparisons, drivers, risks, and decisions needed.