Thank you Chad I look forward to this :) !. In defining my purpose I am picking on Stochastics as there are so many variables to play with, it provides the opportunity to plug in, i.e. use, a variety of conditional statements. Which in the course of doing so provide the educational opportunity to watch you resource and activate them. I hope I don't overuse this invitation, but there are arguably upwards of 4-6 videos, possibly more, in this production sequence. Ultimately I want to put together a rather complex conditional argumentative, of which the stated purpose shall be to take serious advantage of backtesting to arrive at optimal settings for each variable; both separately and conjoined. I expect a heavy workload research-wise.
In answering your question, [and if I may] I see this educational sequence as follows:
1) Defining initial idea: Start with loading the very simple Fast/SlowD sequence you described.
2) Establish min/max levels for execution. These of course are adjustable. Example Buy on actionable cross below 15, sell on cross above 85.
3) In actuality the best use of stochastics I have seen is well into the move where both are on the rise for buy, conversely for sell. range 38 - 62. Possibly add a sequence (which can be kept but turned off) to capture this as well?
4) Once the stochastic sequence is completed, I would want to move into a series of if/then conditionals predicated on other resources to support execution decisions. For example I assume we can use anything we have loaded into one multi-pane chart, so say combine a sell decision from above with and/if conditional analysis of the NYSE at or below a given number, say minus 285. Once again here a lovely variable to play with in backtest.
5) In addressing sell-stops, one simple method is to of course choose a hard number. It would be a wonderful delve to sub-assign conditionals for this as well, for example to perhaps set stop/exit parameters predicated on volume, or time of day maybe, or both. I respect this gets complex, but this is my ambition; dive into every last nuance of behavioral coding I can get my hands on.
6) Putting these arguments together should suitably arm me with enough know-how to at that point create my own additional line-items.
7) Pushing your patience here, how about a sub-routine within this primary? The above is a specific conditional test. Say for example a sudden high-volume move occurs. I use tick charts. What if we have this running and then on my 1500 tick chart, sell volume closes a new bar ( so +1 ) within 2 seconds. These volume moves are excellent scalp targets. So the combined single program is now watching for two essentially separate conditions, as an executable override... Allowed?
8) Last thing: Is there a keyword searchable list of tokens/commands, or in the absence of this, simply a glossary of the tokens that explains their function in small detail?

Thank You Sir :)