Stats
Actions
Tags
From powertools
Run a Binstack decision-making analysis. Binstack chooses between competing options by checking each against stack-ranked priorities using binary materiality (does this option materially move the needle -- yes or no?) rather than weighted scoring. Best for: (1) Prioritizing a backlog of features, projects, or initiatives where you need one winner, (2) Choosing between alternatives that seem 'close' on paper but differ in strategic impact, (3) Decisions where defensibility matters -- explaining 'why this and not that' to stakeholders. Not ideal for: cost/effort tradeoff analysis (use ROI), exploring a problem space (use HEAD), or decisions with a single dominant criterion that needs no framework. Trigger on: 'binstack', 'prioritize these options', 'which should we build next', 'rank these features', or when the user has multiple options and needs a clear, defensible pick.
How this skill is triggered — by the user, by Claude, or both
Slash command
/powertools:binstackThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A decision framework that replaces weighted rubrics with binary materiality checks against stack-ranked priorities.
A decision framework that replaces weighted rubrics with binary materiality checks against stack-ranked priorities.
Binary materiality -- either an option materially moves the needle on an attribute, or it doesn't. No 1-5 scales. Material means measurably significant: "10% revenue bump," not "slight improvement."
Stack-ranked attributes -- rank what matters most, in order. No numerical weights. Just a priority list.
List the options under consideration.
Produce a priority-ordered list of attributes relevant to the decision. Be specific -- "20% decrease in cancellations" beats "improve retention." Tailor the stack to current circumstances.
Example stacks:
For each attribute, set a concrete bar for what counts as material impact. Examples: "at least 10% revenue increase," "cuts support tickets by 40%," "saves 5 hours/week." If quantification is impossible, articulate a clear qualitative bar.
Work through the stack from the top priority down:
Present the winner and the reasoning chain:
Winner: Option X
- Materially addresses [Priority 1]: [evidence]
- Survived over Option Y, which failed [Priority 1]
- Survived over Option Z, which failed [Priority 2]
Include a "why not" for each eliminated option.
npx claudepluginhub jordangaston/claude-plugins --plugin powertoolsRuns prioritization frameworks (RICE, ICE, MoSCoW, Weighted Scoring, Kano) against a feature list, producing a comparison table and executive recommendation.
Ranks requirements, features, backlog items, and initiatives using MoSCoW, Kano model, weighted scoring, and value-effort matrices.
Apply RICE, ICE, MoSCoW, Kano, and Value vs Effort frameworks for prioritizing features, roadmaps, backlogs, and trade-offs.