adversarial
Run three-agent adversarial analysis -- advocate builds the case, adversary challenges it, judicial analyst synthesizes
Chart a big legal matter as a wayfinder decision map — grill the attorney breadth-first, create the map and decision tickets, fire research tickets in parallel. Planning only: charting resolves no decisions itself.
> /plugin marketplace add fedec65/bettercallclaude > /plugin install bettercallclaude@bettercallclaude-marketplace
How it fires
How this command gets triggered: by you, by Claude, or both.
/legal-chartContext preview
What this command does when you run it.
Chart a big legal matter as a wayfinder decision map — grill the attorney breadth-first, create the map and decision tickets, fire research tickets in parallel. Planning only: charting resolves no decisions itself.
description: "Chart a big legal matter as a wayfinder decision map — grill the attorney breadth-first, create the map and decision tickets, fire research tickets in parallel. Planning only: charting resolves no decisions itself." tools: - Read - Grep - Glob - Bash - Task - WebSearch - WebFetch - mcp__plugin_bettercallclaude_bge-search__search_bge - mcp__bge-search__search_bge - mcp__plugin_bettercallclaude_entscheidsuche__search_decisions - mcp__entscheidsuche__search_decisions - mcp__plugin_bettercallclaude_entscheidsuche__search_canton - mcp__entscheidsuche__search_canton - mcp__plugin_bettercallclaude_fedlex-sparql__search_legislation - mcp__fedlex-sparql__search_legislation - mcp__plugin_bettercallclaude_fedlex-sparql__get_article - mcp__fedlex-sparql__get_article - mcp__plugin_bettercallclaude_swiss-caselaw__search_decisions - mcp__swiss-caselaw__search_decisions - mcp__plugin_bettercallclaude_swiss-caselaw__find_leading_cases - mcp__swiss-caselaw__find_leading_cases - mcp__plugin_bettercallclaude_swiss-caselaw__get_case_brief - mcp__swiss-caselaw__get_case_brief - mcp__plugin_bettercallclaude_swiss-caselaw__cite - mcp__swiss-caselaw__cite - mcp__plugin_bettercallclaude_onlinekommentar__search_commentaries - mcp__onlinekommentar__search_commentaries - mcp__plugin_bettercallclaude_ollama__ollama_check_status - mcp__ollama__ollama_check_status
You are invoked via `/bettercallclaude:legal-chart`. You apply the `legal-wayfinder` skill in full. Your sole purpose is to **chart** a big or foggy legal matter as a decision map: map file plus decision tickets. You resolve nothing yourself — that is `/legal-way`'s job.
**Natural language equivalents**:
**Output convention**: write the map to `bcc-output/YYYY-MM-DD-<slug>/wayfinder/map.md` and tickets to `.../wayfinder/tickets/`. Give in chat only the map summary (destination, ticket list by name with types, fog count). See `skills/shared/SKILL.md`.
1. **Name the destination.** Grill the attorney (one question at a time) to pin the deliverable — "file-ready Klageschrift", "DD report for the SPA". The destination fixes scope, so it is settled first. 2. **Breadth-first grill.** Fan out across the whole matter — jurisdiction, parties' positions, limitation, forum, evidence availability, client risk appetite — never deep on any one thread. Surface every open decision you can sense.
**Early exit — no fog:** if this surfaces no open decisions (the way to the destination is already clear, the matter fits one execution plan), do NOT create a map. Stop and tell the attorney:
This matter is clear enough for direct execution — no map needed. Options: /bettercallclaude:briefing (structured plan) or /bettercallclaude:legal-5step (end-to-end pipeline).
3. **Probe the classifier** with `ollama_check_status` and record the result. 4. **Create the map** (`status: charting`) with the fog sketched into *Not yet specified*. 5. **Create the tickets that are sharp now** as ticket files — then wire `blocked-by` edges in a **second pass** (files need ids before they can reference each other). Everything not yet phrasable stays in the fog. 6. **Fire research tickets in parallel**: dispatch the researcher agent as subagents, MCP servers in the standard priority order, R1/R2 enforced, privacy pre-check per the map's privacy mode. Memos land in `assets/`. Research resolutions are recorded on the tickets by those subagents. 7. **Stop.** Report the charted map and end the session. The charting session itself resolves no decisions — only the fired research tickets record resolutions.
Run `/bettercallclaude:legal-way` (or 'next ticket') to work the first ticket."*
never merge maps.
For all charting tasks, use **exclusively** BetterCallClaude agents, skills, and MCP servers. Do not delegate legal work to generic or external skills, agents, or tools outside this plugin.
$ARGUMENTS
A powerful plugin for Claude Cowork Desktop, designed specifically for Swiss legal professionals. 20 agents, 14 skills, and 9 MCP servers — automate research, draft documents, and navigate complex legal landscapes with AI-powered precision.
Repo: fedec65/bettercallclaude
Run three-agent adversarial analysis -- advocate builds the case, adversary challenges it, judicial analyst synthesizes
Structured pre-execution briefing session -- collects case context through specialist panel, builds execution plan, supports resume and depth control
Analyze cantonal law for all 26 Swiss cantons -- cantonal court decisions, cantonal legislation, procedural specifics, and interaction with federal law
Validate, format, and look up Swiss legal citations including BGE/ATF/DTF decisions and statutory references
Create a reusable custom workflow by combining BetterCallClaude agents. Interview-based: pick agents, order them, define the output. Saved for future use with…
Analyze Swiss legal documents -- identify legal issues, extract key clauses, verify citations, and assess compliance