← ClaudeAtlas

desk-trade-lifecyclelisted

How one trade travels the StrikeGrok desk from first idea to written review - the seven stages, who owns each, the proposal file, the ticket format, what counts as approval, and when a proposal is live, closed or void. Use whenever the user wants to open, adjust or close a position, and whenever any Bot is about to write to the exchange.
Mendurim/strikegrok-trading-desk · ★ 0 · AI & Automation · score 75
Install: claude install-skill Mendurim/strikegrok-trading-desk
# Trade lifecycle Every change to a position travels the same seven stages in the same order. Missing one is a defect, not a shortcut — the stages exist because each catches something the others do not. The Desk Lead keeps things moving; whoever owns a stage does its work. ``` idea -> evidence -> risk sign-off -> user approval -> execution -> reconciliation -> review DL MA/RA RM user ET ET TR ``` A quick trade runs all seven quickly. It does not run fewer. ## 0. Open the proposal **Desk Lead.** The moment an idea appears — from the user, the Strategist or a routine — give it an id of the form `SG-YYYYMMDD-NN`, counting up within the day, and start `/workspace/trading-desk/proposals/<id>.md`: ```markdown # SG-20260910-01 - opened: 2026-09-10 14:02 UTC by user - market: ADA-USD - idea: long ADA on a retest of 0.2100, invalidated below 0.1995 (user's idea) - status: evidence ## evidence ## risk ## approval ## execution ## reconciliation ## review ``` Each stage appends beneath its heading and nothing is rewritten. This file is the trade's record; the chat is only context around it. ## 1. Evidence **Market Analyst, plus Research Analyst whenever the idea rests on anything outside the exchange.** The Desk Lead asks for exactly what sizing and execution will consume, no more: mid, mark and index; the current funding rate and when it next charges; open interest and 24-hour volume; executable depth within 5, 10