agentleFS
Sign inStart free
Sach1ngSach1ng/PM-operating-OS/skills/meeting-to-actions/SKILL.md

meeting-to-actions

Skill3 starsChanged 20 days agoMITView on GitHub

Help PMs turn raw meeting notes into structured, prioritized action items. Use after any meeting to extract decisions and next steps.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When asked "what did we decide?" or "what are the action items?"

    line 15
  2. Distinctive:

    Every action has an owner

    line 60
  3. Distinctive:

    No duplicate or overlapping actions

    line 62

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Meeting to Actions

Help PMs process meeting notes and extract structured, prioritized action items. Turns unstructured discussion into clear ownership and deadlines.

When to Use

  • Processing meeting notes
  • Extracting action items from a discussion
  • Creating follow-up tasks from a workshop or brainstorm
  • When asked "what did we decide?" or "what are the action items?"
  • Post-meeting recap and distribution

Process / Template

1. Review Raw Notes

  • Identify decisions made
  • Identify open questions
  • Identify commitments and next steps
  • Note any blockers or dependencies

2. Extract Action Items

For each action, capture:

  • Action — what needs to be done (verb-first, specific)
  • Owner — who is responsible
  • Due date — when it's due
  • Dependencies — what must happen first
  • Type — decision, deliverable, follow-up, blocker

3. Prioritize

  • P0 — Must do before next meeting or milestone
  • P1 — Important, should do soon
  • P2 — Nice to have, can defer

4. Structure the Output

Decisions Made

  • Bullet list of decisions with brief context

Action Items

PriorityActionOwnerDueDependencies
P0[Action][Name][Date][If any]

Open Questions

  • Questions that need resolution (with owner if known)

Blockers / Risks

  • Anything that could derail progress

5. Validate

  • Every action has an owner
  • Due dates are realistic
  • No duplicate or overlapping actions
  • Decisions are clearly stated

Output

A Meeting-to-Actions document with:

  • Decisions made (for record)
  • Prioritized action items with owners and dates
  • Open questions
  • Blockers/risks

Format: scannable, copy-paste ready for Slack, email, or project tool.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free