From umbraco-upgrade
Generate a formal migration architecture plan for upgrading an Umbraco project from version 15 to 17. Takes audit findings (from umbraco-upgrade-audit) and produces a phased, risk-assessed migration plan with decision points and recommended strategies. Use this skill when someone needs an upgrade plan, migration architecture, migration strategy, upgrade roadmap, or when they have audit results and need to turn them into an actionable technical plan. Also trigger when someone asks "how should we approach this upgrade", "what's the migration strategy", or "plan the Umbraco 17 upgrade". This skill produces an architecture plan that feeds into the umbraco-upgrade-tasker skill.
How this skill is triggered — by the user, by Claude, or both
Slash command
/umbraco-upgrade:architectThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Transform audit findings into a structured, phased migration architecture plan. The plan should give a technical lead or architect everything they need to understand scope, sequence, risk, and decisions.
Transform audit findings into a structured, phased migration architecture plan. The plan should give a technical lead or architect everything they need to understand scope, sequence, risk, and decisions.
umbraco-upgrade-audit (preferred)Read these reference files from the plugin's root references/ directory (two directories up from this skill: ../../references/):
../../references/breaking-changes-15-to-16.md — what breaks at the U16 boundary../../references/breaking-changes-16-to-17.md — what breaks at the U17 boundary../../references/package-compatibility.md — version mapping and compatibility../../references/migration-playbook.md — specific migration recipesAlso read the plan template local to this skill:
references/plan-template.md — architecture document templateIf an audit report JSON is available, analyze it to determine:
Upgrade Strategy Decision
Effort Classification Map each finding to one of:
Risk Assessment For each area, assess:
Produce a plan using the template in references/plan-template.md (local to this skill directory). The plan has these sections:
Define which approach and why:
Option A: Stepped Upgrade (15 → 16 → 17)
Phase 1: U15 → U16
- TinyMCE → TipTap migration
- Async migration recompile
- Examine composer ordering
- Package updates to U16 versions
- Full regression test
Phase 2: U16 → U17
- .NET 9 → .NET 10
- UTC date migration
- Models builder package
- NPoco 6.x updates
- Removed extension methods
- Client-side import updates
- Forms license migration
- Full regression test
Option B: Direct Upgrade (15 → 17)
Single Phase:
- Update all NuGet to U17
- .NET 9 → .NET 10
- Address ALL breaking changes from both U16 and U17
- Full regression test
Regardless of strategy, break work into these phases:
Phase 0: Preparation (before touching code)
Phase 1: Framework & Infrastructure
Phase 2: Server-Side Breaking Changes
Phase 3: Client-Side / Backoffice Changes
Phase 4: Configuration & Licensing
Phase 5: Testing & Validation
Phase 6: Deployment
Identify all decisions that need human input before proceeding:
| ID | Decision | Options | Recommendation | Impact | Needed By |
|---|---|---|---|---|---|
| D-001 | Upgrade strategy | Stepped vs Direct | Based on findings | HIGH | Phase 0 |
| D-002 | TinyMCE handling | Auto-migrate vs 3rd party package | Auto-migrate | MEDIUM | Phase 0 |
| D-003 | Models builder mode | Keep InMemoryAuto vs switch to SourceCodeAuto | Switch | LOW | Phase 2 |
| ... | ... | ... | ... | ... | ... |
| ID | Risk | Probability | Impact | Mitigation | Owner |
|---|---|---|---|---|---|
| R-001 | Third-party package incompatible | MEDIUM | HIGH | Identify alternatives early | Tech Lead |
| R-002 | UTC migration corrupts dates | LOW | HIGH | Test on DB backup first | DBA |
| R-003 | TipTap content rendering differs | MEDIUM | MEDIUM | Spot-check 50 content pages | QA |
| ... | ... | ... | ... | ... | ... |
Save the architecture plan as:
upgrade-plan/architecture-plan.md — the full documentupgrade-plan/architecture-plan.json — structured data for the tasker skillWhen running as the coordinator/architect agent:
{
"plan_metadata": {
"project_name": "string",
"current_version": "15.x.x",
"target_version": "17.x.x",
"strategy": "stepped|direct",
"estimated_effort_days": { "min": 0, "max": 0 },
"team_size": 0,
"plan_date": "ISO-8601"
},
"phases": [
{
"phase_number": 0,
"name": "Preparation",
"description": "string",
"estimated_days": { "min": 0, "max": 0 },
"dependencies": [],
"work_items": [
{
"id": "WI-001",
"title": "string",
"description": "string",
"category": "recompile|find-replace|refactor|rebuild|configure|verify",
"effort": "XS|S|M|L|XL",
"risk": "LOW|MEDIUM|HIGH|CRITICAL",
"workstream": "backend|backoffice|devops|qa|all",
"source_findings": ["CS-001", "CS-005"],
"playbook_ref": "migration-playbook.md#7"
}
]
}
],
"decisions": [...],
"risks": [...]
}
npx claudepluginhub twofoldtech-dakota/umbraco-upgrade --plugin umbraco-upgradeAutonomous migration planning and execution: analyzes a migration target (framework upgrade, API version bump, deprecation removal), maps blast radius, produces phased plan with compatibility layers, and optionally executes via build's refactor mode.
Orchestrates full migration workflows from current state analysis through planning, incremental implementation, and verification for technologies, platforms, and architecture patterns with rollback planning.
Orchestrates complete migration workflows for frameworks (e.g., Vue 2→3, Express→Fastify), databases (MySQL→PostgreSQL), and architectures (REST→GraphQL, monolith→microservices) with analysis, incremental execution, and rollback.