---
name: bevy-upgrade
description: "TODO: Use the skill-creator skill to write this. See scaffolding goals below."
---

# Bevy Upgrade — Version Migration Guide

> **This skill is a scaffold.** Use `/skill-creator` to create the full skill content from the research material.

## Scaffolding Goals

1. **Use the `skill-creator:skill-creator` skill** to create the full SKILL.md content
2. Feed it the version-change annotations from research reports 01-06 in [`docs/workpad/research/bevy-skill-research/`](../../../../docs/workpad/research/bevy-skill-research/00-index.md)
3. The skill should trigger when the user asks to upgrade/migrate Bevy versions, or when the `bevy` skill detects upgrade work
4. Core content:
   - Breaking-change chain from 0.16 through 0.19+
   - Rename tables (old name -> new name, which version)
   - Semantic shifts (behavior changes, not just renames)
   - Step-by-step migration patterns for each version bump
   - Common upgrade pitfalls and their fixes
5. Populate `references/` with per-version-transition files (e.g., `0.17-to-0.18.md`, `0.18-to-0.19.md`)
6. The skill should be invocable both directly and from the `bevy` skill

## Reference Material

Same research as the `bevy` skill — version-change annotations are woven into each report:

- [01-plugins.md](../../../../docs/workpad/research/bevy-skill-research/01-plugins.md) — Plugin API changes across versions
- [02-ecs-core.md](../../../../docs/workpad/research/bevy-skill-research/02-ecs-core.md) — ECS API renames and new patterns
- [03-hierarchy.md](../../../../docs/workpad/research/bevy-skill-research/03-hierarchy.md) — Parent->ChildOf transition
- [04-events-observers.md](../../../../docs/workpad/research/bevy-skill-research/04-events-observers.md) — Event/Message split
- [05-input.md](../../../../docs/workpad/research/bevy-skill-research/05-input.md) — Input API changes
- [06-camera-gotchas.md](../../../../docs/workpad/research/bevy-skill-research/06-camera-gotchas.md) — Camera API changes