Menü
Generic migration orchestrator that reads CHANGELOG.md to understand and execute version-specific migrations
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Determine feature slug interactively by auto-detecting next number and prompting user for description
Share personal documents to the shared namespace with atomic git commit and push
Use when creating implementation plans to generate properly structured plans with phases, success criteria, and project references.
Use when documenting research findings to create properly structured research documents with frontmatter, sections, and file references.
ALWAYS check this skill before using grep, glob, Task tool, or doing any codebase exploration. Guides you to use specialized agents that are more efficient than basic tools.
Use when writing tests to ensure they follow project conventions. References patterns from thoughts/notes/testing.md.
Basierend auf der SOC-Berufsklassifikation
| name | upgrade-plugin |
| description | Generic migration orchestrator that reads CHANGELOG.md to understand and execute version-specific migrations |
Orchestrate project-level migrations by reading CHANGELOG.md as the single source of truth for migration steps.
Called by /workflows:upgrade command to handle the upgrade process.
Read thoughts/.version in the project directory:
current: v1.2.2
migrated_from: v1.2.1
migration_date: 2026-02-03
If file doesn't exist, detect from directory structure and create it.
Read CHANGELOG.md from the plugin directory to understand:
The CHANGELOG contains all version-specific migration logic.
Follow the migration steps described in CHANGELOG:
After successful migration, update thoughts/.version:
current: v1.3.0
migrated_from: v1.2.2
migration_date: 2026-02-04
thoughts/.version1. User runs /workflows:upgrade
2. Skill reads thoughts/.version → "v1.2.2"
3. Skill reads CHANGELOG.md → finds v1.3.0 migration section
4. Skill follows migration steps from CHANGELOG
5. Skill asks user questions via AskUserQuestion
6. Skill executes migration
7. Skill updates thoughts/.version → "v1.3.0"
8. Skill generates report
This design means the skill never needs updating - only CHANGELOG changes per version.