Thinkerbell
Blog
← The AI Requirements Toolkit

Step by step · no experience assumed

How to install the toolkits

Enough people have written to me about this that it deserves its own page. If you have never used GitHub or typed a command into a terminal, start here — there is also a route that skips installing anything at all.

First, what you are actually installing

Nothing frightening. Each toolkit is a folder of Markdown text files — the same kind of document you would write in Word, just plain text. They contain instructions: how to run a requirements workshop, what makes an acceptance criterion testable, which questions to ask before comparing two regulations.

Installing a “plugin” hands those instructions to your AI assistant so it follows the method without you pasting anything. No program is installed on your computer beyond the assistant itself, and no code runs behind your back — you can read every file first, on GitHub, in your browser.

Two words you will meet

A marketplace is just a catalogue — telling your assistant “this GitHub repository has things you can install”. A plugin is one item from that catalogue. That is why installing takes two commands instead of one: point at the catalogue, then pick from it.

Pick a route

All four get you to the same place. Take the first one if the words “terminal” or “command line” make you tense.

A · Claude desktop app — recommendedDownload an app, click through a normal installer, type two commands into a chat box. No terminal.B · Claude Code in a terminalThe classic route. One install command, then the same two commands as above.C · Codex, in the ChatGPT terminalSame idea, one extra step: Codex needs its GitHub plugin installed before it can find the toolkit.D · No install at allOpen the files on GitHub, copy the one you need, paste it into any chat. Works with any assistant, on any plan.

Route A

Claude desktop app — no terminal

Claude Code — the thing that runs the skills — also comes as a normal desktop application. You install it the way you install any other app.

  1. Check your Claude plan

    You need Claude Pro, Max, Team or Enterprise. The free Claude plan does not include Claude Code, and the install will not work without one of those.

  2. Download and install the app

    Get it from claude.com/download for macOS or Windows (Linux is available as a beta). Open the downloaded file and follow the installer, exactly like any other program.

    On Windows you also need Git for Windows installed the first time you open the Code tab — install it, then restart the app.

  3. Sign in and open the Code tab

    Launch Claude, sign in with your Claude account, and click the Code tab at the top. Choose any folder when it asks — it does not have to be a software project. A folder for your requirements documents is perfect.

  4. Type the two install commands

    In the chat box, type the first line and press Enter, then the second. They start with a slash — that is how you tell Claude it is a command rather than a question.

    Install the Requirements Engineering Toolkit
    ›/plugin marketplace add clarityisrare/ai-requirements-toolkit
    ›/plugin install requirements-toolkit@ai-requirements-toolkit

    Copy both lines with the button, then paste and send them one at a time.

  5. Confirm it worked

    Click the + button next to the prompt box and choose Plugins — you should see the toolkit listed with its skills. If the install message said Run /reload-plugins to activate, send /reload-plugins first.

Route B

Claude Code in a terminal

A terminal is a window where you type instructions instead of clicking them. On a Mac, press ⌘ + Space, type Terminal, press Enter. On Windows, press the Start button and type PowerShell.

  1. Install Claude Code

    Copy the line for your system, paste it into the terminal window, press Enter, and wait for it to finish.

    macOS, Linux, WSL
    ›curl -fsSL https://claude.ai/install.sh | bash
    Windows PowerShell
    ›irm https://claude.ai/install.ps1 | iex

  2. Check it installed

    Type claude --version and press Enter. You should see a version number. If you get command not found, close the terminal, open a new one, and try again — the new command only appears in fresh windows.

  3. Start it in a folder

    Type claude and press Enter. The first time, it opens your browser so you can log in with your Claude account. Any folder works — it does not need to be code.

  4. Add the toolkit

    Now you are talking to Claude. Send these two lines, one at a time.

    Install the Requirements Engineering Toolkit
    ›/plugin marketplace add clarityisrare/ai-requirements-toolkit
    ›/plugin install requirements-toolkit@ai-requirements-toolkit

    If the install message says Run /reload-plugins to activate, send /reload-plugins next.

  5. Confirm and use it

    Send /plugin list to see what is installed. Then just describe your task in plain English — “help me turn this business request into testable requirements” — and the right skill picks itself up. To be explicit, type the skill's full name, e.g. /requirements-toolkit:requirements-writer.

Route C

Codex, in the ChatGPT terminal

