Skip to main content
Generalgtmagents

versioning-dashboard

Dashboard pattern for tracking doc coverage across product versions,

Stars
259
Source
gtmagents/gtm-agents
Updated
2026-04-03
Slug
gtmagents--gtm-agents--versioning-dashboard
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/gtmagents/gtm-agents/HEAD/plugins/technical-writing/skills/versioning-dashboard/SKILL.md -o .claude/skills/versioning-dashboard.md

Drops the SKILL.md into .claude/skills/versioning-dashboard.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

Versioning Dashboard Skill

When to Use

  • Managing multiple product versions, editions, or deployment models.
  • Coordinating deprecations, migrations, and long-term support documentation.
  • Reporting readiness and gaps to leadership during launches.

Framework

  1. Version Inventory – list active versions, release dates, support windows, and owners.
  2. Artifact Coverage – matrix of docs/tutorials/guides per version + locale + channel.
  3. Change Log Hooks – tie version changes to release notes, migration guides, and alert cadence.
  4. Risk & Action Log – highlight outdated assets, missing locales, or compliance needs.
  5. Reporting Layer – KPIs (coverage %, SLA adherence, reader metrics) with filters for audience or product area.

Templates

  • Dashboard sheet with pivoted coverage views and status chips.
  • Migration tracker linking deprecated features to comms + doc updates.
  • Executive summary slide with version highlights and asks.

Tips

  • Integrate with source control metadata to auto-update coverage status.
  • Highlight dependencies (SDKs, integrations) when versions shift.
  • Pair with plan-documentation-roadmap, publish-release-documentation, and update-api-reference workflows.