~ / rigs / hamitsarmis / strategy-team

hamitsarmis/strategy-team

Claude Code agent team that researches, backtests and vets trading strategies against pre-registered criteria. Engine, registry and Docker stack are built; it places no orders.

↗ GitHub ★ 0 MIT updated 12d ago project Claude Code
share on X
ARCHETYPE
Pragmatist
A balanced, no-drama setup: some rules, some tools, nothing extreme.
CONTEXT TAX · EVERY TURN
~855 tokens
Featherweight · median rig: 2.3k · breakdown
GUARDRAILS
1/5
No YOLO mode · details
Quality 15/100 Guardrails v2

Copy this rig

# review before running: this installs third-party code
$ npx degit hamitsarmis/strategy-team/.claude ./rig-strategy-team  # inspect, then merge into .claude/

MCP servers are added to Claude Code at local scope; env vars are shown as YOUR_… placeholders — we never store values. Files are fetched with degit into a separate folder so you can review before merging.

$ curl -fsSL --create-dirs -o .claude/agents/developer.md https://raw.githubusercontent.com/hamitsarmis/strategy-team/main/.claude/agents/developer.md
$ curl -fsSL --create-dirs -o .claude/agents/manager.md https://raw.githubusercontent.com/hamitsarmis/strategy-team/main/.claude/agents/manager.md
$ curl -fsSL --create-dirs -o .claude/agents/researcher.md https://raw.githubusercontent.com/hamitsarmis/strategy-team/main/.claude/agents/researcher.md
$ curl -fsSL --create-dirs -o .claude/agents/reviewer.md https://raw.githubusercontent.com/hamitsarmis/strategy-team/main/.claude/agents/reviewer.md

Merge into .claude/settings.json (project) or ~/.claude/settings.json (user). Hook commands reference scripts in the source repo — copy those too.

{
  "permissions": {
    "deny": [
      "Read(./data/holdout/**)",
      "Read(../strategy-team-holdout/**)",
      "Bash(docker *)"
    ]
  }
}

Subagents (4)

developer
model: opus
Implements one strategy spec as strategies/<id>.py against the fixed engine interface, writes its causality test, runs engine.check, engine.prescreen and the full in-sample run, and records status in
managerApplies the pre-registered CRITERIA.md to a reviewed strategy's in-sample and out-of-sample results and decides drop, rework (once) or promote to the one-shot holdout; finalizes holdout results into a
researcherFinds candidate trading strategies from tiered sources and writes structured, testable specs into specs/, registering them in the registry. Does NOT judge edge and writes no code. Use for /research, t
reviewerAdversarial reviewer for developed strategies. Audits the code for lookahead, cost omissions, undeclared parameters and session leaks, then runs the engine's fixed robustness matrix to try to break th

Slash commands (7)

/decide/develop/promote/research/review/run-batch/status

Permissions

deny (3)
Read(./data/holdout/**)
Read(../strategy-team-holdout/**)
Bash(docker *)
ask (0)
—
allow (11)
Bash(uv run python -m registry *)
Bash(python -m registry *)
Bash(uv run python -m engine.*)
Bash(python -m engine.*)
Bash(uv run python -m notify *)
Bash(python -m notify *)
Bash(uv run pytest *)
Bash(date *)
Bash(git status *)
Bash(git log *)
Bash(git diff *)

Similar rigs

copied ✓