Legal Playbook
Create a standardized legal playbook for "$ARGUMENTS". Define decision trees, approval thresholds, pre-approved templates, escalation criteria, and timeline expectations for recurring legal scenarios.
Note: AI-generated legal content does not constitute legal advice. Consult a qualified attorney.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"legal-legal-playbook","workflow":"legal","phase":4,"project":"<project>","event":"skipped","artifact":"04-govern.md","note":"<reason or \"none given\">"}.
Prerequisites
Part of a workflow. This skill is phase 4 (Govern) of the Legal Lifecycle workflow (legal); cross-domain workflows run it too. First check .singularskills/log.jsonl for an open run for this project: a run-started line with "project":"<project>" and no later run-finished line for the same workflow and project. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the workflow skill with the workflow the user asked for, or legal when they named none, followed by <project>; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.
Run this skill's gate before writing: sh <this skill's folder>/scripts/gate.sh <project> <project root>, where <project root> is the folder that contains .singularskills/ (use . when you are already there). If it exits non-zero, stop and tell the user what it printed, unless --skip-checks was given (see Arguments). On a refusal, before you stop, append this line to .singularskills/log.jsonl (create the folder and file if missing): {"ts":"<ISO timestamp>","skill":"legal-legal-playbook","workflow":"legal","phase":4,"project":"<project>","event":"refused","artifact":"04-govern.md","note":"<what the gate printed>"}. Once the gate has passed, or under --skip-checks once you have appended the skipped line, append this line before you start work: {"ts":"<ISO timestamp>","skill":"legal-legal-playbook","workflow":"legal","phase":4,"project":"<project>","event":"started","artifact":"04-govern.md","note":""}.
Check that .singularskills/legal/<project>/00-assess.md exists. If it does not exist, stop and tell the user:
"Run an Assess skill first (e.g. /legal-risk-assessment <project>) to generate the prerequisite assessment artifact."
Process
Read inputs:
- Read
.singularskills/legal/<project>/00-assess.md for risk context, jurisdiction, and organizational profile
- Review any existing legal artifacts in
.singularskills/legal/<project>/
Identify recurring legal scenarios:
- Contract negotiation — standard terms, acceptable deviations, deal-breakers
- Data breach response — detection, containment, notification, remediation
- Employee termination — voluntary, involuntary, for cause, layoff procedures
- IP dispute — infringement claims, cease-and-desist responses, defensive actions
- Vendor onboarding — due diligence, contract requirements, risk assessment
- M&A due diligence — legal review scope, red flags, documentation requirements
- Regulatory inquiry — response protocols, document preservation, communication rules
- Tailor scenarios to the specific needs of ""
Create decision tree for each scenario:
- Define the triggering event (what initiates the scenario)
- Map decision points with if/then logic (if X, then Y)
- Identify the possible outcomes at each branch
- Include time constraints at each decision point
- Document the rationale for each recommended path
Define approval thresholds:
- Pre-approved actions — what can proceed without legal review (e.g., standard NDA execution, routine contract renewals under a value threshold)
- Legal review required — what needs internal legal sign-off (e.g., non-standard terms, contracts above value threshold, new vendor categories)
- Outside counsel required — what needs external legal involvement (e.g., litigation, complex regulatory matters, high-value transactions)
- Set clear monetary and risk-based thresholds for each level
List pre-approved templates and fallback positions:
- For each scenario, identify available templates (NDAs, standard contracts, response letters)
- Define preferred terms and acceptable fallback positions for negotiations
- Document which template modifications are acceptable without additional review
- Maintain version control references for all templates
Set escalation criteria:
- Define when to involve internal legal counsel
- Define when to involve outside counsel
- Define when to notify executive leadership
- Include specific triggers: monetary thresholds, reputational risk, regulatory exposure, litigation threats
- Set maximum response times for each escalation level
Include timeline expectations:
- Standard turnaround times for each scenario type
- Expedited process for urgent matters
- SLA definitions for legal team response
- External dependencies and typical third-party timelines
Organize playbook by audience:
- Sales team — contract negotiation, NDA procedures, deal approval workflows
- Engineering — open-source compliance, IP considerations, security incident response
- HR — employment law procedures, termination protocols, discrimination/harassment response
- Procurement — vendor assessment, contract review, supplier risk management
- Each audience section should be self-contained with relevant scenarios only
Write the artifact — append to .singularskills/legal/<project>/04-govern.md under a ## Legal Playbook section. Create the file with a # Govern — <project> heading if it does not exist; if a ## Legal Playbook section already exists, replace only that section. The section contains:
- Scenario Index — overview of all covered scenarios with quick-reference links
- Decision Trees — visual decision flow per scenario
- Approval Matrix — thresholds and required approvals by scenario and value
- Templates and Fallback Positions — available templates with modification guidelines
- Escalation Guide — when and how to escalate by scenario type
- Timeline Expectations — standard and expedited turnaround times
- Audience-Specific Guides — tailored playbook sections per team
Output
The legal playbook appended to .singularskills/legal/<project>/04-govern.md. Present a summary to the user highlighting:
- Number of scenarios covered and their categorization
- Key approval thresholds and escalation triggers
- Available pre-approved templates
- Audience-specific guide overview
Record the run. After you have written your section, append this line to .singularskills/log.jsonl (the started line of Prerequisites, with "event":"finished"): {"ts":"<ISO timestamp>","skill":"legal-legal-playbook","workflow":"legal","phase":4,"project":"<project>","event":"finished","artifact":"04-govern.md","note":""}.
This artifact is shared by every skill of phase 4 (Govern). The frontmatter is written once, by whoever creates the file: if you create it, open it with the block below (skill is the phase title, started the time of that first write; gate is passed when the gate ran clean and skipped under --skip-checks); if it already exists, leave the block alone except to update finished and to set gate to the worst value among the sections (skipped over passed).
---
skill: Govern
workflow: legal
phase: 4
project: <project>
started: <ISO timestamp>
finished: <ISO timestamp>
agent: <the agent you run in, or "unknown">
gate: <passed|skipped>
---
Open your ## Legal Playbook section with one italic line, *<skill name> · <ISO timestamp> · gate: <passed|skipped>* (your skill name is legal-legal-playbook).
End your section with ### Decisions and ### Open questions (one level under your ## Legal Playbook heading, so the section stays one block), in this shape:
### Decisions
- <what was chosen> — <why> — <what was rejected>
### Open questions
- <what the next phase or a reviewer must settle>
1---2name: legal-legal-playbook3description: Create a legal playbook for recurring scenarios — contract negotiation, breach response, terminations, IP disputes, vendor onboarding — with decision trees, approval thresholds, escalation rules and turnaround times per team. Use when the user wants sales, HR, engineering or procurement to handle routine legal situations without asking legal every time.4metadata:5 source: https://skillmd.com/skills/bromso/legal-legal-playbook6 argument-hint: "[project] [--skip-checks]"7 workflow: legal8 phase: 49 artifact: 04-govern.md10---1112# Legal Playbook1314Create a standardized legal playbook for "$ARGUMENTS". Define decision trees, approval thresholds, pre-approved templates, escalation criteria, and timeline expectations for recurring legal scenarios.1516> **Note:** AI-generated legal content does not constitute legal advice. Consult a qualified attorney.1718**Arguments.** `$ARGUMENTS` may contain the project name and optional flags. Take the first token as `<project>` and treat `--skip-checks` as a flag; never include flags in file paths. All paths below use `<project>`. If `--skip-checks` is present, skip the prerequisite check and, **before writing any artifact**, append one line to `.singularskills/log.jsonl`: `{"ts":"<ISO timestamp>","skill":"legal-legal-playbook","workflow":"legal","phase":4,"project":"<project>","event":"skipped","artifact":"04-govern.md","note":"<reason or \"none given\">"}`.1920## Prerequisites2122**Part of a workflow.** This skill is phase 4 (Govern) of the Legal Lifecycle workflow (`legal`); cross-domain workflows run it too. First check `.singularskills/log.jsonl` for an open run for this project: a `run-started` line with `"project":"<project>"` and no later `run-finished` line for the same `workflow` and `project`. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the `workflow` skill with the workflow the user asked for, or `legal` when they named none, followed by `<project>`; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.2324Run this skill's gate before writing: `sh <this skill's folder>/scripts/gate.sh <project> <project root>`, where `<project root>` is the folder that contains `.singularskills/` (use `.` when you are already there). If it exits non-zero, stop and tell the user what it printed, unless `--skip-checks` was given (see Arguments). On a refusal, before you stop, append this line to `.singularskills/log.jsonl` (create the folder and file if missing): `{"ts":"<ISO timestamp>","skill":"legal-legal-playbook","workflow":"legal","phase":4,"project":"<project>","event":"refused","artifact":"04-govern.md","note":"<what the gate printed>"}`. Once the gate has passed, or under `--skip-checks` once you have appended the `skipped` line, append this line before you start work: `{"ts":"<ISO timestamp>","skill":"legal-legal-playbook","workflow":"legal","phase":4,"project":"<project>","event":"started","artifact":"04-govern.md","note":""}`.2526Check that `.singularskills/legal/<project>/00-assess.md` exists. If it does not exist, stop and tell the user:2728> "Run an Assess skill first (e.g. `/legal-risk-assessment <project>`) to generate the prerequisite assessment artifact."2930## Process31321. **Read inputs:**33 - Read `.singularskills/legal/<project>/00-assess.md` for risk context, jurisdiction, and organizational profile34 - Review any existing legal artifacts in `.singularskills/legal/<project>/`35362. **Identify recurring legal scenarios:**37 - **Contract negotiation** — standard terms, acceptable deviations, deal-breakers38 - **Data breach response** — detection, containment, notification, remediation39 - **Employee termination** — voluntary, involuntary, for cause, layoff procedures40 - **IP dispute** — infringement claims, cease-and-desist responses, defensive actions41 - **Vendor onboarding** — due diligence, contract requirements, risk assessment42 - **M&A due diligence** — legal review scope, red flags, documentation requirements43 - **Regulatory inquiry** — response protocols, document preservation, communication rules44 - Tailor scenarios to the specific needs of "<project>"45463. **Create decision tree for each scenario:**47 - Define the triggering event (what initiates the scenario)48 - Map decision points with if/then logic (if X, then Y)49 - Identify the possible outcomes at each branch50 - Include time constraints at each decision point51 - Document the rationale for each recommended path52534. **Define approval thresholds:**54 - **Pre-approved actions** — what can proceed without legal review (e.g., standard NDA execution, routine contract renewals under a value threshold)55 - **Legal review required** — what needs internal legal sign-off (e.g., non-standard terms, contracts above value threshold, new vendor categories)56 - **Outside counsel required** — what needs external legal involvement (e.g., litigation, complex regulatory matters, high-value transactions)57 - Set clear monetary and risk-based thresholds for each level58595. **List pre-approved templates and fallback positions:**60 - For each scenario, identify available templates (NDAs, standard contracts, response letters)61 - Define preferred terms and acceptable fallback positions for negotiations62 - Document which template modifications are acceptable without additional review63 - Maintain version control references for all templates64656. **Set escalation criteria:**66 - Define when to involve internal legal counsel67 - Define when to involve outside counsel68 - Define when to notify executive leadership69 - Include specific triggers: monetary thresholds, reputational risk, regulatory exposure, litigation threats70 - Set maximum response times for each escalation level71727. **Include timeline expectations:**73 - Standard turnaround times for each scenario type74 - Expedited process for urgent matters75 - SLA definitions for legal team response76 - External dependencies and typical third-party timelines77788. **Organize playbook by audience:**79 - **Sales team** — contract negotiation, NDA procedures, deal approval workflows80 - **Engineering** — open-source compliance, IP considerations, security incident response81 - **HR** — employment law procedures, termination protocols, discrimination/harassment response82 - **Procurement** — vendor assessment, contract review, supplier risk management83 - Each audience section should be self-contained with relevant scenarios only84859. **Write the artifact** — append to `.singularskills/legal/<project>/04-govern.md` under a `## Legal Playbook` section. Create the file with a `# Govern — <project>` heading if it does not exist; if a `## Legal Playbook` section already exists, replace only that section. The section contains:8687 - **Scenario Index** — overview of all covered scenarios with quick-reference links88 - **Decision Trees** — visual decision flow per scenario89 - **Approval Matrix** — thresholds and required approvals by scenario and value90 - **Templates and Fallback Positions** — available templates with modification guidelines91 - **Escalation Guide** — when and how to escalate by scenario type92 - **Timeline Expectations** — standard and expedited turnaround times93 - **Audience-Specific Guides** — tailored playbook sections per team9495## Output9697The legal playbook appended to `.singularskills/legal/<project>/04-govern.md`. Present a summary to the user highlighting:98- Number of scenarios covered and their categorization99- Key approval thresholds and escalation triggers100- Available pre-approved templates101- Audience-specific guide overview102103**Record the run.** After you have written your section, append this line to `.singularskills/log.jsonl` (the `started` line of Prerequisites, with `"event":"finished"`): `{"ts":"<ISO timestamp>","skill":"legal-legal-playbook","workflow":"legal","phase":4,"project":"<project>","event":"finished","artifact":"04-govern.md","note":""}`.104105This artifact is shared by every skill of phase 4 (Govern). The frontmatter is written once, by whoever creates the file: if you create it, open it with the block below (`skill` is the phase title, `started` the time of that first write; `gate` is `passed` when the gate ran clean and `skipped` under `--skip-checks`); if it already exists, leave the block alone except to update `finished` and to set `gate` to the worst value among the sections (`skipped` over `passed`).106107```yaml108---109skill: Govern110workflow: legal111phase: 4112project: <project>113started: <ISO timestamp>114finished: <ISO timestamp>115agent: <the agent you run in, or "unknown">116gate: <passed|skipped>117---118```119120Open your `## Legal Playbook` section with one italic line, `*<skill name> · <ISO timestamp> · gate: <passed|skipped>*` (your skill name is `legal-legal-playbook`).121122End your section with `### Decisions` and `### Open questions` (one level under your `## Legal Playbook` heading, so the section stays one block), in this shape:123124```markdown125### Decisions126- <what was chosen> — <why> — <what was rejected>127128### Open questions129- <what the next phase or a reviewer must settle>130```