thread-to-decision-live
Turn a REAL Slack thread (or channel) into a logged decision — read it, extract what was decided, who owns what, and record it in Notion — not a template for writing decisions. Use when asked to capture the decision from this thread, log what we agreed, turn this Slack discussion into a decision record, or close this out in Cowork. Reads the thread via the Slack connector, distils the decision / owners / next steps / open questions, and produces a decision-record artifact written to a Notion database (with the source thread linked).
npx skills add mohitagw15856/pm-claude-skills --skill thread-to-decision-live --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Thread to Decision (Live) Decisions made in chat evaporate — three weeks later no one remembers what was agreed or who owns it. In Claude Cowork this skill reads the *real* thread, pins down the decision and its owners, and writes a durable record into Notion, with the source linked, so the agreement survives the scroll. ## What This Skill Produces - **The decision record** — the decision, the rationale, who decided, owners, next steps with dates, and open questions - **A Notion entry** — the record written to the user's decision-log database (or an artifact if no DB is set) - **The confirmation loop** — anything ambiguous flagged back to the user before it's logged as settled ## Required Inputs Ask for these if not provided: - **The thread/channel** — a Slack link or the channel + rough time - **Where to log it** — the Notion decision-log database (or produce an artifact to paste) - **The stakes** — reversible-and-cheap vs one-way-door — depth of the record follows ## Framework: What a Decision Record Needs 1. **The decision** — stated as a choice made, not a discussion had. 2. **The rationale** — the why, and the main alternative rejected. 3. **Owners & next steps** — who does
- What This Skill Produces
- Required Inputs
- Framework: What a Decision Record Needs
- Execution (Cowork)
- Output Format
- Decision
- Rationale
- Owners & next steps
- Open questions
- Source
- Quality Checks
- Anti-Patterns
- Example Trigger Phrases
What does the thread-to-decision-live skill do?
Turn a REAL Slack thread (or channel) into a logged decision — read it, extract what was decided, who owns what, and record it in Notion — not a template for writing decisions. Use when asked to capture the decision from this thread, log what we agreed, turn this Slack discussion into a decision record, or close this out in Cowork. Reads the thread via the Slack connector, distils the decision / owners / next steps / open questions, and produces a decision-record artifact written to a Notion database (with the source thread linked).
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill thread-to-decision-live --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.