breakout-trade-planner — Claude Code skill: breakout trade plans
Turns VCP screener output into Minervini-style trade plans with entry, stop and target levels, position sizing and Alpaca order templates.
npx skills add tradermonty/claude-trading-skills --skill breakout-trade-planner -a claude-codeWhat breakout-trade-planner does
Feed the skill a VCP screener JSON file carrying schema_version: "1.0" and it returns finished trade plans. Position size is derived from the worst-case entry price, portfolio risk limits are enforced, and the order templates match the Alpaca API: a stop-limit bracket for pre-placement and a limit bracket for entries taken after confirmation. Two files come out — breakout_trade_plan_YYYY-MM-DD_HHMMSS.json with the structured plans and a .md report you can read.
Every candidate has to clear the Minervini Gate. That means valid_vcp, a rating in good/strong/textbook, worst-case risk at or under 8.0%, and for breakout-state names both volume on the move and a distance from pivot inside --max_chase_pct. Names filtered out by the gate or by portfolio caps land in their own buckets, so nothing disappears silently.
Install the packages listed in requirements.txt first; without them the planner will not run. No API keys are involved, since everything is computed from local files. Treat the order templates as planning artifacts rather than broker permission: if a plan could produce same-day round trips or margin use, check your broker's intraday controls. FINRA replaced the old pattern-day-trader day-count and $25,000 minimum-equity rules with intraday margin standards effective 2026-06-04, and brokers may phase in through 2027-10-20.
What it helps with
- size a position off the worst-case entry price
- split screener candidates into orders, revalidation and watchlist
- keep total open risk under a portfolio cap
- produce an Alpaca stop-limit bracket template
- drop candidates that fail the Minervini Gate
Example prompts for the agent
- Build trade plans from
reports/vcp_screener_2025-01-15.jsonwith account size 100000 and risk 0.5% - Walk me through the entry and stop levels for each order and why the position is that size
- Rerun the plans with
--max-portfolio-heat-pct 4.0
How to install breakout-trade-planner
1Skills CLI (Vercel)
npx skills add tradermonty/claude-trading-skills --skill breakout-trade-planner -a claude-code2Manually: put the files in place
~/.claude/skills/breakout-trade-planner/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/breakout-trade-planner/
1Skills CLI (Vercel)
npx skills add tradermonty/claude-trading-skills --skill breakout-trade-planner -a codex2Manually: put the files in place
.agents/skills/breakout-trade-planner/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add tradermonty/claude-trading-skills --skill breakout-trade-planner -a cursor2Manually: put the files in place
.cursor/skills/breakout-trade-planner/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install tradermonty/claude-trading-skills breakout-trade-planner2Manually: put the files in place
.github/skills/breakout-trade-planner/SKILL.md1Skills CLI (Vercel)
npx skills add tradermonty/claude-trading-skills --skill breakout-trade-planner -a gemini-cli2Platform CLI
gemini skills install https://github.com/tradermonty/claude-trading-skills --path skills/breakout-trade-plannerManually: put the files in place
.devin/skills/breakout-trade-planner/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add tradermonty/claude-trading-skills --skill breakout-trade-planner -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about breakout-trade-planner
How do I install breakout-trade-planner in Claude Code?
Run npx skills add tradermonty/claude-trading-skills --skill breakout-trade-planner -a claude-code. The skill lands at ~/.claude/skills/breakout-trade-planner/SKILL.md.
What does breakout-trade-planner do?
It builds Minervini-style trade plans from VCP screener output: entry, stop and target levels, position sizing against portfolio risk, and Alpaca order templates.
Does the skill need API keys?
No. The planner reads a local VCP screener JSON file. You do need the packages from requirements.txt installed before running it.
Source text
SKILL.md · MIT
--- name: breakout-trade-planner description: Generate Minervini-style breakout trade plans from VCP screener output with worst-case risk calculation, portfolio heat management, and Alpaca-compatible order templates (stop-limit bracket for pre-placement, limit bracket for post-confirmation). Use when user has VCP screener results and wants actionable trade plans with entry/stop/target levels and position sizing. --- # 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: 1. **Actionable Orders** — Pre-breakout candidates with order templates 2. **Revalidation** — Breakout-state candidates needing live confirmation 3. **Watchlist** — Developing VCP candidates to monitor 4. **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: pre_place (stop-limit) vs post_confirm (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 | | risk_pct_worst | <= 8.0% | <= 8.0% | | breakout_volume | — | True | | distance_from_pivot | — | <= max_chase_pct | | 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 templates - `breakout_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
© tradermonty · MIT · tradermonty/claude-trading-skills