# AI use cases for Iso 24495 (GaZmagik/iso-24495) Repo: [GaZmagik/iso-24495](https://github.com/GaZmagik/iso-24495) | Use cases: 5 | Page: https://dedupedai.com/use-cases/gazmagik-iso-24495/ A set of seven Agent Skills and a Claude Code plugin that help people and AI agents write, audit, and structure text in plain language, based on ISO 24495 principles. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Audit a Markdown or text file for plain language issues: https://dedupedai.com/use-cases/gazmagik-iso-24495/audit-markdown-for-plain-language/ - Rewrite contract or licence clauses in plain language: https://dedupedai.com/use-cases/gazmagik-iso-24495/rewrite-licence-clauses-plainly/ - Make code names, comments, and error messages easier to read: https://dedupedai.com/use-cases/gazmagik-iso-24495/plainer-code-comments-and-errors/ - Hold every Codex response to plain language rules: https://dedupedai.com/use-cases/gazmagik-iso-24495/enforce-plain-language-in-codex-responses/ - Run a plain language gap analysis across an organisation: https://dedupedai.com/use-cases/gazmagik-iso-24495/run-organisation-plain-language-gap-analysis/ ## How to audit a Markdown or text file for plain language issues with Iso 24495 Repo: [GaZmagik/iso-24495](https://github.com/GaZmagik/iso-24495) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Run the text audit on one file or folder and get findings with file, line, and rule. **Who it is for:** A technical writer or maintainer preparing a policy, guide, or README who wants a mechanical check before publishing. **The problem:** Long sentences, legalese, skipped heading levels, and unexplained acronyms are easy to miss when reading your own draft. **The outcome:** A list of findings, each with its file, line, rule, and explanation, with no changes made to the file. ### Steps 1. Add the marketplace: `/plugin marketplace add https://github.com/GaZmagik/iso-24495.git` 2. Install the plugin: `/plugin install iso-24495-plain-language@iso-24495` 3. Run the audit on one file: `/iso-24495-plain-language:iso-24495-text-audit docs/policy.md` 4. Review each finding and make the edits yourself, since the audit changes nothing. ### Prompt to paste into your agent ```text Using the iso-24495 repository, run the iso-24495-text-audit skill on . Report each finding with its file, line, rule, and explanation, and make no edits. Verify that the report states that zero findings does not prove the text suits its audience. ``` ### Caveat The audit covers only the rules it implements and reads English only, so a clean result does not show that a document suits its readers. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/gazmagik-iso-24495/audit-markdown-for-plain-language/ ## How to rewrite contract or licence clauses in plain language with Iso 24495 Repo: [GaZmagik/iso-24495](https://github.com/GaZmagik/iso-24495) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Apply the legal writing skill to contract, licence, or compliance text. **Who it is for:** A contract owner or compliance lead who must make licence or policy wording readable for staff or customers. **The problem:** Legal text uses legalese, unnamed actors, and cross-references that point at nothing a reader can find. **The outcome:** Clauses with standard modal verbs, named actors, defined terms, and a summary layer over the operative text, with legal accuracy kept. ### Steps 1. Add the marketplace: `/plugin marketplace add https://github.com/GaZmagik/iso-24495.git` 2. Install the plugin: `/plugin install iso-24495-plain-language@iso-24495` 3. Ask the agent to apply the skill by name, for example: "Apply `iso-24495-2` to this licence text." 4. Check each rewritten clause against the original for any change in legal meaning before you use it. ### Prompt to paste into your agent ```text Using the iso-24495 repository, apply the iso-24495-2 skill to the clauses in . Return the rewritten text with a summary layer and defined terms, and list any clause where the legal meaning may have changed. Verify that each clause keeps its named actors and modal verbs. ``` ### Caveat The README says technical and legal accuracy always supersede formatting rules, so a lawyer must review any rewritten clause before use. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/gazmagik-iso-24495/rewrite-licence-clauses-plainly/ ## How to make code names, comments, and error messages easier to read with Iso 24495 Repo: [GaZmagik/iso-24495](https://github.com/GaZmagik/iso-24495) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Apply the code skill to source files so readers can follow order, names, and errors. **Who it is for:** A developer reviewing a module that new team members find hard to follow. **The problem:** Units appear in an unhelpful order, names are unclear, and error messages do not say what the reader should do next. **The outcome:** Suggested changes to file structure, naming, comments, and error text, with correctness kept. ### Steps 1. Add the marketplace: `/plugin marketplace add https://github.com/GaZmagik/iso-24495.git` 2. Install the plugin: `/plugin install iso-24495-plain-language@iso-24495` 3. Ask the agent to apply the code skill to one file, for example: "Apply `iso-24495-code` to this module." 4. Run your existing tests before and after accepting changes. ### Prompt to paste into your agent ```text Using the iso-24495 repository, apply the iso-24495-code skill to . Return proposed changes to unit order, names, comments, and error messages, each with a reason. Verify that the proposed changes do not alter behaviour by running the project's tests. ``` ### Caveat The README says the code skill is measured to change how Claude structures a file at no cost to correctness, which is a project measurement, not a guarantee for your code. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/gazmagik-iso-24495/plainer-code-comments-and-errors/ ## How to hold every Codex response to plain language rules with Iso 24495 Repo: [GaZmagik/iso-24495](https://github.com/GaZmagik/iso-24495) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Add the iso-24495-style skill to AGENTS.md so every Codex answer follows the core rules. **Who it is for:** A developer who uses Codex CLI on a team project and wants consistent, plain answers from the agent. **The problem:** Agents default to filler preambles, long sentences, and passive voice unless their instructions say otherwise. **The outcome:** Codex applies the output style to each response in that project. ### Steps 1. Add the marketplace: `codex plugin marketplace add https://github.com/GaZmagik/iso-24495.git` 2. Install the plugin: `codex plugin add iso-24495-plain-language@iso-24495` 3. Add this line to your project's `AGENTS.md`: Apply `iso-24495-style` to every response. 4. Start a new Codex session and check that a response has no filler opening and uses short sentences. ### Prompt to paste into your agent ```text Using the iso-24495 repository, confirm that the iso-24495-style skill is installed for this project and that AGENTS.md names it. Answer a test question in plain language with no filler opening, then report which style rules the answer follows. Verify the AGENTS.md line is present before you report success. ``` ### Caveat The README notes that an AGENTS.md inside a plugin is ignored, so the line must go in your project's own AGENTS.md or ~/.codex/AGENTS.md. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/gazmagik-iso-24495/enforce-plain-language-in-codex-responses/ ## How to run a plain language gap analysis across an organisation with Iso 24495 Repo: [GaZmagik/iso-24495](https://github.com/GaZmagik/iso-24495) | Difficulty: Advanced | Time: 1 hour | Basis: From the README Use the Part 4 skill and Bun tooling to score and track plain language maturity. **Who it is for:** A compliance or communications lead who must assess plain language across many organisational documents and repeat the check over time. **The problem:** Without a consistent scoring method, teams cannot compare plain language maturity or show progress between reviews. **The outcome:** A maturity assessment with deterministic scoring and an append-only audit trend, based on the provisional Part 4 guidance. ### Steps 1. Install Bun from https://bun.sh 2. Clone the repository and open its root folder 3. Run `bun test` to check the tooling before you rely on it 4. Invoke the `iso-24495-4` skill by name and point it at your document set. 5. Keep the audit trend file, since each run is appended to it. ### Prompt to paste into your agent ```text Using the iso-24495 repository, apply the iso-24495-4 skill to the document set at . Return the five-dimension maturity scores and the findings behind each score. Verify that the bun test suite passes before you trust the output. ``` ### Caveat The Part 4 skill is provisional guidance based on an unpublished committee draft, so its scores are not a measure of ISO conformance. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/gazmagik-iso-24495/run-organisation-plain-language-gap-analysis/