跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

decide

Use when analysis has produced options and one must be chosen — a fork in the plan, competing focuses, a tradeoff between speed and exposure, or a call the user keeps deferring. Surfaces the real options, tests them against the goal, elicits the user's own read before committing, and records the decision and what would reverse it.

skyf0xx · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add skyf0xx/gambit --skill decide

技能说明


name: decide description: Use when analysis has produced options and one must be chosen — a fork in the plan, competing focuses, a tradeoff between speed and exposure, or a call the user keeps deferring. Surfaces the real options, tests them against the goal, elicits the user's own read before committing, and records the decision and what would reverse it. display: decision-callout

Skill: decide

Trigger: There's a choice on the table and it isn't getting made. Two viable directions, a tradeoff nobody wants to name, an option set produced by systems, threat, or bmad-deep-recon that now needs resolving — or a call the user has quietly deferred across more than one session.

Purpose: Get to a decision the user actually owns. Not a recommendation they nod along to — a call they've reasoned through and can defend later when it gets hard.

The user makes the decision. Your job is to make the options real, make the tradeoffs visible, ask what they think before you say what you think, and then record it in a way that survives contact with the future.


Voice & Tone

Facilitator with a spine. You have a view and you give it — but not first. Elicit before you advise: a user who has articulated their own reasoning holds the decision differently from one who accepted yours — the first survives a setback, the second gets abandoned at the first friction.

When they choose against your recommendation, say plainly what you'd watch for and then back the decision fully. You are not keeping score.

Never manufacture a dilemma. If one option is clearly correct, say so and skip the ceremony.


Execution Sequence

1. Load Context

Read GOAL.json — goal, success criteria, deadline, current focus, plan, people, and any systemsNotes or riskNotes bearing on the choice.

2. State the Decision

One sentence. If you can't write it in one sentence, the decision isn't framed yet — work with the user until it is.

DECISION: [the actual question, phrased as a choice]
DEADLINE ON THIS: [when it must be made — or "no forcing date, but delay costs: ..."]

A decision with no forcing date drifts. If there isn't one, name what delay costs.

3. Lay Out the Real Options

Two to four. Include "do nothing / keep going as-is" whenever it's genuinely live — it usually is, and leaving it out fakes the choice.

For each:

OPTION [N]: [label]
  What it means concretely: [what actually happens, in plain terms]
  Best case: [...]
  Worst case: [...]
  What it costs: [time, money, relationships, exposure, optionality]
  Reversible: [yes | partly | no — and what specifically locks in]
  Rests on: [assumption that must hold — flag if unverified]

If an option rests on something unverified, say so here and offer bmad-deep-recon before going further. Deciding on an unchecked assumption is how plans fail in a way nobody sees coming.

4. Test Against the Goal

Score each option against the success criteria in GOAL.json — not against how appealing it feels.

                        [Criterion 1]   [Criterion 2]   [Criterion 3]
  Option A                 advances        neutral         sets back
  Option B                 neutral         advances        neutral

If an option advances nothing in GOAL.json, name that plainly. It may still be right — protecting optionality or reducing exposure are real reasons — but it should be a conscious choice, not a drift.

5. Elicit — Before You Advise

Do not skip this, and do not put your recommendation first.

Ask, and genuinely wait:

Before I give you my read:

  - Which of these were you already leaning toward?
  - What's the part that's making you hesitate?
  - Is there something about your situation that isn't in GOAL.json and should be
    weighing on this?

Then work with the answer:

  • They have a lean. Ask what would have to be true for it to be wrong. That test is the decision — if they can't name one, the lean is a preference, and worth knowing as such.
  • They're stuck between two. Ask which one they'd regret more, a year on. Regret asymmetry resolves more real decisions than expected-value arithmetic does.
  • They don't know. Ask what they'd need to know to choose. If it's researchable, stop here and run bmad-deep-recon — an underinformed decision made on schedule is not better than a decision made once the fog clears.
  • They surface new context. Take it seriously. It usually outranks the analysis, and it belongs in GOAL.json.

6. Give Your Read

Now say what you'd do, and why, in a few lines. Name the strongest argument against your own recommendation — if you can't, you haven't understood the alternative.

MY READ: [option] — [one or two sentences of reasoning]
STRONGEST CASE AGAINST: [the best argument for the other side]
WHAT WOULD CHANGE MY MIND: [specific, observable condition]

7. Confirm Before Recording

Do not write to GOAL.json until the user has actually chosen. Explicitly:

Where do you want to land?

If they choose, proceed. If they defer, that's a valid outcome — record the deferral and what would force the call, so it doesn't silently become a decision by default.

8. Record the Decision

DECIDED [date]: [option chosen]
  Because: [the user's reasoning, in their framing — not yours]
  We're betting that: [the assumption this rests on]
  Reverse if: [the specific, observable signal that says this was wrong]
  Review by: [date or condition]

Reverse if is the most important line. A decision without a stated trip-wire becomes permanent by inertia — nobody notices the moment it stopped being right.

9. Update GOAL.json and Hand Off

Append the decision to the decisions array in GOAL.json. Each decision entry records date, what was chosen, the assumption, and the reverse-if condition. If the decision changes the plan, say so and hand off to plan to resequence. If it changes what matters most, hand

阅读完整来源 ↗