gspec-migrate

Migrate legacy gspec Markdown files to spec-version v1 format.

6|2|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/gballer77/gspec --skill gspec-migrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gspec-migrate
Source: https://github.com/gballer77/gspec/tree/main/pages/.claude/skills/gspec-migrate
Command: npx skills add https://github.com/gballer77/gspec --skill gspec-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Legacy gspec documents frequently use outdated frontmatter or lack versioning, causing drift from the current specification format and breaking automated tooling.

Core Features & Use Cases

  • Frontmatter normalization: updates spec-version to v1 and migrates legacy gspec-version fields.
  • Content preservation: preserves all substantive content while reorganizing structure to the current format.
  • Inventory and verification: scans gspec files, reports migration status, and verifies post-migration integrity.
  • Bulk workflow: handles migration across gspec/ and features/ directories for multiple files.

Quick Start

Run the gspec-migrate workflow to inventory all gspec files, migrate legacy frontmatter to spec-version v1, and verify content preservation.

Frequently Asked Questions about gspec-migrate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate legacy gspec markdown files to the spec-v1 format?

To migrate legacy gspec markdown files to the spec-v1 format, run the gspec-migrate workflow to inventory all files under gspec/ and features/, update frontmatter to spec-version v1, and preserve content while reorganizing structure.

Why do my outdated gspec documents cause drift and break automated tooling?

Outdated gspec documents cause drift and break automated tooling because they frequently lack versioning or use legacy frontmatter like gspec-version instead of the current spec-version field required by the latest specification format.

Can I bulk migrate frontmatter across multiple markdown files in gspec and features directories?

Yes, you can bulk migrate frontmatter across multiple markdown files because the migration workflow handles inventory and content preservation across all gspec files located in both the gspec/ and features/ subfolders.

Does the gspec migration process preserve the original content of my markdown files?

The gspec migration process preserves all substantive content while reorganizing the structure to match current skill definitions, ensuring that your original markdown text remains intact during the frontmatter normalization.

What is the best way to verify markdown frontmatter integrity after updating spec-version to v1?

The best way to verify frontmatter integrity after updating spec-version to v1 is to use the migration workflow's built-in verification step, which scans gspec files, reports migration status, and checks post-migration integrity.