agent-loop-ext
Crash-resilient external agent loop with state persistence and CI/CD integration
Migrate the .aiwg/ directory from single-framework layout to the multi-framework layout with an automatic backup
$ npx -y skills add jmagly/aiwg --skill migrate-workspace --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/migrate-workspaceContext preview
The summary Claude sees to decide when to auto-load this skill.
Migrate the .aiwg/ directory from single-framework layout to the multi-framework layout with an automatic backup
namespace: aiwg name: migrate-workspace platforms: [all] description: Migrate the .aiwg/ directory from single-framework layout to the multi-framework layout with an automatic backup
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.
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
| 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` |
When triggered:
1. **Always dry-run first** unless the user explicitly confirms or passes `--yes`:
2. **Extract arguments**:
3. **Run the appropriate command**:
# 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**:
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.
**User**: "Migrate my workspace"
**Extraction**: Migration requested — dry-run before applying
**Action** (step 1):
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`.
**User**: "What would the workspace migration do?"
**Extraction**: Preview-only, no confirmation needed
**Action**:
aiwg migrate-workspace --dry-run
**Response**: Shows the planned moves table (as above) and stops. Does not prompt for confirmation.
**User**: "Do I need to migrate my workspace?"
**Extraction**: Check whether migration is needed
**Action**:
aiwg migrate-workspace --dry-run
**Response**: "Your workspace is already on the multi-framework layout. No migration needed."
**User**: "Go ahead and migrate the workspace"
**Extraction**: User has already seen dry-run output and is confirming
**Action**:
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
If the user's intent is ambiguous:
Reusable project context and specialist workflows for the AI tools you already use. Plan software, coordinate specialist reviews, prepare campaigns, investigate incidents, organize research, curate media, and maintain operational knowledge.
Repo: jmagly/aiwg
Crash-resilient external agent loop with state persistence and CI/CD integration
Detect requests for iterative autonomous agent loops and route to the appropriate loop executor
Automatically execute tests when code-generating agents modify source files, enforcing the execute-before-return pattern
Enable agent loops to learn from similar past tasks and share patterns across loops
Query and manage the executable feedback debug memory
Execute tests on generated code and iterate until passing