[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79TRWDN0NS53SS9DPFCH2SD":3,"skill-same:01M79TRWDN0NS53SS9DPFCH2SD":53},{"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":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M79TRWDN0NS53SS9DPFCH2SD","release-strategy-architect",null,"Architect-level release practice — small-batch delivery, feature flag and canary strategy, expand\u002Fcontract database changes, rollback versus roll-forward decisions, and the versioning and communication that keep releases boring. Use when deciding how code reaches users.","SriAkhilSJ\u002FPulseAIRepo","SriAkhilSJ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206201543?v=4","01M79RWFD1Q09B89SXTTKKJY6Z","Sri Akhil SJ","01M79RWFE26NPG0BZ1FRNX376H",0,"MIT","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ftesting-and-deployment-architect\u002Frelease-strategy-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: release-strategy-architect\ndescription: Architect-level release practice — small-batch delivery, feature flag and canary strategy, expand\u002Fcontract database changes, rollback versus roll-forward decisions, and the versioning and communication that keep releases boring. Use when deciding how code reaches users.\nlicense: MIT\ncompatibility: Any stack; feature flag service optional\nmetadata:\n  crusor-domain: website-architect\n  crusor-path: website-architect\u002Ftesting-and-deployment-architect\u002Frelease-strategy-architect\n  crusor-origin: original\n  crusor-sources: \"12factor.net; martinfowler.com\u002Farticles\u002Ffeature-toggles.html; sre.google\u002Fworkbook\u002Fcanarying-releases\"\n  crusor-triggers: \"release strategy, feature flags, canary, blue green, rollback, rollout, deployment frequency, versioning\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# Release Strategy Architect\n\nA release is **a reversible step**, not an event. If it cannot be undone in one\naction, it is not a release — it is a gamble.\n\n## When to use\n\n- Planning how changes reach users, or deploys feel risky.\n- Adding flags, canaries, or multi-environment rollout.\n- A rollback is impossible because a migration already ran.\n\n## When NOT to use\n\n- Choosing the pipeline stages themselves (see `ci-cd-architect`).\n\n## Decision 1 — Small batches\n\n- Deploy often and small; batch size is the strongest predictor of incident\n  duration.\n- Separate **deploy** (code present, switched off) from **release** (users\n  affected).\n- A change that needs a maintenance window is a design that skipped this rule.\n\n## Decision 2 — Flags\n\n| Flag type | Lifetime | Owner |\n|---|---|---|\n| release flag | days | the team shipping |\n| experiment flag | weeks | product |\n| ops\u002Fkill switch | permanent | on-call |\n| permission flag | permanent | entitlements (not a flag) |\n\n- Every flag has an owner and a removal date; stale flags are debt with a blast\n  radius.\n- Flag evaluation must be fast and fail-safe: on error, serve the last known\n  good state.\n- Never use flags to choose a database schema shape you cannot migrate.\n\n## Decision 3 — Rollout mechanics\n\n| Strategy | Use when |\n|---|---|\n| all-at-once | low risk, easy rollback, non-critical internal services |\n| canary (1% → 10% → 50% → 100%) | user-facing changes with metrics to judge |\n| blue\u002Fgreen | need instant cutover and instant revert |\n| ring\u002Fcohort | enterprise customers and staged exposure |\n\n- Canary needs a judge: error rate, latency, business metric — defined before\n  rollout, not eyeballed.\n- Automated abort on SLO burn; a human watching a graph is not a control.\n\n## Decision 4 — Data is the hard part\n\n- Schema changes are expand\u002Fcontract: add compatible structure, dual-write,\n  backfill, switch reads, remove old — across releases.\n- Never drop or rename a column in the same release that stops using it.\n- Backfills are batched, idempotent, resumable, and monitored.\n- \"Rollback\" of a data migration is a forward migration, not a restore from\n  backup — plan it.\n\n## Decision 5 — Rollback vs roll-forward\n\n- Decide the trigger in advance: error rate above X for Y minutes → revert.\n- Rollback must not depend on a schema reversal; that is why data changes ship\n  separately.\n- Roll-forward is acceptable when the fix is small and known; document which\n  path you chose and why.\n- Post-release verification: smoke journey plus the metric that justified the\n  release.\n\n## Decision 6 — Communication\n\n- Version numbers or changelogs for anything external; internal services use\n  commit-based deployment records.\n- Release notes name user-visible changes, not commits.\n- Announce risky releases in the team channel with the rollback command in the\n  message.\n\n## Failure modes at scale\n\n- One deploy containing 40 changes, one of which breaks the site — bisecting in\n  production.\n- 300 permanently-on flags; nobody knows which code is live.\n- A migration dropped a column, and rollback means restoring a backup.\n- Canary deployed to 1% but the metric chosen cannot detect the bug.\n- Friday deploy with the one person who knows the rollback on holiday.\n\n## Verification receipts\n\n1. Deployment frequency and change failure rate over the last quarter.\n2. Flag inventory with owner and expiry; count of flags older than 90 days.\n3. Canary run with an automated abort demonstrated.\n4. Migration plan for a live table (expand\u002Fcontract, separately deployable).\n5. Rollback drill executed and timed.\n","# Release Strategy Architect\n\nA release is **a reversible step**, not an event. If it cannot be undone in one\naction, it is not a release — it is a gamble.\n\n## When to use\n\n- Planning how changes reach users, or deploys feel risky.\n- Adding flags, canaries, or multi-environment rollout.\n- A rollback is impossible because a migration already ran.\n\n## When NOT to use\n\n- Choosing the pipeline stages themselves (see `ci-cd-architect`).\n\n## Decision 1 — Small batches\n\n- Deploy often and small; batch size is the strongest predictor of incident\n  duration.\n- Separate **deploy** (code present, switched off) from **release** (users\n  affected).\n- A change that needs a maintenance window is a design that skipped this rule.\n\n## Decision 2 — Flags\n\n| Flag type | Lifetime | Owner |\n|---|---|---|\n| release flag | days | the team shipping |\n| experiment flag | weeks | product |\n| ops\u002Fkill switch | permanent | on-call |\n| permission flag | permanent | entitlements (not a flag) |\n\n- Every flag has an owner and a removal date; stale flags are debt with a blast\n  radius.\n- Flag evaluation must be fast and fail-safe: on error, serve the last known\n  good state.\n- Never use flags to choose a database schema shape you cannot migrate.\n\n## Decision 3 — Rollout mechanics\n\n| Strategy | Use when |\n|---|---|\n| all-at-once | low risk, easy rollback, non-critical internal services |\n| canary (1% → 10% → 50% → 100%) | user-facing changes with metrics to judge |\n| blue\u002Fgreen | need instant cutover and instant revert |\n| ring\u002Fcohort | enterprise customers and staged exposure |\n\n- Canary needs a judge: error rate, latency, business metric — defined before\n  rollout, not eyeballed.\n- Automated abort on SLO burn; a human watching a graph is not a control.\n\n## Decision 4 — Data is the hard part\n\n- Schema changes are expand\u002Fcontract: add compatible structure, dual-write,\n  backfill, switch reads, remove old — across releases.\n- Never drop or rename a column in the same release that stops using it.\n- Backfills are batched, idempotent, resumable, and monitored.\n- \"Rollback\" of a data migration is a forward migration, not a restore from\n  backup — plan it.\n\n## Decision 5 — Rollback vs roll-forward\n\n- Decide the trigger in advance: error rate above X for Y minutes → revert.\n- Rollback must not depend on a schema reversal; that is why data changes ship\n  separately.\n- Roll-forward is acceptable when the fix is small and known; document which\n  path you chose and why.\n- Post-release verification: smoke journey plus the metric that justified the\n  release.\n\n## Decision 6 — Communication\n\n- Version numbers or changelogs for anything external; internal services use\n  commit-based deployment records.\n- Release notes name user-visible changes, not commits.\n- Announce risky releases in the team channel with the rollback command in the\n  message.\n\n## Failure modes at scale\n\n- One deploy containing 40 changes, one of which breaks the site — bisecting in\n  production.\n- 300 permanently-on flags; nobody knows which code is live.\n- A migration dropped a column, and rollback means restoring a backup.\n- Canary deployed to 1% but the metric chosen cannot detect the bug.\n- Friday deploy with the one person who knows the rollback on holiday.\n\n## Verification receipts\n\n1. Deployment frequency and change failure rate over the last quarter.\n2. Flag inventory with owner and expiry; count of flags older than 90 days.\n3. Canary run with an automated abort demonstrated.\n4. Migration plan for a live table (expand\u002Fcontract, separately deployable).\n5. Rollback drill executed and timed.\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":31},{"crusor-path":25,"crusor-domain":26,"crusor-origin":27,"crusor-sources":28,"crusor-triggers":29,"crusor-verified-on":30},"website-architect\u002Ftesting-and-deployment-architect\u002Frelease-strategy-architect","website-architect","original","12factor.net; martinfowler.com\u002Farticles\u002Ffeature-toggles.html; sre.google\u002Fworkbook\u002Fcanarying-releases","release strategy, feature flags, canary, blue green, rollback, rollout, deployment frequency, versioning","2026-10-30","Any stack; feature flag service optional","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fwebsite-architect\u002Ftesting-and-deployment-architect\u002Frelease-strategy-architect","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ","Studying in CMR institute of Technology\r\n2024 - 2028","2026-11-13 21:02:23",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add SriAkhilSJ\u002FPulseAIRepo --skill release-strategy-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill release-strategy-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill release-strategy-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ftesting-and-deployment-architect\u002Frelease-strategy-architect\u002FSKILL.md",true,[],[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M79TTAJNACCNXCEN3649CMMD","interaction-patterns-architect","Architect-level interaction design in code — choosing established patterns over invented ones, feedback and latency behaviour, destructive-action safeguards, navigation and overlay conventions, and the state model behind every interactive surface. Use when a screen has to behave, not just look.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Finteraction-patterns-architect\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M79TT2ESKB1TKZBYY9KYJHV9","design-system-ops-architect","Architect-level operation of a design system in code — token pipelines and versioning, component API and variant policy, the catalogue as the contract, adoption metrics, and the governance that stops a system from forking into three. Use when a component library must survive several teams.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-system-ops-architect\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79TSV0PWGNK3PRX9P4JDR9N","design-handoff-architect","Architect-level design handoff — what must be specified before implementation starts, tokens over raw values, responsive and content-limit contracts, state matrices, and the review loop that catches drift between design and code. Use when a design is about to become code.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-handoff-architect\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79TSJS9BFXNP696FMJ9GKDA","content-microcopy-architect","Architect-level UI content — where strings live, voice and terminology consistency, error and empty-state copy as part of the interface, translation-ready authoring, and the content model a product needs before it multiplies screens. Use when the words in the interface matter as much as the pixels.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fcontent-microcopy-architect\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79TSCNBST3N1M68V1KPH9HQ","ui-ux-implementation-architect","Architect-level direction for turning a design into working UI — the handoff contract, component ownership versus screen-level layout, interaction and state conventions, design QA gates, and the review habits that keep an implementation faithful without frozen pixels. Use before any specific UI implementation skill.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79TS4N6A4D2QQ433VXS5D0R","test-strategy-architect","Architect-level test strategy — allocating assertions across unit, integration, contract and end-to-end layers, designing for testability through dependency boundaries, fixture and data strategy, and the flake and coverage policies that keep a suite trustworthy. Use when defining how a codebase is tested.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ftesting-and-deployment-architect\u002Ftest-strategy-architect\u002FSKILL.md",[],[]]