Find some way for the apt and yum provisioners to derive from this, perhaps?
It's possible that this is exposing some weakness in the hierarchy I created, too. Given a second go, I might approach this with composition rather than inheritance (A provisioner would take a Distribution and a Deployer or something like that, distribution handling distro-specific idioms and deployers interacting with the provisioner and distribution to lay bits on the system, Linux would be an abstract distro, Debian and RHEL would be concrete implementations, yum, apt and chef would be deployers, etc)
There may be other approaches that simply take what I mentioned here and implement via inheritance (Base->Linux->(Debian|RHEL)->(apt|chef|yum)), but I do agree that the RHEL-centric nature at the very least indicates this should be clarified, perhaps through the naming of the plugin if it is to be accepted as-is (something like RhelChefProvisioner)