Describe the setup in observable terms
Write down what has to be true for a setup to exist. If you use words such as “strong”, “clean” or “obvious”, explain what they mean in measurable terms. Include the instruments and timeframes you want to discuss.
Separate entry, management and exit
An entry rule is only one part of a strategy. Describe when an order should be placed, how open positions should be handled and what closes them. Explain what should happen if conditions change before an entry occurs.
Define the boundaries
List the limits and exceptions you want scoped: exposure, position sizing, trading sessions and conditions in which the system should stay out. If a provider imposes restrictions, bring the current written rules to the discussion.
Explain how you will review the build
Software acceptance and strategy profitability are different questions. Agree how the implementation will be checked against the specification, which test cases matter and what evidence should accompany the handover.
Start a conversation, not an assumption
A brief opens a scoping discussion. It does not establish feasibility, price or delivery time. Use the planner to produce a summary, then share it when you are ready. Avoid including passwords or private account credentials.