[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSC87D2K8XEMKEJRB2VMSN":3,"skill-same:01M7CSC87D2K8XEMKEJRB2VMSN":49},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7CSC87D2K8XEMKEJRB2VMSN","release-notes-writing",null,"Use when the stakeholder asks for release notes or a changelog - group done\u002Freleased work into Added, Changed, Deprecated, Removed, Fixed and Security, in outcome language, with task references","makifbaysal\u002Ftasktrooper","makifbaysal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F25031940?v=4","01M7CRG3ZCSYZSSEVDMW3DEYC8","Mehmet Akif Baysal","01M7CRG401FJ8YAXH5ER730XYV",122,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fproduct-manager\u002Fskills\u002Frelease-notes-writing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: release-notes-writing\ncategory: pm\ndescription: Use when the stakeholder asks for release notes or a changelog - group done\u002Freleased work into Added, Changed, Deprecated, Removed, Fixed and Security, in outcome language, with task references\nsource: olivierlacan\u002Fkeep-a-changelog 1.1.0 (MIT), phuryn\u002Fpm-skills release-notes (MIT), adapted\n---\n# Release Notes Writing\n\n## Overview\n\nRelease notes tell users what changed for THEM, not what the team did. The failure mode is internal jargon and a flat list of task titles that mean nothing to a user. Changelogs are for humans, not machines — don't dump git log or task titles verbatim.\n\n**Core principle:** User-visible outcomes, grouped by Keep a Changelog's categories, in plain language.\n\n## Where the material comes from\n\n- `list_board_tasks` filtered to `done`\u002F`released` for the period asked about.\n- `get_task_pull_request` on each one for detail (what actually shipped, not just the title).\n- TaskTrooper has no epic\u002Fparent task — deliver the notes in chat, or as a document (`add_task_document`) on whichever task the stakeholder names, never a phantom \"release epic\".\n- The system's own batch release cut auto-generates `### Features` \u002F `### Fixes` sections from `KEY Title`. Writing implementation-task-spec titles as action + user-visible object (not an internal component name) makes that auto-generated text usable on its own — keep that in mind even when you're not the one writing this document.\n\n## Structure\n\n- **Added** — new user-visible capability.\n- **Changed** — behavior changes users must know about (a moved button, a changed default).\n- **Deprecated** — soon-to-be-removed, still working.\n- **Removed** — gone.\n- **Fixed** — defects resolved, described by the symptom the user saw, not the internal cause.\n- **Security** — a vulnerability closed; state impact, not exploit detail.\n- **Action required** — anything in Changed\u002FRemoved that is breaking: what the user must do and by when.\n\nWrite user-facing language, no internal jargon. Put task keys in parentheses for traceability.\n\n## Worked Example\n\n```markdown\n## Release 2026-07-16\n\n### Added\n- Export a project's tasks to CSV from the board (LLM-142).\n\n### Fixed\n- Deleting a task with subtasks no longer shows an error (LLM-150).\n\n### Changed\n- Task titles are now capped at 200 characters (LLM-138).\n\n### Action required\n- None this release.\n```\n\nContrast the bad version: *\"LLM-142 TaskExporter service; LLM-150 fix nil deref in cascade.\"* — accurate to the team, meaningless to a user.\n\n## Common Mistakes\n\n- Internal jargon (\"nil deref\", \"N+1\").\n- Task titles pasted verbatim instead of user outcomes.\n- Omitting \"Changed\" → users surprised by a moved feature.\n- A breaking change with no \"Action required\" line.\n- Attaching the document to an invented \"release epic\" task.\n\n## Red Flags\n\n- A note a user couldn't understand.\n- No task key for traceability.\n- A Removed\u002FChanged entry with nothing telling the user what to do about it.\n","# Release Notes Writing\n\n## Overview\n\nRelease notes tell users what changed for THEM, not what the team did. The failure mode is internal jargon and a flat list of task titles that mean nothing to a user. Changelogs are for humans, not machines — don't dump git log or task titles verbatim.\n\n**Core principle:** User-visible outcomes, grouped by Keep a Changelog's categories, in plain language.\n\n## Where the material comes from\n\n- `list_board_tasks` filtered to `done`\u002F`released` for the period asked about.\n- `get_task_pull_request` on each one for detail (what actually shipped, not just the title).\n- TaskTrooper has no epic\u002Fparent task — deliver the notes in chat, or as a document (`add_task_document`) on whichever task the stakeholder names, never a phantom \"release epic\".\n- The system's own batch release cut auto-generates `### Features` \u002F `### Fixes` sections from `KEY Title`. Writing implementation-task-spec titles as action + user-visible object (not an internal component name) makes that auto-generated text usable on its own — keep that in mind even when you're not the one writing this document.\n\n## Structure\n\n- **Added** — new user-visible capability.\n- **Changed** — behavior changes users must know about (a moved button, a changed default).\n- **Deprecated** — soon-to-be-removed, still working.\n- **Removed** — gone.\n- **Fixed** — defects resolved, described by the symptom the user saw, not the internal cause.\n- **Security** — a vulnerability closed; state impact, not exploit detail.\n- **Action required** — anything in Changed\u002FRemoved that is breaking: what the user must do and by when.\n\nWrite user-facing language, no internal jargon. Put task keys in parentheses for traceability.\n\n## Worked Example\n\n```markdown\n## Release 2026-07-16\n\n### Added\n- Export a project's tasks to CSV from the board (LLM-142).\n\n### Fixed\n- Deleting a task with subtasks no longer shows an error (LLM-150).\n\n### Changed\n- Task titles are now capped at 200 characters (LLM-138).\n\n### Action required\n- None this release.\n```\n\nContrast the bad version: *\"LLM-142 TaskExporter service; LLM-150 fix nil deref in cascade.\"* — accurate to the team, meaningless to a user.\n\n## Common Mistakes\n\n- Internal jargon (\"nil deref\", \"N+1\").\n- Task titles pasted verbatim instead of user outcomes.\n- Omitting \"Changed\" → users surprised by a moved feature.\n- A breaking change with no \"Action required\" line.\n- Attaching the document to an invented \"release epic\" task.\n\n## Red Flags\n\n- A note a user couldn't understand.\n- No task key for traceability.\n- A Removed\u002FChanged entry with nothing telling the user what to do about it.\n",{"name":5,"source":24,"category":25,"description":7},"olivierlacan\u002Fkeep-a-changelog 1.1.0 (MIT), phuryn\u002Fpm-skills release-notes (MIT), adapted","pm","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Fproduct-manager\u002Fskills\u002Frelease-notes-writing",18,"https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper","https:\u002F\u002Ftasktrooper.ai","https:\u002F\u002Fgithub.com\u002Fmakifbaysal","Senior Software Developer","2026-11-15 04:50:29",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add makifbaysal\u002Ftasktrooper --skill release-notes-writing",{"tool":41,"command":42},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill release-notes-writing",{"tool":44,"command":45},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill release-notes-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fproduct-manager\u002Fskills\u002Frelease-notes-writing\u002FSKILL.md",true,[],[50,56,63,70,77,84],{"skillNo":51,"name":52,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7CSVEPQW6J6TD6CS2T5FPNZ","visual-craft","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fvisual-craft\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7CSVAQG91ETHQ0HBNZDG5FR","ux-copy","Use when you write any words a user reads in a mockup or a hand-off - content language and voice, buttons, labels, errors, empty states, confirmations, numbers and dates, and the longest-string check","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fux-copy\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7CSV6H0J38659NDXHJQ8396","screen-mockup-html","Use when you draw screens as the design task's HTML mockup - ONE canvas document holding every screen and every variant side by side, the sanitizer-safe recipe, phone and wide frames, the states grid, static control states, and the loopback self-check with screenshots at 375, 768 and 1440 attached to the task","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fscreen-mockup-html\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7CSV3JFRF3BM3XK52M7YEYR","performance-awareness","How the performance score moves for your role. Use when the score context shows a declining trend, or before handing off work you have not self-checked against every criterion.","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fperformance-awareness\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7CSTZDH00YRF5SCT7BRT9QD","design-variants","Use when a screen design needs variants - how many, variants as side-by-side rows on the one canvas, what makes two variants genuinely different, recommending one, how the human's choice is read, and narrowing to the chosen one in revision","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-variants\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7CSTV6P3SM3PAE28DB0RF77","design-system-authoring","Use when you derive, change or extend a design system - where tokens live per stack, the DTCG token tree, role-based names for both themes, base vs layer vs drift, the DESIGN.md section order, the inventory format, the contrast check and the lint every proposal returns","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-system-authoring\u002FSKILL.md",[],[]]