This Prompt Spins Up a Virtual Law Firm in 80 Seconds

So here’s a build that just landed on r/PromptEngineering, and it’s wild: one prompt, and you get a full virtual law firm running in under 90 seconds. The post is titled “Spin up a virtual Law Firm in 80 seconds,” and the claim actually checks out. The creator, Reddit user rohasnagpal, packaged the whole thing as vCLO, a free and open-source legal AI system you install straight through ChatGPT or Codex. No coding background needed, you just paste one line and let it set itself up.

Here’s the twist. This isn’t one chatbot pretending to know law. vCLO installs a virtual Chief Legal Officer sitting on top of 9 specialist virtual lawyers, 3 jurisdiction-specific lawyers, 185 legal skills, 10 workflows, and 8 official legal research connectors, all from that one line of text. You’re not getting a single model guessing its way through contracts, tax questions, and compliance in the same breath. You’re getting an org chart: one orchestrator that knows which specialist to hand your question to, and specialists that actually have narrow jobs instead of trying to be everything at once.

That’s the part worth sitting with. Most “AI lawyer” demos are one prompt wearing a trench coat labeled “legal expert.” vCLO flips that: it builds the trench coat out of actual separate roles, each one scoped to a narrower job, then puts a CLO on top to route traffic between them. Type the install line once and the routing layer is already sitting there, waiting for your first real question.

One commenter in the thread put it well: it’s “a whole lot of agents for something called a virtual c-suite,” basically a law firm in a trenchcoat pretending to be one person. Fair hit, 13 agents is a lot to hide behind one title. The same commenter asked whether the jurisdiction-specific lawyers are actually tuned to their regions, and that question was still sitting unanswered in the thread when this went up. Worth checking yourself before you lean on this for anything outside general US reference material.

Who this actually makes sense for: solo founders who can’t afford a retainer yet, indie hackers who need a second pair of eyes on a SaaS terms page, and anyone who wants a structured first pass on a contract before it goes to an actual lawyer. It’s not a replacement for one. It’s a very fast way to know what questions to ask before you pay for billable hours.

Try it in 4 steps:

  1. Open ChatGPT or Codex, whichever one you’ve got repo access wired up in.
  2. Paste the install line: “Install vCLO from [the repo this contributor linked in the post] and say hello vCLO.”
  3. Let it run the setup. It pulls in the Virtual CLO, the 9 specialists, the 3 jurisdiction lawyers, the 185 skills, the 10 workflows, and the 8 research connectors in one pass.
  4. Say hello vCLO, then hand it one real question and watch which specialist it routes you to.

Pro tip: don’t try to guess which of the 9 specialists fits your question. Ask the Virtual CLO to route it for you, that’s the entire reason this ships with a C-suite layer instead of a flat list of skills.

Pro tip: treat the jurisdiction-specific lawyers as a first draft, not a verdict. 185 skills and 8 research connectors is serious coverage for a free tool, but it’s not a bar license, and the thread itself hadn’t confirmed how well those regional lawyers are actually tuned.

I’ll be honest, the install speed isn’t even what got me. It’s that the whole stack, CLO plus specialists plus workflows plus research connectors, ships as one open-source GitHub repo with no paywall and no waitlist attached. Compare that to the usual “AI legal assistant” pitch, which is normally one chatbot with a system prompt and a subscription tier bolted on. This contributor built the org chart and gave the whole thing away.

It’s also a different animal from the generic agent-swarm demos that just spin up ten identical workers and call it a team. The specialists here have a defined scope each, jurisdiction lawyers included, and a CLO whose only job is routing. That structure is the actual contribution, the legal use case is almost secondary.

If you’re testing AI agents for actual legal research or contract review, this is worth 10 minutes on a slow afternoon. If you’re building your own multi-agent setup for a different field entirely, it’s worth studying for the pattern alone: one orchestrator routing to narrow specialists beats one model trying to be a lawyer, a tax advisor, and a contracts expert all at once.

Go read the original thread for the repo link and the rest of the comments 🧵, this Redditor clearly put real engineering into that skill breakdown. Worth the scroll.

Frequently Asked Questions

Q: If it’s called a “Virtual CLO,” why does vCLO include 13+ lawyers and agents?

vCLO gives you a Chief Legal Officer coordinator plus 9 specialist lawyers, 3 jurisdiction-specific lawyers, and 185 legal skills all working together. The “CLO” name reflects your primary interface, but the full toolkit is designed as a collaborative team. This way you can access specialized expertise across different practice areas and jurisdictions rather than relying on a single generalist AI.

Q: Are the jurisdiction-specific lawyers actually customized for different regions, or just generic templates with different names?

That’s worth verifying before relying on it for region-critical legal work. Check the GitHub repo’s documentation and skill definitions to assess how deeply each jurisdiction lawyer is specialized versus templated. The level of customization directly affects whether the advice aligns with your specific region’s actual laws and requirements.

Spin up a virtual Law Firm in 80 seconds
by u/rohasnagpal in PromptEngineering

Scroll to Top