![\"AI](\"https:\/\/i0.wp.com\/www.attorneyatwork.com\/wp-content\/uploads\/2026\/04\/Actionable-law-firm-SOPs.jpg?resize=770%2C495&ssl=1\" "\\"\\"")
Table of contents<\/h2>\n\n- Your SOPs Are Collecting Dust: Here Is What to Do About It<\/a><\/li>\n
- The Problem With Traditional SOPs<\/a><\/li>\n
- Beyond the Binder: Enter AI Skills for Law Firms<\/a>\n
\n- What Is an AI Skill?<\/a><\/li>\n<\/ul>\n<\/li>\n
- Breaking Workflows Into Pieces With Claude<\/a><\/li>\n
- The Markdown Advantage<\/a>\n
\n- The Skill becomes the source of truth.<\/a><\/li>\n<\/ul>\n<\/li>\n
- Where to Start With AI Skills<\/a><\/li>\n
- More From Ernie Svenson and the 80\/20 Principle<\/a><\/li>\n<\/ul>\n<\/div>\n
Your SOPs Are Collecting Dust: Here Is What to Do About It<\/h2>\n
Let\u2019s say that you\u2019re inspired to systematize your law practice, and so you meticulously document how things should be done \u2014 client intake steps, document formatting preferences, billing procedures.\u00a0 They\u2019re stored in a shared folder (or God forbid, a paper binder).<\/p>\n
Then what happens? Nobody uses directions. Including you.\u00a0<\/p>\n
Look, here\u2019s the harsh truth.<\/p>\n
Standard operating procedures are great in theory. In practice, they often relate to software that steadily changes. The screenshots and video guides become outdated and no longer accurate. In other words, useless.<\/p>\n
I am not here to tell you that all SOPs are useless. A well-run business still needs documented processes, maybe even some that are stored in paper form.\u00a0<\/p>\n
But modern businesses now need to account for AI-driven workflows. And the traditional form of SOPs is a bottleneck for those workflows. In fact, traditional SOPs are becoming less useful for many kinds of workflows, not just the AI ones.<\/p>\n
The Problem With Traditional SOPs<\/h2>\n
The friction with written SOPs is not the writing. It is everything that happens after.<\/p>\n
You write a 10-step intake checklist. Six months later, you add a new practice area and forget to update it. A year later, your assistant finds the old version and follows the wrong steps. Or more likely, nobody looks at it at all because pulling up a document, reading through it, and translating it into action takes more effort than just winging it.<\/p>\n
Written SOPs are static. They describe a process but do not participate in it. They are a reference document when what you actually need is a working tool.<\/p>\n
Beyond the Binder: Enter AI Skills for Law Firms<\/h2>\n
In my last column<\/a>, I wrote about switching from ChatGPT to Claude and discovering what I had been missing. One of the things I mentioned was Claude\u2019s ability to build custom AI Skills \u2014 reusable instruction sets that tell Claude exactly how to handle a specific task.<\/p>\nI want to go deeper on that idea here, because I think AI Skills represent something more significant than a productivity trick. AI skills for law firms are the modern replacement for how we store and apply process knowledge.<\/p>\n
What Is an AI Skill? <\/h3>\n
A Skill is a plain-text file, written in markdown, that contains your instructions for a specific task. It can include your preferences, your templates, your decision criteria, your formatting rules \u2014 anything you would put in an SOP. The difference is that instead of sitting in a folder waiting to be read, it lives inside Claude and gets applied automatically every time you do that task.<\/p>\n
Here is a simple example.<\/strong> Say you have a standard way you want demand letters drafted \u2014 a specific structure, a tone, certain information that always needs to be included. Traditionally, you would write that up as an SOP or a template with instructions.<\/p>\nWith a Skill, you write those same instructions in a format Claude can follow. Then every time you ask Claude to draft a demand letter, it already knows your preferences. No looking anything up. No reminding anyone. The process is built into the tool.<\/p>\n
Breaking Workflows Into Pieces With Claude<\/h2>\n
The real power shows up when you start thinking in terms of \u201cconnected Skills\u201d rather than a single monolithic SOP.<\/p>\n
Take document drafting, which is something every lawyer does constantly. Instead of one massive set of instructions, you can break the workflow into discrete steps: a drafting Skill that selects from your library of templates and handles the initial draft, a review Skill that checks for your law firm\u2019s voice and formatting standards, and a finalizing Skill that handles the finishing touches \u2014 adding your letterhead, checking typography, and preparing the document for delivery.<\/p>\n
Each Skill has a focused job. Each one can be updated independently. And Claude moves through them in sequence, applying the right context at each stage.<\/p>\n
This is not theoretical. I use this approach for my own content workflows, and the lawyers in my community who have started building Skills are finding the same thing: once you set them up, the quality and consistency of the output go up immediately.<\/p>\n
The Markdown Advantage<\/h2>\n
Here is something that might not be obvious at first. Because Skills are written in plain-text markdown, they are readable by both AI and people. That means your Skill file can serve double duty.<\/p>\n
If you need to hand a process to a human \u2014 a new assistant, a contract attorney, a colleague covering your cases \u2014 you can share the markdown file directly. It reads like a clear set of instructions. Or you can have Claude convert it into a formatted Word document with headers, numbered steps, and your firm\u2019s branding.<\/p>\n
The Skill becomes the source of truth. <\/h3>\n
The human-readable SOP becomes a downstream output \u2014 one that Claude can regenerate any time the underlying process changes.<\/p>\n
This flips the traditional approach on its head. Instead of writing an SOP and hoping it gets followed, you build a working instruction set that produces both AI-guided execution and human-readable documentation from the same source.<\/p>\n
Skills Evolve, Rigid Checklists Do Not<\/h2>\n
Maintenance is the other advantage of AI Skills for law firms. Traditional SOPs start decaying the moment you finish writing them. Updating them requires finding the document, editing it, and redistributing it \u2014 which is why most of them never get updated.<\/p>\n
Skills are different. When something in your process changes, you tell Claude to update the Skill. It does. The next time you run that workflow, the updated instructions are already in place. No redistribution. No version-control headaches. No wondering whether someone is working from the old version.<\/p>\n
Claude can also help you build Skills in the first place. You do not have to know Markdown or write instructions from scratch. You can describe your process conversationally, and Claude will structure it into a working Skill. Then you use it, notice what needs tweaking, and refine it together.<\/p>\n
Where to Start With AI Skills<\/h2>\n
If this is new to you, the best first Skill to build is probably something you do often and wish were more consistent \u2014 drafting a particular type of document, running through an intake process, or preparing for a specific kind of meeting.<\/p>\n
Start with one. Describe your process to Claude<\/a>. Let it build the Skill. Use it a few times and see what needs adjusting. You will be surprised how quickly the output starts matching what you actually want \u2014 and how much less time you spend getting there.<\/p>\nThe shift here is not about abandoning documentation. It is about putting your process knowledge somewhere it actually gets used. <\/p>\n
SOPs told people what to do. Skills tell your AI how to do it \u2014 and they can still tell people what to do when that is what you need.<\/p>\n
For solo and small-firm lawyers especially, this is a meaningful change. You do not have a training department or an operations team to enforce process consistency. Now you do not need one. Your processes live inside the tool you are already using, and they work every time you show up.<\/p>\n
More From Ernie Svenson and the 80\/20 Principle<\/h2>\n
Why I Switched From ChatGPT to Claude (And What Finally Pushed Me Over)<\/a><\/p>\nLoom for Lawyers: Why You Should Be Creating Shareable Videos<\/a><\/p>\nTop 8 Tech Tools for Solo and Small Firm Lawyers to End the Chaos<\/a><\/p>\nAI Tools for Lawyers: Why You Shouldn\u2019t Stick to Just One<\/a><\/p>\nOur Fingers Can\u2019t Keep Up With AI<\/a><\/p>\nImage \u00a9 iStockPhoto.com. <\/p>\n
\n![\"\"](\"https:\/\/i0.wp.com\/www.attorneyatwork.com\/wp-content\/uploads\/2023\/06\/AttorneyatWork-Logo-%C2%AE-2021-1.jpg?resize=372%2C106&ssl=1\" "\\"\\"")
<\/a><\/figure>\n\nSign up for Attorney at Work\u2019s daily practice tips newsletter here<\/a> and subscribe to our podcast<\/a>, Attorney at Work Today.<\/strong><\/p>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"AI skills are more than a productivity trick, says Ernie Svenson. They are the modern replacement for how we store and apply process knowledge. Here’s how custom skills reinvent SOPs for your law firm’s daily workflows. The post How Using AI Skills for Law Firm Workflows Can Turbocharge Your SOPs appeared first on Articles, Tips […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[17],"tags":[],"class_list":["post-149268","post","type-post","status-publish","format-standard","hentry","category-legal_matters"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/posts\/149268","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/comments?post=149268"}],"version-history":[{"count":0,"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/posts\/149268\/revisions"}],"wp:attachment":[{"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/media?parent=149268"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/categories?post=149268"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/tags?post=149268"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- \n
- What Is an AI Skill?<\/a><\/li>\n<\/ul>\n<\/li>\n
- Breaking Workflows Into Pieces With Claude<\/a><\/li>\n
- The Markdown Advantage<\/a>\n
- \n
- The Skill becomes the source of truth.<\/a><\/li>\n<\/ul>\n<\/li>\n
- Where to Start With AI Skills<\/a><\/li>\n
- More From Ernie Svenson and the 80\/20 Principle<\/a><\/li>\n<\/ul>\n<\/div>\n
Your SOPs Are Collecting Dust: Here Is What to Do About It<\/h2>\n
Let\u2019s say that you\u2019re inspired to systematize your law practice, and so you meticulously document how things should be done \u2014 client intake steps, document formatting preferences, billing procedures.\u00a0 They\u2019re stored in a shared folder (or God forbid, a paper binder).<\/p>\n
Then what happens? Nobody uses directions. Including you.\u00a0<\/p>\n
Look, here\u2019s the harsh truth.<\/p>\n
Standard operating procedures are great in theory. In practice, they often relate to software that steadily changes. The screenshots and video guides become outdated and no longer accurate. In other words, useless.<\/p>\n
I am not here to tell you that all SOPs are useless. A well-run business still needs documented processes, maybe even some that are stored in paper form.\u00a0<\/p>\n
But modern businesses now need to account for AI-driven workflows. And the traditional form of SOPs is a bottleneck for those workflows. In fact, traditional SOPs are becoming less useful for many kinds of workflows, not just the AI ones.<\/p>\n
The Problem With Traditional SOPs<\/h2>\n
The friction with written SOPs is not the writing. It is everything that happens after.<\/p>\n
You write a 10-step intake checklist. Six months later, you add a new practice area and forget to update it. A year later, your assistant finds the old version and follows the wrong steps. Or more likely, nobody looks at it at all because pulling up a document, reading through it, and translating it into action takes more effort than just winging it.<\/p>\n
Written SOPs are static. They describe a process but do not participate in it. They are a reference document when what you actually need is a working tool.<\/p>\n
Beyond the Binder: Enter AI Skills for Law Firms<\/h2>\n
In my last column<\/a>, I wrote about switching from ChatGPT to Claude and discovering what I had been missing. One of the things I mentioned was Claude\u2019s ability to build custom AI Skills \u2014 reusable instruction sets that tell Claude exactly how to handle a specific task.<\/p>\n
I want to go deeper on that idea here, because I think AI Skills represent something more significant than a productivity trick. AI skills for law firms are the modern replacement for how we store and apply process knowledge.<\/p>\n
What Is an AI Skill? <\/h3>\n
A Skill is a plain-text file, written in markdown, that contains your instructions for a specific task. It can include your preferences, your templates, your decision criteria, your formatting rules \u2014 anything you would put in an SOP. The difference is that instead of sitting in a folder waiting to be read, it lives inside Claude and gets applied automatically every time you do that task.<\/p>\n
Here is a simple example.<\/strong> Say you have a standard way you want demand letters drafted \u2014 a specific structure, a tone, certain information that always needs to be included. Traditionally, you would write that up as an SOP or a template with instructions.<\/p>\n
With a Skill, you write those same instructions in a format Claude can follow. Then every time you ask Claude to draft a demand letter, it already knows your preferences. No looking anything up. No reminding anyone. The process is built into the tool.<\/p>\n
Breaking Workflows Into Pieces With Claude<\/h2>\n
The real power shows up when you start thinking in terms of \u201cconnected Skills\u201d rather than a single monolithic SOP.<\/p>\n
Take document drafting, which is something every lawyer does constantly. Instead of one massive set of instructions, you can break the workflow into discrete steps: a drafting Skill that selects from your library of templates and handles the initial draft, a review Skill that checks for your law firm\u2019s voice and formatting standards, and a finalizing Skill that handles the finishing touches \u2014 adding your letterhead, checking typography, and preparing the document for delivery.<\/p>\n
Each Skill has a focused job. Each one can be updated independently. And Claude moves through them in sequence, applying the right context at each stage.<\/p>\n
This is not theoretical. I use this approach for my own content workflows, and the lawyers in my community who have started building Skills are finding the same thing: once you set them up, the quality and consistency of the output go up immediately.<\/p>\n
The Markdown Advantage<\/h2>\n
Here is something that might not be obvious at first. Because Skills are written in plain-text markdown, they are readable by both AI and people. That means your Skill file can serve double duty.<\/p>\n
If you need to hand a process to a human \u2014 a new assistant, a contract attorney, a colleague covering your cases \u2014 you can share the markdown file directly. It reads like a clear set of instructions. Or you can have Claude convert it into a formatted Word document with headers, numbered steps, and your firm\u2019s branding.<\/p>\n
The Skill becomes the source of truth. <\/h3>\n
The human-readable SOP becomes a downstream output \u2014 one that Claude can regenerate any time the underlying process changes.<\/p>\n
This flips the traditional approach on its head. Instead of writing an SOP and hoping it gets followed, you build a working instruction set that produces both AI-guided execution and human-readable documentation from the same source.<\/p>\n
Skills Evolve, Rigid Checklists Do Not<\/h2>\n
Maintenance is the other advantage of AI Skills for law firms. Traditional SOPs start decaying the moment you finish writing them. Updating them requires finding the document, editing it, and redistributing it \u2014 which is why most of them never get updated.<\/p>\n
Skills are different. When something in your process changes, you tell Claude to update the Skill. It does. The next time you run that workflow, the updated instructions are already in place. No redistribution. No version-control headaches. No wondering whether someone is working from the old version.<\/p>\n
Claude can also help you build Skills in the first place. You do not have to know Markdown or write instructions from scratch. You can describe your process conversationally, and Claude will structure it into a working Skill. Then you use it, notice what needs tweaking, and refine it together.<\/p>\n
Where to Start With AI Skills<\/h2>\n
If this is new to you, the best first Skill to build is probably something you do often and wish were more consistent \u2014 drafting a particular type of document, running through an intake process, or preparing for a specific kind of meeting.<\/p>\n
Start with one. Describe your process to Claude<\/a>. Let it build the Skill. Use it a few times and see what needs adjusting. You will be surprised how quickly the output starts matching what you actually want \u2014 and how much less time you spend getting there.<\/p>\n
The shift here is not about abandoning documentation. It is about putting your process knowledge somewhere it actually gets used. <\/p>\n
SOPs told people what to do. Skills tell your AI how to do it \u2014 and they can still tell people what to do when that is what you need.<\/p>\n
For solo and small-firm lawyers especially, this is a meaningful change. You do not have a training department or an operations team to enforce process consistency. Now you do not need one. Your processes live inside the tool you are already using, and they work every time you show up.<\/p>\n
More From Ernie Svenson and the 80\/20 Principle<\/h2>\n
Why I Switched From ChatGPT to Claude (And What Finally Pushed Me Over)<\/a><\/p>\n
Loom for Lawyers: Why You Should Be Creating Shareable Videos<\/a><\/p>\n
Top 8 Tech Tools for Solo and Small Firm Lawyers to End the Chaos<\/a><\/p>\n
AI Tools for Lawyers: Why You Shouldn\u2019t Stick to Just One<\/a><\/p>\n
Our Fingers Can\u2019t Keep Up With AI<\/a><\/p>\n
Image \u00a9 iStockPhoto.com. <\/p>\n
\n<\/a><\/figure>\n\nSign up for Attorney at Work\u2019s daily practice tips newsletter here<\/a> and subscribe to our podcast<\/a>, Attorney at Work Today.<\/strong><\/p>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
AI skills are more than a productivity trick, says Ernie Svenson. They are the modern replacement for how we store and apply process knowledge. Here’s how custom skills reinvent SOPs for your law firm’s daily workflows. The post How Using AI Skills for Law Firm Workflows Can Turbocharge Your SOPs appeared first on Articles, Tips […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[17],"tags":[],"class_list":["post-149268","post","type-post","status-publish","format-standard","hentry","category-legal_matters"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/posts\/149268","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/comments?post=149268"}],"version-history":[{"count":0,"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/posts\/149268\/revisions"}],"wp:attachment":[{"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/media?parent=149268"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/categories?post=149268"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/tags?post=149268"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- Where to Start With AI Skills<\/a><\/li>\n
- Breaking Workflows Into Pieces With Claude<\/a><\/li>\n