Menu
Use when a complete module needs migration to the target architecture - runs 6 phases with approval gates.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when you need a comprehensive code audit covering security, performance, architecture, and dependencies before a release, major refactor, or compliance review.
Use when you want to iteratively build a feature using a PRD as source of truth, with progress tracking and fresh-context iterations - the Autopilot technique for autonomous development.
Use when starting a complex feature, exploring unclear requirements, or needing to challenge assumptions before committing to a design - before /plan.
Use when you need a comprehensive code review combining architecture, security, and test perspectives - especially before merging, releasing, or after major changes.
Use when creating marketing copy for landing pages, email campaigns, product descriptions, or social media - with A/B variants and conversion-focused frameworks.
Use when optimizing landing pages, signup flows, checkout processes, or any user-facing page for higher conversion rates - before A/B testing.
| name | migration-migrate-module |
| description | Use when a complete module needs migration to the target architecture - runs 6 phases with approval gates. |
| user-invocable | true |
| argument-hint | [module-path] |
| allowed-tools | Read, Write, Edit, Bash, Glob, Grep |
Migrate an entire module to the target architecture from docs/ARCHITECTURE.md.
Module/Path: $ARGUMENTS
Use @migrator to coordinate the full migration in phases:
src/modules/[name]/ and move files.types.ts + .contracts.ts + adapterValidate build/tsc/tests after each phase. Ask for approval before each phase.