Agile teams usually work closely together and therefore have little need to document how they are doing things. In addition to that, agile teams usually seek to automate repetitive tasks and have their process descriptions in form of scripts.

But if the need arises, that a team decides to document how specific things should be done, the checklist document type is useful. It may also be the first attempt to describe a process before it is scripted. Some processes may not be scriptable, because they mainly describe the interaction between roles in the team. The document may also concentrate on answering the why instead of the how questions. It may be a mere anchor to reference a script from the wiki documentation.