[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74G8CAM1M3NGQ7DFXM1SXQ1":3,"skill-same:01M74G8CAM1M3NGQ7DFXM1SXQ1":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},"01M74G8CAM1M3NGQ7DFXM1SXQ1","write-release-notes",null,"Author customer-facing release notes — headline, user-benefit framing, breaking changes called out, no internal-jargon component names.","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-communication\u002Fskills\u002Fwrite-release-notes\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: write-release-notes\ndescription: Author customer-facing release notes — headline, user-benefit framing, breaking changes called out, no internal-jargon component names.\n---\n\n# write-release-notes\n\n> Customer-facing release notes. Different from CHANGELOG: the audience is users, not engineers. Tone is announcement + benefit, not changelog rollup.\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 release is being prepared and you want notes the customer-facing site \u002F email blast can use.\n- The internal CHANGELOG exists; this skill repackages it for users.\n\n## Related skills\n\n- [`polymath-release:release-notes`](..\u002F..\u002F..\u002Fpolymath-release\u002Fskills\u002Frelease-notes\u002FSKILL.md)\n  — engineer-facing release notes drafted directly from\n  `CHANGELOG.md` `[Unreleased]`. Run that first for the version-bump\n  notes; this skill repackages them for customers (announcement +\n  benefit framing, no internal-jargon component names).\n- [`polymath-release:changelog`](..\u002F..\u002F..\u002Fpolymath-release\u002Fskills\u002Fchangelog\u002FSKILL.md)\n  — append the canonical `[Unreleased]` entry that both this skill\n  and `polymath-release:release-notes` consume.\n\n## Inputs\n\n- The version being released + date.\n- The CHANGELOG entries since the last release (or `git log --oneline`).\n- Optional: any customer-reported issues that this release fixes (call out individually).\n\n## Procedure\n\n1. **Headline**: one sentence on the most important change. Lead with the benefit, not the mechanism.\n2. **What's new**: each `Added` from the CHANGELOG, restated in customer language. Skip internal-only changes.\n3. **Notable changes**: `Changed`, `Fixed`, `Security`, `Deprecated`, `Removed` that customers will notice.\n4. **Breaking changes**: own section. Migration path required for each. If anyone has to change anything in their code or workflow, this section is mandatory.\n5. **Known issues**: shipping ≠ no-bugs. Be honest about what's pending.\n6. **Security fixes**: credit the reporter when they consented; cite the advisory ID.\n7. **Claims trace to sources.** A speedup, a fixed bug, or a number must come from the CHANGELOG, a PR, or a measurement — every figure traces to the source material; a missing one is written `[TBD: \u003Cwhat>]` and listed in the summary.\n\n## Style\n\n- Active voice (\"We added X\" or \"X now does Y\").\n- User benefit, not implementation (\"Faster check-outs\" beats \"Optimized the cart query\").\n- No internal component names (\"the checkout API\" not \"v2-cart-svc\").\n- No emojis.\n\n## Output\n\n```text\nRelease notes — Polymath v1.4.0 (2026-05-24)\n\nHeadline:\n  Refunds now complete in under a second — a 4× speedup for high-volume merchants.\n\nWhat's new\n  - Refund creation is now sub-second at P95 across all regions.\n  - You can now view refund status in the timeline view of an order.\n\nNotable changes\n  - Idempotency-Key is now required on refund creation (previously optional).\n    See the migration note below.\n\nBreaking changes\n  - `POST \u002Fv1\u002Frefunds` now requires an `Idempotency-Key` header on every\n    request. Calls without it return 400.\n    Migration: include a UUID `Idempotency-Key` per refund attempt.\n\nSecurity fixes\n  - SEC-2026-0042 (Medium): IDOR on \u002Fv1\u002Forders\u002F{id}\u002Frefunds — fixed in 1.4.0.\n    Reported by \u003Cname>. See advisory link.\n\nKnown issues\n  - The new timeline view doesn't yet render correctly on Safari 15. Tracked in #1234.\n```\n\n## Quality bar\n\n- Headline names benefit, not mechanism.\n- Breaking changes have a Migration line each.\n- Internal jargon scrubbed; if the customer wouldn't recognize a component name, replace it.\n- Active voice.\n- Security fixes credit reporters who consented.\n\n## Anti-patterns to avoid\n\n- Pasting the CHANGELOG without rewriting for customer audience.\n- \"Performance improvements\" without a number.\n- Burying breaking changes in the middle of \"Notable changes\".\n- Marketing puffery (\"We're excited to announce …\"). Just say what changed.\n","# write-release-notes\n\n> Customer-facing release notes. Different from CHANGELOG: the audience is users, not engineers. Tone is announcement + benefit, not changelog rollup.\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 release is being prepared and you want notes the customer-facing site \u002F email blast can use.\n- The internal CHANGELOG exists; this skill repackages it for users.\n\n## Related skills\n\n- [`polymath-release:release-notes`](..\u002F..\u002F..\u002Fpolymath-release\u002Fskills\u002Frelease-notes\u002FSKILL.md)\n  — engineer-facing release notes drafted directly from\n  `CHANGELOG.md` `[Unreleased]`. Run that first for the version-bump\n  notes; this skill repackages them for customers (announcement +\n  benefit framing, no internal-jargon component names).\n- [`polymath-release:changelog`](..\u002F..\u002F..\u002Fpolymath-release\u002Fskills\u002Fchangelog\u002FSKILL.md)\n  — append the canonical `[Unreleased]` entry that both this skill\n  and `polymath-release:release-notes` consume.\n\n## Inputs\n\n- The version being released + date.\n- The CHANGELOG entries since the last release (or `git log --oneline`).\n- Optional: any customer-reported issues that this release fixes (call out individually).\n\n## Procedure\n\n1. **Headline**: one sentence on the most important change. Lead with the benefit, not the mechanism.\n2. **What's new**: each `Added` from the CHANGELOG, restated in customer language. Skip internal-only changes.\n3. **Notable changes**: `Changed`, `Fixed`, `Security`, `Deprecated`, `Removed` that customers will notice.\n4. **Breaking changes**: own section. Migration path required for each. If anyone has to change anything in their code or workflow, this section is mandatory.\n5. **Known issues**: shipping ≠ no-bugs. Be honest about what's pending.\n6. **Security fixes**: credit the reporter when they consented; cite the advisory ID.\n7. **Claims trace to sources.** A speedup, a fixed bug, or a number must come from the CHANGELOG, a PR, or a measurement — every figure traces to the source material; a missing one is written `[TBD: \u003Cwhat>]` and listed in the summary.\n\n## Style\n\n- Active voice (\"We added X\" or \"X now does Y\").\n- User benefit, not implementation (\"Faster check-outs\" beats \"Optimized the cart query\").\n- No internal component names (\"the checkout API\" not \"v2-cart-svc\").\n- No emojis.\n\n## Output\n\n```text\nRelease notes — Polymath v1.4.0 (2026-05-24)\n\nHeadline:\n  Refunds now complete in under a second — a 4× speedup for high-volume merchants.\n\nWhat's new\n  - Refund creation is now sub-second at P95 across all regions.\n  - You can now view refund status in the timeline view of an order.\n\nNotable changes\n  - Idempotency-Key is now required on refund creation (previously optional).\n    See the migration note below.\n\nBreaking changes\n  - `POST \u002Fv1\u002Frefunds` now requires an `Idempotency-Key` header on every\n    request. Calls without it return 400.\n    Migration: include a UUID `Idempotency-Key` per refund attempt.\n\nSecurity fixes\n  - SEC-2026-0042 (Medium): IDOR on \u002Fv1\u002Forders\u002F{id}\u002Frefunds — fixed in 1.4.0.\n    Reported by \u003Cname>. See advisory link.\n\nKnown issues\n  - The new timeline view doesn't yet render correctly on Safari 15. Tracked in #1234.\n```\n\n## Quality bar\n\n- Headline names benefit, not mechanism.\n- Breaking changes have a Migration line each.\n- Internal jargon scrubbed; if the customer wouldn't recognize a component name, replace it.\n- Active voice.\n- Security fixes credit reporters who consented.\n\n## Anti-patterns to avoid\n\n- Pasting the CHANGELOG without rewriting for customer audience.\n- \"Performance improvements\" without a number.\n- Burying breaking changes in the middle of \"Notable changes\".\n- Marketing puffery (\"We're excited to announce …\"). Just say what changed.\n",{"name":5,"description":7},"main","23f6e21841a39580c9da2b5ec941f39dda17cd86","plugins\u002Fpolymath-communication\u002Fskills\u002Fwrite-release-notes","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 write-release-notes",{"tool":36,"command":37},"bunx","bunx skills add MohammadBafkar\u002Fpolymath --skill write-release-notes",{"tool":39,"command":40},"pnpm","pnpm dlx skills add MohammadBafkar\u002Fpolymath --skill write-release-notes","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-communication\u002Fskills\u002Fwrite-release-notes\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",[],[]]