Strategy Backtest — Historical Performance & Optimization

Overview

Supports systematic trading strategy workflows: backtest rules on history, optimize parameters (e.g. grid search), and report results. Typical building blocks include moving-average crosses, MACD, RSI, and custom signals—implemented with libraries such as Backtrader or similar.

Trigger keywords: backtest, trading strategy, quant, algorithmic trading, Sharpe, drawdown, optimize parameters, walk-forward

Prerequisites

pip install pandas numpy backtrader matplotlib

Capabilities

1. Backtest engine — run strategies on historical OHLCV (or vendor-specific) data.
2. Performance analytics — annualized return, max drawdown, Sharpe-like ratios, win rate (definitions must match your implementation).
3. Parameter search — grid or bounded search over strategy parameters with out-of-sample caution (see references/strategy_backtest_guide.md).

Commands

Usage (from repository root)

python3 scripts/skills/strategy-backtest/scripts/strategy_backtest_tool.py backtest --strategy ma_cross --symbol SPY --period 3y
python3 scripts/skills/strategy-backtest/scripts/strategy_backtest_tool.py optimize --strategy ma_cross --fast 5-20 --slow 20-60
python3 scripts/skills/strategy-backtest/scripts/strategy_backtest_tool.py report --format markdown

Use symbols and venues appropriate to your data feed (e.g. SPY, QQQ, or local indices)—the examples above are illustrative.

Output format (for the agent’s report)

# Strategy backtest report

**Generated**: YYYY-MM-DD HH:MM

## Key findings
1. [Finding 1]
2. [Finding 2]
3. [Finding 3]

## Metrics snapshot
| Metric | Value | Notes |
|--------|-------|-------|
| CAGR | X% | … |
| Max drawdown | Y% | … |
| Sharpe (if defined) | Z | window & rf assumption |

## Analysis
[Grounded in actual run outputs—no fabricated fills or equity curves.]

## Risks & limitations
- Past performance ≠ future results; costs, slippage, and survivorship bias matter.

References

Core

• Backtrader documentation
• Backtrader on GitHub

Community & critique

• Hacker News — backtesting pitfalls
• Reddit r/algotrading

Notes

• Base all numbers on script or notebook output—never invent trades or metrics.
• Mark missing fields as unavailable instead of guessing.
• Not investment advice; comply with local regulations for research vs advisory.
• Prefer stating assumptions (fees, spread, leverage, timezone, corporate actions).