メニュー
Use when invoked as a subprocess to process open DEV inbox tickets in the trader project. Triggered by dev-inbox-pending.json flag file. Implements fixes using TDD + superpowers workflow, replies to each ticket, clears flag when inbox is empty.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | dev-inbox-processor |
| description | Use when invoked as a subprocess to process open DEV inbox tickets in the trader project. Triggered by dev-inbox-pending.json flag file. Implements fixes using TDD + superpowers workflow, replies to each ticket, clears flag when inbox is empty. |
You are a DEV subprocess. Your job: read open tickets, implement each fix, reply, clear the flag.
TRADER_ROLE=dev — you MAY run trader dev reply/opt/assistants/traderPATH="$HOME/.local/bin:$PATH" uv run trader ...read ticket → plan → implement (TDD) → test → commit → reply → next ticket
PATH="$HOME/.local/bin:$PATH" uv run trader dev list --open
PATH="$HOME/.local/bin:$PATH" uv run trader dev show DEV-NNN
Process tickets in priority order: critical → high → medium → low.
REQUIRED SUB-SKILL: Use superpowers:writing-plans for any ticket with complexity M or L.
For S-complexity tickets: inline plan is fine — 3–5 steps, written here before touching code.
REQUIRED SUB-SKILL: Use superpowers:test-driven-development — write failing test first, implement minimal code to pass, commit.
Run tests with:
PATH="$HOME/.local/bin:$PATH" uv run python -m pytest tests/unit/ -q --tb=short
TRADER_ROLE=dev PATH="$HOME/.local/bin:$PATH" uv run trader dev reply DEV-NNN \
--status resolved \
--summary "One-line description of what was done" \
--commit COMMIT_SHA \
--files-touched "trader/foo.py,tests/unit/test_foo.py"
Use resolved_with_caveat + --caveat "..." if the fix is partial.
Use rejected + --summary "reason" if the ticket is invalid or already fixed.
After ALL open tickets are resolved:
PATH="$HOME/.local/bin:$PATH" uv run trader dev check
This removes .trader/state/dev-inbox-pending.json. The polling cron stops activating.
resolved if tests fail..trader/events.jsonl directly — use trader dev CLI only.depends-on), skip it and note in reply.fix(scope): short description
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Scope = the primary file's module (e.g., ibkr, pulse, catalyst).
Use when the user wants to run their daily pre-market workflow — a structured morning brief covering economic risk, market health, geopolitical events, news digest, sentiment scores, strategy signals, portfolio review, open orders, and trade decisions.
Use when the user wants to analyze, simulate, or execute an options strategy — covered calls, protective puts, spreads, iron condors, straddles, earnings plays — or needs Greeks analysis, P/L simulation, IV assessment, or position sizing for options trades.
Use when the user wants a comprehensive portfolio review — allocation analysis, diversification health, risk metrics, rebalancing recommendations, or position-level trim/add/hold/sell action plans.
Use when running, testing, or automating the trader CLI tool — invoking commands, parsing output, placing orders, fetching quotes, or reading account/position data.
Use when the trader agent needs to file, query, or review a DEV ticket. Single-channel communication between the agent and the developer over .trader/events.jsonl. Triggers on "I need DEV to fix X", "file a DEV ticket", "is DEV-NNN done", "what's open in the dev inbox", or any time the agent identifies a bug, missing feature, or config drift it cannot self-fix.
Use when validating a trading strategy through backtesting, stress-testing parameters, evaluating out-of-sample performance, or deciding whether to deploy, refine, or abandon a strategy using `trader strategies backtest` and `trader strategies optimize`.