| name | intake-triage |
| title | Intake Triage |
| description | Classify an incoming legal-work request and route it to the right team. |
| author | stubbi |
| author_url | https://github.com/stubbi/companies-legal/tree/main/legal-and-contracts/skills/intake-triage |
| license | Apache-2.0 |
| version | 0.1.0 |
| execution_mode | open |
| jurisdiction | general |
| practice | general |
| language | en |
Intake Triage
Port-original skill. Hand-authored for Legal & Contracts. Owned by the CEO role.
When to fire
Any new work request arriving without an explicit team / agent assignment. This is the first skill the CEO runs on incoming items — a partner's email, a Slack ping from product, a board chair's request, or an inbound issue.
Inputs
- The raw request: an email, a meeting note, a Slack message, an issue body.
- Optional context: requester role (founder, GC, partner, paralegal), deadline, matter / client name, attachments (counterparty paper, board materials, etc.), jurisdiction.
Outputs
A triage decision written back as a short note on the request:
team: contracts | corporate | research-review | escalate
primary_agent: <agent-slug>
secondary_agents: [<agent-slug>, ...]
priority: P0 | P1 | P2 | P3
deadline: <ISO date or "asap" or "best-effort">
attorney_owner: <name of supervising attorney>
boundaries: [<note>, ...]
