skills.rest
amoutiers
amoutiersCOMMUNITY
Explore all skills by this author →
GitHub

migrate-from-speckit

Migrate GitHub spec-kit projects to maxi conventions with preview and confirmation.

1|Updated May 28, 2026
Search Tags:#automation#cli#migration#spec-kit#migrate#maxi
One-click install
npx skills add https://github.com/amoutiers/maxi-superpowers --skill migrate-from-speckit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migrate-from-speckit
Source: https://github.com/amoutiers/maxi-superpowers/tree/main/skills/migrate-from-speckit
Command: npx skills add https://github.com/amoutiers/maxi-superpowers --skill migrate-from-speckit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates migration of GitHub spec-kit projects to maxi conventions by orchestrating the safe transfer of specs and constitution, and applying standardized frontmatter to align with maxi.

Core Features & Use Cases

  • Preview the migration plan without writing files (via --preview)
  • Apply migration with explicit confirmation (via --apply) and clobber guards to protect originals
  • Produce maxi artifacts (docs/maxi/specs, docs/maxi/constitution.md) and infer per-spec status from existing spec-kit artifacts

Quick Start

Invoke /maxi:migrate-from-speckit on your repo to preview the migration plan and then apply it with confirmation.

Frequently Asked Questions about migrate-from-speckit

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

FAQPage Schema
How do I migrate spec-kit projects to maxi conventions safely?▼

To migrate spec-kit projects to maxi conventions safely, run a guided migration script that previews changes without writing files, requires explicit confirmation, and preserves originals before copying content into docs/maxi/ paths. It targets repositories with a .specify/ directory and specs/ folders.

Can I preview spec-kit to maxi migration changes before applying them?▼

Yes, you can preview spec-kit to maxi migration changes by running the migration script with the --preview flag. This generates a non-destructive preview of the migration plan without writing files, allowing you to review standardized frontmatter updates and docs/maxi/ path mappings.

Does the maxi migration script preserve original spec-kit files?▼

Yes, the maxi migration script preserves original spec-kit files by using clobber guards to protect originals during the --apply phase. It requires explicit user confirmation before copying content into docs/maxi/ paths and applying standardized frontmatter.

What frontmatter fields are updated when migrating specs to maxi?▼

When migrating specs to maxi, the migration script updates the spec.md frontmatter fields for slug, created, updated, and status. It infers the per-spec status from existing spec-kit artifacts to align with maxi conventions.

What directory structure is required to migrate from spec-kit to maxi?▼

To migrate from spec-kit to maxi, your repository must have a .specify/ directory and specs/ folders. The deterministic workflow via migrate.sh targets these paths and produces maxi artifacts in docs/maxi/specs and docs/maxi/constitution.md.

Related Skills

Explore More Software Engineering Skills→
hiromailyhiromaily
126

shell-scripts

Format, lint, and validate shell scripts with shfmt and shellcheck.

Community
Advanced
amoutiersamoutiers
1

specify

Automate feature specification drafting with brainstorming and template formatting in Maxi.

Community
Advanced
avivsinaiavivsinai
181

bkt

Automate Bitbucket DC and Cloud repository, PR, branch, webhook, and pipeline workflows via CLI.

Community
Intermediate
miethemiethe

artifact-tracking

Create, update, query, and validate YAML+Markdown tracking artifacts.

Community
Advanced