skills.rest
Leiisawesome
LeiisawesomeCOMMUNITY
Explore all skills by this author →
GitHub

live-execution

Translate trading signals into live broker executions with idempotent order handling.

Updated Mar 2, 2026
Search Tags:#risk-management#idempotency#state-machine#safety-controls#order-routing#live-execution#backtest-parity
One-click install
npx skills add https://github.com/Leiisawesome/feelies --skill live-execution
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: live-execution
Source: https://github.com/Leiisawesome/feelies/tree/main/.cursor/skills/live-execution
Command: npx skills add https://github.com/Leiisawesome/feelies --skill live-execution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Live Execution Architect translates signals into safe, latency-aware live trades and ensures parity with backtests through explicit state machines, idempotent order handling, and robust safety controls.

Core Features & Use Cases

  • Idempotent order submission to prevent duplicate executions
  • Explicit order state machine governing CREATED, SUBMITTED, ACKNOWLEDGED, PARTIALLY_FILLED, FILLED, CANCEL_REQUESTED, CANCELLED, REJECTED, EXPIRED
  • Broker-ground truth reconciliation and deterministic order IDs
  • Safe broker integration with retry, timeout, and drift-detection mechanisms
  • Safety controls including kill switches, circuit breakers, and capital throttling
  • Backtest/live parity enforcement to detect structural drift
  • Use cases: live order execution, broker integration, kill switch/circuit breaker deployment, and drift monitoring

Quick Start

Configure and run the live-execution pipeline to translate signals into safe, latency-aware trades with idempotent orders and broker reconciliation.

Frequently Asked Questions about live-execution

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent duplicate live order executions when sending trading signals to a broker?▼

Idempotent order submission prevents duplicate live order executions by assigning deterministic order IDs to every trading signal. This guarantees that retried or delayed requests are recognized and processed exactly once, avoiding unintended position accumulation during broker communication timeouts.

What is an order state machine and how does it manage live execution lifecycle?▼

An order state machine governs the live execution lifecycle through explicit states like CREATED, SUBMITTED, PARTIALLY_FILLED, FILLED, and CANCELLED. It tracks each order's progression, ensuring safe transitions and preventing invalid actions during latency-aware live trading operations.

How do I enforce backtest parity and detect structural drift in automated trading systems?▼

Backtest parity enforcement detects structural drift in automated trading systems by comparing live execution behavior against backtested expectations. It monitors explicit order state machines and position reconciliation to identify and alert on discrepancies between simulated and live broker environments.

What safety controls are needed for live broker integration and order routing?▼

Safety controls for live broker integration include kill switches, circuit breakers, and capital throttling. These mechanisms protect automated order routing by halting trades or limiting exposure during latency spikes, drift detection, or unexpected broker reconciliation failures.

How does position reconciliation work against a broker's ground truth?▼

Position reconciliation against a broker's ground truth continuously compares your internal tracked positions with the broker's actual records. This process identifies and corrects drift in filled quantities, ensuring your automated trading system maintains accurate state during live execution.

Can I use this approach for live execution in any automated trading system?▼

Yes, this approach applies to live execution in any automated trading system requiring broker integration. It suits systems needing risk management, order routing, and safety controls, provided they can implement the orchestrator-backed pipeline and deterministic order ID framework.

Related Skills

Explore More Software Engineering Skills→
vignesh2027vignesh2027
6

quant-trader

Generate structured trading signals with entry, target, stop_loss, and Kelly Criterion risk sizing.

Community
Advanced
skrymerskrymer

backtest

Run backtests against the Udgaard API and save trade-by-trade results.

Community
Advanced
hxhyyyhxhyyy

vnpy-export

Translate Vibe-Trading strategy logic into vnpy CtaTemplate Python classes.

Community
Advanced
rizaldiemrizaldiem

spring-boot-saga-pattern

Coordinates distributed transactions across Spring Boot microservices using compensating actions and Kafka or RabbitMQ messaging.

Community
Advanced