사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/tradermonty/claude-trading-skills --skill breakout-trade-planner시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Breakout Trade Planner
Generate trade plans from VCP screener output following Mark Minervini's breakout methodology. Calculate position sizes using worst-case entry prices, enforce portfolio risk limits, and output Alpaca API-compatible order templates.
When to Use
- User has VCP screener JSON output and wants trade plans
- User asks for breakout entry/stop/target calculation
- User wants Alpaca order templates for VCP breakout candidates
- User needs position sizing with portfolio heat management
Prerequisites
- VCP screener JSON output with
schema_version: "1.0" - No API keys required (works with local JSON files)
- No external skill dependencies (position sizing is built-in)
Workflow
Step 1: Generate Trade Plans
Run the planner with VCP screener output:
bash
python3 skills/breakout-trade-planner/scripts/plan_breakout_trades.py \
--input reports/vcp_screener_YYYY-MM-DD.json \
--account-size 100000 \
--risk-pct 0.5 \
--output-dir reports/Step 2: Review Output
Read the generated JSON and Markdown reports. Present:
- Actionable Orders — Pre-breakout candidates with order templates
- Revalidation — Breakout-state candidates needing live confirmation
- Watchlist — Developing VCP candidates to monitor
- Rejected/Deferred/Constrained — Candidates filtered by Gate or portfolio limits
Step 3: Explain Trade Plans
For each actionable order, explain:
- Entry levels (signal vs worst-case) and stop-loss placement
- R-multiple targets and reward-risk ratio
- Two execution modes: preplace (stop-limit) vs postconfirm (limit after 5min confirmation)
- Portfolio risk contribution and cumulative heat
- Broker and intraday constraints: these templates are planning artifacts, not broker permission. If the plan could create same-day round trips or use margin, confirm the user's broker-specific intraday/day-trading controls. FINRA replaced the old pattern-day-trader day-count and $25,000 minimum-equity requirements with intraday margin standards effective 2026-06-04, with broker phase-in allowed through 2027-10-20.
Minervini Gate (Filtering Criteria)
Candidates must pass ALL conditions:
| Condition | Pre-breakout | Breakout |
|---|---|---|
| valid_vcp | True | True |
| rating_band | good/strong/textbook | good/strong/textbook |
| riskpctworst | <= 8.0% | <= 8.0% |
| breakout_volume | — | True |
| distancefrompivot | — | <= maxchasepct |
| current_price | — | <= worst_entry |
CLI Parameters
| Parameter | Default | Description |
|---|---|---|
| --account-size | (required) | Account equity in dollars |
| --risk-pct | 0.5 | Base risk % per trade |
| --max-position-pct | 10.0 | Max single position % |
| --max-sector-pct | 30.0 | Max sector exposure % |
| --max-portfolio-heat-pct | 6.0 | Max total open risk % |
| --target-r-multiple | 2.0 | Take-profit R-multiple |
| --stop-buffer-pct | 1.0 | Stop buffer below contraction low |
| --max-chase-pct | 2.0 | Max chase above pivot |
| --pivot-buffer-pct | 0.1 | Pivot buffer for buy-stop trigger |
| --current-exposure-json | None | Existing portfolio exposure |
Output
breakout_trade_plan_YYYY-MM-DD_HHMMSS.json— Structured plans with order templatesbreakout_trade_plan_YYYY-MM-DD_HHMMSS.md— Human-readable report
Exchange Calendar and Replay
Install requirements.txt before running the planner. --as-of accepts either YYYY-MM-DD (00:00 America/New_York) or an offset-bearing ISO-8601 timestamp. Plan validity uses the current not-yet-closed XNYS session or the next real session after a close, weekend, or exchange holiday.
Resources
references/minervini_entry_rules.md— Entry methodology and rules
