Use when open-xquant artifacts must be checked for version/run/final traceability before comparison, report review, migration, or final selection.
Compile an open-xquant strategy spec preview and audit that material SPEC execution semantics are preserved in compiled_plan.json before backtests.
Audit strategy_idea_brief.json and the brainstorm conversation before strategy_spec.yaml construction begins.
Audit strategy_spec.yaml field provenance before backtests.
Author workspace-local OpenXQuant custom components from component_request.json, with tests, manifest hashing, catalog refresh, and no global SDK mutation.
Guide a user through the open-xquant pre-spec strategy idea workflow and produce strategy_idea_brief.json before any strategy_spec.yaml work begins.
Use when report chart assets, figures, visual evidence, plotting scripts, or notebook-like assets are required for an open-xquant experiment report.
Configure and reason about open-xquant trading rules, exits, risk holds, and rebalance limits; use when the user asks for stop loss, take profit, drawdown guards, holding limits, or rule components.