AI Skill Report Card
Turning Notes Into Action Plans
Quick Start15 / 15
Paste raw meeting notes, get back:
- Decisions table (what was decided, owner, deadline, status)
- Open questions / unresolved items
- Follow-up list for anything overdue from prior meetings (if provided)
Example input:
Team sync 3/14 - Sarah says we need to finalize vendor pick by next Fri.
Mike will send budget draft tomorrow. Discussed the API migration, decided to
push it to Q3. Need someone to own the client email - nobody volunteered.
Example output:
| Decision / Action | Owner | Deadline | Status |
|---|---|---|---|
| Finalize vendor pick | Sarah | Fri 3/21 | Open |
| Send budget draft | Mike | Fri 3/15 | Open |
| Push API migration to Q3 | — | Q3 | Decided |
| Draft client email | Unassigned | — | ⚠️ Needs owner |
Recommendation▾
Add an edge case for conflicting duplicate action items across multiple meetings
Workflow14 / 15
Progress:
- Step 1: Parse notes — separate decisions made from action items from open discussion/parking lot
- Step 2: Extract owner for each action item (flag "Unassigned" if none named)
- Step 3: Extract or infer deadline (flag "No deadline" if none given — don't invent one)
- Step 4: Build the table, sorted by deadline (soonest first, no-deadline items last)
- Step 5: Cross-check against any previously tracked items the user provides
- Step 6: Flag overdue items (deadline < today) at the top with ⚠️ and suggest a follow-up message
- Step 7: List unresolved/ambiguous items separately so nothing silently drops
Recommendation▾
Clarify how to handle notes with no dates at all (relative date inference)
Examples19 / 20
Example 1 — Clear notes: Input: "Decided to move launch to April 10. Priya owns the press release, due April 3. John still needs to confirm budget approval — no date given."
Output:
| Decision / Action | Owner | Deadline | Status |
|---|---|---|---|
| Draft press release | Priya | Apr 3 | Open |
| Confirm budget approval | John | No deadline given | ⚠️ Needs deadline |
| Launch date moved | — | Apr 10 | Decided |
Example 2 — Overdue follow-up (given prior tracked items): Input: Prior table shows "Send contract to legal — Dana — due 3/10" (today is 3/18, no update given in new notes).
Output:
⚠️ OVERDUE (1)
| Action | Owner | Was Due | Days Overdue |
|---|---|---|---|
| Send contract to legal | Dana | 3/10 | 8 |
Suggested follow-up message:
"Hi Dana — following up on sending the contract to legal, which was due 3/10.
Any blockers, or do you have a new ETA?"
Example 3 — Ambiguous/no owner: Input: "Someone needs to look into the pricing complaint." Output:
| Decision / Action | Owner | Deadline | Status |
|---|---|---|---|
| Investigate pricing complaint | Unassigned | No deadline | ⚠️ Needs owner + deadline |
Flag for next meeting: assign owner for pricing complaint investigation.
Recommendation▾
Consider adding a brief note on handling very long transcripts (chunking strategy)
Best Practices
- Never invent an owner or deadline — mark missing fields explicitly so gaps are visible, not hidden.
- Keep "Decisions" (no action needed, just recorded) separate from "Action Items" (owner must do something).
- Sort the action table by urgency: overdue → due soonest → no deadline.
- When given history, always diff against it rather than starting fresh each time.
- Keep follow-up messages short, neutral, and non-accusatory — ask for status/ETA, not an excuse.
- If notes are ambiguous about who owns something, say so explicitly rather than guessing from context.
Common Pitfalls
- Don't merge "discussed" topics with "decided" topics — discussion ≠ decision.
- Don't assign a deadline just to fill the cell; "No deadline given" is valid and more honest.
- Don't drop items that seem minor (e.g., "someone should check X") — put them in open questions instead of silently omitting.
- Don't mark something overdue without confirming "today's" date — ask if not provided.
- Don't bury overdue/unassigned items at the bottom — surface them first since they need the most attention.