# 1:1 notes (/skills/one-on-one)

**Updates, blockers and actions for each person.** Turns a 1:1 conversation into notes; use after a one-on-one, check-in or mentoring call.

- **Version:** 2.0.0
- **Catalogue name:** `one-on-one`

## Example [#example]

Input:

> **Priya:** so how's the migration going
>
> **Dan:** pretty good I moved the billing tables over on Monday um but I'm stuck on the invoices job it needs a new API key from finance
>
> **Priya:** okay I'll get you that key by Wednesday. and honestly the runbook you wrote was great the on-call team has used it twice already
>
> **Dan:** oh thanks. I'll have the invoices job moved by the end of next week then

Output:

> ### Dan
> **Updates**
> - Moved the billing tables over on Monday
> **Blockers**
> - Needs a new API key from finance for the invoices job
> ### Feedback
> - Priya to Dan: the runbook was great, and the on-call team has used it twice already
> ### Actions
> - [ ] Priya: get Dan the API key by Wednesday
> - [ ] Dan: move the invoices job by the end of next week

## Instructions [#instructions]

These are the instructions the Skill follows, as the catalogue publishes them.

```markdown
Turn a one-on-one conversation into notes both people can look back on.

The text is a transcript in turns, each paragraph starting with the speaker's name in bold (`**Ana:** words`), or one person's recap with no names.

1. For each person with news about their own work, a ### heading with their name, then **Updates** (what they did) and **Blockers** (what stops them) as - bullets, in the third person. Write a label only when it has a bullet under it.
2. ### Feedback, then one - bullet per piece of praise or criticism of the other person's work, as "Giver to receiver: what was said". Feedback is never an update.
3. ### Actions, then one - [ ] item per promise to do something: the owner's name, a colon, the task, and the due date when it was said. A promise is never an update.

Who owns a promise: "I'll" means the person whose turn it is. In "**Ana:** I'll chase design by Thursday" the owner is Ana, so the item is "- [ ] Ana: chase design by Thursday".

ScribeKey names the document itself, so start at the first section with no title line. Leave out any heading or label with nothing under it; never write an empty bullet or "None". Keep feedback exactly as strong or as soft as it was said. Keep each speaker's name exactly as written, "Speaker 2" included.

Example of the shape:
### Ken
**Updates**
- Shipped the export screen
**Blockers**
- Waiting on design for the empty state
### Feedback
- Ana to Ken: the release notes were clear and on time
### Actions
- [ ] Ana: ask design for the empty state by Thursday

Keep only the parts the text has. Criticism and a promise in reply, "**Lee:** The demo slipped and it cost us the client call. **Jo:** Sorry, I'll send a status note every Monday.", give no person headings:
### Feedback
- Lee to Jo: the demo slipped and it cost the client call
### Actions
- [ ] Jo: send a status note every Monday

Check: every update, blocker, piece of feedback and action appears once, under the right person, and nothing appears that neither person said.

Every name, number, date and fact comes from the text exactly as given, in the language of the text. Write the headings and labels in the language of the text.
```

[View on GitHub](https://github.com/scribekey-app/scribekey-skills/blob/1d3ec0c702b1cb247de18f0465f73d0782a075de/skills/one-on-one/SKILL.md)