prioritize-bets
Form, compare and select bets, each an intervention with an outcome mechanism toward a current objective, with its hardest assumption, the strongest alternative, a next commitment and continue/change/stop conditions. Use after objectives exist and commercial choices are available, and when a review or new evidence changes which bets deserve concentration.
LeanOS-Technologies · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add LeanOS-Technologies/strategy --skill prioritize-bets技能说明
name: prioritize-bets description: Form, compare and select bets, each an intervention with an outcome mechanism toward a current objective, with its hardest assumption, the strongest alternative, a next commitment and continue/change/stop conditions. Use after objectives exist and commercial choices are available, and when a review or new evidence changes which bets deserve concentration.
prioritize-bets
Writes bet-portfolio under the shared document rules.
When and what it decides
The question: which interventions, run together, most credibly move the current objective, and what would make us continue, change or stop each? Consume only what the choice depends on.
Inputs and authority
objectives(required): the outcomes bets must serve.opportunities,target-segments,positioning-decision,revenue-model,offer-catalogue,price-book: the commercial configuration the bets act on. Read their statuses: a proposed offer is a proposal.channel-map, available capabilities,experiment-result, the currentfocus-plan.- A bet never changes a member's choice; it states which choice it relies on and proposes changes to the owning member.
Method
Record sources, exact owner quotes and calculation premises in the relevant table’s basis or source cells. Carry decision status in its status column and the document’s role; prose states choices and ambition directly.
- Develop routes to the objectives, ambition included. Form each bet as condition → intervention → customer or operating response → objective contribution. Use objective trade-offs §2 to connect commercial progress with reach, adoption, authority or scale. Treat the hardest consequential assumption as a design input and specify the demonstration, comparison or market action that tests it. Record premises and estimates in Hypothesis and basis; record bet status in Disposition.
- Classify each as establish, exploit or resolve (portfolio choice §1). A resolve bet names the later decision it can change.
- Compare real alternatives, always including continuing current work. Use the dimensions that differ: contribution, time to a readable result, delivery conditions, dependencies, reversibility, options opened. Use expected value only when outcomes, horizon and probabilities are defensible; otherwise compare scenarios and find the preference reversal (§2). Count learning once.
- Assemble the portfolio. Keep bets that reinforce; resolve competition for the same customers' attention, product scope or owner decisions (§3). Name the strongest forgone bet and the condition that would revive it.
- Set controls before results. For each bet: observation horizon, continue/change/stop conditions with their basis, and the next commitment. A threshold placed where the bet already passes is not a control.
- Hand to focus. Each selected bet has a next action and its actual dependency, ready for set-focus.
Evaluate and correct
| Defect | Detect by | Correct by |
|---|---|---|
| Restated goal as mechanism | "Do X to achieve the objective" with no customer behaviour | Write the customer or operating response that links them |
| Fabricated precision | Probabilities or response numbers without basis | Replace with scenarios and a reversal condition |
| Double-counted learning | Learning listed as a separate benefit beside the decision it improves | Keep only the decision consequence |
| Backfilled thresholds | Stop condition already met or unreachable | Set it from the objective's decision point |
| Orphan bet | Objective reference missing or unresolved | Attach to an objective or drop; if no objective fits, report for set-objectives |
| Money in the bet | Amounts or hour estimates | Remove; name a needed purchase in the next action for set-focus |
Run the group check; REF findings on the Objective column are defects of this skill.
Recovery
- NeedData: no objectives. Route to set-objectives first, or proceed on a proposed objective stated as such.
- NeedData: a commercial document is missing. Form the bet on what exists, mark the reliance as open and name the owning member.
- Conflict: two bets need incompatible choices (different target segments). Present both with the reversal condition; the owner chooses.
Example
Illustrative fixture: fictional venture.
Brindlewick pursues wider use of own-format reporting (OBJ-1) and paid app use on real jobs (OBJ-2). A report demonstration serves both by making the professional idea inspectable.
## Bets and mechanisms
| ID | Objective | Scope | Intervention | Expected outcome | Mechanism | Commercial references |
| --- | --- | --- | --- | --- | --- | --- |
| BET-1 | OBJ-1, OBJ-2 | Independent inspectors | Prepare a worked own-format report and a paid app offer | Inspectors reuse the approach and some buy the tool | A visible example shows how captured judgment becomes a client report; the app makes repeated production practical | TGT-1, OFR-1 |
## Commitment and comparison
| Bet | Disposition | Next action | Dependency | Rationale | Alternative |
| --- | --- | --- | --- | --- | --- |
| BET-1 | proposed | Build the worked report from the available app | An inspector-approved sample | Connects professional adoption to a deliverable commercial offer | A product feature page makes fewer professional ideas available to reuse |
## Evidence and control
| Bet | Hypothesis and basis | Observation horizon | Continue, change or stop | Next commitment |
| --- | --- | --- | --- | --- |
| BET-1 | [hypothesis] inspectors can recognise and reuse the approach; [owner: "The desktop app works"]. Test the hardest assumption by having an inspector apply the example to a different re
阅读完整来源 ↗