#scalling

As detailed in this Deviantart post, Adora as She-Ra has multiple universal feats, but it wouldn't be fair to exactly scale other characters fighting her to this, especially that the story does not show them in this realm of power (there is also the power and durability inconsistency as mentioned in the comment, but on that latter).

Let's first start with Catra. We know Catra can contend as a near equal with She-Ra, even overwhelm her at times, and in the comic The Legend of the Fire Princess, Catra and Scorpia fighting together actually managed to defeat She-Ra.

Scorpia also managed to force out the Sword of Protection from Adora (as She-Ra hands). Rebel Princess Guide does have Adora explain Scorpia is almost as strong as She-Ra, suggesting Adora was caught by surprise of someone being also so strong (Adora is a sincere and not arrogant person, and was impressed by Scorpia here, so I think she would wrote of se exceeded her in strength).

The Battle for Bright Moon episode is also notable. In this, and previous episode, the overclocked Black Garnet caused a planet wide storm, that disrupted and weakened all of other Runestones, affecting all of the planet. As shown in the calculation here, just causing such storm is enough energy to destroy a "small planet" (akin in size to Mercury, dwarf planets objects are more or counted on vsbattles as large moons).

And this not all the Black Garnet caused, only a part of it - it also caused Tidal Waves, Fire Storms, Earthquakes all around the planet.

Adora, after regaining her faith in herself, dispelled the planetary storm, and other effects of the Black Garnet, even visibly overpowering it.

Later, Adora empowered Glimmer, Bow, Perfuma, Mermista, Netossa, Spinerella and Frosta, and in turn they empowered her back. With this Adora (exceeding her past power when she overpowered the Black Garnet) used a rainbow beam that one shot the Horde army, though literally blowing them away as the energy rainbow touched them.

Catra was also hit by this attack, but actually initially managed to struggle against it, and being struck by the full force of it (as opposed to others). She was kinda damaged by it, but nowhere close to critically, and retreated in part as she realized she and the Horde don't have now any chance at wining.

In season 5, Catra got struck by lightning magic from a chipped Scorpia, and survived relatively unharmed, if weakened.

The same attack after three strikes detransformed Adora, and latter caused her problems turning back into She-Ra.

(Though it should be noted Adora was here at an disadvantage, as she was fighting fully defensively at Perfuma's urging to not harm Scorpia, but still shows the power of Scorpia's lightning.)

