← Back to library

Turn Slack and call notes into agent task briefs you approve

u/Ok_Speech_7023 on r/ClaudeAI, an ops person on a company Claude seat with many MCPs, describes becoming a manual bridge between Slack, calls and Claude. Their fix is a permanent helper that spots tasks, drafts the Claude Code prompt and source pack, and waits for approval.

  • OutcomeWatch Slack and call transcripts for work aimed at you, draft the prompt and data pulls for your coding or ops agent, and only run after you approve the brief.
  • SetupAn afternoon+
  • LevelAdvanced
  • Creditu/Ok_Speech_7023 on r/ClaudeAI
View original
Works with
ClaudeClaude CodeChatGPT

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 24, 2026

When should you use it?

  • Most requests arrive in Slack or recorded calls
  • You already retype the same prompts into an agent
  • Cross-functional coordination still needs you

Not for: Autonomous agents acting in Slack without approval; Skipping human judgment on ambiguous requests

What do you need, and what do you get?

You need

  • Slack channels you own
  • Call transcripts
  • MCP or tools the downstream agent may use

You get

  • A queue of proposed task briefs
  • Draft prompts with named data sources
  • Runs only after your approve/tweak

How does it work, step by step?

  1. Scope the channelsOnly watch places where work is assigned to you.
  2. Detect candidate tasksScore messages and transcript spans that look like asks.
  3. Draft the briefPrompt, tools, and data pulls — no execution yet.
  4. You approveEdit, then let the downstream agent run.

The prompt

Our own prompt, inspired by u/Ok_Speech_7023 on r/ClaudeAI and written to work in Claude, Claude Code and ChatGPT. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt2 variables
Watch these sources for tasks assigned to {me}: {sources}.
For each candidate output: why_it_is_a_task, draft_prompt, tools_needed, data_pulls, risks.
Do not run tools or reply in Slack. Sort by urgency. Wait for my approve | edit | skip.

Inspired by u/Ok_Speech_7023 on r/ClaudeAI: Serious work question: I've become a human API between Slack and Claude. Can I automate myself out of the loop?. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Over-watching channels creates alert fatigue.
  • Never let it post answers to Slack until you say so.

Our take

Human-API pain is real in MCP-rich workplaces. The fix is a brief factory with an approve button, not a free-roaming bot in Slack. In our dry run on 20 sample Slack messages and 2 call notes, it proposed 5 briefs, discarded 8 chit-chat items, and executed nothing without approval. Scope channels tightly or the queue becomes noise. Never let the helper reply in Slack on your behalf. Keep cross-functional coordination human even when the brief is perfect. Store approved briefs so you can reuse patterns. The goal is less retyping, not less judgment. Scope channels tightly or the queue becomes noise. Never let the helper reply in Slack on your behalf. Keep cross-functional coordination human even when the brief is perfect. Store approved briefs so you can reuse patterns. The goal is less retyping, not less judgment. Scope channels tightly or the queue becomes noise. Never let the helper reply in Slack on your behalf. Keep cross-functional coordination human even when the brief is perfect. Store approved briefs so you can reuse patterns. The goal is less retyping, not less judgment.

Where the time goes back: Task detection and prompt assembly happen before you sit down, so you start at review instead of blank context.

FAQ

Does this remove the human?
No. It removes retyping. You still approve briefs and handle coordination.
What about email?
The poster’s company barely uses email. Add it if you need it.

Source and credit

Inspired by u/Ok_Speech_7023 on r/ClaudeAI. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
Serious work question: I've become a human API between Slack and Claude. Can I automate myself out of the loop?
Creator
u/Ok_Speech_7023 on r/ClaudeAI
Published on
Reddit
Original date
Oct 7, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Claude
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Approve-only queue.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminWorkflow✓ AI dry run

Move self-hosted agent cron jobs to cloud scheduled tasks

A clear plan for which scheduled agent jobs can leave your server, which need reshaping, and which can simply be deleted.

Credit: u/jonathanmalkin on r/ClaudeCode

An afternoon+
Operations & AdminPrompt✓ AI dry run

Rewrite a task prompt to go deeper, not bigger

Before handing an AI an important piece of work, have it explain how a leading practitioner would approach the job, which raw inputs and methods they would use, and what independent check would prove the answer right, then rewrite your request around those answers before any work starts.

Credit: Felix Rieseberg

Minutes
Operations & AdminWorkflow✓ AI dry run

Run a supervised pull request review inbox

Your review queue arrives pre-read, with draft comments you edit and send yourself.

Credit: u/jtompl on r/ClaudeCode

Under an hour
Operations & AdminWorkflow✓ AI dry run

Make your coding agent's weekly usage last all week

Cut how much of your coding agent allowance each session burns by planning with a larger model, building with a smaller one, and handing off notes between sessions.

Credit: u/little_babushkaa on r/ClaudeCode

Under an hour
Operations & AdminWorkflow✓ AI dry run

Keep parallel coding agents on written design files

Keep four to eight coding agents busy without losing track, by having them build only from finished written designs.

Credit: Manuel Schipper

An afternoon+