[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74GC4ENMHZNK2RFV4RA9CMR":3,"skill-same:01M74GC4ENMHZNK2RFV4RA9CMR":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},"01M74GC4ENMHZNK2RFV4RA9CMR","comms-update",null,"Draft an incident communication update — plain language, status (investigating\u002Fidentified\u002Fmonitoring\u002Fresolved), impact, next-update ETA.","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-incident\u002Fskills\u002Fcomms-update\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: comms-update\ndescription: Draft an incident communication update — plain language, status (investigating\u002Fidentified\u002Fmonitoring\u002Fresolved), impact, next-update ETA.\n---\n\n# comms-update\n\n> Draft one comms update (status page \u002F customer email \u002F internal stakeholder note). Output is the update, ready for the comms lead to approve — this skill drafts; posting is a separate, approved step (`polymath-chat:post-incident-comms`, `polymath-chat:post-statuspage-update`).\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 sev1\u002Fsev2 needs an external update.\n- Stakeholders need an internal update during a long incident.\n- A workflow's comms step generates a draft (e.g. `respondToIncident` paired with `polymath-chat:post-incident-comms`).\n\n## Inputs\n\n- The incident's current facts (required): what users see, start time, scope, mitigation status — from the incident channel or the IC. Anything unconfirmed is left out or stated as unknown, never guessed.\n- Audience (required): external (status page, customers) or internal stakeholders.\n- The previous update (optional) — the new one says what changed since.\n- Drafting is not posting: publishing goes through `polymath-chat` skills, which confirm before sending.\n\n## Procedure\n\n1. **Status** — pick one from a fixed scale:\n   - **investigating** — we know there's a problem; we don't know the cause.\n   - **identified** — we know the cause; mitigation in progress.\n   - **monitoring** — we believe we've mitigated; watching to confirm.\n   - **resolved** — service is healthy; postmortem to follow.\n2. **Audience** — externals (status page, customer email) get different language than internal stakeholders. Pick once.\n3. **Plain language** — what users see and can\u002Fcan't do. Not \"ELB target group degraded\".\n4. **Workarounds** — if any, name them simply.\n5. **Next-update ETA** — always specify. \"Next update in 30 minutes\" beats silence.\n6. **What we know \u002F don't know** — both sections present. Don't speculate.\n\n## Output\n\n```text\nUpdate #3 — Refund processing degraded\n\nStatus: identified\n\nWhat's happening:\n  Customers attempting to issue a refund are seeing errors. New refunds\n  are being queued internally and will process once we restore service.\n  Existing orders, account access, and other operations are unaffected.\n\nImpact:\n  - All customers attempting refunds since 14:02 UTC.\n  - Refunds queued during this window are expected to process after\n    recovery; we will confirm once the queue has drained.\n\nWhat we're doing:\n  Rolled back the recent refund-service deploy. Metrics improving; we\n  are watching to confirm recovery.\n\nWhat we know:\n  A bad deploy of refund-service introduced a regression in the\n  payment-provider integration. The rollback restores prior behavior.\n\nWhat we don't know yet:\n  Whether the queued refunds will all process within the next 15\n  minutes (estimated based on queue depth).\n\nNext update in 15 minutes, at 14:35 UTC.\n```\n\n## Quality bar\n\n- One of the four fixed status values.\n- Next-update ETA stated.\n- \"What we don't know yet\" present and honest.\n- No internal-jargon component names.\n- No \"due to a database issue\" — that's the cause, not the impact.\n\n## Anti-patterns to avoid\n\n- \"We are aware of an issue\" without saying what's broken.\n- Silence between updates.\n- Speculation about root cause in the comms update.\n- Promising a fix ETA you can't keep.\n","# comms-update\n\n> Draft one comms update (status page \u002F customer email \u002F internal stakeholder note). Output is the update, ready for the comms lead to approve — this skill drafts; posting is a separate, approved step (`polymath-chat:post-incident-comms`, `polymath-chat:post-statuspage-update`).\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 sev1\u002Fsev2 needs an external update.\n- Stakeholders need an internal update during a long incident.\n- A workflow's comms step generates a draft (e.g. `respondToIncident` paired with `polymath-chat:post-incident-comms`).\n\n## Inputs\n\n- The incident's current facts (required): what users see, start time, scope, mitigation status — from the incident channel or the IC. Anything unconfirmed is left out or stated as unknown, never guessed.\n- Audience (required): external (status page, customers) or internal stakeholders.\n- The previous update (optional) — the new one says what changed since.\n- Drafting is not posting: publishing goes through `polymath-chat` skills, which confirm before sending.\n\n## Procedure\n\n1. **Status** — pick one from a fixed scale:\n   - **investigating** — we know there's a problem; we don't know the cause.\n   - **identified** — we know the cause; mitigation in progress.\n   - **monitoring** — we believe we've mitigated; watching to confirm.\n   - **resolved** — service is healthy; postmortem to follow.\n2. **Audience** — externals (status page, customer email) get different language than internal stakeholders. Pick once.\n3. **Plain language** — what users see and can\u002Fcan't do. Not \"ELB target group degraded\".\n4. **Workarounds** — if any, name them simply.\n5. **Next-update ETA** — always specify. \"Next update in 30 minutes\" beats silence.\n6. **What we know \u002F don't know** — both sections present. Don't speculate.\n\n## Output\n\n```text\nUpdate #3 — Refund processing degraded\n\nStatus: identified\n\nWhat's happening:\n  Customers attempting to issue a refund are seeing errors. New refunds\n  are being queued internally and will process once we restore service.\n  Existing orders, account access, and other operations are unaffected.\n\nImpact:\n  - All customers attempting refunds since 14:02 UTC.\n  - Refunds queued during this window are expected to process after\n    recovery; we will confirm once the queue has drained.\n\nWhat we're doing:\n  Rolled back the recent refund-service deploy. Metrics improving; we\n  are watching to confirm recovery.\n\nWhat we know:\n  A bad deploy of refund-service introduced a regression in the\n  payment-provider integration. The rollback restores prior behavior.\n\nWhat we don't know yet:\n  Whether the queued refunds will all process within the next 15\n  minutes (estimated based on queue depth).\n\nNext update in 15 minutes, at 14:35 UTC.\n```\n\n## Quality bar\n\n- One of the four fixed status values.\n- Next-update ETA stated.\n- \"What we don't know yet\" present and honest.\n- No internal-jargon component names.\n- No \"due to a database issue\" — that's the cause, not the impact.\n\n## Anti-patterns to avoid\n\n- \"We are aware of an issue\" without saying what's broken.\n- Silence between updates.\n- Speculation about root cause in the comms update.\n- Promising a fix ETA you can't keep.\n",{"name":5,"description":7},"main","23f6e21841a39580c9da2b5ec941f39dda17cd86","plugins\u002Fpolymath-incident\u002Fskills\u002Fcomms-update","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 comms-update",{"tool":36,"command":37},"bunx","bunx skills add MohammadBafkar\u002Fpolymath --skill comms-update",{"tool":39,"command":40},"pnpm","pnpm dlx skills add MohammadBafkar\u002Fpolymath --skill comms-update","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-incident\u002Fskills\u002Fcomms-update\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",[],[]]