Use when the user wants to run their daily pre-market workflow — a structured morning brief covering economic risk, market health, geopolitical events, news digest, sentiment scores, strategy signals, portfolio review, open orders, and trade decisions.
Use when the user wants to analyze, simulate, or execute an options strategy — covered calls, protective puts, spreads, iron condors, straddles, earnings plays — or needs Greeks analysis, P/L simulation, IV assessment, or position sizing for options trades.
Use when the user wants a comprehensive portfolio review — allocation analysis, diversification health, risk metrics, rebalancing recommendations, or position-level trim/add/hold/sell action plans.
Use when invoked as a subprocess to process open DEV inbox tickets in the trader project. Triggered by dev-inbox-pending.json flag file. Implements fixes using TDD + superpowers workflow, replies to each ticket, clears flag when inbox is empty.
Use when running, testing, or automating the trader CLI tool — invoking commands, parsing output, placing orders, fetching quotes, or reading account/position data.
Use when the trader agent needs to file, query, or review a DEV ticket. Single-channel communication between the agent and the developer over .trader/events.jsonl. Triggers on "I need DEV to fix X", "file a DEV ticket", "is DEV-NNN done", "what's open in the dev inbox", or any time the agent identifies a bug, missing feature, or config drift it cannot self-fix.
Use when validating a trading strategy through backtesting, stress-testing parameters, evaluating out-of-sample performance, or deciding whether to deploy, refine, or abandon a strategy using `trader strategies backtest` and `trader strategies optimize`.
Use when the user wants a trend analysis, support/resistance levels, pattern recognition, or probability-weighted price scenarios for a specific ticker.