execution

Modify execution engine components within a controlled development environment.

2|2|Updated Feb 12, 2025

Search Tags:#testing #python #execution #engineering #risk-management #alpaca #order-management

Ready to run

npx skills add https://github.com/kimrejstrom/alpacalyzer-algo-trader --skill execution

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: execution
Source: https://github.com/kimrejstrom/alpacalyzer-algo-trader/tree/main/.claude/skills/execution
Command: npx skills add https://github.com/kimrejstrom/alpacalyzer-algo-trader --skill execution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables safe modification of the execution engine, signal queue, position tracker, cooldown manager, or order manager.

Core Features & Use Cases

Scope: Constrained changes to the execution subsystem, tests, and configuration to avoid unintended impacts on strategies or agents.
Use Case: You need to update the execution cycle to adjust the order flow or add a custom processing step in a test environment.

Quick Start

Apply changes to the execution layer by editing src/alpacalyzer/execution/.py and related test files under tests/test_execution_.py, then run the execution test suite.

Frequently Asked Questions about execution

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

FAQPage Schema

How do I safely modify an order execution engine without breaking strategy logic?▼

To safely modify an execution engine, constrain changes to the execution subsystem files and run the dedicated execution test suite in a controlled development environment. This isolation prevents unintended impacts on strategies or agents while updating the order flow.

What is the safest way to add a custom processing step to an order management workflow?▼

The safest way to add custom processing steps to order management is editing the execution layer source files and updating corresponding test files. This controlled approach ensures risk-free updates to the order flow within a test environment.

Can I update the position tracker and signal queue without affecting active trading agents?▼

Yes, you can update the position tracker and signal queue without affecting agents by constraining modifications to the execution subsystem. This isolated change approach enforces a well-defined interface to avoid unintended impacts on strategies.

How do I test execution layer changes for risk management before deploying to live trading?▼

Test execution layer changes by editing the execution source files and running the execution test suite under tests/test_execution_*.py. This comprehensive testing practice in a controlled development environment ensures risk-free updates to the engine.

Does modifying the cooldown manager in an execution workflow require isolated testing?▼

Yes, modifying the cooldown manager requires isolated testing within the execution subsystem. Enforcing a well-defined interface and running comprehensive tests ensures that changes to the cooldown manager do not impact strategies or agents.

What are the limitations of updating the execution layer in a Python trading system?▼

Execution layer updates are limited to the execution subsystem, including the engine, signal queue, position tracker, cooldown manager, and order manager. Changes must avoid unintended impacts on strategies or agents by enforcing a well-defined interface and isolated testing.