skills.rest
outcomeeng
outcomeengOFFICIAL
Explore all skills by this author →
WebsiteGitHub

migrating-spec-to-spx

Migrate legacy specs to SPX structure with naming and verification rules.

1|Updated Jan 6, 2026
Search Tags:#verification#migration#reference#workflows#specs#spx#migration-records
One-click install
npx skills add https://github.com/outcomeeng/claude --skill migrating-spec-to-spx-outcomeeng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migrating-spec-to-spx
Source: https://github.com/outcomeeng/claude/tree/main/plugins/spx-legacy/skills/migrating-spec-to-spx
Command: npx skills add https://github.com/outcomeeng/claude --skill migrating-spec-to-spx-outcomeeng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ALWAYS invoke this skill when migrating specs to spx, reviewing migrations, or debugging migration issues. NEVER migrate specs without this skill.

Core Features & Use Cases

  • Provides domain knowledge for migration operations and acts as an authoritative reference for naming, coverage, and verification rules.
  • Serves as a guide for both migrators and reviewers to ensure consistent practices and traceable migrations.
  • Helps maintain SPX-MIGRATION.md records and aligns DONE.md documentation with SPX records.

Quick Start

Read this skill fully before starting migration and use it as the authoritative source during migrations and reviews.

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 structure?▼

Migrate legacy specs to the SPX structure by applying provided naming conventions, verification rules, and best practices to generate traceable SPX-MIGRATION.md records.

What is an SPX-MIGRATION.md record used for?▼

An SPX-MIGRATION.md record documents the migration of legacy specs to the SPX structure, serving as an authoritative reference for migrators and reviewers to align with DONE.md.

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

Verify migration coverage by applying the Skill's verification rules to ensure legacy specs align with the SPX structure and DONE.md as the source of truth.

Can I review or debug a spec migration without an authoritative reference?▼

Reviewing or debugging spec migration issues requires an authoritative reference for naming and coverage rules to ensure consistent practices and traceable migrations across specs and SPX structures.

When should I reference DONE.md during a spec migration?▼

Reference DONE.md during a spec migration when you need the source of truth to align documentation with SPX records and generate accurate SPX-MIGRATION.md outputs.

Related Skills

Explore More Software Engineering Skills→
simonheimlichersimonheimlicher
1

migrating-spec-to-spx

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

Community
Basic
simonheimlichersimonheimlicher
1

architecting-typescript

Create Architecture Decision Records for TypeScript architecture decisions.

Community
Advanced
outcomeengineeringoutcomeengineering
1

migrating-spec-to-spx

Migrate software specifications from 'specs/' to the 'spx/' framework.

Official
Advanced
seohowseohow

audit-urls

Analyze website URLs for structural issues and generate SEO migration plans.

Official
Intermediate