order-management

Execute Alpaca stock orders from TradeSignal objects with idempotency and retries.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/bitandbytes/Argus --skill order-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: order-management
Source: https://github.com/bitandbytes/Argus/tree/main/.claude/skills/order-management
Command: npx skills add https://github.com/bitandbytes/Argus --skill order-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides developers in building the execution layer of an Alpaca-based trading pipeline, translating validated TradeSignal objects into live or paper orders and coordinating the daily run.

Core Features & Use Cases

  • Implements the Alpaca OrderManager, TradingPipeline orchestrator, and the run_daily entry point to turn signals into executable actions.
  • Enforces idempotency, retry with exponential backoff, and position tracking to ensure safe, repeatable daily runs.
  • Integrates with risk checks and exit logic to coordinate end-to-end daily trading workflows.

Quick Start

Run the daily pipeline to submit and manage orders for the current trading day.

Frequently Asked Questions about order-management

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

FAQPage Schema
How do I automate Alpaca order execution with idempotency and retry logic?

Automate Alpaca order execution by implementing an OrderManager that translates TradeSignal objects into live or paper orders, enforcing idempotency and applying retry backoff on API errors to ensure safe, repeatable daily runs.

What is the best way to manage a daily trading pipeline for Alpaca orders?

Manage a daily trading pipeline by using a TradingPipeline orchestrator with a run_daily entry point, coordinating validated TradeSignal objects into executable entry and exit actions while tracking positions throughout the trading day.

How do bracket orders with stop-loss and take-profit work in an Alpaca trading pipeline?

Bracket orders with stop-loss and take-profit work by submitting entry orders alongside attached exit orders, coordinating risk checks and exit logic to manage positions automatically once the Alpaca entry order is filled.

Does this order execution approach support safety checks before submitting live trades?

Yes, the order execution approach applies safety checks prior to submission, integrating risk checks and exit logic to validate TradeSignal objects before they become live or paper orders on the Alpaca platform.

Why does my Alpaca trading pipeline submit duplicate orders during daily runs?

Duplicate orders during daily runs occur when idempotency is not enforced; implementing idempotent entry and exit ordering ensures that repeated pipeline executions do not resubmit or duplicate existing Alpaca trades.

Can I run paper trading orders through the same pipeline as live trading?

Yes, you can run paper trading orders through the same pipeline, as the execution layer translates validated TradeSignal objects into either live or paper orders on Alpaca using the same orchestration logic.