What are good principles for naming an algorithm?
The bumper sticker idea is quite smart, provided it is indeed the same general approach being applied. Otherwise it becomes gimmicky. Also, IMO, it would be better if XYZ has some functional meaning besides just being catchy, but I understand this is not always easy.

For instance, suppose A and B are heap sort and bubble sort respectively. Suppose your general approach has something to do with hashing, and makes the sort faster. A name like Hashed heap sort and Hashed bubble sort would make more sense and have better recall value/correct association than say, Snappy heap sort and snappy bubble sort. This may be an oversimplified example, but the point about functionality is worth remembering.

Ultimately, the line between gimmicky and legacy is not predefined, and it's not in your hands. Since you've already published XYZ-method A, you could see how the response to that nomenclature has been (are other authors using that name? Do your collegaues and co-workers call it by that name? Do other people see it catching on?). If the response is positive, and the above points are met, you could go for XYZ-method B. Else consider learning from this experience and make a fresh start with a new name.