Writing clear strategies

Short checklist for describing rules the model can turn into code. Vague text produces vague code; specificity wins.

Checklist

  • Name the asset and timeframe
    Example: daily bars on AAPL, or a basket you list tickers for. Say long-only unless you mean otherwise.
  • Entry and exit in the same description
    If you only say when to buy, add at least one rule for when to flatten or take profit.
  • Use numbers for indicators
    RSI 14, SMA 20 / 50, MACD 12-26-9 — not “fast vs slow average.”
  • One primary signal
    Add filters after the core idea works. Too many conflicting rules at once are hard to validate.

Template you can paste

Universe: [tickers]. Bars: daily.
Buy when [indicator A] crosses above [indicator B] and [filter] is true.
Sell when [exit condition], or after [N] bars in the trade, whichever comes first.
Size: risk [x]% of equity per trade using [stop definition].

More examples

The full guidelines page has good and bad examples plus supported indicators.

Open strategy guidelines