Menu
Use when picking between options - produces a recommendation with explicit alternative considered and reason rejected
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | making-a-decision |
| description | Use when picking between options - produces a recommendation with explicit alternative considered and reason rejected |
| kind | workflow |
| audience | anyone |
| ai-tools | any |
| complexity | simple |
| time | 10-30 min |
| version | 1.0.0 |
| source | bundled |
Produces a written decision with the criteria, the options scored, the recommendation, the runner-up, and the reason the runner-up lost. Documents what would change your mind.
A written decision document: criteria + scoring + recommendation + alternative + reversal trigger.
This is a workflow.
In one sentence. ("Should I X or Y.")
3-5 criteria, weighted (numeric or simple high/med/low).
Score every option against every criterion. A 3-option, 4-criterion grid is enough.
Based on the score, name the winner.
Explicitly name the second-best option.
State: "I considered [runner-up] and rejected it because [reason]." The reason must be specific (cite criteria, not "it wasn't as good").
"I would change my mind if [concrete event or metric]." The trigger must be observable.
Input: Pick between two analytics vendors: Acme and Beta.
Output:
Decision: Pick Acme as our analytics vendor.
Criteria (weighted 1-3):
- Price (3): Acme $40k/yr, Beta $25k/yr
- Integration with our stack (3): Acme native, Beta needs adapter
- Time to first dashboard (2): Acme 1 day, Beta 1 week
- Support quality (2): both 8/10
- Future-proofing (1): Acme hot, Beta cooling
Scoring: Acme wins on integration, time-to-first-dashboard, future-proofing. Beta wins on price.
Recommendation: Acme.
Considered alternative: Beta. Rejected because integration cost would erase the price advantage in year 1, and the slower time-to-first-dashboard delays our Q3 reporting commitment.
Would change mind if: Acme raises price by >40% at renewal, OR Beta releases native integration before we sign.
Use when the meta-builder routes to kind=discipline. Generates a discipline spell with the rule, excuses table, warning signs, and hard gates.
Use when the user wants to capture a repeatable task as a reusable spell, or asks "how do I build a workflow / skill / framework for X"
Use when the meta-builder routes to kind=subagent. Generates a spell that dispatches one or more subagents to do work in parallel or in isolation.
Use when the meta-builder routes to kind=workflow. Generates a workflow spell with explicit stages, checkpoints, and loop-back conditions.
Use when composing multiple spells into a chain that runs end-to-end (e.g. brainstorm -> plan -> execute -> verify).
Use when browsing what spells are available - bundled seeds, your personal library, or both. Filter by kind, audience, or update status.
