skills.rest
outcomeengineering
outcomeengineeringOFFICIAL
Explore all skills by this author →
GitHub

migrating-spec-to-spx

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides the essential knowledge and guidance to migrate software specifications from an older 'specs/' directory structure to the modern Outcome Engineering framework ('spx/'), ensuring a smooth and accurate transition of code and documentation.

Core Features & Use Cases

  • Migration Guidance: Understand the process, naming conventions, and success criteria for migrating specs.
  • Verification: Learn how to verify that migrations are complete and accurate, including test coverage parity.
  • Failure Mode Avoidance: Get insights into common pitfalls and how to avoid them during migration.
  • Use Case: A development team needs to refactor their existing codebase and documentation. They use this Skill to understand the exact steps, file renamings, and verification checks required to move their legacy specifications into the new spx/ structure.

Quick Start

Use the migrating-spec-to-spx skill to understand the process of migrating legacy specs to the spx structure.

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

Migrating legacy specs to the spx framework involves renaming files from the legacy specs directory and co-locating tests within the new spx structure. This ensures accurate architectural refactoring and documentation alignment.

What is the Outcome Engineering spx directory structure?▼

The Outcome Engineering spx directory structure is a modern framework replacing legacy specs folders. It standardizes software specifications by co-locating tests and refactoring codebase architecture to ensure coverage parity.

How do I verify test coverage parity when refactoring specs?▼

Verifying test coverage parity during spec migration involves checking that all tests from the legacy directory are successfully co-located in the spx structure. This prevents missing tests during architectural refactoring.

What are common failures when migrating specifications to a new directory?▼

Common migration failures include incorrect file renaming and losing test coverage parity. Avoid these pitfalls by following detailed steps and verification checks for moving legacy specifications into the spx structure.

Can I co-locate tests when moving specs to the spx standard?▼

Yes, co-locating tests is a core step when moving specs to the spx standard. The migration process explicitly covers renaming files and co-locating tests to ensure complete documentation and codebase coverage.

Related Skills

Explore More Software Engineering Skills→
outcomeengoutcomeeng
1

migrating-spec-to-spx

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

Official
Basic
j-showj-show

review-helper

Review git diffs, apply fixes, and verify with pnpm check and test commands.

Official
Advanced
alirezarezvanialirezarezvani
763

readme-updater

Automate README updates by parsing diffs and detecting relevant code changes.

Community
Basic
askferretaskferret

dia-migration

Upgrade DIA artifacts to the latest version by renaming files and updating metadata.

Community
Advanced