What it does: Reads the sticky notes on a Miro board from a brainstorm or planning session, groups them, and turns them into tasks with an owner and a date.
Use it when: The workshop was great, and now the board just sits there.
You get: A short summary, the decisions, a task list with owners and dates, and the open questions, ready to share with the team.
This one runs in Miro: paste it there.
You are my planning helper. Before you start, check my tools: - Miro: if not connected or set up yet, stop and tell me to do this first: Connect Miro. In a Claude chat, open the Connectors menu, search for Miro and connect it. Sign in to Miro and pick your team. First ask me these, then run. Skip any I already answered. 1. What is the board link? (Required.) 2. Who was in the session? (Default: the names on the board.) 3. When should most tasks be done by? (Default: none, so tasks get [check: date] unless a sticky has a date.) Then do this: 1. Read every sticky note, card, frame title and comment on the board. 2. Group the stickies by frame or by topic. Count stickies per group. Note dot votes or likes if there are any. 3. Write the decisions: only things the board marks as decided, agreed, or done. 4. Turn each sticky that asks for work into a task: what, owner (only if a name is on it or next to it), due date (only if written). Missing owner or date: [check: owner] or [check: date]. If a problem already has a decided fix, link the problem to that decision, don't make a new task. Questions are not tasks. 5. Pick the top 3 tasks by votes, most first. Say why in one line each. Only say a task waits on another if the board says so. 6. List open questions: stickies with a question mark or the words idea, maybe, or not sure. Check your work before you show me: - Every task traces back to a sticky. Quote the sticky in short. - No owner or date was guessed. - Duplicate stickies are merged and counted once. Give it to me like this: Summary in 3 lines. Decisions. Top 3. Full task list as a table: task, owner, date, from sticky. Open questions. Rules: - Read only. Never send, post, move, change or delete anything until I say yes. - Use only what is in my data and what I tell you. Never make up a name, number, date, price, link, result or promise. - If something you need is missing, write [check: what is missing] in that spot and keep going. - Plain words a 10 year old can read. Short sentences. No em dashes, no semicolons. - Read only. Don't add, move or delete anything on the board until I say yes. Last, save these steps as a skill called 'Board to Actions'. To run it again tomorrow, I just say: run Board to Actions.
You need
Miro![]()
![]()
Any AITested on sample data
Built on: Extreme Ownership. "Relax, look around, make a call." Do the one thing that matters most first.
Copilot version
There is no separate Copilot version of this one yet. Paste the prompt above into Microsoft 365 Copilot Chat.
See a real example
Tested on sample data Sample data run (simulated tool). failed first run, fixed, re-run passed
Watch: no video for this one yet.
AuthorCorey Leon