It should be also noted here it was stated in season 4 and 5 First Ones restricted the power of the Runestones and Princesses, draining their power to the Heart of Etheria. Adora partially lifted this restriction in Battle for Bright Moon (indeed it does seem Adora unlocked the Runestones power enough they can at least resist and stop the overclocked Black Garnet in the future, hence this plan wasn't repeated), and their was further released in the season 4 finale. So it is at least very much probable now Scorpia has access to greater power than the Black Garnet's power, than it even had when overclocked, especially seeing her feats in the battle with Season 5 She-Ra.

I's also worth mentioning this She-Ra transformation (that fought im season 5 with Scorpia) is one Adora can use to full power, not restricted by the First One made Sword of Protection. The same power was shown in season 3 as capable of destroying reality and collapsing time and space, as well as Adora using it it to restore reality. Not saying Scorpia outright scales to that, but shows the magnitude of her unlocked power by season 5.

These attacks wouldn't blow a planet, but probably contained similar amounts of share energy but much more focused. Especially that this level of power is consistent with what was presented in the series storyline.

It should also explored (as it's also relevant for latter feats) that in the season 4 episode "Pulse", the giant Pulse-Bot, when self destructing, would wipe out half of the Whispering Woods. Whispering Woods (at least in a large part) surrounds the Kingdom of Bright Moon, one of the largest kingdoms of Etheria (only rivaled by the Horde Empire and Kingdom of Frost), and it was similarly large in other canons. So this is probably an explosion powerful enough to wipe out a medium country (or medium US state) at least.

It's also notable the Whispering Woods are supernaturally durable, with Horde forces not being able to destroy it for over two decades. In general previous an energy of a overclocked Black Garnet, was needed to do such damage. It wouldn't be all of these energy used, but still shows the amounts of energy required.

Now I mention this, as Hordak chosen to use his arm canon to blast through the Sea Gate, over using a variant of the Giant Pulse Bot even as a bomb, suggesting it's shots have more energy. (The Sea Gate itself before season one, survived over a decade at least of attacks by Horde Forces, slowly wearing it down, before Adora restored it to full operations.)

This stacks with other things the power of the arm canon was shown to do. Notably, during Catra's fight with Hordak, it was clear Catra knew she wouldn't survive being shot by Hordak's blast a second time. It's possible even her surviving the first time, was due to her possible nine lives ability (as suggested by the series creator Nate Stevenson, though it's unsure if he was serious), which seemingly allows her to avoid certain death 8 times, though it's possible it allowed her to avoid latter blasts. And again it might been a joke.

Both though options show the arm canon blasts were significantly more powerful than the rainbow energy blast, and Scorpia's lightning, with both being portrayed as less (even visibly less) of a lethal danger to Catra, while she avoided Hordak's blasts at all cost:

Hordak's durability in this fight is also notable - he took multiple hits in succession from Catra, including to his unarmored head (on which an about 700 metric ton metal claw also was dropped) and back. Catra was here fighting fully with the intent to kill, as she was fighting here for her life.

Catra's kick also shattered Hordak's arm canon, which used the same technology and composition as his armor, and the arm canon could contain the massive energies it generated before firing them, further showing the share force here behind Catra's strikes in this fight.

This curiously does suggest even without armor (and possibly supporting the idea the armor was depowered after Catra torn out the LUVD crystal), and in his decrepit state, Hordak is very durable (despite and outside of his body slowly falling apart on it's own), possibly strong, despite the same reason (as he had to lift the giant metal claw from himself), if certainly actions requiring large amounts of strength causing him immense pain, and causing further injuries to him. But the adrenaline rush from being immensely pissed at Catra (and despairing Entrapta's seeming death), and well just his psychological state, possibly overrode these (well the pain).

In general, I think this puts Catra, Hordak and Scorpia in the (at least) planetary range of attack power and durability.

To be clear, there are inconsistencies with some other situations characters seem visibly weaker or more vulnerable...but this happens a lot in fiction. Including other incarnations of Masters of the Universe, as written in the dA post I linked at start. And some examples from non-SPOP and non-Filmation shows:

He-Man being tied and fully immobilized by Tuvar's electric bola in the 2002 series (episode "Monster Within"):

and in the same episode by Badra using aggressive vines

In both cases, He-Man was presented as being at a visible risk of dying here.

in the DC Masters of the Universe comics, Despara/Despata keeping up in a fight with both Adam and Teela, and was doing very well, until Battle Cat's surprise attack interrupted the fight (2013 He-Man and the Masters of the Universe #1-#2 He-Man):

So I think we can agree these are understandable.

In general, I think this a good middle ground, as one could scale Hordak, Catra and Scorpia higher of Adora's feats, though I discussed also issues with that.

There is an entire ecosystem of process frameworks that claim to scale agile. Most of them bring in a whole host of new roles, activities, and abstractions. This can be and should be a real concern for an organization already doing well. And this here is precisely where the rub is. If you find yourself in a position to significantly grow, it probably means you are doing things well. And if you are are doing well, what you’re doing is already working. So why then would you upend everything and adopt a totally foreign process? That’s scary. It should be scary.

Growth does not come without risk. And the risk is not simply not improving relative to the investment received. The risk is that your organization actually slows down and becomes far less effective than you were with prior to trying to scale up. This actual risk is worse than the principle of diminishing returns, which states that additions to an input yield progressively smaller, or diminishing, increases in output. No, this risk is captured in Brooks Law. The first formulation of Brooks Law states that adding resources to a late software project makes it slower. 

There is no small amount of research that has been done in this area and the principal causes of the slowdown described in Brooks Law are as follows:

Indivisible work. Nine women can't make a baby in one month.

Onboarding time. Adding resources saps the time of existing productive resources.

Communication channel overhead.  Everyone working on the same task needs to keep in sync, so as more people are added they spend more time trying to find out what everyone else is doing. Consider three feature teams that need to maintain general alignment on technical architecture and product vision. There are three possible lines of communication between them. One line between each team. Now let’s double that to six teams. There are now 15 lines of communication between those teams. A 100% increase in resources has created a 400% in coordination overhead. Let’s assume you are fortunate enough to need to grow your team resources by 200%. This takes your coordination overhead to 1100%! As you can see, this is untenable and we are only talking about the implications of moving from 3 to 9 teams.

Without blindly adopting any one of the highly complex scaled agile systems, what can be done to keep your organization’s existing cadence and address the above problems? Before we address each of these points, there is good news. If you are reading this in anticipation of growth and a scaling challenge, you have already won a significant battle. The most important thing an organization can do to prevent Brooks Law is to get in front of it and address it before it happens. Fixing the scaling problem before it happens is the most effective measure for preventing it. If this is not the case and you are already feeling the pain of growing inefficiencies, there is hope. We’re going to step through each pain point and address them with proven mitigation strategies.

To address the divisibility problem, ensure you are organized around user-facing features leveraging feature teams. This might seem obvious because if you are already doing Scrum” then you are already organized in this way. But, sadly, it is very possible to use the same language of scrum while not being doing scrum at all. Let’s review a few things that should be true if you are really operating in a feature team way. To review, a feature team is “a cross-functional and cross-component team that can pull end-customer features from the product backlog and complete them.” This setup has a number of practical consequences.

A feature team should have dedicated, not frequently changed, team members.

Feature teams should deliver new “vertically sliced” capabilities (stories) and not just a stream of indiscriminate engineering tasks.

A feature team should work within a clearly defined feature area with a bounded context.

Feature teams should employ micro-services and micro-frontends in order to retain autonomy and maintain decoupling from one another.

The above practices address the divisibility problem by slicing an application up by feature areas and works backward from the highest point of value, user-facing capabilities.To mitigate the ramp-up problem, implement the following strategies.

To mitigate the ramp-up problem, implement the following strategies:

Build new teams by seeding them with existing experienced people.

Make the engineering onboarding runway-to-productivity as short as possible. Get a baseline for how long it takes new engineers to be productive and then try to cut that time my introducing things like turn-key environment setups and automatically generated helpful documentation.

Capture and reuse learning sessions in the form of instructional videos that can be consumed during by new folks during the onboarding process.

To reduce communication-channel overhead, implement the following measures:

A recurring scrum-of-scrums to address feature team coordination.

Architecture meetings for each tribe to socialize design patterns.

Iterative delivery practiced in such a way that new features get merged every sprint to ensure convergence, not divergence.