Prompt Builder and Build Plans

Prompt Builder turns an incomplete new EA or indicator request into a specification that can be implemented in stages. Xen can offer it before the first build when important decisions are missing or several features depend on each other. The review gives you Plan with Prompt Builder, Build in Xen anyway and Edit original request.

The offer is intended for new builds, rather than every message in an established project. A focused modification should not need a new plan. If you proceed with an ambiguous request, read the returned assumptions because Xen still needs some interpretation of the missing rules.

Answer the questions

Questions focus on details that affect implementation. For an EA, these can include signal timing, direction, sizing, exits or sessions. For an indicator, they can concern calculations, display and confirmation. Answer with the behaviour you want to observe rather than guessing which MQL5 function should implement it.

Let Xen Answer for Me supplies editable suggestions. Review every answer before composing the plan, especially risk, repeated trades and stop distances. Suggestions are design choices for you to approve, not facts about your intended strategy. Edit them until they describe the system you want to test.

Review the stages

The Build Plan explains the approach, records assumptions and presents a sequence of prompts. Read the stages together before starting. An EA can establish signals and basic exits first, then add sizing and trailing controls. An indicator can establish its calculation before display details and alerts.

Correct wrong assumptions at this point instead of carrying them through several files. Each stage should have an observable outcome, such as one entry per completed-bar signal. Broad goals such as “make it robust” need a clearer explanation of what should change and how you will check it.

Test between stages

Run the first stage and keep the complete returned source. Compile it in MetaEditor and inspect the relevant behaviour on a chart or in Strategy Tester. Continue when that stage works, or return a focused description of the discrepancy before adding another feature.

A plan organises development but does not replace inspection. Pin or download a tested version before a substantial change, then use Requirements Verification against the final agreed rules. Keep local test notes alongside the .mq5 files so you know which version produced each result.