Menu

Individual skill

thread-to-decision

0upvotes

Land a sprawling chat thread on an actual decision — the summarize-and-fork move (positions restated, the question isolated), the decider-and-deadline injection, and the recorded close that ends the forty-message orbit. Use when asked this thread is going in circles, get a decision out of this discussion, summarize where we landed, or why do our threads never conclude. Produces the thread summary with positions attributed, the isolated decision question, the closure message, and the decision record.

plugins/pm-cowork/skills/thread-to-decision/SKILL.md

Read pinned source

Source commit e0009a385c480fb0b5687e7412df67c7c64f7cee

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,542
Repository last updated
Nov 11, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Thread To Decision Skill

Threads orbit because nobody performs the landing: forty messages in, three positions have emerged, two side-quests have spawned, and every participant believes a different thing was "basically agreed." The landing is a *move*, performable by anyone (not just the boss): summarize the positions fairly with names, isolate the actual question from the side-quests, inject the missing structure — a decider and a deadline ([async-instead](../async-instead/SKILL.md) closure rules) — and when the call lands, record it where decisions live, because a decision that exists only at message 47 doesn't exist.

## What This Skill Produces

- **The summary message** — the thread compressed: the question, the positions with names, the side-quests parked
- **The structure injection** — decider named (or proposed), deadline set, silence-meaning declared
- **The closure message** — the decision, its why, dissent acknowledged
- **The record** — the decision logged durably, linked back to the thread

## Required Inputs

Ask for these if not provided:
Back to top