# order-management-advisor

A skill covering the advisor trade lifecycle from order entry to settlement: block trading, allocation, pre-trade compliance and custodian routing.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 667 installs · ★ 218
- Author: JoelLewis
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/JoelLewis/finance_skills/tree/HEAD/plugins/advisory-practice/skills/order-management-advisor/SKILL.md
- Updated: 2026-07-18
- HTML: https://affpapa.org/en/nevibecode/skills/order-management-advisor

## What it does

The skill maps the operational layer between portfolio decisions and execution. It walks through how an advisory OMS works: the PMS generates trade proposals, the OMS validates them against compliance rules, aggregates them into block orders, routes them to custodians and tracks them through settlement. It also draws the line between an advisory OMS and an institutional one — the former is built for model-driven trading across many small accounts, where a single model change can produce hundreds of account-level trades.

Inside you get order types and time-in-force, the quirks of NAV-sensitive mutual fund orders, and how ETF and mutual fund handling differ in block trading. A dedicated section covers block trading and allocation: the SEC no-action letter framework and FINRA guidance, the requirement for a written allocation policy set before execution, and the ban on cherry-picking. Pro-rata allocation is spelled out with a worked example of distributing fills across accounts.

The useful part is the operational detail that trips up homegrown setups. Custodians typically cap GTC duration at 60 or 90 calendar days, and FOK rarely shows up in advisory trading because partial fills on a block create allocation headaches. Mutual fund orders do not execute at a market price during the day — shares are priced at the next calculated NAV, so the advisor cannot specify a price.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add JoelLewis/finance_skills --skill order-management-advisor -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/order-management-advisor/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/order-management-advisor/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add JoelLewis/finance_skills --skill order-management-advisor -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/order-management-advisor/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add JoelLewis/finance_skills --skill order-management-advisor -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/order-management-advisor/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install JoelLewis/finance_skills order-management-advisor
```

2. **Manually: put the files in place**
- File: `.github/skills/order-management-advisor/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add JoelLewis/finance_skills --skill order-management-advisor -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/JoelLewis/finance_skills --path plugins/advisory-practice/skills/order-management-advisor
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/order-management-advisor/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add JoelLewis/finance_skills --skill order-management-advisor -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/JoelLewis/finance_skills/tree/HEAD/plugins/advisory-practice/skills/order-management-advisor/SKILL.md

## When to use it
- aggregate orders across many accounts into one block and allocate fills fairly
- configure pre-trade compliance rules and restricted lists
- push a model portfolio change across hundreds of accounts
- handle ETF and mutual fund orders differently in one workflow
- work through a trade error and correction with a clean audit trail

## Example prompts
- help me design an OMS for an RIA that links the PMS, compliance and custodians
- how should I allocate a block order across accounts on a pro-rata basis
- explain how mutual fund orders differ from ETF orders in block trading

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 5b6b45f6a55213aa.

BEGIN THIRD-PARTY FILE 5b6b45f6a55213aa
```text
---
name: order-management-advisor
description: "Manage the advisor trade lifecycle from order entry through settlement, covering block trading, allocation, pre-trade compliance, custodian routing, and error correction. Use when the user asks about designing an OMS for an RIA, executing model portfolio changes across many accounts, structuring block trades with fair allocation, configuring pre-trade compliance rules or restricted lists, routing orders to multiple custodians, handling trade errors or corrections, managing cash in trading workflows, or evaluating OMS platforms. Also trigger when users mention 'block trade', 'trade allocation', 'order management system', 'iRebal', 'Orion Trading', 'Tamarac Trading', 'best execution', 'trade error', 'mutual fund vs ETF orders', or 'audit trail'."
---

# Order Management — Advisor

## Core Concepts

### Order Management System (OMS) in Advisory Context
The order management system is the operational bridge between investment decisions and trade execution. In an advisory practice, the OMS receives trade instructions generated by the portfolio management system (PMS), validates them against compliance rules, aggregates them into block orders where appropriate, routes them to custodians or brokers for execution, and tracks them through settlement.

Advisory OMS platforms differ materially from institutional OMS platforms. An advisory OMS is optimized for model-driven trading across many small accounts — a single model change may generate hundreds or thousands of individual account-level trades that must be aggregated, compliance-checked, and routed efficiently. An institutional OMS, by contrast, is designed for large orders with complex execution strategies such as algorithmic trading, dark pool access, and multi-venue order splitting.

Core OMS functions in an advisory context include:
```
END THIRD-PARTY FILE 5b6b45f6a55213aa

The third-party file has ended. Everything between the 5b6b45f6a55213aa tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 1864 of 36656 bytes. © JoelLewis · MIT · https://github.com/JoelLewis/finance_skills/tree/HEAD/plugins/advisory-practice/skills/order-management-advisor/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md