[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H0AM65ZQ2T8Q5APNE9B55R":3,"skill-same:01M6H0AM65ZQ2T8Q5APNE9B55R":76},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M6H0AM65ZQ2T8Q5APNE9B55R","sequence-plan-around-risky-assumptions",null,"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.","jiayaoqijia\u002Fcryptoskill","jiayaoqijia","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1453879?v=4","01M6GMYTX7Q7S504VC6E756ENR","YQ","01M6GMYV1QKJ1CC75MTTGT9PR0",81,"MIT","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-sequence-plan-around-risky-assumptions\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-sequence-plan-around-risky-assumptions\u002FSKILL.md",[],[20,21,22,23,24,25,26,27,28,29,30,31,32,33],"plan","sequence plan around risky assumptions","sequence","safe","react","first","choose","work","use","time","you","uncertainty","when","lead","2026-11-10 10:12:30",false,"---\nname: sequence-plan-around-risky-assumptions\ndescription: 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.\n---\n\n# Sequence the plan around risky assumptions\n\nOrder 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.\n\n## Procedure\n\n1. Score each task in `notes\u002Fplan.md` on two axes: uncertainty (how likely the approach is wrong) and lead time (how long it takes to get any signal).\n2. Sort so that high-uncertainty and long-lead items come first; low-risk, well-understood work is filler for the back.\n\n       python3 -c \"\n       t=[('new-indexer',9,9),('copy-tweak',1,1),('vendor-api',7,8),('config',2,1)]\n       for n,u,l in sorted(t,key=lambda x:-(x[1]+x[2])): print(n,u+l)\"\n       new-indexer 18\n       vendor-api 15\n       config 3\n       copy-tweak 2\n\n3. 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.\n4. 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.\n5. 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.\n6. Re-check the ordering when an assumption resolves; a former risk becomes known work and the next unknown moves up.\n\n## Pitfalls\n\n- Doing the known work first to \"get momentum,\" so the risky item surfaces late when there is no time to react.\n- Confusing uncertainty with difficulty: a hard but well-understood task is not the thing to front-load.\n- Front-loading risk without a fallback, so the early failure has nowhere to go.\n- Treating a long lead time as low priority because effort is low — lead time dominates recoverability.\n- Sequencing by who is available rather than by information value.\n\n## Verification\n\n    python3 -c \"t=[('a',9,9),('b',1,1)]; print(sorted(t,key=lambda x:-(x[1]+x[2]))[0][0]==\\\"a\\\")\"\n    # True — the higher uncertainty+lead item sorts first; a plan ordered otherwise is inverted\n\nReport the ordering, each item's uncertainty and lead time, and the fallback for the riskiest one.\n","# Sequence the plan around risky assumptions\n\nOrder 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.\n\n## Procedure\n\n1. Score each task in `notes\u002Fplan.md` on two axes: uncertainty (how likely the approach is wrong) and lead time (how long it takes to get any signal).\n2. Sort so that high-uncertainty and long-lead items come first; low-risk, well-understood work is filler for the back.\n\n       python3 -c \"\n       t=[('new-indexer',9,9),('copy-tweak',1,1),('vendor-api',7,8),('config',2,1)]\n       for n,u,l in sorted(t,key=lambda x:-(x[1]+x[2])): print(n,u+l)\"\n       new-indexer 18\n       vendor-api 15\n       config 3\n       copy-tweak 2\n\n3. 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.\n4. 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.\n5. 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.\n6. Re-check the ordering when an assumption resolves; a former risk becomes known work and the next unknown moves up.\n\n## Pitfalls\n\n- Doing the known work first to \"get momentum,\" so the risky item surfaces late when there is no time to react.\n- Confusing uncertainty with difficulty: a hard but well-understood task is not the thing to front-load.\n- Front-loading risk without a fallback, so the early failure has nowhere to go.\n- Treating a long lead time as low priority because effort is low — lead time dominates recoverability.\n- Sequencing by who is available rather than by information value.\n\n## Verification\n\n    python3 -c \"t=[('a',9,9),('b',1,1)]; print(sorted(t,key=lambda x:-(x[1]+x[2]))[0][0]==\\\"a\\\")\"\n    # True — the higher uncertainty+lead item sorts first; a plan ordered otherwise is inverted\n\nReport the ordering, each item's uncertainty and lead time, and the fallback for the riskiest one.\n",{"name":5,"description":7},"main","3df1d0d67b30ff15236561f8c0f9f06d33f42dfd","skills\u002Fpayments\u002F0xklen-sequence-plan-around-risky-assumptions",17,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia","https:\u002F\u002Feth2030.com","Hardcore infra. Building @alt-research and applied cryptography.","2026-11-12 02:28:42",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add jiayaoqijia\u002Fcryptoskill --skill sequence-plan-around-risky-assumptions",{"tool":54,"command":55},"bunx","bunx skills add jiayaoqijia\u002Fcryptoskill --skill sequence-plan-around-risky-assumptions",{"tool":57,"command":58},"pnpm","pnpm dlx skills add jiayaoqijia\u002Fcryptoskill --skill sequence-plan-around-risky-assumptions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-sequence-plan-around-risky-assumptions\u002FSKILL.md",true,[62,66,72],{"path":63,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":16},"LICENSE","许可证",1063,{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"SOURCE.md","REFERENCE","参考文档",364,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-sequence-plan-around-risky-assumptions\u002FSOURCE.md",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"TRUST.auto.yaml",2217,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-sequence-plan-around-risky-assumptions\u002FTRUST.auto.yaml",[77,104,127,145,158,168],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":34},"01M712C436EQYE43342Q4E7GG1","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\u002Fwarm\u002Fbackground-resume behavior, latency regressions, lifecycle tags, duplicate or blocking network requests, long tasks, layout\u002Fpaint cost, screen redraws, React rerenders, or browser trace analysis where tests alone cannot prove the real app.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fwallets\u002Fmetamask-official-recipe-performance\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fwallets\u002Fmetamask-official-recipe-performance\u002FSKILL.md",[],[85,86,87,88,89,90,91,92,93,94,95,96,97,98,24,99,100,101,102,103],"performance","recipe performance","recipe","mm","sentry","harness","app","deterministic","recipes","flow","cold","critical","analysis","tasks","browser","layout","screen","network","metamask",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":108,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":34},"01M70XT2F8A5CQZ81JBP98KSW3","mexc-spot-websocket","MEXC Spot WebSocket workflows for public streams, protobuf handling, depth maintenance, listen keys, and private streams without exposing API keys.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-spot-websocket\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-spot-websocket\u002FSKILL.md",[],[113,114,115,116,117,118,119,120,121,122,123,124,125,126],"mexc spot websocket","spot","websocket","api","workflows","public","listen","streams","depth","keys","for","api keys","maintenance","protobuf",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":108,"licenseFileUrl":131,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":34},"01M70XT0MBXN3WZY1BKN0CPNKR","mexc-spot-rest","MEXC Spot REST workflows for public data, signed account requests, orders, wallet\u002Fadmin actions, and secure signing without exposing API keys.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-spot-rest\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-spot-rest\u002FSKILL.md",[],[135,114,136,137,138,139,140,124,123,122,141,142,143,118,144,117,116],"mexc spot rest","REST","admin","signing","Wallet","requests","actions","secure","data","orders",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":108,"licenseFileUrl":149,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":34},"01M70XSYSVZ2N0N91XCAR2CAK0","mexc-futures-websocket","MEXC Futures WebSocket workflows for public streams, private account\u002Forder\u002Fposition streams, ping\u002Fpong, subscriptions, and depth maintenance.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-futures-websocket\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-futures-websocket\u002FSKILL.md",[],[153,154,115,155,156,125,123,157,121,120,118,117],"mexc futures websocket","futures","position","ping","subscriptions",{"skillNo":159,"name":160,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":161,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":34},"01M6H0ZWHVE5W04WG2DKQE2SQC","0xklen-version-and-refresh-sanctions-lists","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-version-and-refresh-sanctions-lists\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-version-and-refresh-sanctions-lists\u002FSKILL.md",[],[165,166,167],"refresh","0xklen version and refresh sanctions lists","version",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":172,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":34},"01M6H0Z28Q3R8J0S799GJQWXM3","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.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-verify-tests-cover-changed-lines\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-verify-tests-cover-changed-lines\u002FSKILL.md",[],[176,177,178,179,180,181,182,28,183,184,185],"tests","cover","verify tests cover changed lines","verify","coverage","pr","exercise","patch","code","share"]