# Action Item Tracking Agent

> An action-item agent that extracts owners, tasks, and due dates from meetings, tracks status, and flags ambiguous ownership instead of inventing it.

- **Category:** Meeting & Call Intelligence
- **Difficulty:** Intermediate
- **Setup time:** 35 min
- **Stacks:** Claude, LangGraph, OpenAI
- **Version:** 2.0.0 (updated 2026-06-21)
- **Source:** https://agent-kits.com/kit/action-item-tracker

## Overview

Extracts action items from meeting notes or transcripts: task, owner, and due date.

Captures only what was actually agreed, citing where each item came up.

Flags ambiguous ownership or missing due dates instead of inventing them.

Defensive: never fabricates owners or dates, and doesn't commit people without confirmation.

## When to use it

- You want action items reliably captured from meetings and tracked.
- You have notes or transcripts to extract from.
- You want ambiguous ownership flagged rather than guessed.
- You want follow-ups drafted for review, not auto-assigned.

## When not to use it

- You want it to assign owners and dates even when the meeting didn't — it won't.
- You expect it to auto-commit people to tasks without confirmation.
- You have no notes or transcript to work from.
- You want it to nag attendees automatically without review.

## Architecture

- **Transcript intake** — Receives the meeting notes or transcript to extract action items from.
- **Action-item extractor** — Identifies explicitly stated or agreed action items, ignoring general discussion that wasn't turned into a task.
- **Owner & date resolver** — Assigns an owner and due date only where the meeting clearly established them.
- **Ambiguity flagger** — Marks unclear ownership or missing dates as needing confirmation rather than guessing.
- **Source linker** — Ties each action item back to where it came up so it's traceable and verifiable.
- **Status tracker** — Tracks each item's status over time as open or completed.
- **Follow-up drafting** — Drafts reminders and follow-ups for review instead of auto-messaging people.

## Files in this bundle

- `system-prompt.md` — the agent's system prompt
- `tools.json` — tool/function definitions the agent expects
- `workflow.md` — step-by-step run loop
- `.env.example` — environment variables to fill in
- `kit.json` — full structured metadata
- `starters/` — minimal starter snippets
- `LICENSE` — Apache-2.0 (code, configuration, and schema)
- `LICENSE-CONTENT` — CC BY 4.0 (specification text and documentation)
- `NOTICE` — attribution and trademark notice
- `run.py` — **runnable demo**: real agent loop with mock tools (`pip install anthropic`, set `ANTHROPIC_API_KEY`, `python run.py`)
- `agentaz.json` / `agentaz.schema.json` — AgentAz™ governance spec + schema

## Implementation notes

- Extract only explicitly committed action items; manufacturing tasks from general discussion clutters the tracker and creates work nobody agreed to.
- Never fabricate owners or due dates; 'unassigned' and 'no date' with a flag are correct outputs when the meeting didn't establish them.
- Don't commit people to tasks they didn't accept; flag ambiguous ownership for confirmation to avoid false accountability.
- Tie every item to its source in the meeting so owners can verify what they're being held to.
- Draft reminders for review rather than auto-messaging people, which can feel like nagging and damage trust.
- Preserve the agreed scope of a task; don't expand or reinterpret what someone signed up for.
- Reserve the strong model for ambiguous ownership and scope judgment; a cheaper model can extract clear commitments.

## Variations

- **Basic — Action extractor:** Pulls explicitly agreed action items from a meeting with owners and dates where stated. On demand.
- **Advanced — Tracked items with flags:** Adds ambiguity flagging, source linking, status tracking, and review-only follow-up drafts — no fabricated owners or dates.
- **Enterprise — Meeting accountability layer:** Adds meeting-tool and task-system integration, owner confirmation workflows, cross-meeting tracking, and reporting on follow-through.

## FAQ

**Will it assign owners the meeting didn't?**

No. It assigns an owner only when the meeting clearly established one. If ownership is unclear, it marks the item unassigned and flags it for confirmation rather than pinning it on a random attendee.

**Does it make up due dates?**

No. It captures a due date only when one was stated. If no date was set, it records 'no date' and flags the item, instead of inventing a deadline nobody agreed to.

**Could it create tasks nobody committed to?**

No. It extracts only explicitly agreed action items. General discussion isn't turned into a task unless someone actually committed to it, and it even lists what it chose not to make into action items for transparency.

**Will it message people automatically?**

It drafts reminders and follow-ups for your review rather than auto-sending them, so you stay in control and people aren't nagged by a bot without approval.

**Can I trace where an item came from?**

Yes. Each action item links back to where it came up in the meeting, so owners can verify exactly what they're being held accountable for.

**Does it track completion?**

Yes. It tracks each item's status over time and can draft follow-ups on open items for you to review and send.


---

© 2026 AgentKits · www.agent-kits.com

**Open source.** Code, configuration, and the AgentAz™ schema are licensed under
**Apache-2.0**; specification text and documentation under **CC BY 4.0** (with
attribution to AgentKits, link to https://www.agent-kits.com). See LICENSE, LICENSE-CONTENT,
and NOTICE in this bundle. "AgentAz" and "AgentKits" are trademarks of AgentKits.

**Flagship reference blueprint.** View the source, AgentAz™ spec, and frozen v1.0 schema
in the public registry: https://github.com/agent-kits/agentaz
Original: https://agent-kits.com/kit/action-item-tracker
