Commitments Tracker

People make promises out loud in meetings, and then the meeting ends and nobody writes them down. This skill reads your notes or transcript and builds the tracker. Then you keep it, and bring it back after the next meeting.

Paste in notes from one meeting or several. You can also add the meeting date and who was there, but you don’t have to.

What it does

• Quotes the source. Every row quotes the line the promise came from, so you can check it against the meeting. A long quote gets trimmed to a sentence or two.
• Puts unowned work first. If the meeting agreed something needs doing and nobody took it, it lands in “Needs an owner”. Each one shows what’s waiting on it. You can find an owner, take it on, or drop it.
• Flags unanswered asks. If someone asked a named person for something and got no clear answer, it goes in “Asked, not answered”.
• Splits firm from unsure. Clear promises go in “Open commitments”. Weak ones (“I might”, “we could”) go in “Check these”.
• Marks what’s overdue. It compares each date to the day you run it. If it doesn’t know today’s date, it uses the date of your newest meeting and tells you so. A promise with no calendar date never shows as overdue.
• Lists work that repeats. If someone says they do a task by hand on a schedule, it goes in “Work that repeats”. That’s not a promise, but it’s a good thing to map later.
• Updates your tracker. Give it the tracker and the next meeting. Every item keeps its ID, nothing gets removed, and finished items move to “Done and dropped”. Anything the new meeting doesn’t mention stays, with a note.
• Drafts notes you can send. You get a short message for each person it can name, so they can confirm their own list. It skips anyone it couldn’t name for sure. It never sends anything.
• Leaves private matters out. A promise about someone else’s pay, performance, hiring, leaving, health, family, money, or a legal matter doesn’t go in the tracker. You only see a count of what it left out.

How to use it

1. Say “pull the commitments from this meeting” and paste your notes or transcript.
2. Answer its question if it asks one. It may ask who a speaker is, or what date the meeting was.
3. Read the tracker. Start with “Needs an owner” and “Asked, not answered”.
4. Confirm any name marked “(likely)”. It only drafts a note for a person once their name is confirmed.
5. Save the tracker. After your next meeting, give it back along with the new notes.

Output format

You get one document called “Commitments tracker”. It has a header with the counts, then these sections in order: “Needs an owner”, “Asked, not answered”, “Waiting on each other”, “Open commitments”, “Check these”, “Work that repeats”, and “Done and dropped”. It ends with a list of the meetings it covers and what it left out. Empty sections are skipped.

The chat reply stays short. It tells you what needs you first, what changed, and gives you a note for each person it could name. Then it suggests next steps.

Pitfalls

• The tracker is the memory. The skill doesn’t remember anything on its own, so give it your tracker every time you add a meeting.
• “Check these” holds items to confirm. Some of them won’t be real commitments, so check them before you count on them.
• A draft note can state a date the person never said. If the date came from someone else’s request, the note asks them to confirm it. Read each note before you send it.
• It can miss things. When it can’t tell if something is a promise at all, it leaves it out. A promise in weak words still goes in “Check these”. So the tracker isn’t the full record of the meeting.
• Private promises are missing on purpose. Things like an offer, a performance plan, or someone leaving won’t be there. You’ll only see the count.
• After an update, check that your old items are still there. It’s told to keep every ID and remove nothing, but it rewrites the whole tracker each time.
• If your assistant can read and write files, it looks for a file called commitments-tracker.md in the folder you’re working in. It updates that file and saves a copy of the old one first.
• It doesn’t send messages, chase people, or share the tracker.
• The tracker holds names and quotes from your meetings. Treat it like any private document. Read it before you share it, because the private filter can miss something.

This skill needs no MCP server and no extra files. It is a single SKILL.md.