Last Tuesday I sat in our weekly ops sync and watched three items from the previous week get re-discussed for the third time in a row. Nobody had dropped the ball on purpose. The decisions were just buried in a 140-message Slack thread that everyone had muted by Wednesday afternoon, somewhere between a gif of a startled raccoon and a forty-message debate about whether the new lunch vendor was actually good. I am the person on the team who is supposed to keep us organised. I had a sticky note on my monitor that said 'find a better system,' and it had been there for four months, slowly becoming a personal attack.
The cost of this was not abstract. Every week we burned the first fifteen minutes of a sixty-minute meeting reconstructing what we had already agreed to. Two people would remember it one way, one person would swear we tabled it, and our newest hire would sit there politely confused, watching the adults relitigate the same decision like it was Groundhog Day with a worse soundtrack. I started dreading my own meeting.
Slack is a conversation, not a task system
Here is the thing nobody on a remote team wants to admit out loud: Slack is fantastic for talking and catastrophic for accountability. Action items get sandwiched between reactions, tangents, and the inevitable 'lol' someone drops at message 47. The person who got tagged with a task genuinely does not remember it, because by the time they scrolled back to find it the thread had grown another sixty messages and a side-quest about office plants. We were not a careless team. We were a team without a memory, and you cannot hold people accountable to a record that nobody can read.
What the prompt actually does
I copied the entire 140-message thread and dropped it into Claude Sonnet 4.6 with the Slack Thread → Action Items with Real Owners and Due Dates prompt. Sonnet is the right model for this because it follows the structure tags faithfully and it is genuinely careful about not inventing things — which matters enormously when the whole point is trust. Ten seconds later I had a table with eight tasks. Every single owner had been pulled straight from the @mentions in the thread. No invented names, which was the exact failure mode I had been terrified of after watching a different tool confidently assign a task to someone who had not even been in the channel.
Three of the eight tasks came back flagged 'No date set,' and that flag turned out to be the most useful thing in the entire output. It forced me to chase those three dates down before the meeting even ended, while the relevant people were still in the room and could not pretend they had not seen the message. The decisions section was cleanly separated from the open questions, so for the first time the ambiguity was visible instead of pretending to be a conclusion.
- It names only owners who actually appear in the thread — I have run it dozens of times and never once seen it hallucinate a person
- Decisions sit in their own section, separate from open questions, so genuine ambiguity stops masquerading as agreement
- The action items come out as a clean Markdown table that pastes straight into Notion or Linear with zero reformatting
- It chewed through a 200-message thread in under fifteen seconds without dropping anything or summarising the life out of it
The twenty-minute habit that made it stick
I now paste the output into a pinned message at the top of each project channel the moment a discussion wraps. Your name sits next to a task, in writing, in public, with a priority attached. There is no plausible deniability, and — more importantly — nobody has to go spelunking through a muted thread to find out what they signed up for. Our follow-through on weekly actions went from roughly half to over eighty percent inside a single month. I did not run a change-management program or buy a project tool with a per-seat price that made finance wince. I just removed the excuse.
When the thread is more of a planning session than a status update, I hand the same paste to my Meeting Agenda Builder from a One-Line Goal prompt and let it turn the open questions into a structured agenda for the follow-up. The two prompts together basically run my week, and they cost me nothing but the twenty minutes it took to learn how to paste a thread into a box.
Takeaway
The robot did not make my team more diligent or more conscientious. It made the work visible, and visible work gets done — that is the entire trick. Grab the Slack Thread → Action Items with Real Owners and Due Dates prompt on Prompt Dock and run it on your own muted, doom-scrolled, raccoon-gif-infested channel. The sticky note is finally off my monitor, and I peeled it off myself, which felt better than I expected.