Code Design Rationale Investigator
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
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.
MITAuto-check passed
Install Thread To Decision Live
$ npx skills add mohitagw15856/pm-claude-skills --skill thread-to-decision-live -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills thread-to-decision-live --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/thread-to-decision-live .claude/skills/thread-to-decision-live && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "thread-to-decision-live" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/thread-to-decision-live into .claude/skills/thread-to-decision-live/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "thread-to-decision-live", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/thread-to-decision-liveType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill thread-to-decision-live -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills thread-to-decision-live --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/thread-to-decision-live .agents/skills/thread-to-decision-live && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "thread-to-decision-live" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/thread-to-decision-live into .agents/skills/thread-to-decision-live/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "thread-to-decision-live", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill thread-to-decision-live -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills thread-to-decision-live --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/thread-to-decision-live .cursor/skills/thread-to-decision-live && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "thread-to-decision-live" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/thread-to-decision-live into .cursor/skills/thread-to-decision-live/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "thread-to-decision-live", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/thread-to-decision-live--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill thread-to-decision-live -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills thread-to-decision-live --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/thread-to-decision-live .gemini/skills/thread-to-decision-live && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "thread-to-decision-live" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/thread-to-decision-live into .gemini/skills/thread-to-decision-live/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "thread-to-decision-live", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills thread-to-decision-liveInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill thread-to-decision-live -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/thread-to-decision-live .github/skills/thread-to-decision-live && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "thread-to-decision-live" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/thread-to-decision-live into .github/skills/thread-to-decision-live/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "thread-to-decision-live", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill thread-to-decision-live -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills thread-to-decision-live --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/thread-to-decision-live .opencode/skills/thread-to-decision-live && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "thread-to-decision-live" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/thread-to-decision-live into .opencode/skills/thread-to-decision-live/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "thread-to-decision-live", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
thread-to-decision-live- GitHub stars
- 1.4k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 553 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
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.
- Works in 5 steps: The decision — stated as a choice made,… → The rationale — the why, and the main… → Owners & next steps — who does what by… → …
- Asked to capture the decision from this thread
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: What a Decision… and Execution (Cowork), plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Thread To Decision Live is an agent skill from mohitagw15856/pm-claude-skills. 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…
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with Notion and Slack. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to capture the decision from this thread
- Log what we agreed
- Turn this Slack discussion into a decision record
- Close this out in Cowork
Example prompts
- “/thread-to-decision-live”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- The decision — stated as a choice made, not a discussion had.
- The rationale — the why, and the main alternative rejected.
- Owners & next steps — who does what by when; a decision with no owner isn't one.
- Open questions — what's still unresolved, so it isn't mistaken for settled.
- Provenance — a link to the source thread and the date.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Thread To Decision Live loads about 1.1k tokens when it runs. Until then it costs about 141 tokens; SKILL.md has 553 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 553 words, ~1,065 tokens.
Download SKILL.mdSave it as
.claude/skills/thread-to-decision-live/SKILL.md (or your agent's skills folder).- name
- thread-to-decision-live
- description
- 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).
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
- The decision — stated as a choice made, not a discussion had.
- The rationale — the why, and the main alternative rejected.
- Owners & next steps — who does what by when; a decision with no owner isn't one.
- Open questions — what's still unresolved, so it isn't mistaken for settled.
- Provenance — a link to the source thread and the date.
Execution (Cowork)
- Read the thread — via the Slack connector, pull the full thread/channel window. Read every message; don't summarise from the first and last.
- Distil — separate the decision from the debate. Identify who actually decided, the rationale, the owners named, and what stayed open.
- Confirm the ambiguous — if the thread never clearly lands, say so and ask; never manufacture a decision that wasn't made.
- Write to Notion — via the Notion connector, create an entry in the decision-log database with the fields above and the Slack permalink. If no DB is configured, emit the record as an artifact.
- Report — link the new Notion entry and list any open questions still needing an owner.
Guardrails: don't invent a decision, an owner, or a date not present in the thread; distinguish "decided" from "leaning"; write only to the specified database; if a connector is unauthorised, produce the record inline and say what couldn't be written.
Show full SKILL.md (177 more words)Show less
Output Format
A Decision Record:
Decision
the choice made — one line
Decided by: … · Date: … · Reversibility: one-way / two-way
Rationale
- why; main alternative rejected and why
Owners & next steps
| Owner | Action | By |
|---|
Open questions
- … (needs an owner)
Source
- Slack thread: [link] · Logged to: [Notion entry]
Quality Checks
- The decision is stated as a choice, not a discussion summary
- Every owner/date comes from the thread, not invented
- "Decided" is distinguished from "still leaning / open"
- The source thread is linked and the record was written to the named destination
- Open questions are listed rather than smoothed over
Anti-Patterns
- Manufacturing a decision the thread never reached — flag it as unresolved.
- Assigning owners no one agreed to.
- Logging to the wrong place — write only to the specified DB.
- A summary of the chat instead of a decision record.
Example Trigger Phrases
- "Capture the decision from this Slack thread and log it in Notion."
- "Turn this discussion into a decision record."
- "What did we actually agree here? Write it to the decision log."
- "Close this thread out with owners and next steps in Cowork."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/thread-to-decision-live of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Thread To Decision Live next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Thread To Decision Live this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Code Design Rationale Investigatorcursor/plugins | 11k | 9 repos | ~2.6k | Automated safety check: Pass | None | |
| ComposioComposioHQ/composio | 30k | 1 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Connect Apps with ComposioComposioHQ/awesome-claude-skills | 77k | 3 repos | ~557 | Automated safety check: Pass | None | |
| Claap Weekly RecapOthmane-Khadri/YALC-the-GTM-operating-system | 318 | — | ~5.4k | Automated safety check: Pass | MIT | |
| Composio Cloud Toolsquarqlabs/argus | 279 | — | ~543 | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Composio
ComposioHQ/composio
Route and complete Composio work across Composio For You and Composio Platform.
Connect Apps with Composio
ComposioHQ/awesome-claude-skills
Connects an agent to 1000+ external apps through the Composio Tool Router plugin, so it can actually send emails, create issues and post messages instead of only drafting them.
Claap Weekly Recap
Othmane-Khadri/YALC-the-GTM-operating-system
Turns a week of Claap-recorded sales calls into action items and focus blocks on a Notion Kanban, delivered with a Slack summary.
Composio Cloud Tools
quarqlabs/argus
Routes requests to external SaaS apps such as GitHub, Gmail, Google Calendar, Slack, Notion and Linear through cloud tools, with safeguards on irreversible actions.
Enterprise Search
ZhixiangLuo/10xProductivity
Search your entire company's institutional knowledge in one query — Slack, Confluence, Jira, Linear, Notion, GitHub, plus any AI or multi-source search tool listed in verifiedconnections.md.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Questions about Thread To Decision Live
What does Thread To Decision Live 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. Thread To Decision Live is an agent skill from mohitagw15856/pm-claude-skills. 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.
When should I use Thread To Decision Live?
Thread To Decision Live fits situations like: asked to capture the decision from this thread; log what we agreed; turn this Slack discussion into a decision record; close this out in Cowork.
How do I install Thread To Decision Live in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill thread-to-decision-live -a claude-code`. Or copy the skill folder (skills/thread-to-decision-live in mohitagw15856/pm-claude-skills) into .claude/skills/thread-to-decision-live in your project. Claude Code loads it when a task matches its description.
How do I install Thread To Decision Live in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill thread-to-decision-live -a codex`. Or copy the skill folder (skills/thread-to-decision-live in mohitagw15856/pm-claude-skills) into .agents/skills/thread-to-decision-live in your project. Codex loads it when a task matches its description.
Can I use Thread To Decision Live in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill thread-to-decision-live -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/thread-to-decision-live, .gemini/skills/thread-to-decision-live, .github/skills/thread-to-decision-live and .opencode/skills/thread-to-decision-live in your project.
What does Thread To Decision Live need to run?
SKILL.md names no scripts, command-line tools or credentials: Thread To Decision Live is instructions for the agent only.
Does Thread To Decision Live access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Thread To Decision Live safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Thread To Decision Live use?
Thread To Decision Live is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Thread To Decision Live use?
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Thread To Decision Live?
Skills that share tags, products or a category with Thread To Decision Live: Code Design Rationale Investigator (cursor/plugins, 11k stars), Composio (ComposioHQ/composio, 30k stars), Connect Apps with Composio (ComposioHQ/awesome-claude-skills, 77k stars) and Claap Weekly Recap (Othmane-Khadri/YALC-the-GTM-operating-system, 318 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Thread To Decision Live?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.