migrating-spec-to-spx

Guide legacy spec migrations to the SPX CODE framework with verification rules.

1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/simonheimlicher/spx-claude --skill migrating-spec-to-spx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrating-spec-to-spx
Source: https://github.com/simonheimlicher/spx-claude/tree/main/plugins/spx/skills/migrating-spec-to-spx
Command: npx skills add https://github.com/simonheimlicher/spx-claude --skill migrating-spec-to-spx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill consolidates domain knowledge for migrating specs to the SPX CODE framework, providing a structured reference to guide migrations, reviews, naming, and verification without performing the migration itself.

Core Features & Use Cases

  • Knowledge base for legacy-to-SPX migrations, including naming conventions, ADR handling, and coverage verification.
  • Guidance for practitioners on when to invoke the migrator agent vs reviewer, and how to validate migrations with SPX-MIGRATION.md.
  • Operational workflow templates for migration tasks, reviews, and auditing, enabling consistent, auditable results across teams.

Quick Start

  • Read this skill before starting migrations.
  • When migrating, consult the <success_criteria> and <verification_gates> sections, then execute migrations with the designated SPX agents.
  • When reviewing migrations, reference this skill to verify naming, test mappings, and coverage checks.

Frequently Asked Questions about migrating-spec-to-spx

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

FAQPage Schema
How do I migrate legacy specs to the SPX code framework?

Migrate legacy specs to the SPX code framework by consulting this skill's knowledge base for naming conventions, building a full sharing map, and validating test coverage at the legacy-file level. Use the SPX-MIGRATION.md file to guide and document the entire process.

What naming conventions are required for SPX spec migrations?

SPX spec migrations require specific naming conventions outlined in this skill's knowledge base. Adhering to these conventions ensures consistent migrations and verifications, enabling practitioners to maintain structured references and execute migrations with designated SPX agents.

How do I verify test coverage when migrating specs to SPX?

Verify test coverage when migrating specs to SPX by validating coverage at the legacy-file level. The skill provides verification rules and gates to check test mappings, ensuring that all legacy stories within a capability are fully covered before completing the migration.

Does this skill perform the spec migration automatically?

No, this skill does not perform the spec migration automatically. It serves as a consolidated knowledge base that provides structured reference, operational workflow templates, and verification rules to guide practitioners through manual migrations and reviews.

When should I use the migrator agent versus the reviewer for SPX migrations?

Use the migrator agent to execute the actual migration of stories to the SPX framework, and use the reviewer to audit completed migrations. This skill provides guidance on when to invoke each agent and how to validate results using SPX-MIGRATION.md.

Can I review completed SPX migrations using this skill?

Yes, you can review completed SPX migrations by referencing this skill to verify naming conventions, check test mappings, and validate coverage. It includes operational workflow templates for auditing to ensure consistent and auditable results across teams.