Productivity Blueprint
Safety checkedTurn a meeting transcript into assigned, dated Hive cards
Keep meeting commitments from slipping into notes or losing their owners and dates. Review transcript-backed tasks, approve the plan, then verify the Hive cards and links were created correctly.
Install Prompt
Copy this prompt and paste it into your AI agent to install.
What problem does this solve?
After a meeting, the follow-ups sit in someone's notes. One person types them into the task tool, often late. Some cards have no owner or no date. A week later, nobody is sure who agreed to what.
This Blueprint turns the transcript into cards while the meeting is fresh. Each card has a source quote, so you can see where it came from. A task with no clear owner is shown as "no owner". It is not hidden, and it is not guessed.
How does it work?
Claude reads a meeting transcript and lists the tasks that people agreed to. It shows you a table with owner and due date. After your yes, it creates the cards in the Hive project you name, then reads them back from Hive to check them.
Status: built and run. Last run on Nov 19, 2026, in Claude with the Hive connector, on a live Hive workspace.
- Give the transcript. Paste it into Claude, with the meeting date and the project name.
- Find the tasks. Claude reads all of it. For each agreed task it writes a short title, the owner named in the talk, the due date, a short source quote and a line of context. If a speaker names steps ("first reproduce it, then patch it"), these become sub-cards. Ideas, "maybe" items, open questions and decisions go on a separate list. They do not become cards.
- Match people and project. Claude looks up each owner in your Hive workspace and finds the project. If a person is not a workspace member, the card gets no owner, and the name is written in the card text. Claude does not invite anyone.
- Check for duplicates. Claude searches the project for each task title. A task with the same title as a card there is marked "already exists". A card that looks like the same work under other words is shown to you as a possible duplicate, with its owner and date. You decide.
- Show the plan and ask. You see a table with owner, date and source. You reply yes, yes with changes, or no.
- Create and check. After your yes, Claude creates the cards, with owners, dates and sub-cards. Then it reads them back from Hive and compares them with the plan. You get a list with links.
Example from our run, on an invented meeting: a 30-line transcript about a bakery website relaunch gave 5 tasks and 2 sub-cards. Two cards had an owner (the workspace member named in the talk). Three cards had no owner, because their owners were not workspace members. One task had no date. A marketing idea, a loyalty-app idea, an open question about delivery, and a payment decision stayed off the board. Claude read all 7 cards back, and the owners, dates and parent link matched the plan.
We then ran it two more times, each time in a new Claude session that had only the skill file. On the same meeting plus two new tasks, it found 7 tasks, marked 1 as already there and 4 as possible duplicates, and created only the 2 new cards. On a different meeting, it found 6 tasks. It created 5 cards and 2 sub-cards, and it did not create the one task that was already on the board.
What's the biggest win?
Follow-ups reach the board with an owner, a date and a source line while people still remember the meeting. You approve the list first, so nothing lands in a project by surprise. The gaps are visible: a card with no owner or no date says so. In our tests, a new Claude session that had only the skill file went from the transcript to checked cards in about one minute, not counting the time you take to read the plan.
What's required to run this?
- A Hive workspace and the Hive connector in Claude. Set-up steps: https://hive.com/integrations/claude?utm_source=g2&utm_medium=blueprint&utm_campaign=meeting-to-tasks
- An existing Hive project, and permission to create cards in it.
- A meeting transcript, pasted from any source.
- We ran the card creation step in a workspace on Hive's Free plan.
- The meeting date, so that "Friday" becomes a real date.
- The skill file from this Blueprint, added to Claude as a skill or pasted as the first message.
What are the constraints?
- It works from a transcript that you paste. It does not join, record or fetch meetings.
- It does not guess. If no owner is named, or the person is not a workspace member, the card has no owner. If no date is stated, the card has no date.
- Dates such as "next Wednesday" depend on the meeting date you give. Check the dates in the table.
- Two people with the same name, or a nickname, can cause a wrong match. Claude asks when more than one person matches. We tested this in a workspace with one member.
- Hive itself does not stop duplicate cards. Claude searches the project for each task title first. It skips a task with the same title, and it asks you about a card that looks like the same work. The search works on title words, so it can miss a duplicate.
- It creates cards only. It does not message the owners and it does not invite anyone. Hive notifies each person who becomes the owner of a card, as it does when you assign a card by hand.
- Long transcripts may lose detail. For a long meeting, run the transcript in parts.
- It runs when you start it. We tested it in Claude.
Tools in this Blueprint
About This Blueprint
- Industry
- Advertising & Marketing
More Blueprints to explore
Send Weekly Product Defect Reports
Catch product defects before scattered support tickets obscure a rising trend. Weekly reports group faults by product and type, compare them with the prior four weeks, and include customer photos and quotes for faster quality investigations.
Urska Blagojevic
GTM Lead at Yuma AI (YC W23)
Fix Wrong AI Agent Answers Before They Recur
Stop the same support mistake from frustrating customers again: trace incorrect Yuma replies to the Handbook, missing order data, failed actions, or bugs, then test a proposed fix before publishing it. A weekly report highlights recurring causes and the next tickets to investigate.
Urska Blagojevic
GTM Lead at Yuma AI (YC W23)
Onboard a new agency client in Hive from a project template
Avoid a client’s first week starting with unowned tasks or a missing kickoff. The setup shifts template dates, flags weekend deadlines and open owners, then verifies approved updates in Hive before handing over a week-one list and welcome-note draft.