Development

TYPO3 Upgrade Effort Model

Generic effort model for TYPO3 LTS upgrades: per-version risk multipliers (v14 Fluid 5 strict VHs, HashService removal, TSFE removal, asset-pipeline removal), breaking-change baselines, compatibility matrix, Rector coverage adjustments, 7-phase assessment workflow. Pair with team history.

Latest release v1.4.2

Install

Choose a supported route below. Package contents, agent registration and runtime dependencies can differ between installers.

  1. Claude Code via this marketplace
    /plugin install typo3-upgrade-effort-model@netresearch-claude-code-marketplace

    First add the marketplace once in Claude Code: /plugin marketplace add netresearch/claude-code-marketplace. Then install the selected plugin. For setup and installation scopes, see Claude Code plugin setup A plugin can include several skills and additional components.

  2. npx interactive skill selection
    npx skills add https://github.com/netresearch/typo3-upgrade-effort-model-skill

    Requires Node.js 22.20+. Run from the target project, then choose the source skills and agents in the installer. Uses the skills CLI from skills.sh Installs skill instructions. Extra plugin hooks, commands and external runtime tools are not installed by this route.

  3. composer require PHP project, as a package
    composer require netresearch/typo3-upgrade-effort-model-skill

    Allow the Composer skill installer to activate and approve skill registration when prompted. Requires netresearch/composer-agent-skill-plugin Discovers trusted skill packages and registers their instructions in AGENTS.md. Runtime tools may need separate setup.

  4. composer skills:add PHP project, direct source
    composer skills:add netresearch/typo3-upgrade-effort-model-skill

    Install and activate netresearch/composer-agent-skill-plugin first; approve the selected source's skill registration. Provided by netresearch/composer-agent-skill-plugin Pins source repositories without a Packagist package and records them in composer.skills.lock. Runtime dependencies remain separate.

What you can do with it

  • v14 risk-multiplier table (Fluid 5 strict VHs, HashService removal, TSFE removal, asset-pipeline removal, magic finders, EXT:form hooks, …)
  • per-extension baselines for v10→v14 paths
  • TYPO3 ↔ PHP version-compatibility matrix
  • generic extension classification (core / public-active / public-stale / customer-custom / heavily-customised)
  • 7-phase assessment workflow with command-level detail
  • Rector coverage discount per target version

What you get back

  • Effort ranges per extension and project from the documented workflow, with the team's calibration factor applied separately.

What it expects in your project

Check the source README for current examples, requirements and limitations. Open full README

Tags

  • development
  • typo3