mcpField
V
versioning-dashboard

versioning-dashboard

github.com/gtmagentsDocuments42863 installsUpdated 30w ago
Repository

About versioning-dashboard

versioning-dashboard is a documentation skill for tracking product versions, documentation coverage, migrations, and launch readiness. It organizes version and content status into filtered reports and provides templates for dashboards and executive updates.

Key features

  1. 01Inventory of versions and support windows
  2. 02Documentation coverage by version and locale
  3. 03Release-note and migration-guide tracking
  4. 04Risk and action logs
  5. 05Filtered readiness reporting
  6. 06Dashboard and migration templates

Use cases

  1. 01Tracking documentation across product editions
  2. 02Coordinating deprecations and migrations
  3. 03Reporting launch readiness and documentation gaps

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gtmagents/gtm-agents --skill versioning-dashboard

After installing, type/versioning-dashboardin Claude Code to confirm it loaded.

Details

From the project README

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.

Comments

Markdown supported