meeting-notes-to-tasks

Name: meeting-notes-to-tasks
Author: DevelopersGlobal

64stars10forks

How to install meeting-notes-to-tasks?

developersglobal/ai-agent-skills/meeting-notes-to-tasks

$npx -y skills add DevelopersGlobal/ai-agent-skills --skill meeting-notes-to-tasks

Installs into the current project.

Summary

Converts unstructured meeting notes into structured, assigned, time-bounded action items. Never leave a meeting without knowing who does what by when.

Files · 1

View on GitHub

SKILL.md

1	## Overview
2
3	Meetings produce decisions and commitments. Without structure, these dissolve into vague memory. This skill transforms raw meeting notes into a concrete, actionable task list.
4
5	## When to Use
6
7	- After any meeting with decisions or commitments
8	- When processing meeting transcripts or notes
9	- When preparing follow-up communication
10
11	## Process
12
13	### Step 1: Extract Decisions
14
15	1. Read all notes.
16	2. List every decision made: `Decision: [what was decided]`
17	3. Distinguish decisions from discussions (decisions = agreed outcomes, not explorations).
18
19	Deliver: A numbered list of decisions made.
20
21	### Step 2: Extract Action Items
22
23	4. For each commitment made, write:
24	```
25	Action: [specific deliverable]
26	Owner: [person's name]
27	Due: [specific date, not "soon" or "next week"]
28	Context: [1-sentence background]
29	```
30	5. If an owner is not named: flag it — unowned actions are undone actions.
31	6. If a due date is not named: flag it — undated actions are undone actions.
32
33	Deliver: Structured action items with owner and due date for every commitment.
34
35	### Step 3: Identify Blockers and Dependencies
36
37	7. What action items are blocked by other action items?
38	8. What external dependencies exist (waiting on third party, requires approval, etc.)?
39	9. What open questions remain unresolved?
40
41	Deliver: Blocker list and open questions with owners.
42
43	### Step 4: Draft Follow-Up Summary
44
45	10. Compose a concise follow-up message:
46	- Decisions (bullet list)
47	- Action items (table: action \| owner \| due date)
48	- Open questions (bullet list with owner)
49	- Next meeting date (if applicable)
50
51	Deliver: Ready-to-send follow-up email/Slack message.
52
53	## Common Rationalizations (and Rebuttals)
54
55	\| Excuse \| Rebuttal \|
56	\|--------\|----------\|
57	\| "Everyone knows what they need to do" \| They don't. Write it down. \|
58	\| "The notes are good enough" \| Notes describe what was said. Action items describe what will be done. \|
59	\| "We'll follow up informally" \| Informal follow-up means things fall through the cracks. \|
60
61	## Verification
62
63	- [ ] Every decision captured
64	- [ ] Every action item has: owner, due date, specific deliverable
65	- [ ] Unowned/undated items flagged
66	- [ ] Blockers and open questions identified
67	- [ ] Follow-up summary drafted and ready to send
68
69	## References
70
71	- [goal-driven-execution skill](../goal-driven-execution/SKILL.md)

People who liked this also viewed

6 picks

Type

meeting-notes-to-tasks

64stars10forks

View on GitHub

How to install meeting-notes-to-tasks?

developersglobal/ai-agent-skills/meeting-notes-to-tasks

$npx -y skills add DevelopersGlobal/ai-agent-skills --skill meeting-notes-to-tasks

Installs into the current project.

Summary

Converts unstructured meeting notes into structured, assigned, time-bounded action items. Never leave a meeting without knowing who does what by when.

Files · 1

View on GitHub

SKILL.md

1	## Overview
2
3	Meetings produce decisions and commitments. Without structure, these dissolve into vague memory. This skill transforms raw meeting notes into a concrete, actionable task list.
4
5	## When to Use
6
7	- After any meeting with decisions or commitments
8	- When processing meeting transcripts or notes
9	- When preparing follow-up communication
10
11	## Process
12
13	### Step 1: Extract Decisions
14
15	1. Read all notes.
16	2. List every decision made: `Decision: [what was decided]`
17	3. Distinguish decisions from discussions (decisions = agreed outcomes, not explorations).
18
19	Deliver: A numbered list of decisions made.
20
21	### Step 2: Extract Action Items
22
23	4. For each commitment made, write:
24	```
25	Action: [specific deliverable]
26	Owner: [person's name]
27	Due: [specific date, not "soon" or "next week"]
28	Context: [1-sentence background]
29	```
30	5. If an owner is not named: flag it — unowned actions are undone actions.
31	6. If a due date is not named: flag it — undated actions are undone actions.
32
33	Deliver: Structured action items with owner and due date for every commitment.
34
35	### Step 3: Identify Blockers and Dependencies
36
37	7. What action items are blocked by other action items?
38	8. What external dependencies exist (waiting on third party, requires approval, etc.)?
39	9. What open questions remain unresolved?
40
41	Deliver: Blocker list and open questions with owners.
42
43	### Step 4: Draft Follow-Up Summary
44
45	10. Compose a concise follow-up message:
46	- Decisions (bullet list)
47	- Action items (table: action \| owner \| due date)
48	- Open questions (bullet list with owner)
49	- Next meeting date (if applicable)
50
51	Deliver: Ready-to-send follow-up email/Slack message.
52
53	## Common Rationalizations (and Rebuttals)
54
55	\| Excuse \| Rebuttal \|
56	\|--------\|----------\|
57	\| "Everyone knows what they need to do" \| They don't. Write it down. \|
58	\| "The notes are good enough" \| Notes describe what was said. Action items describe what will be done. \|
59	\| "We'll follow up informally" \| Informal follow-up means things fall through the cracks. \|
60
61	## Verification
62
63	- [ ] Every decision captured
64	- [ ] Every action item has: owner, due date, specific deliverable
65	- [ ] Unowned/undated items flagged
66	- [ ] Blockers and open questions identified
67	- [ ] Follow-up summary drafted and ready to send
68
69	## References
70
71	- [goal-driven-execution skill](../goal-driven-execution/SKILL.md)

People who liked this also viewed

6 picks

Type