Allow nested/recursive expansion of variables in build invocation

I have several build jobs that all share the same build invocation that contains several variables that are build agent capabilities. Whenever this invocation changes, I have to go and edit the many jobs that use it.

What I would like to be able to do is defined the build invocation as a single global variable, that itself uses variables that are capabilities of the build agent. This would allow me to define the invocation in one place which would simplify maintenance.

Another alternative would be to introduce build invocation templates that can be shared among jobs (across different plans). These templates could themselves have variables that could be unique to the job that must be configured there, which would allow the common parts of the invocation to be defined centrally yet still facilitate differences per job.