mypos-legal-copilot

File a ticket's attachments and current draft into the right SharePoint matter-type folder.

Send the lawyer-reviewed AI draft, file the final email + documents to SharePoint, and transition the ticket to Done.

One-time setup -- configure SharePoint folder, create matter-type subfolders, register the daily 08:00 CET schedule.

Sweep the Jira board -- triage every To-Do legal ticket end-to-end. Runs daily at 08:00 CET on weekdays.

Read unread emails in the legal mailbox, dedupe against existing Jira tickets, create new tickets for new matters, and triage each one.

Triage a single Jira ticket or pasted email -- classify, dedupe, draft, review, file, post.

Runs the Devil's advocate review skill over a draft legal response and returns a structured verdict (approve / revise / escalate) with line-level findings. Invoked by /triage, /triage-board, and /triage-inbox after the legal-triage-* skill produces a draft, but BEFORE the draft is posted to Jira or saved to Outlook AI Drafts. The subagent runs in isolation so its findings don't pollute the main triage context.

STUB -- references the published Devil's advocate review skill. This stub exists so the plugin can ship without bundling the skill body. The actual skill body is published in the `anthropic-skills` plugin (or wherever the team has published it). Use this skill via the `triage-reviewer` subagent which loads the published version.

STUB reference to the published `legal-triage-claims` skill. Triage incoming claims, disputes, complaints, threatened/active legal proceedings -- whether against myPOS or by myPOS against a third party. Identifies nature/status of the claim, parties, financial exposure, deadlines. Always escalates -- claims trigger human_review_required regardless of confidence.

STUB reference to the published `legal-triage-contract-review` skill. Triage and structure incoming contract review requests (MSAs, SOWs, SaaS agreements, vendor contracts, supplier agreements, partnership agreements, similar commercial documents). Extracts metadata, flags risk areas, identifies missing info, and produces structured output for Jira field mapping and Ironclad routing.

STUB reference to the published `legal-triage-corporate-change` skill. Triage requests for changes to a myPOS group entity -- incorporations, dissolutions, name changes, registered address updates, director appointments/resignations, share transfers, capital changes, statutory filings, internal restructurings, mergers. Identifies entity, change type, jurisdiction, and regulatory filing requirements.

STUB reference to the published `legal-triage-gtcs` skill. Triage requests to draft, review, update, or approve myPOS's own General Terms & Conditions, terms of service, merchant agreements, cardholder terms, partner terms, or any standard-form contractual document myPOS publishes at scale. Identifies which document changes, the reason, affected markets and customer segments.

STUB reference to the published `legal-triage-inspection-support` skill. Triage inspection support requests -- regulatory inspections, supervisory visits, on-site exams by licensing authorities, formal information requests from regulators in the context of inspection or supervisory review. Distinct from a standalone regulatory question -- inspection support involves active regulatory scrutiny of myPOS. Always escalates -- triggers human_review_required regardless of confidence.

STUB reference to the published `legal-triage-kyc` skill. Triage KYC support requests where teams or external counterparties ask Legal to provide corporate documentation ABOUT myPOS entities (Articles of Association, Certificates of Incorporation, shareholding structures, UBO declarations, director passports, good standing certificates, notarised documents, apostilles). Identifies entity, extracts requested documents, flags ambiguities, assesses priority/SLA.

STUB reference to the published `legal-triage-materials-review` skill. Triage requests to review external-facing material before publication -- marketing copy, ads, website content, brochures, press releases, event materials, social media, sales decks, product documentation, promotional materials. Flags regulatory compliance, misleading claims, financial promotion rules, IP, and brand/legal sign-off concerns.

STUB reference to the published `legal-triage-nda` skill. Triage and structure incoming NDA requests -- extracts NDA fields, flags missing info, assesses priority/SLA, surfaces risk flags, and produces structured output ready for Jira field mapping and Ironclad routing. Trigger when input mentions NDA, non-disclosure agreement, confidentiality agreement, or CDA.

STUB reference to the published `legal-triage-project` skill. Triage complex, multi-task or ongoing legal involvement that doesn't fit a single contract / NDA / regulatory question -- product launches needing cross-workstream sign-off, market entries requiring licences + contracts + regulatory guidance together, major commercial deals with parallel legal tracks. Scopes the work, identifies business owner and timeline, flags complexity and risk.

STUB reference to the published `legal-triage-regulatory-question` skill. Triage requests asking Legal for guidance on a regulatory requirement, rule, or obligation -- or where a regulatory authority has sent a question or information request to myPOS. Identifies regulation/jurisdiction, classifies question type, assesses urgency, flags escalation needs, and produces structured Jira output.

File legal matter documents (drafts, Devil's advocate reviews, attachments, sent emails) to the team's shared SharePoint folder using the team's filing convention. Reads filing rules from `_knowledge/sharepoint-map.md` so lawyers can change folder names and naming templates without code changes. Invoked by `/triage`, `/file-to-sharepoint`, and `/reply-and-close`.