desk-trade-lifecycle
FeaturedThe end-to-end procedure for one trade on the HyperGrok desk - from an idea to a reviewed, journaled result - with the ticket format, who owns each stage, and what "done" looks like. Use whenever the user wants to open, adjust or close a position, or whenever any Bot is about to touch the exchange write path.
Install
Quality Score: 88/100
Skill Content
Details
- Author
- galleonlabs
- Repository
- galleonlabs/hypergrok-trading-desk
- Created
- 3 weeks ago
- Last Updated
- yesterday
- Language
- Python
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
desk-trade-lifecycle
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.
desk-operating-model
How the HyperGrok trading desk works as a team of Grok Bots - roles, seats, shared workspace, evidence standard, approval model and handoff format. Use when setting up the desk, when a Bot is unsure who owns something, or when a request does not fit the normal trade lifecycle.
desk-operating-model
The rules every Bot on the StrikeGrok desk follows - who holds which job, where the desk keeps its files, what counts as evidence, how the user's approval works and why it is not the gate, and the format for handing work between Bots. Use when setting up the desk, when ownership of a task is unclear, or when a request does not fit the ordinary trade lifecycle.