Skip to main content
User Stories

Case 16: Legal Analysis Skill

Scenario

David is a senior partner at a law firm with over 20 years in commercial disputes. He has a clear methodology: timeline, identify issues, assess evidence strength, then litigation strategy. The problem: it’s all in his head. Each new case means repeating the process; training juniors is hard. He wanted to turn it into a reusable tool.

File Prep

David organizes each case in a folder: 
Desktop/Case-Smith-Contract-Dispute/
├── Complaint.docx
├── Contract-Scan.pdf
├── Amendment.pdf
├── Chat-Screenshots/
│   ├── 2024-01-chat.png
│  ├── 2024-03-chat.png
│  └── ...
├── Bank-Transfer-Records.pdf
└── Opposing-Counsel-Letter.pdf
1

Select your folder

Select the case folder.
2

Run analysis

Read all materials in this folder and analyze using this framework:
1. Timeline: list events in chronological order
2. Issues: identify core disputes (validity, breach, damages, etc.)
3. Evidence:
   - For each issue: our evidence vs. likely rebuttals
   - Strength (strong/medium/weak)
   - Gaps and how to strengthen
4. Strategy: main arguments, fallbacks, risks
5. Produce a case analysis report (Word)
3

Package as Skill (optional)

After a good run, tell QoderWork:
Package this analysis flow as a Skill named "Commercial Dispute Case Analysis":
- Input: case materials folder
- Output: timeline + issues + evidence analysis + strategy report
- Framework fixed; content varies by case
Junior lawyers can now run the Skill on a case folder and get a standardized report for David to review.

Key Metrics

MetricResult
Experience reuse20 years of practice in a Skill
Team enablementJuniors produce quality analysis
DepthStrong legal domain use case

Pro Tips

Use Skill packaging to turn your methodology into a reusable tool. David: (1) wrote the analysis framework in the prompt clearly, and (2) used create-skill to turn the flow into a Skill with defined inputs and outputs. The result: team can run it consistently, and his expertise stays in the team. Run it once with a structured prompt, then package as a Skill for the whole team.
Getting Started
Installation
Features
Workbenches
Best Practices
User Stories