How do I install the Swarm Migrate skill?

Run npx skillmds@latest add anmarhani/swarm-migrate in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Swarm Migrate safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Swarm Migrate?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Swarm Migrate free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Swarm Migrate?

AnmarHani (@anmarhani) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Swarm Migrate by anmarhani — Agent Skill

Name: Swarm Migrate
Author: AnmarHani

Swarm Migrate

Bring existing projects into the SwarmVault — register, mirror docs, optionally mine the repo into SDLC artifacts and resume the flow mid-phase (brownfield adoption). Use when the user wants existing projects migrated/connected to the vault, or an existing codebase placed into the SDLC flow.

AnmarHani a8b8c08 2.5 KB Updated Sep 17, 2026

File contents

swarm-migrate — existing-project migration

Three tiers per project; each deeper tier is opt-in with its cost stated up front. Idempotent: re-running repairs, never duplicates.

1. Discover

List candidates: swarmvault.py register --import-claude covers Claude Code users' ~/.claude.json in one shot; otherwise the user names paths. Ask WHICH projects to migrate (multi-select) and, per project, the isolation flag.

2. Immediate tier (cheap, always)

Per chosen project: register + marker → first sync (mirrors existing CLAUDE.md/AGENTS.md/README/docs and any existing memory; builds the MOC) → wire the platforms they name with setup/wire (as swarm-init step 3; one command, no manual file edits). The project is now queryable.

3. Digest tier (token-costing, opt-in)

State the rough cost first. Analyze the repo → 10 Projects/<P>/<P> Digest.md (architecture, conventions, entry points — not generated, so sync preserves it) + seed memories for footguns found in code comments/READMEs/issue notes.

4. SDLC adoption tier (most token-costing, opt-in) — place it IN the flow

Mine first, ask second (swarm-spec's brownfield mode does the work):

Sources: README, docs/, existing plan/TODO files, issue exports, test suites, the code.
Produce docs/SRS.md + feature specs marked status: mined-draft, every statement with provenance (file:line).
Detect the de-facto phase — e.g. "14 of 20 mined features implemented, no design doc" — and write flow-state accordingly.
Gap interview via the question queue: only gaps, conflicts, low-confidence items. Never re-ask what the repo answers.
Remaining work → tickets. From here /swarm-flow resumes the project mid-phase like any SwarmVault project.

Close

Ask once (if unset): vault as default for new projects? Show the security disclaimer (swarm-init step 4) if this user hasn't seen it. Huge monorepo → scope the deep tiers to user-chosen subpaths. A project containing its own Obsidian vault → exclude that folder from doc mirroring (no vault-in-vault).

Influences: Jeffallan's spec-miner & legacy-modernizer; the original Claude Vault migration — see CREDITS.md.

---name: swarm-migratedescription: Bring existing projects into the SwarmVault — register, mirror docs, optionally mine the repo into SDLC artifacts and resume the flow mid-phase (brownfield adoption). Use when the user wants existing projects migrated/connected to the vault, or an existing codebase placed into the SDLC flow.---# swarm-migrate — existing-project migrationThree tiers per project; each deeper tier is opt-in with its cost stated up front.Idempotent: re-running repairs, never duplicates.## 1. DiscoverList candidates: `swarmvault.py register --import-claude` covers Claude Code users'`~/.claude.json` in one shot; otherwise the user names paths. Ask WHICH projects tomigrate (multi-select) and, per project, the isolation flag.## 2. Immediate tier (cheap, always)Per chosen project: register + marker → first `sync` (mirrors existingCLAUDE.md/AGENTS.md/README/docs and any existing memory; builds the MOC) → wire theplatforms they name with `setup`/`wire` (as swarm-init step 3; one command, no manual fileedits). The project is now queryable.## 3. Digest tier (token-costing, opt-in)State the rough cost first. Analyze the repo → `10 Projects/<P>/<P> Digest.md`(architecture, conventions, entry points — not `generated`, so sync preserves it) + seedmemories for footguns found in code comments/READMEs/issue notes.## 4. SDLC adoption tier (most token-costing, opt-in) — place it IN the flowMine first, ask second (swarm-spec's brownfield mode does the work):1. Sources: README, docs/, existing plan/TODO files, issue exports, test suites, the code.2. Produce `docs/SRS.md` + feature specs marked `status: mined-draft`, every statement with provenance (`file:line`).3. Detect the de-facto phase — e.g. "14 of 20 mined features implemented, no design doc" — and write flow-state accordingly.4. Gap interview via the question queue: only gaps, conflicts, low-confidence items. Never re-ask what the repo answers.5. Remaining work → tickets. From here `/swarm-flow` resumes the project mid-phase like any SwarmVault project.## CloseAsk once (if unset): vault as default for new projects? Show the security disclaimer(swarm-init step 4) if this user hasn't seen it. Huge monorepo → scope the deep tiers touser-chosen subpaths. A project containing its own Obsidian vault → exclude that folderfrom doc mirroring (no vault-in-vault).---*Influences: Jeffallan's spec-miner & legacy-modernizer; the original Claude Vaultmigration — see CREDITS.md.*

Frequently asked questions