[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MC4EYT506YDE3BPEP62SSX":3,"skill-same:01M6MC4EYT506YDE3BPEP62SSX":106},{"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":31,"publishedAt":53,"linkOnly":54,"markdownContent":55,"markdownBody":56,"frontMatter":57,"refName":64,"commitSha":65,"skillDirectory":66,"forksCount":67,"repositoryHtmlUrl":68,"repositoryHomepageUrl":69,"ownerHtmlUrl":70,"ownerBlogUrl":71,"ownerDescription":72,"updatedAt":73,"install":74,"resources":87},"01M6MC4EYT506YDE3BPEP62SSX","docs-release-maintenance",null,"Manage developer documentation release, publishing, ownership, freshness, automation, maintenance, SaaS cadence, deprecation, deletion, redirects, and migration alongside software changes. Use when planning docs for a release, defining docs ownership, creating publishing checklists, setting up freshness checks, refreshing existing content, documenting SaaS releases, or retiring stale documentation.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdocs-release-maintenance\u002FSKILL.md",[18,23,28],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52],"docs","docs release maintenance","release","maintenance","when","writing","deprecation","developer-docs","for","developer documentation","technical-writing","cadence","software","manage","releases","publishing","up","developer","planning","code","documentation","2026-11-10 10:12:30",false,"---\nname: docs-release-maintenance\ndescription: Manage developer documentation release, publishing, ownership, freshness, automation, maintenance, SaaS cadence, deprecation, deletion, redirects, and migration alongside software changes. Use when planning docs for a release, defining docs ownership, creating publishing checklists, setting up freshness checks, refreshing existing content, documenting SaaS releases, or retiring stale documentation.\nlicense: MIT\ncompatibility: Codex, Claude Code, and other Agent Skills-compatible clients.\nmetadata:\n  version: \"0.1.0\"\n  displayName: Docs Release Maintenance\n  category: Writing\n  tags: developer-docs,technical-writing,documentation,release-management,maintenance\n---\n\n# Docs Release Maintenance\n\nUse this skill to keep developer documentation aligned with software release and maintenance lifecycles. It covers publishing readiness, ownership, automation, freshness, and responsible deprecation or deletion.\n\nThis skill is derived from *Docs for Developers: An Engineer's Field Guide to Technical Writing*, especially Chapter 7, \"Publishing documentation,\" and Chapter 11, \"Maintaining and deprecating documentation.\" It is expanded with paraphrased guidance from Christopher Gales and the Splunk Documentation Team's *The Product Is Docs: Writing Technical Documentation in a Product Development Group*, especially Chapter 10, \"Maintaining Existing Content,\" Chapter 25, \"Writing SaaS Documentation,\" and Chapter 2, \"Agile.\" Do not copy book prose into user outputs. Source: https:\u002F\u002Flink.springer.com\u002Fbook\u002F10.1007\u002F978-1-4842-7217-6\n\n## Quick Start\n\n1. Load `guidelines.md` to choose the smallest useful reference set.\n2. Identify the release, affected users, docs owners, source of truth, and publication path.\n3. Use `workflows\u002Fplan-doc-release-maintenance.md` for release or maintenance planning.\n4. Use `workflows\u002Frefresh-existing-docs.md` when stale content, patch buildup, or dependency updates require a focused refresh.\n5. Align doc publication, review, testing, announcement, and deprecation with code changes.\n6. Prefer automation that removes known toil; do not automate an unclear process.\n\n## Default Output\n\nWhen planning release or maintenance work, return:\n\n1. **Release or maintenance scope** - code\u002Fproduct change and affected docs.\n2. **User impact** - who is affected and what action they need.\n3. **Publishing checklist** - owner, reviewers, approval, tests, delivery, announcement.\n4. **Maintenance plan** - owners, freshness checks, link checks, linting, generated references.\n5. **Deprecation or deletion plan** - warnings, alternatives, migration guide, redirects, and timing.\n6. **Risks and blockers** - unverified facts, missing owners, or automation gaps.\n\n## Contents\n\n| Need | Start Here |\n|------|------------|\n| Understand release and maintenance concepts | `references\u002Fcore\u002Fknowledge.md` |\n| Apply lifecycle rules | `references\u002Fcore\u002Fknowledge.md` |\n| See checklist examples | `references\u002Fcore\u002Fknowledge.md` |\n| Plan release, maintenance, or deprecation | `workflows\u002Fplan-doc-release-maintenance.md` |\n| Refresh existing docs | `workflows\u002Frefresh-existing-docs.md` |\n| Route by task | `guidelines.md` |\n\n## Core Posture\n\n- Docs should ship with the software change they explain.\n- Every maintained doc needs ownership or an authoritative source.\n- Automation should follow a understood manual process.\n- Maintenance work should assess scope before patching content.\n- Deprecation and deletion are user communication problems, not just cleanup tasks.\n","# Docs Release Maintenance\n\nUse this skill to keep developer documentation aligned with software release and maintenance lifecycles. It covers publishing readiness, ownership, automation, freshness, and responsible deprecation or deletion.\n\nThis skill is derived from *Docs for Developers: An Engineer's Field Guide to Technical Writing*, especially Chapter 7, \"Publishing documentation,\" and Chapter 11, \"Maintaining and deprecating documentation.\" It is expanded with paraphrased guidance from Christopher Gales and the Splunk Documentation Team's *The Product Is Docs: Writing Technical Documentation in a Product Development Group*, especially Chapter 10, \"Maintaining Existing Content,\" Chapter 25, \"Writing SaaS Documentation,\" and Chapter 2, \"Agile.\" Do not copy book prose into user outputs. Source: https:\u002F\u002Flink.springer.com\u002Fbook\u002F10.1007\u002F978-1-4842-7217-6\n\n## Quick Start\n\n1. Load `guidelines.md` to choose the smallest useful reference set.\n2. Identify the release, affected users, docs owners, source of truth, and publication path.\n3. Use `workflows\u002Fplan-doc-release-maintenance.md` for release or maintenance planning.\n4. Use `workflows\u002Frefresh-existing-docs.md` when stale content, patch buildup, or dependency updates require a focused refresh.\n5. Align doc publication, review, testing, announcement, and deprecation with code changes.\n6. Prefer automation that removes known toil; do not automate an unclear process.\n\n## Default Output\n\nWhen planning release or maintenance work, return:\n\n1. **Release or maintenance scope** - code\u002Fproduct change and affected docs.\n2. **User impact** - who is affected and what action they need.\n3. **Publishing checklist** - owner, reviewers, approval, tests, delivery, announcement.\n4. **Maintenance plan** - owners, freshness checks, link checks, linting, generated references.\n5. **Deprecation or deletion plan** - warnings, alternatives, migration guide, redirects, and timing.\n6. **Risks and blockers** - unverified facts, missing owners, or automation gaps.\n\n## Contents\n\n| Need | Start Here |\n|------|------------|\n| Understand release and maintenance concepts | `references\u002Fcore\u002Fknowledge.md` |\n| Apply lifecycle rules | `references\u002Fcore\u002Fknowledge.md` |\n| See checklist examples | `references\u002Fcore\u002Fknowledge.md` |\n| Plan release, maintenance, or deprecation | `workflows\u002Fplan-doc-release-maintenance.md` |\n| Refresh existing docs | `workflows\u002Frefresh-existing-docs.md` |\n| Route by task | `guidelines.md` |\n\n## Core Posture\n\n- Docs should ship with the software change they explain.\n- Every maintained doc needs ownership or an authoritative source.\n- Automation should follow a understood manual process.\n- Maintenance work should assess scope before patching content.\n- Deprecation and deletion are user communication problems, not just cleanup tasks.\n",{"name":5,"license":15,"metadata":58,"description":7,"compatibility":63},{"tags":59,"version":60,"category":61,"displayName":62},"developer-docs,technical-writing,documentation,release-management,maintenance","0.1.0","Writing","Docs Release Maintenance","Codex, Claude Code, and other Agent Skills-compatible clients.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdocs-release-maintenance",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":75,"prompt":85,"zipAvailable":86},[76,79,82],{"tool":77,"command":78},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill docs-release-maintenance",{"tool":80,"command":81},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill docs-release-maintenance",{"tool":83,"command":84},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill docs-release-maintenance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdocs-release-maintenance\u002FSKILL.md",true,[88,94,98,102],{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":93},"guidelines.md","REFERENCE","参考文档",2132,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdocs-release-maintenance\u002Fguidelines.md",{"path":95,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fcore\u002Fknowledge.md",9408,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdocs-release-maintenance\u002Freferences\u002Fcore\u002Fknowledge.md",{"path":99,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":100,"sourceHtmlUrl":101},"workflows\u002Fplan-doc-release-maintenance.md",2299,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdocs-release-maintenance\u002Fworkflows\u002Fplan-doc-release-maintenance.md",{"path":103,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":104,"sourceHtmlUrl":105},"workflows\u002Frefresh-existing-docs.md",2874,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdocs-release-maintenance\u002Fworkflows\u002Frefresh-existing-docs.md",[107,116,124,132,140,148],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":115},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":120,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":115},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":115},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":136,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":115},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":144,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":115},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":152,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":115},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]