Scoping intake pratica

Organizza le informazioni del cliente in brief strutturati con stakeholder, confini di scope, domande aperte e raccomandazioni sui passi successivi.

Learn to build skills

Official alternative

Anthropic maintains an official plugin workflow for this task. Use it when you want the full marketplace plugin with MCP connectors.

Litigation Matter Intake

/plugin install litigation-legal@claude-for-legal

Official outputs require attorney review before client reliance.

Informazioni su questa skill

Organizza le informazioni del cliente in brief strutturati con stakeholder, confini di scope, domande aperte e raccomandazioni sui passi successivi.

Skills provide structured workflow guidance for attorney-supervised use. They are not legal advice and require human review before client reliance.

How to install

Download starter bundle

Download the ZIP and unzip the skill folder.
In Claude: Settings → Capabilities → Skills → Upload skill folder.
In Claude Code or Codex: copy the folder into `.claude/skills/` or `~/.agents/skills/`.
Invoke the skill by describing a task that matches the skill description.

Skills provide structured workflow guidance for attorney-supervised use. They are not legal advice and require human review before client reliance.

Skill content preview

# Matter Intake Scoping

Convert messy client inputs into a structured matter brief.

## Intake sources

- Client emails, call notes, data room indexes, prior proposals
- Business sponsor requests
- Partial contracts or term sheets

## Workflow

1. **Matter snapshot** — type, urgency, parties, jurisdiction
2. **Objectives** — what success looks like for client and legal team
3. **Scope boundaries** — in scope / out of scope / assumptions
4. **Stakeholders** — client, legal, business, external counsel
5. **Risks and unknowns**
6. **Workplan** — phases, deliverables, dependencies
7. **Fee/proposal inputs** — complexity drivers (not pricing advice)

## Output format

```markdown
## Matter brief
## Background
## Objectives
## Scope (in / out / assumptions)
## Stakeholders
## Key documents received
## Open questions
## Proposed next steps
## Escalation triggers
```

## Guardrails

- Do not invent facts not provided by the user.
- Flag conflicts, missing approvals, and regulatory triggers early.
- Keep outputs internal unless user requests client-facing version.