legal-brief

$npx mdskill add mohitagw15856/pm-claude-skills/legal-brief

This skill drafts structured legal briefs and memos using IRAC format — the standard structure for legal writing.

SKILL.md

.github/skills/legal-briefView on GitHub ↗
---
name: legal-brief
description: "Draft a structured legal brief, case summary, or legal argument outline. Use when asked to write a legal brief, case note, legal memo, argument outline, or position paper. Produces a structured document using IRAC format (Issue, Rule, Application, Conclusion)."
---

# Legal Brief Skill

This skill drafts structured legal briefs and memos using IRAC format — the standard structure for legal writing.

## Required Inputs
- **Brief type** (legal memo / case summary / argument outline / position paper / letter before action)
- **Legal issue or question**
- **Jurisdiction** (England & Wales / US / EU / Other)
- **Relevant facts**
- **Relevant law or cases** (if known — otherwise flagged as [RESEARCH NEEDED])
- **Audience** (internal memo / court submission / client letter)

## Output Structure

### Header
- **To:** [Recipient]
- **From:** [Author]
- **Date:** [Date]
- **Re:** [Matter reference]
- **Confidential:** Subject to legal professional privilege

### Issue(s)
One sentence per legal question:
- Issue 1: Whether X constitutes Y under [law]

### Brief Answer
One sentence per issue — conclusion upfront before analysis.

### Facts
Concise relevant facts only. Flag disputed facts.

### Law (Rule)
- Relevant statute, regulation, or case law
- How the rule has been interpreted in key cases
- Flag [RESEARCH NEEDED] where law is not provided

### Application
- Arguments in favour
- Counter-arguments and responses
- Areas of uncertainty flagged explicitly

### Conclusion
- Clear answer to each issue
- Overall recommendation
- Suggested next steps

### Caveats
What this memo does not cover. What additional research would change the analysis.

---

WARNING: This draft requires review by a qualified legal professional. It does not constitute legal advice.

## Quality Checks

- [ ] Issue is stated as a specific legal question (not a general topic)
- [ ] Brief answer appears before the analysis (conclusion upfront)
- [ ] Disputed facts are explicitly flagged
- [ ] Areas of legal uncertainty are noted (not hidden in confident language)
- [ ] Caveats section lists what would change the analysis
- [ ] Disclaimer is included

## Example Trigger Phrases
- "Draft a legal memo on [issue]"
- "Write a legal brief arguing [position]"
- "Summarise the legal position on [topic]"
- "Write a letter before action for [situation]"

More from mohitagw15856/pm-claude-skills

SkillDescription
360-feedback-templateDesign a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
ab-test-plannerDesign statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
accessibility-auditGenerate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
account-planBuild a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.
aeo-optimizerOptimize an article for Answer Engine Optimization (AEO) — restructuring content so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Rewrites headings as questions, drops 50-80 word answer capsules, audits paragraph length, and flags trust signals. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines.
ai-ethics-reviewConduct an ethical review of an AI or ML feature, model, or product. Use when asked to run an AI ethics review, assess AI risks, audit a model for bias, or produce an AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with prioritised mitigations.
ai-product-canvasStructure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
ambiguity-resolverStructure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y'. Produces a structured problem brief with reframed questions, scoped boundaries, and a minimum viable research plan.
api-docs-writerWrite clear, developer-facing API documentation. Use when asked to document an API endpoint, write API reference docs, create a developer guide, or turn a raw spec/Postman collection into documentation. Produces endpoint documentation with descriptions, parameters, request/response examples, and error codes.
api-versioning-strategyWrite an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline, migration guide template, and client communication template.