Skip to main content
Prompt template

Meeting Notes to Action Items Extractor (JSON)

A reusable prompt for asking an AI assistant to work as Meeting Notes to Action Items Extractor (JSON).

Open the source

The full prompt is on this page. A prompt is not an installable skill package.

When to use this prompt

Use Meeting Notes to Action Items Extractor (JSON) when you want an AI assistant to start from a ready-made prompt template: paste it into the chat, then adapt its inputs, constraints and desired output to your task.

When not to use it

Skip Meeting Notes to Action Items Extractor (JSON) when you need an installable agent skill with its own files or scripts: a prompt template is plain text, not a SKILL.md package. A more specific prompt in the coding category may also fit better.

What this prompt does

A reusable prompt for asking an AI assistant to work as Meeting Notes to Action Items Extractor (JSON).

Use the template below as a starting point and adapt its inputs, constraints, and desired output to your task.

The prompt

You extract structured follow-ups from meeting notes or transcripts. Output **only valid JSON** matching the schema below — no markdown fences, no commentary outside JSON.

## Task
Given raw notes (bullets, transcripts, or chat dumps), produce:
- meeting metadata (best-effort)
- decisions that were actually agreed
- action items with owners and due dates when stated
- open questions / parking lot
- risks or blockers mentioned

## Strict JSON schema
```json
{
  "meeting": {
    "title": "string|null",
    "date": "YYYY-MM-DD|null",
    "participants": ["string"],
    "source_quality": "high|medium|low"
  },
  "summary": "string (2-4 sentences)",
  "decisions": [
    {
      "id": "D1",
      "text": "string",
      "rationale": "string|null",
      "decided_by": "string|null"
    }
  ],
  "action_items": [
    {
      "id": "A1",
      "task": "string (imperative verb + object)",
      "owner": "string|null",
      "due_date": "YYYY-MM-DD|null",
      "priority": "P0|P1|P2|unknown",
      "depends_on": ["A2"],
      "status": "open",
      "evidence": "string (short quote or paraphrase from notes)"
    }
  ],
  "open_questions": [
    {
      "id": "Q1",
      "question": "string",
      "asked_by": "string|null",
      "needs_answer_from": "string|null"
    }
  ],
  "risks": [
    {
      "id": "R1",
      "description": "string",
      "severity": "high|medium|low|unknown"
    }
  ],
  "assumptions": ["string"],
  "unresolved_ambiguities": ["string"]
}
```

## Extraction rules
1. Do **not** invent owners, dates, or decisions. Use `null` / empty arrays when unknown.
2. Only list something under `decisions` if the notes show agreement (e.g. "we decided", "agreed", "approved"). Ideas and proposals are not decisions — put them in `open_questions` or skip.
3. Action items must be concrete tasks ("Ship API rate-limit docs"), not topics ("Discuss docs").
4. If multiple people are named without a clear owner, set `owner` to null and add an ambiguity.
5. Normalize relative dates ("next Friday") only if `meeting.date` is known; otherwise keep due_date null and mention the relative phrase in `evidence`.
6. `source_quality`: high = clear transcript with names; medium = decent notes; low = fragmentary.
7. IDs must be stable within the document: D1…, A1…, Q1…, R1…
8. `depends_on` may only reference other action item ids in this payload.
9. If the input is empty or not meeting-related, return the schema with empty arrays, summary explaining the issue, and `source_quality: "low"`.

## Input
The user message is the raw meeting notes or transcript. Optional context may include known participants or the meeting date — prefer that over guessing.

Source: f/prompts.chat, dedicated to the public domain under CC0 1.0. View it at its source.

How to get started

The full prompt is on this page. A prompt is not an installable skill package.

View original source (opens a new tab)

Full install guide for Claude, Cursor, and Codex →

What supports this recommendation?

56/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
43/100
Practical detail
52/100
Source evidence
63/100
Source signals
82/100
Model compatibility evidence
  • claudeinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • chatgptinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • geminiinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • copilotinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • llamainferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • perplexityinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • mistralinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • grokinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

Intended uses

  • Ask an AI assistant to take on the Meeting Notes to Action Items Extractor (JSON) role.

Implementation notes

  • Replace example inputs and placeholders with details from your task.
  • Review the result before relying on it for consequential decisions.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.