[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74GHTRVBPPDENGADHAQ83CT":3,"skill-same:01M74GHTRVBPPDENGADHAQ83CT":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},"01M74GHTRVBPPDENGADHAQ83CT","multi-region-design",null,"Design multi-region deployment — active-active vs standby, RPO\u002FRTO, replication and conflicts, routing, failover. Not single-region HA.","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-scalability\u002Fskills\u002Fmulti-region-design\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: multi-region-design\ndescription: Design multi-region deployment — active-active vs standby, RPO\u002FRTO, replication and conflicts, routing, failover. Not single-region HA.\n---\n\n# multi-region-design\n\n> Going multi-region trades money, latency, and consistency for survivability and locality. Decide what failure you're buying protection from, then pick the cheapest topology that meets the RPO\u002FRTO — and rehearse the failover.\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 requirement for regional-outage survival, a stricter availability SLO than one region can give, or lower latency for global users.\n- Data residency \u002F sovereignty requires data to stay in specific regions.\n- Reviewing an existing \"multi-region\" setup that has never been failed over.\n\nNot this when: multi-AZ high availability within a region meets the target — `polymath-cloud:design-aws-pattern` \u002F `design-azure-pattern` \u002F `design-gcp-pattern`; or only DR backups are needed — define RPO\u002FRTO, then restore tests (`polymath-sre:chaos-experiment`).\n\n## Inputs\n\n- The driver: SLO (`polymath-sre:slo-design`), RTO\u002FRPO per data class, latency target by user region, residency rules, regulatory constraints, and the cost envelope.\n- Current architecture: stateless tiers, datastores and their replication features, queues\u002Fstreams, caches, DNS\u002FCDN, third-party dependencies and their regionality.\n- The consistency needs of each write: what must be globally unique, what can conflict and merge, what may be stale.\n- Historical regional incidents and the dependency map (control planes, identity, DNS, CI\u002FCD, secrets).\n\n## Procedure\n\n1. **Justify it with numbers.** Regional outages are rarer than software failures; compare the availability gain to cost and operational complexity. If single-region multi-AZ plus tested backups meets RTO\u002FRPO, stop. Record which failures the design must survive (AZ, region, provider-wide, control plane, bad deploy — multi-region doesn't fix a bad deploy that replicates everywhere).\n2. **Set RPO\u002FRTO per data class** (not per system): money movement RPO≈0 (synchronous or no loss), catalog data minutes, analytics hours. RPO ≈ replication lag at failure; RTO = detection + decision + failover + warm-up.\n3. **Choose the topology per tier:**\n   - **Backup & restore** (RTO hours, RPO hours; cheapest).\n   - **Pilot light \u002F warm standby** (RTO minutes–tens of minutes; data replicated, compute scaled down or minimal; scale on failover).\n   - **Active-passive hot standby** (RTO minutes; full capacity idle; failover automated or one-button).\n   - **Active-active** (RTO≈0 for the surviving regions; both serve traffic). Requires conflict-free data design and traffic partitioning; highest cost and complexity — justify against warm standby.\n4. **Design data replication per store** — the hard part:\n   - **Single-writer + async replicas**: simple; RPO = lag > 0; promotion needed; cross-region writes pay latency to the leader (or route writes to home region).\n   - **Synchronous cross-region commit** (Spanner, CockroachDB, Aurora global with managed switchover): near-zero RPO, but every commit pays inter-region RTT (tens–hundreds of ms); watch quorum availability if a region is lost.\n   - **Multi-writer \u002F active-active** (DynamoDB global tables, Cosmos DB multi-region writes, Cassandra multi-DC): conflicts happen — define resolution (last-writer-wins by timestamp loses data; per-field merge, CRDTs, or home-region-per-entity avoid it) and which operations can never be multi-writer (balances, inventory, uniqueness).\n   - **Partition by home region** (each user\u002Ftenant has one home region for writes; others read replicas or route): avoids conflicts, satisfies residency, makes failover a per-partition decision.\n   - **Events\u002Fstreams**: mirror topics (MirrorMaker 2, Cluster Linking, Event Hubs geo-replication) with consumer-offset translation; plan for duplicates and reordering across the failover boundary (idempotent consumers).\n   - **Caches** are rebuilt or regionally local; never the replicated source of truth. **Object storage** uses cross-region replication; note its RPO is not zero.\n5. **Traffic routing.** Global DNS (health-checked, low TTL — remember resolvers and clients that ignore TTL), anycast\u002Fglobal load balancer, or CDN origin failover. Define the health check (a *deep* check on dependencies, but not so deep that a minor dependency failure flaps the region), automatic vs human-approved failover (automatic failover of a database can cause split-brain\u002Fdata loss — require a fencing mechanism), and capacity: can the survivor absorb 100% of traffic (N+1 at region level, often ≥ 50–100% headroom, or planned load shedding)?\n6. **Eliminate hidden single-region dependencies**: identity provider, secrets, config, feature flags, CI\u002FCD to deploy the fix, DNS provider, observability, payment\u002FSMS providers, container registries, and any \"global\" service that's actually homed in one region. Draw the dependency map and mark each regional\u002Fglobal\u002Funknown.\n7. **Failover and failback runbook.** Detection → decision criteria and who decides → steps (promote DB, shift traffic, scale up, drain queues) → verification → communication (`polymath-chat:post-statuspage-update`) → failback (re-seed old primary, reverse replication, catch up, switch traffic back in a window). Failback is a second migration — design it, don't assume it.\n8. **Rehearse.** Game days with real traffic shift (`polymath-sre:chaos-experiment`); measure actual RTO and data loss, not designed values; test split-brain fencing and the \"region comes back with stale data\" case. A failover never exercised will not work.\n9. **Residency and compliance.** Map data classes to allowed regions; keep PII home-region-only where required; check that logs, backups, analytics copies, and support tooling don't export it; encryption keys per region.\n10. **Cost and operations.** Duplicate compute, cross-region data transfer, replicated storage, double observability; the added deploy\u002Fconfig\u002Fmigration complexity (schema changes across regions, versions skew during rollout); on-call load. State the incremental cost and compare to the cost of the outage it prevents.\n\n## Output\n\n```text\nMulti-region design: payments API\n\nDriver: SLO 99.99% (regional outage budget: ~4 min\u002Fmonth); RTO 15 min \u002F RPO 0 for ledger, 5 min for the rest; EU data stays in EU.\nFailures covered: region outage, AZ loss. Not covered: bad deploy (canary + rollback — safe-rollout), provider-wide outage.\n\nTopology: active-active for reads\u002FAPI, single-writer per home region for the ledger.\n  Stateless: us-east + eu-west, each sized for 100% of its own traffic + 60% of the other's [VERIFY: load test].\n  Ledger: Postgres per region (home-region partitioning by customer.region); sync replica in a second AZ; async cross-region replica for DR (RPO ≈ lag, p99 2 s) → RPO 0 not met cross-region [TBD: decision — accept ~2 s RPO, or use a synchronous-commit engine and pay the commit latency].\n  Catalog\u002Fprefs: DynamoDB global tables (LWW acceptable; per-field merge for preferences).\n  Events: Kafka per region, MirrorMaker 2 mirroring; consumers idempotent; offsets translated on failover.\n  Cache: regional, rebuilt on failover.\nRouting: global LB with deep health check (DB + queue) hysteresis 3\u002F5; DNS TTL 30 s as fallback; automatic failover for stateless, human-approved promote for ledger with fencing (old primary demoted by revoking its storage credentials).\nHidden dependencies: IdP (global, multi-region), secrets (replicated), feature flags (cached last-known-good), CI\u002FCD (runs from eu-west), SMS provider (single region → fallback provider).\nFailover runbook: detect (3 min) → decide (5 min) → promote + shift (5 min) → verify (2 min) = 15 min target; failback in a planned window after re-seed.\nRehearsal: quarterly game day; last result [TBD]. Residency: EU PII only in eu-west stores; logs scrubbed; per-region KMS keys.\nCost: +[TBD: infra delta] (compute ×1.6, inter-region transfer, double observability) vs outage cost [TBD].\nOpen: [VERIFY: provider rate limits per region], [TBD: ledger RPO decision with finance].\n```\n\n## Quality bar\n\n- The need is justified against cheaper options, and the covered failure types are listed (and the uncovered ones).\n- RPO\u002FRTO are per data class, and each store's replication model states its real RPO and conflict behavior.\n- Hidden single-region dependencies are mapped; survivor capacity is stated.\n- Failover has fencing\u002Fsplit-brain handling, a failback plan, and a rehearsal record or schedule.\n- Residency and cost are explicit.\n\n## Anti-patterns to avoid\n\n- Active-active by default, without a conflict-resolution design — silent data loss with last-writer-wins on money or inventory.\n- A \"DR region\" that was never failed over, or whose capacity is a fraction of production.\n- Automatic database failover without fencing; relying on DNS TTL alone for failover timing.\n- Shipping multi-region while identity, secrets, CI\u002FCD, or DNS live in one region.\n- Treating multi-region as a substitute for safe deploys.\n- Ignoring cross-region latency: synchronous calls between regions in the request path.\n","# multi-region-design\n\n> Going multi-region trades money, latency, and consistency for survivability and locality. Decide what failure you're buying protection from, then pick the cheapest topology that meets the RPO\u002FRTO — and rehearse the failover.\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 requirement for regional-outage survival, a stricter availability SLO than one region can give, or lower latency for global users.\n- Data residency \u002F sovereignty requires data to stay in specific regions.\n- Reviewing an existing \"multi-region\" setup that has never been failed over.\n\nNot this when: multi-AZ high availability within a region meets the target — `polymath-cloud:design-aws-pattern` \u002F `design-azure-pattern` \u002F `design-gcp-pattern`; or only DR backups are needed — define RPO\u002FRTO, then restore tests (`polymath-sre:chaos-experiment`).\n\n## Inputs\n\n- The driver: SLO (`polymath-sre:slo-design`), RTO\u002FRPO per data class, latency target by user region, residency rules, regulatory constraints, and the cost envelope.\n- Current architecture: stateless tiers, datastores and their replication features, queues\u002Fstreams, caches, DNS\u002FCDN, third-party dependencies and their regionality.\n- The consistency needs of each write: what must be globally unique, what can conflict and merge, what may be stale.\n- Historical regional incidents and the dependency map (control planes, identity, DNS, CI\u002FCD, secrets).\n\n## Procedure\n\n1. **Justify it with numbers.** Regional outages are rarer than software failures; compare the availability gain to cost and operational complexity. If single-region multi-AZ plus tested backups meets RTO\u002FRPO, stop. Record which failures the design must survive (AZ, region, provider-wide, control plane, bad deploy — multi-region doesn't fix a bad deploy that replicates everywhere).\n2. **Set RPO\u002FRTO per data class** (not per system): money movement RPO≈0 (synchronous or no loss), catalog data minutes, analytics hours. RPO ≈ replication lag at failure; RTO = detection + decision + failover + warm-up.\n3. **Choose the topology per tier:**\n   - **Backup & restore** (RTO hours, RPO hours; cheapest).\n   - **Pilot light \u002F warm standby** (RTO minutes–tens of minutes; data replicated, compute scaled down or minimal; scale on failover).\n   - **Active-passive hot standby** (RTO minutes; full capacity idle; failover automated or one-button).\n   - **Active-active** (RTO≈0 for the surviving regions; both serve traffic). Requires conflict-free data design and traffic partitioning; highest cost and complexity — justify against warm standby.\n4. **Design data replication per store** — the hard part:\n   - **Single-writer + async replicas**: simple; RPO = lag > 0; promotion needed; cross-region writes pay latency to the leader (or route writes to home region).\n   - **Synchronous cross-region commit** (Spanner, CockroachDB, Aurora global with managed switchover): near-zero RPO, but every commit pays inter-region RTT (tens–hundreds of ms); watch quorum availability if a region is lost.\n   - **Multi-writer \u002F active-active** (DynamoDB global tables, Cosmos DB multi-region writes, Cassandra multi-DC): conflicts happen — define resolution (last-writer-wins by timestamp loses data; per-field merge, CRDTs, or home-region-per-entity avoid it) and which operations can never be multi-writer (balances, inventory, uniqueness).\n   - **Partition by home region** (each user\u002Ftenant has one home region for writes; others read replicas or route): avoids conflicts, satisfies residency, makes failover a per-partition decision.\n   - **Events\u002Fstreams**: mirror topics (MirrorMaker 2, Cluster Linking, Event Hubs geo-replication) with consumer-offset translation; plan for duplicates and reordering across the failover boundary (idempotent consumers).\n   - **Caches** are rebuilt or regionally local; never the replicated source of truth. **Object storage** uses cross-region replication; note its RPO is not zero.\n5. **Traffic routing.** Global DNS (health-checked, low TTL — remember resolvers and clients that ignore TTL), anycast\u002Fglobal load balancer, or CDN origin failover. Define the health check (a *deep* check on dependencies, but not so deep that a minor dependency failure flaps the region), automatic vs human-approved failover (automatic failover of a database can cause split-brain\u002Fdata loss — require a fencing mechanism), and capacity: can the survivor absorb 100% of traffic (N+1 at region level, often ≥ 50–100% headroom, or planned load shedding)?\n6. **Eliminate hidden single-region dependencies**: identity provider, secrets, config, feature flags, CI\u002FCD to deploy the fix, DNS provider, observability, payment\u002FSMS providers, container registries, and any \"global\" service that's actually homed in one region. Draw the dependency map and mark each regional\u002Fglobal\u002Funknown.\n7. **Failover and failback runbook.** Detection → decision criteria and who decides → steps (promote DB, shift traffic, scale up, drain queues) → verification → communication (`polymath-chat:post-statuspage-update`) → failback (re-seed old primary, reverse replication, catch up, switch traffic back in a window). Failback is a second migration — design it, don't assume it.\n8. **Rehearse.** Game days with real traffic shift (`polymath-sre:chaos-experiment`); measure actual RTO and data loss, not designed values; test split-brain fencing and the \"region comes back with stale data\" case. A failover never exercised will not work.\n9. **Residency and compliance.** Map data classes to allowed regions; keep PII home-region-only where required; check that logs, backups, analytics copies, and support tooling don't export it; encryption keys per region.\n10. **Cost and operations.** Duplicate compute, cross-region data transfer, replicated storage, double observability; the added deploy\u002Fconfig\u002Fmigration complexity (schema changes across regions, versions skew during rollout); on-call load. State the incremental cost and compare to the cost of the outage it prevents.\n\n## Output\n\n```text\nMulti-region design: payments API\n\nDriver: SLO 99.99% (regional outage budget: ~4 min\u002Fmonth); RTO 15 min \u002F RPO 0 for ledger, 5 min for the rest; EU data stays in EU.\nFailures covered: region outage, AZ loss. Not covered: bad deploy (canary + rollback — safe-rollout), provider-wide outage.\n\nTopology: active-active for reads\u002FAPI, single-writer per home region for the ledger.\n  Stateless: us-east + eu-west, each sized for 100% of its own traffic + 60% of the other's [VERIFY: load test].\n  Ledger: Postgres per region (home-region partitioning by customer.region); sync replica in a second AZ; async cross-region replica for DR (RPO ≈ lag, p99 2 s) → RPO 0 not met cross-region [TBD: decision — accept ~2 s RPO, or use a synchronous-commit engine and pay the commit latency].\n  Catalog\u002Fprefs: DynamoDB global tables (LWW acceptable; per-field merge for preferences).\n  Events: Kafka per region, MirrorMaker 2 mirroring; consumers idempotent; offsets translated on failover.\n  Cache: regional, rebuilt on failover.\nRouting: global LB with deep health check (DB + queue) hysteresis 3\u002F5; DNS TTL 30 s as fallback; automatic failover for stateless, human-approved promote for ledger with fencing (old primary demoted by revoking its storage credentials).\nHidden dependencies: IdP (global, multi-region), secrets (replicated), feature flags (cached last-known-good), CI\u002FCD (runs from eu-west), SMS provider (single region → fallback provider).\nFailover runbook: detect (3 min) → decide (5 min) → promote + shift (5 min) → verify (2 min) = 15 min target; failback in a planned window after re-seed.\nRehearsal: quarterly game day; last result [TBD]. Residency: EU PII only in eu-west stores; logs scrubbed; per-region KMS keys.\nCost: +[TBD: infra delta] (compute ×1.6, inter-region transfer, double observability) vs outage cost [TBD].\nOpen: [VERIFY: provider rate limits per region], [TBD: ledger RPO decision with finance].\n```\n\n## Quality bar\n\n- The need is justified against cheaper options, and the covered failure types are listed (and the uncovered ones).\n- RPO\u002FRTO are per data class, and each store's replication model states its real RPO and conflict behavior.\n- Hidden single-region dependencies are mapped; survivor capacity is stated.\n- Failover has fencing\u002Fsplit-brain handling, a failback plan, and a rehearsal record or schedule.\n- Residency and cost are explicit.\n\n## Anti-patterns to avoid\n\n- Active-active by default, without a conflict-resolution design — silent data loss with last-writer-wins on money or inventory.\n- A \"DR region\" that was never failed over, or whose capacity is a fraction of production.\n- Automatic database failover without fencing; relying on DNS TTL alone for failover timing.\n- Shipping multi-region while identity, secrets, CI\u002FCD, or DNS live in one region.\n- Treating multi-region as a substitute for safe deploys.\n- Ignoring cross-region latency: synchronous calls between regions in the request path.\n",{"name":5,"description":7},"main","23f6e21841a39580c9da2b5ec941f39dda17cd86","plugins\u002Fpolymath-scalability\u002Fskills\u002Fmulti-region-design","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 multi-region-design",{"tool":36,"command":37},"bunx","bunx skills add MohammadBafkar\u002Fpolymath --skill multi-region-design",{"tool":39,"command":40},"pnpm","pnpm dlx skills add MohammadBafkar\u002Fpolymath --skill multi-region-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-scalability\u002Fskills\u002Fmulti-region-design\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",[],[]]