- Home
- Skills
- Productivity
- Meeting Notes to Action Plan
More screenshots
Works with the AI Agents you already use
Meeting Notes to Action Plan
Convert supplied meeting records into traceable decisions, owned actions, deadlines and unresolved items without inventing agreement.
$5
Meeting Notes to Action Plan
Example session with this skill installed
Process these notes from the Project Phoenix sync on Oct 12. Attendees: Sarah (PM), Mike (Eng). Purpose: Sprint 4 planning. Mode: Action Plan. Notes: Mike said he can finish the API by Friday if Sarah gets him the schema today. Sarah said she will try but might need to check with Design. Sarah also mentioned the budget is tight.
- Read your context and instructions
- Compiled the meeting notes to
I have processed the Project Phoenix sync notes into a structured Action Plan. I have flagged the schema delivery as a high-priority dependency requiring human confirmation.
Action Plan: Project Phoenix Sprint 4
Meeting Date: 2023-10-12
Participants: Sarah (PM), Mike (Eng)
Mode: Action Plan
| ID | Action Item | Owner | Due Date | Status/Notes |
|---|---|---|---|---|
| ACT-001 | Deliver API schema to Engineering | Sarah (PM) | 2023-10-12 | PENDING - Owner indicated check with Design required. |
| ACT-002 | Complete API development | Mike (Eng) | 2023-10-16 | DEPENDENT - Requires ACT-001 by EOD 2023-10-12. |
Unresolved Items & Risks
- Risk: Budget constraints mentioned by Sarah; impact on Sprint 4 scope is
NOT-SUPPLIED.
Conflict: Mike's Friday deadline is contingent on a schema delivery Sarah has not yet fully committed to (CONFLICT — HUMAN RESOLUTION REQUIRED).
- Missing Context: Participation or approval from the Design team is
NOT-VERIFIED.
Decision Log
- DEC-001: Agreement to target API completion by Friday, contingent on schema availability.
Next steps
- Sarah to confirm schema availability with the Design team.
- Mike to verify if a Monday completion is feasible if schema is delayed.
- Schedule a brief follow-up to address the "tight budget" impact on resource allocation.
Draft meeting record — verify attendance, attribution, decisions, owners, dates, confidentiality and authority before distribution or task creation.
Connects securely to your tools. The creator never sees your data.
About this skill
Convert supplied meeting records into traceable decisions, owned actions, deadlines and unresolved items without inventing agreement. It separates supplied facts, disputes, assumptions and unknowns; applies domain-specific safety and authority boundaries; produces a professional draft plus review checks; and includes an optional local validator for redacted JSON manifests. Core work is network-free and no message, post, payment, approval or platform action is executed.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Productivity.
Does not record meetings, transcribe audio, verify attendance, send minutes, create tasks or calendar events, confirm agreement, or access collaboration platforms. Authenticated Agensi upload, moderation, marketplace acceptance, live runtime, credits and latency were not tested.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 2 months ago
Permissions
File Scopes
This skill reads supplied meeting notes, transcripts, emails, documents, and screenshots to produce traceable summaries, decision logs, action plans, owners, deadlines, dependencies, and unresolved questions. It does not require network access, browser access, terminal commands, external APIs, or environment variables. It must not invent attendance, approvals, owners, deadlines, commitments, or completed work. Missing information must be labeled NOT-SUPPLIED, NOT-VERIFIED, or CONFLICT — HUMAN RESOLUTION REQUIRED.