Kata

1, 3, 4 are resolved.

2 -- it's better now, but it's still multiple output types, namely List[List[int]] and str.

5 -- the description is still hard to comprehend. Main point was, yet again, outlined by JohanWiltink: Give specs first, then examples. Examples should clarify specs, not introduce them.

Specs as in rules? because i have given them before explaining the examples, or something else?.

No, you haven't.

1. You should explain that the input is List[int], and the meaning of input.

2. You should provide exact output type and format (in case of strings output, you should write strings that a user has to return, i.e. 'No trajectory!')

3. You should explain the general picture, before coming to details. You are writing The number 1 in a sequence has an important function which is to converge any number of branches to 1., while you haven't provided an explanation, that user will be given a sequence, and what a branch is, and so on.

How about now i think i have covered most of the points hopefully!.

It is much better now.

Some points are still dubious, though:

The number 1 in a sequence has an important function which is to converge any number of branches to 1. Specify, that in only converges those branches, that... khem, branched on 1 stage. I.e., if you have beginning of sequence [1, 2, 3], there will be 2 * 3 == 6 branches total. The next 1 doesn't converge all branches, but only those that branched on the stage with 3.

Move section Return types before example section and mark it with header.

It's still not really good, that you have multiple return types. Especially, that in some cases you have lists with 2 elements, and in some cases with 3 elements. I will not suggest an improvement here, though.

Okay i understood your points, ill try work out something. Thank you!.

For 80% of description I thought that the task was parse or generate ascii diagrams with /\_!