Track What Was Promised Six Meetings Ago
Connect commitments across weeks so nothing gets quietly dropped
Your team makes commitments in one meeting but by week three no one remembers who promised what. You spend the first ten minutes of every session reconstructing history instead of moving forward.
That is the gap this drop closes. It is a operations skill built for Claude, and it takes about ten minutes to set up the first time. After that it runs in under a minute.
Who should use it
Operations managers running weekly or fortnightly recurring meetings with the same team
How it works
The skill file does five things, in this order.
1. Build a cumulative tracker document. Create one document that logs every commitment with meeting date, owner, due date, and status across all sessions.
2. Feed Claude the tracker plus new notes. Paste your tracker and the raw notes from today's meeting into Claude in one prompt.
3. Ask for status updates and carryovers. Have Claude mark which old commitments were mentioned as done, delayed, or ignored today.
4. Extract net new commitments only. Get Claude to list fresh commitments from today that are not duplicates of existing tracker items.
5. Generate an updated tracker. Ask Claude to output the complete revised tracker with old items updated and new ones appended.
What comes back
A single source of truth that survives across months and surfaces broken promises before they become crises
The mistake to avoid
Copy the updated tracker back into your working document after every meeting so it is always ready for the next session. If someone disputes a commitment, the meeting date stamp in the tracker shows exactly when it was made.
Running it
Save this as SKILL.md inside a folder named after the skill, then drop the folder into your Claude Code skills directory or upload it to a Claude Project. Claude reads the frontmatter to decide when the skill applies, so keep the description line intact. For a one-off run, paste the prompt block directly.
Where this fits
On its own, one skill saves an hour a week. The compounding happens when three or four of them run in sequence on the same input, the same transcript that produces a scope of work also produces the follow-up email and the project brief. That is the point at which it stops being a prompt and starts being an internal tool. If you want that wired into the systems your team already uses, that is the work 67 Digital does.
In the file
You are an operations assistant tracking commitments across a series of recurring meetings.
Below is my CUMULATIVE TRACKER of all commitments from previous meetings:
{paste your existing tracker here}
Below are the RAW NOTES from today's meeting, dated {meeting_date}:
{paste today's raw notes here}
Please do the following:
1. Review the cumulative tracker and identify any items that were mentioned in today's notes as completed, delayed, or discussed.
2. Update the status of those items. If someone said it is done, mark it DONE. If delayed, note the new due date. If discussed but not resolved, mark IN PROGRESS.
3. Identify any commitments in the cumulative tracker that were NOT mentioned today and are overdue. Flag these as AT RISK.
4. Extract any NEW commitments made in today's meeting. Do not duplicate items already in the tracker.
5. For each new commitment, specify: the person responsible, the deliverable, the due date, and today's meeting date as the source.
6. Output a complete updated tracker in table format with columns: Meeting Date | Owner | Commitment | Due Date | Status.
7. Sort by due date, with overdue and at-risk items at the top.
Return only the updated tracker table, no extra commentary.