thread-to-decision
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.
Profile →npx skills add mohitagw15856/pm-claude-skills --skill thread-to-decision --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 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: - **The thread** — the actual messages; summarizing positions requires reading them, and attribution requires care ("A argued X" mus
- What This Skill Produces
- Required Inputs
- Framework: The Landing Rules
- Output Format
- The Summary Message (post this)
- The Closure Message (when decided)
- The Record
- Quality Checks
- Anti-Patterns
What does the thread-to-decision skill do?
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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill thread-to-decision --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.