The concept is a strong part of Water Margin.

The very first chapter opens with Grand Commander Hou disrespecting spirits by opening up a sealed tomb and unintentionally releasing 108 demons who presumably reincarnate as humans, a backstory to the events that follow years later.

This is well shown in the Japanese The Water Margin, but is skipped in the Chinese The Water Margin unfortunately.

The concept is also central to the Suikoden video game.

Actually, now that Ciro Santilli thinks about it, these were already likely meant as a "collectible" element by the author of the original book, as is strongly suggested by all the little illustrations of each character present on the Wikipedia page. Just like e.g. Catholic saints. It's Pokemon, but 2000 years earlier.

Ciro would notably feel many years later, that as he met random people online who were interested in improving eduction, or was otherwise networking to reach his goals, as if he were actually building up his 108 stars of destiny.

A central part, and perhaps the most interesting part of the novel, is how each character has been motivated by injustice to join the rebellion. This reminds Ciro of Final Fantasy VI

The perfect Middle Way between command-line interfaces and GUIs. A thing of great beauty.

Things to do:

Includes:

The exact relationships between those clades is not very clear as there's a bunch of extinct species in the middle we are not sure exactly where they go exactly, some hypothesis are listed at: en.wikipedia.org/w/index.php?title=Tetrapod&oldid=1053601110#Temnospondyl_hypothesis_(TH)

But at least it seems rock solid that those three are actually clades.

This is a good approach. The downside is that while you are developing the implementation and testing interactively you might notice that the requirements are wrong, and then the tests have to change.

One intermediate approach Ciro Santilli likes is to do the implementation and be happy with interactive usage, then create the test, make it pass, then remove the code that would make it pass, and see it fail. This does have a risk that you will forget to test something, but Ciro finds it is a worth it generally. Unless it really is one of those features that you are unable to develop without an automated test, generally more "logical/mathematical" stuff. This is a sort of laziness Driven Development.

Bibliography: