Probably the simplest option is to use an event rule.
Set up an event rule to trigger on the (successful) completion of the last job stream in the sequence with an action to submit the job stream sequence again. The action will need to be a single action as there is no way to execute multiple actions in a specific order. So you would need to have a command action that runs a script to ensure the submission of the job streams in the correct sequence or, if your naming convention allows it, use a single generic conman submit schedule command (assumes the job stream names are ascending numeric order to match the execution sequence!)
You could also use an event rule that submits each job stream in the sequence as each job stream in the sequence completes, but this would need each job stream to have a dependency on a previous instance of the job stream (i.e. FOLLOWS PREVIOUS) so that they would queue up behind each other correctly
You will also need to consider what effect start-of-day will have on the complete process if the sequence of job streams cross the start-of-day (JnextPlan/FINAL) processing time