Watchlist

Watchlist

Manage the curated watchlist: add tickers with alert extraction, remove tickers, or display the current list.

Commands

• /watchlist add TICKER "reason" — add ticker with automatic alert level extraction
• /watchlist add TICKER --breakout 950 --support 880 — add with explicit levels
• /watchlist remove TICKER — remove ticker from watchlist
• /watchlist show — display current watchlist in formatted table

Watchlist Location

The watchlist lives in the plugin's watchlist/ directory at ${CLAUDE_PLUGIN_ROOT}/watchlist/. Files are dated JSON (e.g., 2026-05-17-tech.json). The active watchlist is the most recent file in that directory.

Legacy path (if referenced elsewhere): ~/trading-journal/watchlist.json

Reference Files

• ${CLAUDE_PLUGIN_ROOT}/skills/shared/tool-map.md — MCP tool names and parameters

---

/watchlist add TICKER "reason"

Steps

1. Parse the reason string to extract alert levels:
   • Look for price levels that suggest breakout (resistance, "breaks above", "above $X")
   • Look for support levels ("holds $X", "support at", "above $X")
   • Look for pattern references ("cup and handle", "bull flag", "ascending triangle")
2. Determine asset class:
   • If ticker matches known crypto symbols (BTC, ETH, SOL, etc.) -> crypto
   • Otherwise -> equity
3. Optionally fetch current price context via mcp__tradingview__combined_analysis to validate the alert levels make sense relative to current price
4. Append entry to the active watchlist file:

{
  "ticker": "TICKER",
  "added": "YYYY-MM-DD",
  "source": "manual",
  "direction": "LONG|SHORT",
  "sector": "sector name if known",
  "thesis": "user's reason verbatim",
  "entry_zone": {
    "type": "breakout|pullback|tbd",
    "low": null,
    "high": null,
    "note": "extracted or explicit"
  },
  "stop": null,
  "target": null,
  "regime_at_scan": "current regime if known",
  "rsi_at_scan": null,
  "notes": "any additional context"
}

Explicit Levels

When user provides --breakout or --support flags:

/watchlist add NVDA --breakout 950 --support 880

Map directly:

• --breakout VALUE -> entry_zone.high = VALUE, entry_zone.type = "breakout"
• --support VALUE -> stop = VALUE (approximate stop reference)

Alert Extraction Heuristics

When parsing the free-text reason:

• Numbers preceded by "above", "breaks", "breakout" -> breakout_level
• Numbers preceded by "support", "holds", "floor" -> support_level
• Pattern keywords -> pattern field
• Direction keywords ("bullish", "long", "short", "bearish") -> direction

---

/watchlist remove TICKER

Steps

1. Read the active watchlist file from ${CLAUDE_PLUGIN_ROOT}/watchlist/
2. Find the entry matching the ticker (case-insensitive)
3. Remove it from the array
4. Write the updated file back
5. Confirm removal to the user

If ticker not found, report that it's not on the watchlist.

---

/watchlist show

Steps

1. Read the active watchlist file from ${CLAUDE_PLUGIN_ROOT}/watchlist/
2. Display in a formatted table:

WATCHLIST -- YYYY-MM-DD (N tickers)
====================================
TICKER  | DIR   | SECTOR          | ENTRY ZONE        | STOP    | TARGET  | ADDED
--------|-------|-----------------|-------------------|---------|---------|----------
SEDG    | LONG  | Solar           | PB $48-52         | $42.94  | $79.59  | 2026-05-17
AEVA    | LONG  | Tech/Lidar      | PB $18-18.5       | $16.83  | $27.83  | 2026-05-17
...

3. For each entry, show a one-line thesis summary
4. Flag any tickers where the current price has already passed the entry zone (if able to check)

---

Discovery-Added Entries

When the trade-scan discovery layer adds tickers to the watchlist (source: discovery_scan), it populates all fields including entry_zone, stop, target, and notes. These are richer than manual entries and should be preserved as-is.

---

Error Handling

• Watchlist file doesn't exist -> create it as an empty array, then proceed
• Duplicate ticker on add -> warn user, ask if they want to update the existing entry
• JSON parse error -> report the error, do not silently overwrite