skills.rest
gmotyl
gmotylCOMMUNITY
Explore all skills by this author →
Website𝕏@gmotylGitHub

pavilio-openspec-migrate

Migrate flat plans and specs directories into the OpenSpec change tree using git mv.

Updated Apr 19, 2026
Search Tags:#migration#plans#runbook#openspec#specs#git mv#project layout
One-click install
npx skills add https://github.com/gmotyl/pavilio --skill pavilio-openspec-migrate-gmotyl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pavilio-openspec-migrate
Source: https://github.com/gmotyl/pavilio/tree/main/skills/pavilio-openspec-migrate
Command: npx skills add https://github.com/gmotyl/pavilio --skill pavilio-openspec-migrate-gmotyl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Projects using a legacy flat layout of plans/ and specs/ directories need their planning artifacts relocated into the structured OpenSpec tree without losing git history or altering document content. ## Core Features & Use Cases - Ordered migration runbook: Archives shipped plans first, then relocates living specs, archived plans, and active plans in a load-bearing sequence. - History-preserving moves: Every relocation uses git mv so file history follows each document into the new OpenSpec layout. - Verbatim content preservation: Only paths change; document bytes are never reformatted during migration. - Use Case: A project with projects/<project>/plans/.md and specs/.md files is migrated so living specs land in plans/openspec/specs/<area>/spec.md and archived plans land in plans/openspec/changes/archive/YYYY-MM-DD-<id>/, after which CURRENT.md is retired. ## Quick Start Ask the agent to run /pavilio-openspec-migrate for a named project to relocate its plans and specs into the OpenSpec layout.

Frequently Asked Questions about pavilio-openspec-migrate

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

FAQPage Schema
How do I migrate a project's plans and specs to the OpenSpec layout?▼

Invoke /pavilio-openspec-migrate with the project name. The runbook archives shipped plans first, then uses git mv to relocate living specs, archived plans, and active plans into plans/openspec/, retiring CURRENT.md last.

Does migrating to OpenSpec change the content of my plan documents?▼

No, migration preserves file content verbatim. Only paths change via git mv; the runbook never reformats documents. The only content edits are the delta folds performed when archiving shipped plans in step 1.

Does the OpenSpec migration require an openspec CLI binary?▼

No, there is no openspec binary or child process involved. The entire runbook is skill-owned, consisting of filesystem moves via git mv plus one fold pass for archiving shipped work.

What happens to unshipped active plans during OpenSpec migration?▼

Unshipped active plans are not archived; they migrate as active changes into plans/openspec/changes/<stem>/. Living directly under changes/ rather than archive/ is what marks them as the current change in the new layout.

Can a project remain readable if migration is interrupted partway?▼

Yes, the panel continues listing the legacy flat plans/ until the project's move completes. A half-migrated project stays fully readable between sessions, and CURRENT.md is only deleted as the final step.

Related Skills

Explore More Software Engineering Skills→
JNZaderJNZader

sdd-archive

Merge delta specs into main specs and archive changes with dated reports.

Community
Advanced
evandrodevbrevandrodevbr
1

openspec-archive-change

Validate OpenSpec workflow artifacts and tasks before archiving completed changes.

Community
Advanced
AlmogMaayanAlmogMaayan

openspec-archive-change

Archives completed OpenSpec changes and syncs delta specs into main specifications.

Community
Intermediate
shiftreposhiftrepo

github-repo-restructure

Move repository folders with git mv and update README references.

Official
Advanced