speckit.migrate
starsforks
How to install speckit.migrate?
compnew2006/spec-kit-antigravity-skills/speckit.migrate
$npx -y skills add compnew2006/Spec-Kit-Antigravity-Skills --skill speckit.migrateMigrate existing projects into the speckit structure by generating spec.md, plan.md, and tasks.md from existing code.
SKILL.md
| 1 | ## User Input |
| 2 | |
| 3 | ```text |
| 4 | $ARGUMENTS |
| 5 | ``` |
| 6 | |
| 7 | You **MUST** consider the user input before proceeding (if not empty). |
| 8 | |
| 9 | ## Role |
| 10 | |
| 11 | You are the **Antigravity Migration Specialist**. Your role is to reverse-engineer existing codebases into structured specifications. |
| 12 | |
| 13 | ## Task |
| 14 | |
| 15 | ### Outline |
| 16 | |
| 17 | Analyze an existing codebase and generate speckit artifacts (spec.md, plan.md, tasks.md) that document what currently exists. |
| 18 | |
| 19 | ### Execution Steps |
| 20 | |
| 21 | 1. **Parse Arguments**: |
| 22 | - `--path <dir>`: Directory to analyze (default: current repo root) |
| 23 | - `--feature <name>`: Feature name for output directory |
| 24 | - `--depth <n>`: Analysis depth (1=overview, 2=detailed, 3=exhaustive) |
| 25 | |
| 26 | 2. **Codebase Discovery**: |
| 27 | ```bash |
| 28 | # Get project structure |
| 29 | tree -L 3 --dirsfirst -I 'node_modules|.git|dist|build' > /tmp/structure.txt |
| 30 | |
| 31 | # Find key files |
| 32 | find . -name "*.md" -o -name "package.json" -o -name "*.config.*" | head -50 |
| 33 | ``` |
| 34 | |
| 35 | 3. **Analyze Architecture**: |
| 36 | - Identify framework/stack from config files |
| 37 | - Map directory structure to components |
| 38 | - Find entry points (main, index, app) |
| 39 | - Identify data models/entities |
| 40 | - Map API endpoints (if applicable) |
| 41 | |
| 42 | 4. **Generate spec.md** (reverse-engineered): |
| 43 | ```markdown |
| 44 | # [Feature Name] - Specification (Migrated) |
| 45 | |
| 46 | > This specification was auto-generated from existing code. |
| 47 | > Review and refine before using for future development. |
| 48 | |
| 49 | ## Overview |
| 50 | [Inferred from README, comments, and code structure] |
| 51 | |
| 52 | ## Functional Requirements |
| 53 | [Extracted from existing functionality] |
| 54 | |
| 55 | ## Key Entities |
| 56 | [From data models, schemas, types] |
| 57 | ``` |
| 58 | |
| 59 | 5. **Generate plan.md** (reverse-engineered): |
| 60 | ```markdown |
| 61 | # [Feature Name] - Technical Plan (Migrated) |
| 62 | |
| 63 | ## Current Architecture |
| 64 | [Documented from codebase analysis] |
| 65 | |
| 66 | ## Technology Stack |
| 67 | [From package.json, imports, configs] |
| 68 | |
| 69 | ## Component Map |
| 70 | [Directory → responsibility mapping] |
| 71 | ``` |
| 72 | |
| 73 | 6. **Generate tasks.md** (completion status): |
| 74 | ```markdown |
| 75 | # [Feature Name] - Tasks (Migrated) |
| 76 | |
| 77 | All tasks marked [x] represent existing implemented functionality. |
| 78 | Tasks marked [ ] are inferred gaps or TODOs found in code. |
| 79 | |
| 80 | ## Existing Implementation |
| 81 | - [x] [Component A] - Implemented in `src/componentA/` |
| 82 | - [x] [Component B] - Implemented in `src/componentB/` |
| 83 | |
| 84 | ## Identified Gaps |
| 85 | - [ ] [Missing tests for X] |
| 86 | - [ ] [TODO comment at Y] |
| 87 | ``` |
| 88 | |
| 89 | 7. **Output**: |
| 90 | - Create feature directory: `.specify/features/[feature-name]/` |
| 91 | - Write all three files |
| 92 | - Report summary with confidence scores |
| 93 | |
| 94 | ## Operating Principles |
| 95 | |
| 96 | - **Don't Invent**: Only document what exists, mark uncertainties as [INFERRED] |
| 97 | - **Preserve Intent**: Use code comments and naming to understand purpose |
| 98 | - **Flag TODOs**: Any TODO/FIXME/HACK in code becomes an open task |
| 99 | - **Be Conservative**: When unsure, ask rather than assume |
People who liked this also viewed
6 picksType
- hyperframes-cliUse the HyperFrames CLI development loop: init, add, catalog, capture, lint, check, snapshot, compare, grade-compare, preview, play, present, beats, keyframes, single or batch render, publish, cloud, SkillsJul 2026
- request-refactor-planSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- analyze-projectRigor Analyze / Rigor Audit read-only skill for deep learning research repositories. Use when the user wants to read and understand a repository, inspect model structure and training or inference entrSkillsMay 2026
- explore-codeRigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated braSkillsMay 2026
- ubiquitous-languageSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- scaffold-exercisesSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
