
GitHub's legal and business teams used Copilot CLI—a tool that accepts plain-language requests—to build internal AI tools without writing traditional code.
Ngandu Kasuku, a product attorney, created terms-ai to draft contracts faster and more consistently, cutting his review time roughly in half; Jesse Geraci, an online safety counsel, built a desktop app for legal workflows like DMCA analysis and contract review using plain-language instructions in Markdown.
The shift shows that non-technical professionals can automate repetitive work by using AI to encode their own methodology and judgment, rather than waiting for engineers or external vendors.
What happened
GitHub's legal, program management, and business teams—not engineers—used GitHub Copilot CLI to build internal tools that automate repetitive work. Ngandu Kasuku, a product attorney, created terms-ai, a contract drafting tool that cut his review and drafting time roughly in half. Jesse Geraci, an online safety counsel, built a desktop app for analyzing source code and handling DMCA notices, expanding it to cover contract review, NDA triage, risk assessment, and compliance checks—all using plain-language instructions rather than traditional code.
Why it matters
The tools show that non-technical professionals can use AI to solve their own workflow problems without hiring engineers or waiting for vendor software. Both lawyers used GitHub Copilot CLI to turn repetitive, time-consuming tasks into structured, reusable processes—Kasuku by organizing documents and drafting resources in one repository, Geraci by encoding legal methodology into readable Markdown files that his team could edit and customize. This approach kept human judgment central while making workflows more consistent and scalable.
What to watch
The tools are designed for specific legal workflows but hint at a broader pattern: any job with repetitive, rule-based tasks (contract review, compliance checks, data analysis, triage) may be automatable without traditional software development. Both builders emphasized that these are decision-support systems, not replacements for professional judgment—Kasuku noted his tool still has room to improve, and Geraci stressed that his legal Copilot "shouldn't be treated" as a replacement for legal review.
GitHub's legal and business team built a series of internal AI tools using Copilot CLI, a feature that accepts plain-language requests to generate and customize workflows. The team—lawyers, program managers, and business professionals—faced common pain points: repetitive tasks like reviewing similar contracts and answering recurring legal questions. Using Copilot CLI, they discovered they could build solutions without hiring engineers or waiting for external vendors.
Ngandu Kasuku, a product attorney, initially used Copilot CLI for one-off tasks but realized he could build something larger around how he actually worked. He created terms-ai, a contract drafting tool that organized key documents, instructions, and workflows in a single repository. The tool includes an internal drafting style guide based on plain-language legal principles—Kasuku had long favored simple language over archaic terms like "heretofore" and "therewith," and discovered an entire legal drafting movement shared this view. The tool also accesses a library of previously completed agreements, allowing it to draw on approved, access-controlled templates when partners send new agreements or addenda. Since building terms-ai, Kasuku has cut his review and drafting time roughly in half, and his provisions are now more consistent across agreements. The tool and its general workflow are open source, though sensitive agreements are kept in an internal repository.
Jesse Geraci, an online safety counsel, started with a different problem: analyzing source code quickly and accurately to evaluate DMCA (Digital Millennium Copyright Act) notices. His original project began as a set of GitHub Copilot instructions for recurring tasks—DMCA triage, code comparison, license checks, and circumvention review—that aimed to turn one-off prompts into something a legal team could trust. Rather than writing source code, Geraci used his legal skills to build plain-language instruction sets, policy references, and report templates. The workflow grew to include different analysis modes for clients (faster outputs with escalation recommendations) and lawyers (deeper review with both-sides arguments), as well as integrated external data sources. When he handed it to the team, they immediately adopted it and asked Copilot to do more. The foundation evolved into a full desktop app with a clean interface for running predefined legal workflows. Although the app required writing some code, the core instructions—which customize behavior and control workflow routing—remain written in plain, editable Markdown. The app now handles many in-house workflows beyond DMCA code analysis: contract review, NDA triage, risk assessment, compliance checks, and response drafting. Under the hood, it routes work through reusable skills and agents (intake, playbook alignment, risk scoring, evidence verification, escalation routing, report assembly), but legal teams control behavior through readable Markdown rather than engineering changes. Geraci emphasized that his tool is a structured decision-support system designed to keep human review central while making legal analysis more consistent, transparent, and scalable—not a replacement for legal judgment.
The article presents a case study in how non-technical professionals are using AI tooling to solve their own workflow problems. Both Ngandu Kasuku and Jesse Geraci came to GitHub Copilot CLI with a narrow, repetitive pain point—contract drafting and DMCA analysis, respectively—and discovered that they could build lasting solutions without engineering support. The key difference between their initial approaches and their final tools was architectural: Kasuku moved from one-off prompts to a single repository that centralized documents, instructions, and resources, which reduced copying and pasting and made drafting more consistent. Geraci similarly transformed ad-hoc prompts into structured instruction sets (written in plain language and Markdown) that encoded his legal methodology—including different analysis modes for clients versus lawyers, external data integration, and escalation routing—all without traditional code. Both stressed that their tools are decision-support systems, not replacements for human judgment; Kasuku acknowledged that terms-ai "still has a long way to go," and Geraci explicitly cautioned that his tool "shouldn't be treated" as a replacement for legal review. This positioning matters because it suggests that the value of these tools lies not in automation per se, but in making professional workflows more consistent, transparent, and scalable while keeping human expertise central.
AI-summarized, only the topics you pick — one digest a day via Email, Slack, or Discord.
Free · takes 30 seconds · unsubscribe anytime
Ask AI anything about this article. Q&As are published on this page for other readers too.
SpaceX AI has launched Grok Bot, an AI agent designed to handle workplace tasks and operate digital tools with…

TSMC says competition in advanced chip packaging for AI is shifting beyond single-device performance metrics t…

Passive component distributor Nichidenbo reported that supply of MLCCs (multilayer ceramic capacitors) and oth…

Foxconn reported second-quarter net profit of NT$59.97 billion ($1.86 billion), up 35 percent year-on-year, be…

Owlet Inc reported Q2 2026 total revenue of $33.9 million, up 29.9% year-over-year, with gross margin expandin…

Taiwan's Foxconn reported second-quarter net profit of T$59.97 billion ($1.86 billion) for April–June, up 35%…

The AI news that matters, in one minute each morning.
Sign up free