[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74GHB9P9QGYB0QP66MSWDW6":3,"skill-same:01M74GHB9P9QGYB0QP66MSWDW6":44},{"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":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M74GHB9P9QGYB0QP66MSWDW6","safe-rollout",null,"Design a safe progressive rollout — flags, canary\u002Fblue-green, ring stages, SLO health gates, automated rollback, kill switch. Rollout mechanics, not env promotion or A\u002FB experiments.","MohammadBafkar\u002Fpolymath","MohammadBafkar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F34940462?v=4","01M74G540TQFZWK6KVAPKFVGNR","Mohammad Bafkar","01M74G541HG19QP9V5DQCJVKYE",0,"MIT","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-release\u002Fskills\u002Fsafe-rollout\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: safe-rollout\ndescription: Design a safe progressive rollout — flags, canary\u002Fblue-green, ring stages, SLO health gates, automated rollback, kill switch. Rollout mechanics, not env promotion or A\u002FB experiments.\n---\n\n# safe-rollout\n\n> Ship change to users gradually, watch the signals that matter, and make rollback the default reflex — not a heroic incident response.\n\n**Mode:** analytical — judgment inside a fixed frame. Keep the output shape; every verdict cites its evidence; unknowns are marked `[TBD]` or `[VERIFY]`, never filled in.\n\n## When to use\n\n- A change is risky enough that an all-at-once deploy is unwise: large blast radius, new infra, irreversible data path.\n- The user asks how to roll out behind a flag, do a canary, or stage a percentage rollout safely.\n- A workflow invokes `polymath-release:safe-rollout`.\n\nThis designs *rollout mechanics*. It is not promoting a build across environments (`polymath-devops:env-promotion`), running an A\u002FB experiment to learn (`polymath-data:run-experiment` \u002F the `experimentToGA` workflow), or defining the SLO itself (`polymath-sre:slo-design` — consume it here).\n\n## Inputs\n\n- The change and its blast radius (who\u002Fwhat breaks if it's wrong).\n- Reversibility: is it flag-toggleable, or does it touch data\u002Fschema?\n- The SLIs\u002FSLOs that define \"healthy\" for the affected journey. Absent: run `polymath-sre:slo-design` first, or propose gate thresholds marked `[VERIFY: SLO]` — never a gate without a number.\n- Designing the rollout never executes it: flag flips, traffic shifts, and deploys are shown as commands for the operator and run only on their explicit go-ahead.\n\n## Procedure\n\n1. **Choose the technique** by reversibility and infra:\n   - *Feature flag* — app-level, instant off; the default for code-path changes.\n   - *Canary \u002F ring* — route a small % (or internal ring) to the new version; widen on health.\n   - *Blue-green* — full standby environment; instant cutover + cutback. Use for infra\u002Fruntime swaps.\n2. **Stage the ramp** — e.g. internal → 1% → 5% → 25% → 100%, with a bake time per stage.\n3. **Define health gates** — the SLIs and thresholds that must hold to advance; tie to `polymath-sre:slo-design`. Breach = halt + auto-rollback, not a page-and-wait.\n4. **Automate rollback** — flag-off \u002F route-back \u002F redeploy-previous; state the trigger and the expected time-to-safe.\n5. **Kill switch** — a single, tested control that disables the change instantly, independent of the deploy pipeline.\n6. **Data\u002Firreversibility** — for schema\u002Fdata changes, pair with expand\u002Fcontract migration; a flag cannot roll back a destructive write.\n7. **Slug** from the change name: a workflow's `${workflow.slug}` wins; otherwise lowercase it, replace each run of characters outside `a-z0-9` with `-`, trim `-` at the ends, and cut to ≤ 60 characters at a `-`. An existing file at the target path is updated in place (show the diff), never duplicated.\n8. Write `docs\u002Frollouts\u002F\u003Cslug>.md`.\n\n## Output\n\n`docs\u002Frollouts\u002F\u003Cslug>.md`, in this shape:\n\n```text\nRollout: checkout-v2        technique: canary (new service) + feature flag `checkout_v2`\n\nStages (advance only when every gate holds for the full bake):\n  internal (staff)  bake 24h\n  1%                bake 2h\n  5%                bake 4h\n  25%               bake 24h (covers a daily peak)\n  100%\n\nHealth gates (vs. the control cohort, from slo-design):\n  checkout success rate ≥ 99.5%  ·  p95 latency ≤ 800 ms  ·  payment-provider 5xx ≤ 0.2%\nRollback (automatic): any gate breached for 5 consecutive minutes → route 100% back to v1; time-to-safe ≤ 2 min\nKill switch: flag `checkout_v2` off — independent of the deploy pipeline; tested in staging on 2026-10-20\nIrreversible: order-table write path is expand\u002Fcontract — v2 writes both columns until the contract phase\nOperator commands (run on explicit go-ahead only): \u003Cflag \u002F traffic-shift commands per stage>\n```\n\n## Quality bar\n\n- Every stage has an explicit advance criterion (a metric + threshold), not \"looks fine\".\n- Rollback is automated and its trigger is a measured signal, not human judgment alone.\n- A kill switch exists and is independent of a full redeploy.\n- Irreversible (data) changes are called out and not hidden behind a flag that can't actually undo them.\n\n## Anti-patterns\n\n- \"Canary\" that is one box for five minutes with no health gate (theater).\n- Flag with no kill switch or no removal plan (flags become permanent tech debt).\n- Rollback that requires a manual redeploy under incident pressure.\n","# safe-rollout\n\n> Ship change to users gradually, watch the signals that matter, and make rollback the default reflex — not a heroic incident response.\n\n**Mode:** analytical — judgment inside a fixed frame. Keep the output shape; every verdict cites its evidence; unknowns are marked `[TBD]` or `[VERIFY]`, never filled in.\n\n## When to use\n\n- A change is risky enough that an all-at-once deploy is unwise: large blast radius, new infra, irreversible data path.\n- The user asks how to roll out behind a flag, do a canary, or stage a percentage rollout safely.\n- A workflow invokes `polymath-release:safe-rollout`.\n\nThis designs *rollout mechanics*. It is not promoting a build across environments (`polymath-devops:env-promotion`), running an A\u002FB experiment to learn (`polymath-data:run-experiment` \u002F the `experimentToGA` workflow), or defining the SLO itself (`polymath-sre:slo-design` — consume it here).\n\n## Inputs\n\n- The change and its blast radius (who\u002Fwhat breaks if it's wrong).\n- Reversibility: is it flag-toggleable, or does it touch data\u002Fschema?\n- The SLIs\u002FSLOs that define \"healthy\" for the affected journey. Absent: run `polymath-sre:slo-design` first, or propose gate thresholds marked `[VERIFY: SLO]` — never a gate without a number.\n- Designing the rollout never executes it: flag flips, traffic shifts, and deploys are shown as commands for the operator and run only on their explicit go-ahead.\n\n## Procedure\n\n1. **Choose the technique** by reversibility and infra:\n   - *Feature flag* — app-level, instant off; the default for code-path changes.\n   - *Canary \u002F ring* — route a small % (or internal ring) to the new version; widen on health.\n   - *Blue-green* — full standby environment; instant cutover + cutback. Use for infra\u002Fruntime swaps.\n2. **Stage the ramp** — e.g. internal → 1% → 5% → 25% → 100%, with a bake time per stage.\n3. **Define health gates** — the SLIs and thresholds that must hold to advance; tie to `polymath-sre:slo-design`. Breach = halt + auto-rollback, not a page-and-wait.\n4. **Automate rollback** — flag-off \u002F route-back \u002F redeploy-previous; state the trigger and the expected time-to-safe.\n5. **Kill switch** — a single, tested control that disables the change instantly, independent of the deploy pipeline.\n6. **Data\u002Firreversibility** — for schema\u002Fdata changes, pair with expand\u002Fcontract migration; a flag cannot roll back a destructive write.\n7. **Slug** from the change name: a workflow's `${workflow.slug}` wins; otherwise lowercase it, replace each run of characters outside `a-z0-9` with `-`, trim `-` at the ends, and cut to ≤ 60 characters at a `-`. An existing file at the target path is updated in place (show the diff), never duplicated.\n8. Write `docs\u002Frollouts\u002F\u003Cslug>.md`.\n\n## Output\n\n`docs\u002Frollouts\u002F\u003Cslug>.md`, in this shape:\n\n```text\nRollout: checkout-v2        technique: canary (new service) + feature flag `checkout_v2`\n\nStages (advance only when every gate holds for the full bake):\n  internal (staff)  bake 24h\n  1%                bake 2h\n  5%                bake 4h\n  25%               bake 24h (covers a daily peak)\n  100%\n\nHealth gates (vs. the control cohort, from slo-design):\n  checkout success rate ≥ 99.5%  ·  p95 latency ≤ 800 ms  ·  payment-provider 5xx ≤ 0.2%\nRollback (automatic): any gate breached for 5 consecutive minutes → route 100% back to v1; time-to-safe ≤ 2 min\nKill switch: flag `checkout_v2` off — independent of the deploy pipeline; tested in staging on 2026-10-20\nIrreversible: order-table write path is expand\u002Fcontract — v2 writes both columns until the contract phase\nOperator commands (run on explicit go-ahead only): \u003Cflag \u002F traffic-shift commands per stage>\n```\n\n## Quality bar\n\n- Every stage has an explicit advance criterion (a metric + threshold), not \"looks fine\".\n- Rollback is automated and its trigger is a measured signal, not human judgment alone.\n- A kill switch exists and is independent of a full redeploy.\n- Irreversible (data) changes are called out and not hidden behind a flag that can't actually undo them.\n\n## Anti-patterns\n\n- \"Canary\" that is one box for five minutes with no health gate (theater).\n- Flag with no kill switch or no removal plan (flags become permanent tech debt).\n- Rollback that requires a manual redeploy under incident pressure.\n",{"name":5,"description":7},"main","23f6e21841a39580c9da2b5ec941f39dda17cd86","plugins\u002Fpolymath-release\u002Fskills\u002Fsafe-rollout","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath","https:\u002F\u002Fgithub.com\u002FMohammadBafkar","2026-10-29 18:34:59",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add MohammadBafkar\u002Fpolymath --skill safe-rollout",{"tool":36,"command":37},"bunx","bunx skills add MohammadBafkar\u002Fpolymath --skill safe-rollout",{"tool":39,"command":40},"pnpm","pnpm dlx skills add MohammadBafkar\u002Fpolymath --skill safe-rollout","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-release\u002Fskills\u002Fsafe-rollout\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M74GN87EBRHM9N87M7AP1HDD","runbook","Write or refresh an operational runbook for an alert\u002Fsymptom; structured as TL;DR + Pre-checks + Steps + Verification + Rollback + Escalation.","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Frunbook\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M74GN5GPKEC1JEKP2DFQNEQJ","rfc","Draft a lightweight design RFC to docs\u002Frfcs\u002F\u003Cslug>.md; Summary, Motivation, Detailed design, Drawbacks, Alternatives, Unresolved questions. A proposal to debate, not a recorded decision (adr).","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Frfc\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M74GN2F4CWPMV4X09TG4E304","editorial-pass","Review and tighten prose in a Markdown artifact for a target tone (terse, formal, friendly) without dropping information; preserve quotations and load-bearing constraints.","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Feditorial-pass\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M74GMZWGYMZ37C4DYGT6P23G","architecture-review-facilitation","Run an architecture review as a process — entry criteria, reviewer checklist, decision log, and follow-up actions — pairing the design artifact with a red-team pass.","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Farchitecture-review-facilitation\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M74GMXVX0YX3ETDXS527XDGM","architecture-doc","Write a C4-style architecture document; System Context + Containers (+ Components when interesting) with mermaid diagrams. Describes structure, not a decision (adr) or proposal (rfc).","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Farchitecture-doc\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M74GMVG1WSMCK066S3KE6V5K","adr","Write an Architecture Decision Record (Michael Nygard format) to docs\u002Fadrs\u002FNNNN-\u003Cslug>.md; frontmatter validated by the ADR artifact schema. Records a made decision, not a proposal to debate (rfc).","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Fadr\u002FSKILL.md",[],[]]