migrate-workspace
Migrate the .aiwg/ directory from single-framework layout to the multi-framework layout with an automatic backup
What this skill does
# Migrate Workspace You upgrade the `.aiwg/` directory from the old single-framework layout to the new multi-framework layout, moving artifacts into framework-scoped subdirectories. A backup is always created before any changes are applied. ## Triggers Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description): - "upgrade my aiwg structure" → run migration - "move to multi-framework layout" → run migration - "preview workspace migration" → dry-run only - "what would migrate?" → dry-run only ## Trigger Patterns Reference | Pattern | Example | Action | |---------|---------|--------| | Full migration | "migrate my workspace" | Run `aiwg migrate-workspace` | | Dry run | "preview the workspace migration" | Run `aiwg migrate-workspace --dry-run` | | Forced | "migrate workspace, skip confirmation" | Run `aiwg migrate-workspace --yes` | | Check needed | "do I need to migrate?" | Run `aiwg migrate-workspace --dry-run` | ## Behavior When triggered: 1. **Always dry-run first** unless the user explicitly confirms or passes `--yes`: - Run `aiwg migrate-workspace --dry-run` to show what would move. - Report the planned changes to the user. - Ask for confirmation before proceeding. 2. **Extract arguments**: - Is `--dry-run` requested? Report only, no changes. - Has the user already confirmed? Use `--yes` to skip the interactive prompt. - Is there a specific backup path? (optional) 3. **Run the appropriate command**: ```bash # Preview only — no changes aiwg migrate-workspace --dry-run # Full migration (prompts for confirmation) aiwg migrate-workspace # Full migration, skip prompt aiwg migrate-workspace --yes ``` 4. **What the migration does**: - Creates a timestamped backup at `.aiwg/.backup-<timestamp>/` - Creates framework-scoped subdirectories under `.aiwg/frameworks/<name>/` - Moves existing flat artifacts into the appropriate scoped location - Updates `.aiwg/frameworks/registry.json` - Leaves a `MIGRATION.md` log at `.aiwg/` root 5. **Safety guarantee**: The backup is created before any file is moved. If migration fails partway through, `aiwg rollback-workspace` can restore from the backup. 6. **Report the result** — show what was moved, backup location, and how to rollback if needed. ## Examples ### Example 1: Dry run first (default approach) **User**: "Migrate my workspace" **Extraction**: Migration requested — dry-run before applying **Action** (step 1): ```bash aiwg migrate-workspace --dry-run ``` **Response**: ``` Workspace Migration Preview ━━━━━━━━━━━━━━━━━━━━━━━━━━━ Would move: .aiwg/requirements/ → .aiwg/frameworks/sdlc-complete/requirements/ .aiwg/architecture/ → .aiwg/frameworks/sdlc-complete/architecture/ .aiwg/testing/ → .aiwg/frameworks/sdlc-complete/testing/ (+ 5 more directories) Would create backup: .aiwg/.backup-20260401-1423/ No files would be deleted. Proceed with migration? [y/N] ``` After user confirms → run `aiwg migrate-workspace --yes`. ### Example 2: Dry run only **User**: "What would the workspace migration do?" **Extraction**: Preview-only, no confirmation needed **Action**: ```bash aiwg migrate-workspace --dry-run ``` **Response**: Shows the planned moves table (as above) and stops. Does not prompt for confirmation. ### Example 3: Already on new layout **User**: "Do I need to migrate my workspace?" **Extraction**: Check whether migration is needed **Action**: ```bash aiwg migrate-workspace --dry-run ``` **Response**: "Your workspace is already on the multi-framework layout. No migration needed." ### Example 4: Migration with confirmation **User**: "Go ahead and migrate the workspace" **Extraction**: User has already seen dry-run output and is confirming **Action**: ```bash aiwg migrate-workspace --yes ``` **Response**: ``` Backup created: .aiwg/.backup-20260401-1423/ Migrating 8 directories... requirements/ moved architecture/ moved testing/ moved (+ 5 more) registry.json updated. Migration complete. To undo: aiwg rollback-workspace ``` ## Clarification Prompts If the user's intent is ambiguous: - "Would you like me to preview the migration first, or go ahead and apply it?" - "Have you already reviewed the dry-run output, or should I run it first?" ## References - @$AIWG_ROOT/src/cli/handlers/workspace.ts — `migrate-workspace` command handler - @$AIWG_ROOT/docs/cli-reference.md — CLI reference - @$AIWG_ROOT/agentic/code/addons/aiwg-utils/skills/rollback-workspace/SKILL.md — Undoing a migration
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.