I spent my morning shower pondering it, and after a lot of reflection strongly feel that we must do abilities before typing. I had two major reasons:
1) The kind of abilities that are most likely to derail our typing discussion (e.g. immunity-granting abilities) are unlikely to be allowed, as the connection between movepool and ability will be far too tenuous and obscure. Reachzero yesterday outlined that to fulfill our CAP, we must have a clear connection that an outsider can see; that connection won't need to necessarily be as "In Your Face" as Tough Claws or Triage, but I think it'd be hard to make an argument that ANY movepool "supports and synergizes" with say Levitate or Flash Fire - especially since reach also noted that stupidly obvious stuff, like "Adapatability powers up STAB so we gave this mon good STABs", is also off the table, so "Flash fire powers up fire attacks, so we gave it a good fire move" would also not fly.
2) While there's going to be some poll-jumping and challenges no matter what we do, there will be less risk of completely derailing our CAP and failing the concept if we go ability first. As a for-instance that I hope isn't too poll jumpy (it was in the Discord), let's say we do typing first and settle on Fire Dragon for...reasons. Analyzing future abilities or moves for that typing would be poll jumping, so we go with our gut. Now let's say we get to abilities and determine that the screamingly obvious super cool ability for that typing is, in fact, completely broken and stupid. We now have a bad choice - we can further derail our process by kiboshing moves before the movepool phase, or we can audible into a new ability other than the screamingly obvious one and pray we can still fulfill the concept without feeling like "Salamence or Mega-CharX, but with a much lower BST". Both these choices are awful, as they risk either further wrecking our process with even more poll-jumping or making an unviable or failed CAP.
If we do it the other way around, and say we're going to do a powerful Fire-type Wallbreaker with some ability that lets it spam a move and snowball out of control, then when we get to typing we can have an honest conversation about if adding Dragon typing and coverage onto that is a good idea or not. And if we decide "no", the Concept (a powerful Fire-type wallbreaker with an ability that lets it snowball out of control) still works! We can leave it mono-Fire, or add a different typing to grant different coverage or resistances for free switch-ins, or add a typing with other complimentary moves that let it be mixed or more unpredictable, or whatever. It's a much safer route imo.
1) The kind of abilities that are most likely to derail our typing discussion (e.g. immunity-granting abilities) are unlikely to be allowed, as the connection between movepool and ability will be far too tenuous and obscure. Reachzero yesterday outlined that to fulfill our CAP, we must have a clear connection that an outsider can see; that connection won't need to necessarily be as "In Your Face" as Tough Claws or Triage, but I think it'd be hard to make an argument that ANY movepool "supports and synergizes" with say Levitate or Flash Fire - especially since reach also noted that stupidly obvious stuff, like "Adapatability powers up STAB so we gave this mon good STABs", is also off the table, so "Flash fire powers up fire attacks, so we gave it a good fire move" would also not fly.
2) While there's going to be some poll-jumping and challenges no matter what we do, there will be less risk of completely derailing our CAP and failing the concept if we go ability first. As a for-instance that I hope isn't too poll jumpy (it was in the Discord), let's say we do typing first and settle on Fire Dragon for...reasons. Analyzing future abilities or moves for that typing would be poll jumping, so we go with our gut. Now let's say we get to abilities and determine that the screamingly obvious super cool ability for that typing is, in fact, completely broken and stupid. We now have a bad choice - we can further derail our process by kiboshing moves before the movepool phase, or we can audible into a new ability other than the screamingly obvious one and pray we can still fulfill the concept without feeling like "Salamence or Mega-CharX, but with a much lower BST". Both these choices are awful, as they risk either further wrecking our process with even more poll-jumping or making an unviable or failed CAP.
If we do it the other way around, and say we're going to do a powerful Fire-type Wallbreaker with some ability that lets it spam a move and snowball out of control, then when we get to typing we can have an honest conversation about if adding Dragon typing and coverage onto that is a good idea or not. And if we decide "no", the Concept (a powerful Fire-type wallbreaker with an ability that lets it snowball out of control) still works! We can leave it mono-Fire, or add a different typing to grant different coverage or resistances for free switch-ins, or add a typing with other complimentary moves that let it be mixed or more unpredictable, or whatever. It's a much safer route imo.