From claude-workspace
Work through a hard or consequential choice and reach a clear, defensible recommendation. Use when the user is weighing options, stuck between alternatives, facing a tradeoff, or about to commit to something costly or hard to reverse. Frames the real decision and widens the option set, evaluates options against weighted criteria, adversarially checks for motivated reasoning and false binaries, then recommends — with the tradeoff being accepted made explicit. Built to defeat the pre-chosen answer dressed up as analysis.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-workspace:decideThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A four-phase process for making a choice you can stand behind — and explain. The enemies here are the
A four-phase process for making a choice you can stand behind — and explain. The enemies here are the false binary (only seeing two options when there are five) and motivated reasoning (an answer already chosen, with the "analysis" reverse-engineered to justify it). The phases force the option set open, make the criteria explicit before scoring, and put an adversarial pass between evaluation and recommendation. Work them in order.
Pin down what's actually being decided. Ask sharp, batched questions:
Confirm the decision statement and criteria in a line or two, then evaluate.
Assess each option against the criteria. Be even-handed — every option gets a fair hearing, including the one the user dislikes and the "do nothing" baseline. Cover:
Don't crown a winner yet.
Now attack the evaluation, especially any drift toward a foregone conclusion:
Revise the evaluation where these land.
Make a call. A survey of options that ducks the recommendation is a failure of this process.
Deliver it, and offer to save the decision record (e.g. decision-<slug>.md) — the framing, criteria,
and reasoning are worth keeping, so future-you can see why, not just what.
npx claudepluginhub matthb1/claude-workspace --plugin claude-workspaceGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.