---
name: legal-strategy-session
description: Use when the user describes a legal situation (immigration, employment, housing, contracts, a dispute, a government delay) and wants options, a plan, or to understand where they stand before talking to a lawyer. Runs a structured strategy session from three angles, ties every rule to an official source, and ends with the questions to bring to a licensed lawyer. Not legal advice.
metadata:
  id: legal-strategy-session
  version: "1.0.0"
  author: BotPlaza
---

# Legal Strategy Session

> Not legal advice. These bots brainstorm and draft; a licensed lawyer must review anything before it is filed or sent.

## What it does

Turns a messy legal situation into a clear map: the facts, the issues, the realistic options with their risks and timelines, and the exact questions to ask a lawyer. It argues the case from three angles (the strategist, the skeptic, and the procedure checker) so weak spots show up before a lawyer bills an hour. It works well as one bot, or as a team of three bots that each take one angle.

## When to use

- "Can my landlord do this?", "Is this contract clause enforceable?", "Help me get ready for my consult."
- Not for emergencies, court deadlines in the next few days, or criminal charges. In those cases, tell the user to contact a licensed lawyer or legal aid now, and give them the official lawyer referral service for their region.

## Requires

Web search and web access to official sources (government sites, court and tribunal sites, official guidance). No accounts needed. Optional: a notes or docs app where the user keeps case documents.

## Schedule

On demand. Re-run it when something changes in the case (a new letter, a deadline, a reply from the other side).

## Inputs

| Setting | Default | Notes |
|---|---|---|
| `situation` | required | The user's own words. Ask for missing dates, places, and documents in one short batch. |
| `jurisdiction` | ask | Country and province or state. Rules differ a lot; never assume. |
| `goal` | ask | What a good outcome looks like to the user. |
| `angles` | strategist, skeptic, procedure | Add `negotiator` for disputes, or `cost` for a budget-first view. |
| `depth` | standard | `quick` (one page) or `standard` (full map with sources). |

## Steps

1. **Facts.** Restate the facts as a dated timeline. Mark each one as stated by the user, shown in a document, or assumed. Ask about anything that would change the answer.
2. **Issues.** List the legal questions in plain words, for example "Is the delay unreasonable enough to ask a court to order a decision?".
3. **Rules.** For each issue, find the governing rule on an official source: the statute, regulation, government guidance, or a court or tribunal decision. Record the link and the date checked. If you can't verify a rule, write "unverified" and don't rely on it.
4. **Three angles.**
   - *Strategist:* the strongest realistic path to the user's goal, with steps, timeline, and typical costs if published.
   - *Skeptic:* what could go wrong, the other side's best argument, and the weak facts.
   - *Procedure checker:* deadlines, forms, filing fees, who has to sign, and what has to happen first.
5. **Options.** Give 2 to 4 options side by side: what it is, the steps, a rough timeline, the cost range when an official source gives one, the risks, and what it needs from the user.
6. **Lawyer questions.** Write 5 to 8 specific questions that a licensed lawyer in that jurisdiction should answer, ordered by importance.
7. **Next 7 days.** List the concrete actions the user can take now, such as gathering documents, requesting their file, or booking free consultations.

## Output format

```markdown
# Strategy session: {short case name}
*{Jurisdiction} · {date} · Not legal advice. These bots brainstorm and draft; a licensed lawyer must review anything before it is filed or sent.*

## Where you stand
{3 sentences: the situation, the main issue, and the most promising path.}

## Timeline
| Date | What happened | Source |
|---|---|---|

## The issues
1. **{Issue}.** {Rule in plain words.} [source]

## Your options
| Option | Steps | Timeline | Cost | Main risk |
|---|---|---|---|---|

## The skeptic's view
- {Weak point, and how to shore it up}

## Deadlines and procedure
- {Deadline or requirement, with source}

## Questions for your lawyer
1. {Question}

## Next 7 days
- [ ] {Action}
```

## Edge cases

- **Facts conflict:** show both versions and say which documents would settle it.
- **No official source found:** say so. Don't fill the gap with a forum post or model memory.
- **The user wants a single "what should I do":** give the option you'd ask a lawyer about first and say why, while making clear a lawyer has to confirm it.
- **Several jurisdictions involved** (for example a move across a border): split the map by jurisdiction.
- **Run as a team:** each bot writes its angle under its own heading, and one bot merges the results and removes duplicates.

## Boundaries

- Not legal advice. These bots brainstorm and draft; a licensed lawyer must review anything before it is filed or sent.
- Never invent a case, statute, section number, deadline, or fee. A search snippet is not a source; open the page.
- Never file, sign, submit, or contact anyone (the other side, a government office, or a lawyer) on the user's behalf.
- Keep case details in the user's private chat. Never post them to a shared channel without the user's approval.