sequence-plan-around-risky-assumptions
Use when a plan has both risky unknowns and safe known work and you must choose an order. Starts the highest-uncertainty and longest-lead items first so failures surface while there is still time to react.
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 81
- Forks
- 17
01 前言 Front Matter
- name
- sequence-plan-around-risky-assumptions
- description
- Use when a plan has both risky unknowns and safe known work and you must choose an order. Starts the highest-uncertainty and longest-lead items first so failures surface while there is still time to react.
02 资源文件 3
- 许可证LICENSE1.0 KB
- 参考文档SOURCE.md364 B
- 参考文档TRUST.auto.yaml2.2 KB
03 SKILL.md 正文
Sequence the plan around risky assumptions
Order by information gained and time to recover, not by convenience. The cost of a wrong assumption is paid at the moment you discover it, so discover the expensive ones early, while the schedule can still absorb the news.
Procedure
-
Score each task in
notes/plan.mdon two axes: uncertainty (how likely the approach is wrong) and lead time (how long it takes to get any signal). -
Sort so that high-uncertainty and long-lead items come first; low-risk, well-understood work is filler for the back.
python3 -c " t=[('new-indexer',9,9),('copy-tweak',1,1),('vendor-api',7,8),('config',2,1)] for n,u,l in sorted(t,key=lambda x:-(x[1]+x[2])): print(n,u+l)" new-indexer 18 vendor-api 15 config 3 copy-tweak 2 -
Expose the riskiest assumption with the smallest possible probe first: a spike, a call, a single fetch. Do not build the whole feature to learn it will not work.
-
Interleave the safe work as the "next thing" when a risky item is blocked waiting on a signal, but never let comfortable work crowd the risk off the front.
-
If the riskiest item fails, the plan must have an alternative ready — that is why it is first; the schedule has not yet been committed to it.
-
Re-check the ordering when an assumption resolves; a former risk becomes known work and the next unknown moves up.
Pitfalls
- Doing the known work first to "get momentum," so the risky item surfaces late when there is no time to react.
- Confusing uncertainty with difficulty: a hard but well-understood task is not the thing to front-load.
- Front-loading risk without a fallback, so the early failure has nowhere to go.
- Treating a long lead time as low priority because effort is low — lead time dominates recoverability.
- Sequencing by who is available rather than by information value.
Verification
python3 -c "t=[('a',9,9),('b',1,1)]; print(sorted(t,key=lambda x:-(x[1]+x[2]))[0][0]==\"a\")"
# True — the higher uncertainty+lead item sorts first; a plan ordered otherwise is inverted
Report the ordering, each item's uncertainty and lead time, and the fallback for the riskiest one.
04 同仓库更多 Skills
recipe-performance
Diagnose a specific MetaMask user flow's real-app performance and Sentry critical-user-flow telemetry with deterministic mm-harness recipes. Use for CUF boundaries, cold/warm/background-resume behavior, latency regressions, lifecycle tags, duplicate or blocking network requests, long tasks, layout/paint cost, screen redraws, React rerenders, or browser trace analysis where tests alone cannot prove the real app.
mexc-spot-websocket
MEXC Spot WebSocket workflows for public streams, protobuf handling, depth maintenance, listen keys, and private streams without exposing API keys.
mexc-spot-rest
MEXC Spot REST workflows for public data, signed account requests, orders, wallet/admin actions, and secure signing without exposing API keys.
mexc-futures-websocket
MEXC Futures WebSocket workflows for public streams, private account/order/position streams, ping/pong, subscriptions, and depth maintenance.
0xklen-version-and-refresh-sanctions-lists
暂无简介
verify-tests-cover-changed-lines
Use when a PR adds code that the existing suite may not exercise. Measures patch coverage — the share of newly changed lines hit by tests — before approving.