| name | launch-review |
| description | Full launch review against your framework and risk calibration. Use when the user says "review this launch", "legal review for [feature]", "can we ship this", "what are the legal issues with [product]", or references a launch tracker ticket or PRD that needs a category-by-category review memo.
|
| argument-hint | [PRD file | Drive link | tracker ticket ID] |
/launch-review
- Load
~/.claude/plugins/config/claude-for-legal/product-legal/CLAUDE.md → framework + calibration. Stop if placeholders.
- Get PRD + related docs. If tracker connected, pull ticket and comments.
- Walk every framework category using the workflow below.
- Calibrate each finding against the table. Novel = flag explicitly.
- Output review memo in house format. Post summary to ticket if connected.
- Hand off: marketing-claims-review if substantial marketing; feature-risk-assessment if a finding needs depth.
/product-legal:launch-review PROJ-1234
Matter context
Matter context. Check ## Matter workspaces in the practice-level CLAUDE.md. If Enabled is ✗ (the default for in-house users), skip the rest of this paragraph — skills use practice-level context and the matter machinery is invisible. If enabled and there is no active matter, ask: "Which matter is this for? Run /product-legal:matter-workspace switch <slug> or say practice-level." Load the active matter's matter.md for matter-specific context and overrides. Write outputs to the matter folder at ~/.claude/plugins/config/claude-for-legal/product-legal/matters/<matter-slug>/. Never read another matter's files unless Cross-matter context is on.
Destination check
Before producing output, check where it's going. If the user has named a destination (a channel, a distribution list, a counterparty, "everyone"), ask whether it's inside the privilege circle. Public channels, company-wide lists, counterparty/opposing counsel, vendors, and clients (for work product) waive the protection. When the destination looks outside the circle, flag it and offer (a) the privileged version for legal only, (b) a sanitized version for the broader channel, or (c) both — don't silently apply a privileged header and then help paste it somewhere the header won't protect it. See the canonical ## Shared guardrails → Destination check in this plugin's CLAUDE.md.
Purpose
Read the PRD, check every category in this team's framework, calibrate against what actually blocks here (per ~/.claude/plugins/config/claude-for-legal/product-legal/CLAUDE.md), and output a review in house format. Goal: a PM reads it and knows exactly what has to happen before they ship.
Load calibration
Read ~/.claude/plugins/config/claude-for-legal/product-legal/CLAUDE.md:
## Review framework — the categories to check## Risk calibration — what blocks vs. what's FYI at this company## Launch review process — output format## Escalation — when to route up
The calibration table is the difference between this skill and a generic checklist. If the table says "new data collection → PIA, ships in 1-2 days," don't write "this might require a full DPIA and regulatory consultation." Match the team's actual practice.
Workflow
Step 1: Get the inputs
- PRD — from file, Drive, or the launch tracker ticket
- Spec/design doc — if separate
- Marketing plan — if there is one (hands off to marketing-claims-review if substantial)
- Launch date — for urgency calibration
- Launch tracker ticket — if connected, pull it for context and comments
If Jira/Linear MCP is connected, pull the ticket history — often there's context in earlier comments that the PRD doesn't capture.
Step 2: Understand what's launching
Before the checklist, answer in plain English:
- What does this thing do?
- Who uses it — existing users, new users, a new segment?
- What's new vs. what's an extension of something already reviewed?
- Any new data, new vendors, new claims, new jurisdictions?
AI detection — run before the framework walk. Check whether this launch uses
AI in any form: a third-party model, an internally built model, an AI-powered
vendor feature, automated scoring or classification, generative content,
recommendations, predictions. Look for this even if the PRD doesn't label it
"AI" — words like "intelligent", "automated", "personalized", "generated",
"suggested" are tells.
If AI component detected → flag it, then run /ai-governance-legal:use-case-triage [feature]
alongside the framework walk. Category 8 below handles the detail; this flag
ensures it's never skipped even if the PRD is vague.
Step 3: Walk the framework
For each category in ~/.claude/plugins/config/claude-for-legal/product-legal/CLAUDE.md → Review framework. If the team doesn't have one, use the 8-category default below. The categories are stable framing concepts; within each category, research the regulatory regimes applicable to the product's sector, audience, and jurisdictions before calibrating severity. What blocks in one jurisdiction or sector may be routine in another — ~/.claude/plugins/config/claude-for-legal/product-legal/CLAUDE.md captures the team's calibration.
| # | Category | Key question | Auto-skip if |
|---|
| 1 | Contractual commitments | Does this conflict with any customer-facing promise (ToS, SLA, marketing)? | No customer-facing changes |
| 2 | Privacy | New data collection, new purpose, new sharing? | No data changes |
| 3 | Security | New attack surface, new data at rest, new access patterns? | UI-only, no backend change |
| 4 | IP | Third-party code/content? Open-source license check? Outputs that could infringe? | No new dependencies, no user-generated content |
| 5 | Third-party | New vendor, partner, or integration? | No new external parties |
| 6 | Regulatory | Does this touch a regulated sector, audience, or jurisdiction? Research the applicable regimes. | Same users, same sectors, same jurisdictions as existing product |
No silent supplement. If a research query to the configured legal research tool (Westlaw, CourtListener, regulator sites, or firm platform) returns few or no results for a regime, enforcement precedent, or regulator guidance, report what was found and stop. Do NOT fill the gap from web search or model knowledge without asking. Say: "The search returned [N] results from [tool]. Coverage appears thin for [regime / topic]. Options: (1) broaden the search query, (2) try a different research tool, (3) search the web — results will be tagged [web search — verify] and should be checked against the issuing authority before relying, or (4) flag as unverified and stop. Which would you like?" A lawyer decides whether to accept lower-confidence sources.
Source attribution tiering. Tag every citation in the review with its source. For model-knowledge citations, use one of three tiers rather than a single blanket "verify" tag:
[settled] — stable, well-known statutory and regulatory references unlikely to have changed (e.g., FTC Act § 5, GDPR Art. 33, CCPA § 1798.100). Still verify before relying on it to clear a launch, but lower priority.[verify] — model-knowledge citations that are real but should be verified: specific implementing regulations, agency guidance, enforcement actions, case holdings, thresholds, effective dates, post-2023 amendments.[verify-pinpoint] — pinpoint citations (specific subsection letters, volume/page numbers, paragraph numbers) carry the highest fabrication risk and should ALWAYS be verified against a primary source.
Tool-retrieved citations keep their source tag ([Westlaw], [CourtListener], [regulator site], or the MCP tool name); web-search citations remain [web search — verify]; user-supplied citations (from the PRD or seed materials) remain [user provided]. The tiering surfaces the real verification work — a reader who verifies everything verifies nothing. Never strip or collapse the tags.
[platform policy — verify against live docs] — platform rules (Apple App Store Review Guidelines, Google Play policies, Meta / Snap / TikTok creator rules, ESRB / PEGI descriptors, card-network rules, app-store in-app-purchase policies) cited without fetching the live page. Never use [settled] for a platform policy — these change without notice and the model's snapshot is almost always stale. If the launch hinges on a platform rule, fetch the current policy page in-session before relying on it.
| 7 | Marketing claims | Any claims that need substantiation? | No marketing component |
| 8 | AI governance | Does this use AI in any form? Is the use case in the registry? AIA done? Vendor AI terms reviewed? | No AI component detected in Step 2 |
For each category, output:
### [N]. [Category]
**Checked:** [what you looked at]
**Finding:** [Clear | Needs work | Blocker | Skipped]
**Detail:** [what the issue is, if any — specific to the PRD, not generic]
**Calibration:** [per the config CLAUDE.md — this is usually an FYI / usually needs X / usually blocks]
**Action:** [what has to happen, who owns it, by when]
Auto-skip honestly. If a category doesn't apply, say so with a one-line reason. Don't pad.
Sector hints. The 8-category framework above is enterprise-SaaS-shaped. If the launch involves any of the sectors below, add the overlay: ask the overlay question alongside the base-framework question for each affected category, and surface the sector-specific regime before calibrating severity. A launch that checks all 8 boxes but misses a sector regime still ships with a hole.
| Sector | Overlay regimes to surface |
|---|
| Children / minors | COPPA (US — operators of services directed to children under 13 or with actual knowledge), CA AADC / state age-appropriate design codes, platform age ratings (ESRB, PEGI), addictive-design scrutiny (NY Safe for Kids Act, CA SB 976 and analogs), FTC endorsement guides for kid-directed influencers |
| Gaming / loot boxes / in-game currency | Loot-box odds disclosure (CA AB 2476-style, Chinese / Korean / Belgian / Dutch regimes), ESRB / PEGI descriptors (In-Game Purchases, Loot Boxes, Real Gambling), state gambling law (games-of-chance vs. games-of-skill lines, sweepstakes promotions law), FTC dark-patterns guidance, platform-store policies (Apple, Google, console) |
| Financial / fintech | GLBA (NPI, Safeguards Rule, Reg P), state money transmission licensing (MTLs across ~50 states + DC), CFPB UDAAP, state UDAP, bank-partner sponsorship requirements and "true lender" exposure, Reg E / Reg Z where applicable, FINRA if brokerage |
| Health | HIPAA (if CE or BA), FDA SaMD / clinical decision support / general wellness exemption, state health-privacy (WA MHMDA, NV SB 370, CT HIPAA-analog), FTC Health Breach Notification Rule for non-HIPAA entities |
| Education | FERPA (if school or school-acting service provider), state student-privacy (NY Ed Law 2-d, IL SOPPA, CA SOPIPA + AB 1584), COPPA if K-12 data under 13 |
| Employment / HR tech | Title VII, EEOC guidance on AI in hiring, ADA, state AI-hiring laws (IL AIVIA, NYC Local Law 144, CA / CO / UT / NJ analogs under consideration or enacted), state biometric laws (IL BIPA, TX / WA analogs) for video-interview and keystroke products, FCRA for background / verification products |
| Government / public sector | FedRAMP (Low / Moderate / High), FAR / DFARS, CMMC where applicable, state-level equivalents (StateRAMP), CJIS for law-enforcement data, IRS Publication 1075 for tax data, StateRAMP and state procurement rules |
| Consumer / retail / marketing | FTC Act § 5, Made-in-USA rule, Green Guides, CAN-SPAM, TCPA (with TCPA-Shaken/Stir for calls), state auto-renewal (ROSCA, CA ARL, NY GBL § 527-a [consumer] or GOL § 5-903 [B2B services] — verify which applies), state sweepstakes/promotions law |
If a sector hint fires and no dedicated category in the base framework covers it, insert it as a category (e.g., "6a. Sector overlay — children / COPPA + CA AADC"). Don't let it disappear into category 6 Regulatory as an afterthought; the sector regime often supplies the controlling floor, not a footnote.
Step 4: Calibrate severity
For each finding, check against the calibration table in ~/.claude/plugins/config/claude-for-legal/product-legal/CLAUDE.md:
- If it matches a "usually FYI" pattern → note it, don't block
- If it matches "usually requires work" → specify the work, estimate timeline from the table
- If it matches "usually blocks" → flag prominently, route per escalation table
- If it's novel (not in the table) → say so explicitly: "This doesn't match any pattern in the calibration — needs a human call"
Step 5: Assemble the review
Format per ~/.claude/plugins/config/claude-for-legal/product-legal/CLAUDE.md → Launch review process → output format. Prepend the work-product header from ~/.claude/plugins/config/claude-for-legal/product-legal/CLAUDE.md ## Outputs (it differs by user role — see ## Who's using this). If no house format is specified:
[WORK-PRODUCT HEADER — per plugin config ## Outputs]
# Launch Review: [Feature name]
**Reviewed:** [date] | **Launch date:** [date] | **Reviewer:** [name]
**PRD:** [link] | **Ticket:** [link if connected]
---
## Bottom line
[One paragraph: can this ship? What has to happen first?]
**Call:** [Clear to ship | Ship with conditions | Blocked pending X | Needs escalation]
> **Before emitting a "Clear to ship" or "Ship with conditions" call:** Read `## Who's using this` in `~/.claude/plugins/config/claude-for-legal/product-legal/CLAUDE.md`. If the Role is Non-lawyer:
>
> > Clearing a launch is a legal act — once the product ships, the company is committed to the legal posture documented here. Have you reviewed this with an attorney? If yes, proceed. If no, here's a brief to bring to them:
> >
> > [Generate a 1-page summary: the launch, the findings by category, any open questions, the residual risk after conditions, and the three things to ask the attorney before the launch goes out.]
> >
> > If you need to find a lawyer: your professional regulator's referral service is the fastest starting point (state bar in the US; SRA/Bar Standards Board in England & Wales; Law Society in Scotland/NI/Ireland/Canada/Australia; or your jurisdiction's equivalent).
>
> Do not proceed past this gate to a "Clear to ship" or "Ship with conditions" call without an explicit yes. "Blocked pending X" and "Needs escalation" do not require the gate — those are review calls, not clearances.
---
## Findings by category
[All the category blocks from Step 3 — skip-noted categories at the bottom]
---
## Action items
| # | Item | Owner | Due | Blocking? |
|---|---|---|---|---|
| 1 | [specific] | [PM/eng/legal] | [date] | Yes/No |
---
## Escalations
[If any — who, why, drafted per escalation skill]
---
## Notes for next time
[If this launch surfaced a pattern that should update the calibration table]
---
## Citation check
Any cases, statutes, regulations, or enforcement actions referenced in this review were generated by an AI model and have not been verified against a primary source. Before relying on a citation in a launch decision, verify it against a legal research tool (Westlaw, CourtListener, or your firm's research platform) for accuracy, good law status, and current enforcement posture. Fabricated or misquoted citations in launch reviews can steer the business wrong. Source tags on each citation (e.g., , ) show where it came from; tags carry higher fabrication risk and should be checked first.
Step 6: Produce BOTH outputs — the privileged memo AND the redacted ticket comment
⚠️ Privilege warning: Posting the full privileged memo to a Jira/Linear ticket that is widely shared with engineering, PM, and other non-legal roles may waive privilege. Don't paste the full memo into a broadly-shared ticket.
Both of the following are REQUIRED outputs of this skill. Neither is optional. Print them in the order below, with a clear divider between them so the user cannot miss the redacted block.
Output 1 — Privileged launch review memo. The full analysis assembled in Step 5: work-product header, bottom line, findings by category with risk rationale, action items, escalations, notes for next time, citation check. This is internal legal work product. Keep it in your matter file (Drive, DMS, or wherever ~/.claude/plugins/config/claude-for-legal/product-legal/CLAUDE.md says review docs go). Distribute only to people inside the privilege circle.
Output 2 — Redacted ticket-comment block — SAFE TO POST TO TRACKER. After the memo, with a clear --- divider and the header ## SAFE TO POST TO TRACKER (non-privileged), produce a short comment block containing ONLY:
- Launch status: green / yellow / red (i.e., Clear to ship / Ship with conditions / Blocked pending X / Needs escalation)
- Conditions as action items: each condition is a bullet, written as an instruction to the PM/eng ("add PIA link to ticket before ship", "remove 'most accurate' language from homepage copy"). No legal reasoning.
- Deadline per condition.
- Owner per condition.
The redacted block contains NO work-product / privilege header, NO risk rationale, NO internal legal discussion, NO regulatory citations, NO escalation notes. If a condition's phrasing would leak the underlying legal theory ("retaliation risk"), rewrite it as the action ("route to GC before term date").
Example divider and block:
---
## SAFE TO POST TO TRACKER (non-privileged)
**Launch status:** Blocked pending conditions below.
**Conditions:**
- [ ] Attach completed PIA to ticket — Owner: [PM] — Due: [date]
- [ ] Remove "most accurate on the market" copy from homepage draft — Owner: [Marketing] — Due: [date]
- [ ] Confirm with GC before changing retention window — Owner: [PM] — Due: [date]
Paste Output 2 (and only Output 2) to the tracker. Link Output 1 only to the people inside the privilege circle who need to read the full analysis.
Handoffs
- To marketing-claims-review: If there's a substantial marketing component, hand off the claims section.
- To feature-risk-assessment: If a finding is complex enough to need its own doc (e.g., novel AI feature, children's product), spawn a deeper assessment.
- To privacy: If the launch touches personal data, run
/privacy-legal:use-case-triage [feature]. If triage returns PIA REQUIRED or DPIA MANDATORY, run /privacy-legal:pia-generation [feature]. Don't just note "PIA needed" — trigger it.
- To AI governance: If an AI component was detected in Step 2, run
/ai-governance-legal:use-case-triage [feature]. If triage returns CONDITIONAL, run /ai-governance-legal:aia-generation [feature]. If a new AI vendor is involved, run /ai-governance-legal:vendor-ai-review [vendor agreement].
Close with the next-steps decision tree
End with the next-steps decision tree per CLAUDE.md ## Outputs. Customize the options to what this skill just produced — the five default branches (draft the X, escalate, get more facts, watch and wait, something else) are a starting point, not a lock-in. The tree is the output; the lawyer picks.
What this skill does not do
- It doesn't replace a conversation with the PM. Often the PRD is wrong or out of date — the review surfaces questions, a human asks them.
- It doesn't approve the launch. It informs the approval.
- It doesn't retroactively calibrate. If this launch turns out fine (or badly) in a way that should update the calibration table, a human updates ~/.claude/plugins/config/claude-for-legal/product-legal/CLAUDE.md.
