meet

Name: meet
Author: kv0906

2installs33forks

How to install meet?

kv0906/pm-kit/meet

$npx -y skills add kv0906/pm-kit --skill meet

Installs into the current project.

Summary

Process meeting notes into structured notes with extracted decisions, blockers, and action items. Use for "/meet project type title" then paste notes.

Files · 1

View on GitHub

SKILL.md

1	# /meet — Meeting Processing
2
3	Process raw meeting notes into structured notes with extracted decisions, blockers, and action items.
4
5	## Context
6
7	Today's date: `!date +%Y-%m-%d`
8	Recent meetings: `!ls meetings/*.md 2>/dev/null \| tail -5`
9
10	Reference template: @_templates/meeting.md
11	Config: @_core/config.yaml
12	Processing logic: @_core/PROCESSING.md
13
14	## Input
15
16	User input: $ARGUMENTS
17
18	Then user will paste raw notes.
19
20	## Session Task Progress
21
22	```
23	TaskCreate: "Parse meeting metadata"
24	activeForm: "Parsing meeting metadata..."
25
26	TaskCreate: "Extract decisions, blockers, actions"
27	activeForm: "Extracting items from notes..."
28
29	TaskCreate: "Create linked notes"
30	activeForm: "Creating linked notes..."
31	```
32
33	## Processing Steps
34
35	1. Parse Input
36	- Extract project
37	- Extract type: sync, milestone, external
38	- Generate slug from title
39
40	2. Request Notes
41	- If notes not provided, prompt: "Paste your meeting notes:"
42
43	3. Extract from Notes
44	- Decisions: Look for "decided", "agreed", "going with"
45	- Blockers: Look for "blocked", "stuck", "waiting on"
46	- Action Items: Look for "will do", "action:", "TODO", "@name"
47	- Attendees: Look for @mentions or name lists
48
49	4. Create Meeting Note
50	- Filename: `meetings/{date}-{type}-{slug}.md`
51	- Apply template with extracted data
52	- Add `## Links` section
53
54	5. Create Linked Notes
55	- For each decision: Create `decisions/{project}/{date}-{slug}.md`
56	- For each blocker: Create `blockers/{project}/{date}-{slug}.md`
57	- Link back to meeting note
58
59	6. Update References
60	- Add to project index if exists
61
62	7. Append to Vault Log
63	- Append entry to `01-index/_vault-log.md` (see `.claude/rules/vault-log.md`)
64	- Action: `meeting`
65	- Details: summarize what was extracted (decisions, blockers, action items)
66
67	## Output
68
69	```
70	Created: meetings/{date}-{type}-{slug}.md
71	Extracted:
72	- Decisions: {count} (notes created)
73	- Blockers: {count} (notes created)
74	- Action items: {count}
75	```
76
77	## Export (Optional)
78
79	Supports `--docx`, `--pdf` flags. See `.claude/rules/export-formats.md` for layout specs and workflow. Complete normal processing first, then generate the formatted file.

People who liked this also viewed

6 picks

Type

meet

2installs33forks

View on GitHub

How to install meet?

kv0906/pm-kit/meet

$npx -y skills add kv0906/pm-kit --skill meet

Installs into the current project.

Summary

Process meeting notes into structured notes with extracted decisions, blockers, and action items. Use for "/meet project type title" then paste notes.

Files · 1

View on GitHub

SKILL.md

1	# /meet — Meeting Processing
2
3	Process raw meeting notes into structured notes with extracted decisions, blockers, and action items.
4
5	## Context
6
7	Today's date: `!date +%Y-%m-%d`
8	Recent meetings: `!ls meetings/*.md 2>/dev/null \| tail -5`
9
10	Reference template: @_templates/meeting.md
11	Config: @_core/config.yaml
12	Processing logic: @_core/PROCESSING.md
13
14	## Input
15
16	User input: $ARGUMENTS
17
18	Then user will paste raw notes.
19
20	## Session Task Progress
21
22	```
23	TaskCreate: "Parse meeting metadata"
24	activeForm: "Parsing meeting metadata..."
25
26	TaskCreate: "Extract decisions, blockers, actions"
27	activeForm: "Extracting items from notes..."
28
29	TaskCreate: "Create linked notes"
30	activeForm: "Creating linked notes..."
31	```
32
33	## Processing Steps
34
35	1. Parse Input
36	- Extract project
37	- Extract type: sync, milestone, external
38	- Generate slug from title
39
40	2. Request Notes
41	- If notes not provided, prompt: "Paste your meeting notes:"
42
43	3. Extract from Notes
44	- Decisions: Look for "decided", "agreed", "going with"
45	- Blockers: Look for "blocked", "stuck", "waiting on"
46	- Action Items: Look for "will do", "action:", "TODO", "@name"
47	- Attendees: Look for @mentions or name lists
48
49	4. Create Meeting Note
50	- Filename: `meetings/{date}-{type}-{slug}.md`
51	- Apply template with extracted data
52	- Add `## Links` section
53
54	5. Create Linked Notes
55	- For each decision: Create `decisions/{project}/{date}-{slug}.md`
56	- For each blocker: Create `blockers/{project}/{date}-{slug}.md`
57	- Link back to meeting note
58
59	6. Update References
60	- Add to project index if exists
61
62	7. Append to Vault Log
63	- Append entry to `01-index/_vault-log.md` (see `.claude/rules/vault-log.md`)
64	- Action: `meeting`
65	- Details: summarize what was extracted (decisions, blockers, action items)
66
67	## Output
68
69	```
70	Created: meetings/{date}-{type}-{slug}.md
71	Extracted:
72	- Decisions: {count} (notes created)
73	- Blockers: {count} (notes created)
74	- Action items: {count}
75	```
76
77	## Export (Optional)
78
79	Supports `--docx`, `--pdf` flags. See `.claude/rules/export-formats.md` for layout specs and workflow. Complete normal processing first, then generate the formatted file.

People who liked this also viewed

6 picks

Type