Six analysts, one report
A research desk built entirely out of prompts — scanner, chart, news, quant, risk, plan
No code, no broker connection, no execution — six prompted analysts that run in strict order over data you paste, and hand back one report ending in READY FOR HUMAN REVIEW. The design discipline is the interesting part: every analyst is forbidden from inventing a number, and one of the six exists purely to try to kill the idea.
This is a research and decision-support workflow, not a trading bot. Nothing in it connects to a broker or places an order. It never invents prices, news or results — you paste verified data, or it fetches and cites, and you check every figure. Educational only, not investment advice. Trading involves substantial risk, AI output can be wrong or incomplete, and every decision remains yours.
Each analyst sees your input and every previous output
Strict order. The prompt refuses to skip a stage — ask it to, and it names the one you are missing.
Which symbols deserve research
Screens what you supply on volume, momentum, volatility, price action, structure, relative strength and liquidity. Ranks for research — it is explicitly barred from naming a “best trade”, and from claiming it scanned the market when all it saw was your table.
Trend, levels, structure, invalidation
Reads your screenshots and pasted indicator values. Describes only what is visible, labels every line FACT or VIEW, and must not read a price it cannot see. No entries, exits or targets.
Catalysts, events, sources
Organises verified news, earnings, guidance and economic events, each marked CONFIRMED or UNCONFIRMED. Anything it cannot cite is left out and listed under MISSING.
Bull, base and bear as conditions
Works only from the historical rows you paste. Any count must come from those rows and state the sample size. Fabricating backtests, win rates, expectancy or probabilities is forbidden — the honest answer is INSUFFICIENT DATA.
Actively tries to kill the idea
Hunts downside, volatility versus stop width, liquidity, event risk, sizing arithmetic, conflicting signals and missing information. One verdict: REJECT, NEEDS MORE RESEARCH, or CONTINUE TO PLAN.
Assembles, adds nothing
Fills the template from the five outputs, copying figures exactly and preserving every NOT PROVIDED. Final status is always READY FOR HUMAN REVIEW — a document, never an order.
The risk stage is the load-bearing one, and its wording is deliberate. Its best outcome does not mean “take this trade” — it means the research is finally complete enough for a human to look at. A workflow whose most positive verdict is still only “ready to be reviewed” is one that cannot quietly talk you into anything.
What you need — the manual version
And for the optional automated version
One rules block, appended to every analyst
The guide repeats this verbatim at the end of all six prompts. It is shown once here — append it to each analyst prompt below rather than reading it six times. It is doing most of the safety work.
Scanner
Paste a table of what you are watching: symbol, price, % change, volume, average volume, day range, ATR or % range, sector, timestamp, source.
Chart analyst
Attach a daily chart (6 months) and an intraday chart (5m or 15m, today and yesterday). Paste indicator values if you have them.
News analyst
Paste headlines, the latest earnings release or guidance, and the economic calendar — each with a link and timestamp.
Quant analyst
Paste historical data — exported daily OHLCV, plus the index over the same period for regime context.
Risk manager
Paste the four previous outputs. Its only job is to find reasons the setup fails.
The plan template
The plan stage fills this from the five outputs and adds nothing. Copy it into your notes document.
The master prompt — all six in one
Paste once into a project’s instructions or at the top of a chat, then feed it your symbol, screenshots, market data, news and indicators. This is the one to take if you take only one thing.
If you want alerts to trigger it
The honest architecture. Charting software does not talk to the chat product directly — its alert hits a webhook you own, and your backend calls the model API. Webhook alerts need a paid charting tier plus two-factor auth.
There is no broker API, no order placement, and no code path that sizes or sends a real trade. The webhook carries only the alert’s numbers, so the model still sees nothing you did not pass it. Chart screenshots are not in the webhook at all — the automated chart stage works from numeric fields and marks the rest MISSING DATA. Secrets live in .env, never in the front end.
Build prompt for a coding agent
Open an empty folder and paste this. The NEVER clause at the end is the important line.
The three things it must never invent
Five-minute quick start
The prompts and template follow the source guide, with one editorial change: the identical rules footer repeated at the end of all six prompts is factored out and shown once, since reading it six times helps nobody. The source names a specific chat model and tier throughout; those are left generic here, because model names and availability move faster than the workflow does and pinning one dates the whole thing. The worked example in the original is explicitly fictional and is not reproduced.