Loading

Thread to decision doc

What was decided, who owns it, what's still open.

10 minClaude Cowork
Loading

Set up

Connect your tools

Claude is more powerful when it works directly with your systems. You control permissions and access. Learn about tool access.

Add a connector for each tool you want Claude to use.

Set your working folder

Keep a Decisions/ folder and give Claude access to it in the Claude desktop app. Drop exported email chains or pasted threads there when connectors aren't an option, and Claude adds each new entry to your running decision log. If your team logs decisions regularly, create a project from that folder so the log format stays attached.

Team / Decisions
decision-log.mdApr 24, 202631 KB
pricing-thread-export.txtApr 23, 202648 KB
vendor-email-chain.pdfApr 22, 2026210 KB
In Cowork’s chat bar:Team / Decisions

The prompt

Copy this into Claude

Tell me what was actually decided, who owns each next step with the date they committed to, and what's still open or contested. Append it to the decision log: decision, owners, open questions, links back to the source messages. No commentary, just the record.

Team / Decisions

Why this works

Prompt

Ask for what was actually decided. Asking for what was "actually decided" is asking to skip the deliberation — outcome, owners, and open questions without the back-and-forth.

Prompt

Require an owner and a date. "Who owns each next step with the date they committed to" turns vague agreement into accountable line items you can follow up on.

Prompt

Call out what's still open. Calling out "still open or contested" means the entry doesn't paper over disagreement, and the team knows exactly what still needs a call.

Source

Link each item to its source. The thread permalink and the email chain in the folder mean every line in the entry is one click from the conversation that produced it.

Get a better draft

Practice

Add an example to match. Drop an example you like into the folder and Claude matches your structure and voice.

Practice

Ask it to flag uncertainty. Add "flag anything you're not confident about" so you know where to look first when you review the draft.

Make Claude work for you

Tell Claude your own rules for this task, such as your entry format and your sign-off rules, then save what you've done as a skill of your own. A few minutes of conversation and it runs with your standards from then on.

Make what we've done in this task so far into a skill called /decision-log.

Team / Decisions

Review the skill, and save it if Claude hasn't already.

Make it repeatable

Run it whenever a thread gets long

Decisions get buried the moment a thread crosses fifty replies. Ask Claude to set up a scheduled task, or open Scheduled in the sidebar, and /decision-log runs on each thread in your key channels that is marked decided.

Set up a scheduled task for weekdays at 5pm: check #marketing-ops and #leadership for threads with a :decided: reaction since the last run, run /decision-log on each, and append to decision-log.md in Decisions.

Team / Decisions
Scheduled taskActive
Decision-log capture

Runs /decision-log on threads marked decided in watched channels since the last run and appends each to the running log.

Every weekday at 5pmOpen in Claude

To use a folder on your computer during a scheduled task, keep your computer on and awake with the Claude desktop app open so Claude can access it.

Share with your teammates

Your /decision-log skill now carries your entry format, your sign-off rules, and your log location. Share it so anyone on the team can turn a thread into a log entry the same way, and the running log stays consistent no matter who captures it.

Going forward