메뉴
Route a contract issue to the right approver per the escalation matrix in the commercial practice profile, with Turkish-law risk categories, TL thresholds, signature authority, and attorney-review gates. Drafts the ask but never sends or approves it.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
EU AI Act (ve Türkiye uyumu) per-system inventory — track each AI system's role (provider, deployer, importer, distributor, authorized representative, product manufacturer) and risk tier (prohibited, high-risk, limited, minimal, GPAI, GPAI+systemic). Role and tier are assessed per system, not per company. Use when the user says "ai inventory", "add an ai system", "what systems do we have", "classify this ai system", "eu ai act register", or "ai system registry".
Run an AI impact assessment — structured intake, risk analysis, regulatory classification per regime in scope, policy consistency diff, and recommendation with conditions. Uses the house-style structure learned from the seed impact assessment in `~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md`. Use when user says "impact assessment for", "assess this AI use case", "run an AIA", "generate an AIA", "we need to document this AI system", "AI risk assessment for X", or follows a conditional triage result.
Run the cold-start interview — learns your AI governance practice and writes `~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md` from your AI policy, a reference impact assessment, and key vendor AI agreements. Use when the practice profile is missing or contains `[PLACEHOLDER]` markers, or when user says "set up ai governance plugin", "onboard me", "configure ai governance".
Guided customization of your AI governance practice profile — change one thing without re-running the whole cold-start interview. Adjust risk posture, escalation contacts, use-case registry entries, vendor AI positions, AI policy commitments, impact-assessment house style, or matter workspace paths. Use when the user says "change my [thing]", "update my profile", "edit my config", "tune my playbook", or "customize".
Draft a firm AI usage policy from published model policies, adapted to your practice profile — a research-and-synthesis tool whose output is a draft for attorney review and adoption, not a finished policy. Use when user says "draft an AI policy", "we need an AI policy", "build an AI usage policy", "our firm needs a GenAI policy", or similar requests to generate a first-cut internal AI policy.
Diff a new AI regulation or guidance against your current governance posture — surfaces gaps, priorities, and a remediation plan with owners and deadlines. Use when an AI regulation moves (or you learn about one you missed), or when user says "new reg just dropped", "does [regulation] affect us", "gap analysis for EU AI Act (ve Türkiye uyumu)", "compliance check against [AI law or guidance]", or pastes regulatory text.
| name | escalation-flagger |
| description | Route a contract issue to the right approver per the escalation matrix in the commercial practice profile, with Turkish-law risk categories, TL thresholds, signature authority, and attorney-review gates. Drafts the ask but never sends or approves it. |
| argument-hint | [describe the issue, or reference a review memo] |
Sözleşme riskini veya playbook sapmasını doğru onay makamına yönlendirir ve gönderilmeye hazır bir talep taslağı hazırlar. Kararı vermez; mesajı göndermez.
~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md -> ## Escalation.eskalasyon_matrisi:
- can_approve: "Contracts Counsel"
threshold: "standard terms / < 1.000.000 TL"
escalates_to: "Senior Counsel"
via: "Teams / email"
- can_approve: "Head of Legal"
threshold: "non-standard terms / < 10.000.000 TL"
escalates_to: "CFO / General Manager / Board"
via: "approval memo"
automatic_triggers:
- uncapped liability
- cezai şart above playbook / TBK m.179-185 risk
- IP assignment
- KVKK transfer risk
**Onay makamı:** [name / role]
**Kanal:** [email / Teams / meeting / CLM approval]
**Aciliyet:** [deadline]
**Uygulanan playbook:** [sales-side / purchasing-side]
---
Sayın [name],
[Counterparty] ile [agreement type] kapsamında aşağıdaki konuda onayınıza ihtiyaç var.
**Risk / sapma:** [plain Turkish explanation]
**Sözleşmedeki madde:**
> "[short quote]"
**Playbook pozisyonumuz:** [quote or summary from CLAUDE.md]
**Seçenekler:**
1. **Kabul** - [why this may be acceptable]
2. **Revize / karşı öneri** - "[proposed narrow language]"
3. **Durdur / üst onay** - [when realistic]
**Tavsiyem:** [recommendation with reason]
**Karar beklenen tarih:** [date]
[Link to full review memo]
If clearly inside documented fallback, no escalation. If outside fallback or on automatic list, escalate. If ambiguous or the playbook is silent, escalate with the uncertainty stated.