Both toolkits also ship as Codex plugins. Install Codex following OpenAI's instructions, then run the same kind of commands inside it. One extra step here that Claude does not need — and it is the first one.

  1. Install the GitHub plugin first

    Codex cannot read a catalogue from GitHub until its GitHub plugin is installed, so this has to happen before anything else. In the Codex terminal window, open the plugin browser:

    /plugins

    A list of available plugins appears. Find the GitHub icon and double-click it to install. Then start a new Codex session so it is active.

    Skip this and the next step fails with a marketplace error. Claude Code resolves GitHub on its own, which is why routes A and B have no equivalent step.

  2. Add the toolkit

    With the GitHub plugin in place, send these lines one at a time.

    Install in Codex
    ›/plugin marketplace add clarityisrare/ai-requirements-toolkit
    ›/plugin install requirements-toolkit
    ›/reload-plugins

    If the skills still do not appear afterwards, start a new Codex session.

Route D

No install at all

The toolkits were plain text files before they were plugins, and they still are. This route works on a free plan, on a locked-down work laptop, and with any assistant you already use.

  1. Open the repository in your browser

    No account, no download. GitHub is just a website showing folders of documents.

    Requirements Engineering Toolkit →Regulatory Reporting Toolkit →

  2. Open the folder you need

    In the requirements toolkit: prompts for something to paste, checklists to review someone's work, templates to start a document, patterns for a feature you have specified before. Click a .md file to read it.

  3. Copy it and paste it into your chat

    Use the copy button at the top right of the file view, paste it into Claude, ChatGPT or your company assistant, and add your own material underneath. That is the whole trick — the plugin version just saves you the pasting.

Updating and removing

Get the latest version

New skills and fixes land in the repo over time. Refresh the catalogue, then reinstall:

/plugin marketplace update ai-requirements-toolkit

Remove it again

Nothing is left behind, and you can reinstall any time:

/plugin uninstall requirements-toolkit@ai-requirements-toolkit

Every command, in one place

If you skipped the walkthrough, this is all of it. The two toolkits are independent — install one, or both.

Requirements Engineering Toolkit

What it does →
Claude Code
›/plugin marketplace add clarityisrare/ai-requirements-toolkit
›/plugin install requirements-toolkit@ai-requirements-toolkit

Regulatory Reporting Toolkit

What it does →
Claude Code
›/plugin marketplace add clarityisrare/ai-requirements-toolkit
›/plugin install reg-reporting-toolkit@ai-requirements-toolkit

When something goes wrong

In Codex: “marketplace not found”, or the marketplace command errors

Codex needs its own GitHub plugin before it can read a catalogue from GitHub. Type /plugins in the Codex terminal window, find the GitHub icon, double-click it to install, start a new session, then run the two commands again. See Route C. Claude Code does not need this — it reads GitHub by itself.

Do I need a GitHub account?

No. The repositories are public — you can read every file without signing in, and the install commands do not ask you to log in. An account only matters if you want to star the repo or open an issue.

Do I need to know how to code?

No. You type two commands once, and everything after that is a normal conversation in plain English. The toolkits contain Markdown text files — instructions for the assistant — not software that runs on your computer.

Is it free?

The toolkits are free and MIT-licensed, forever. The assistant is not: Claude Code needs a Claude Pro, Max, Team or Enterprise plan — the free Claude plan does not include it. Codex needs a paid ChatGPT plan.

“/plugin” is not recognised

Your Claude Code is too old. Run claude update, or reinstall using the command for your system above, then restart it and try again. Check what you have with claude --version.

It installed, but nothing seems different

Check the message the install printed. If it says Run /reload-plugins to activate, run that command. Otherwise close the assistant and start it again — some installs only take effect in a new session.

The skills still do not show up

Clear the plugin cache and reinstall: close the assistant, run rm -rf ~/.claude/plugins/cache in your terminal, start it again, and repeat the two install commands.

How do I know a skill actually ran?

Claude names the skill it is using as it starts working. You can also force one by typing its full name, for example /requirements-toolkit:requirements-writer, which removes any doubt.

Can I install both toolkits?

Yes. They are separate marketplaces and separate plugins, and they do not interfere with each other. Run each toolkit’s two commands in turn.

Still stuck? Open an issue on the repo, or write to me — the questions I get are what built this page.