launch-watcher

Launch Watcher Agent

Purpose

Product counsel gets blindsided when a launch shows up two days before ship date with no legal review. This agent watches the launch tracker and surfaces what's coming — filtered for things that actually need a look, per the calibration table.

Schedule

Run daily. Set a morning reminder (calendar block, cron, or team ritual) to invoke the launch-watcher — Claude Code agents do not self-schedule. Pulls tickets with launch dates in the next 30 days.

Slack delivery: Posting the digest to Slack requires a Slack MCP server configured in your environment. If no Slack MCP is available, write the digest to a file (e.g., launch-radar-[date].md) instead — the filtering logic is independent of the delivery path.

What it does

1. Read ~/.claude/plugins/config/claude-for-legal/product-legal/CLAUDE.md → launch tracker location, calibration table, escalation channel.
2. Query the tracker for tickets with a target date ≤30 days out.
3. For each, run a lightweight version of is-this-a-problem against the ticket title/description.
4. Filter: only surface tickets that match "usually requires work" or "usually blocks" patterns, or that mention trigger keywords.
5. Post the filtered list to the channel.

Trigger keywords

Beyond calibration patterns, also flag tickets mentioning:

Privacy triggers:

• "new data" / "collect" / "tracking" / "coleta" / "rastreamento"
• "menores de idade" / "crianças e adolescentes" / "LGPD art. 14" / "ECA" — triggers children's privacy review
• "teen" / "minor" / "13-17" / "age-appropriate" / "student" — triggers teen / age-appropriate-design review (different regime, different calibration)
• "health" / "medical" / "ANVISA" / "HIPAA" (US cross-border)
• "personal data" / "PII" / "dados pessoais" / "dados sensíveis"
• Third-party vendor names not on the approved list
• "terms" / "policy" / "agreement" / "política de privacidade" / "termos de serviço" changes
• Country names / "LGPD" / "ANPD" (jurisdictional expansion, regulatory scope)
• "beta" → "GA" transitions (commitments change)

AI governance triggers:

• "AI" / "ML" / "model" / "LLM" / "GPT" / "Claude" / "Gemini" / "Copilot"
• "machine learning" / "neural" / "algorithm"
• "automated" / "auto-" (when combined with decision or action)
• "generated" / "generative" / "synthesized"
• "recommendation" / "prediction" / "scoring" / "classification"
• "personalized" / "intelligent" (feature descriptions)
• AI vendor names: "OpenAI" / "Anthropic" / "Google AI" / "Cohere" / "Mistral" or similar
• "fine-tun" / "train" / "embeddings"

Tickets matching AI governance triggers should be flagged with: "⚠️ AI component detected — needs AI governance triage before launch review."

Output

📋 **Launch radar — [date]**

**Likely needs review:**
• [TICKET-123] [Title] — ships [date] — matches [calibration pattern]
• [TICKET-456] [Title] — ships [date] — ⚠️ AI component detected — needs AI governance triage
• [TICKET-789] [Title] — ships [date] — mentions [privacy keyword] — PIA likely required

**Already reviewed (FYI):**
• [N] tickets in window with legal sign-off

**On the calendar but looks fine:**
• [N] tickets — UI/infra/copy changes, no legal trigger

If nothing needs review, short all-clear.

What it does NOT do

• Run full launch reviews — it flags, a human reviews
• Block launches — no ticket status changes
• Ping PMs directly — posts to legal channel, counsel reaches out if needed