Foreman

Foreman / Install

Install Foreman.

One folder of markdown. Nothing compiles and nothing runs, so it installs anywhere an agent reads files.

Your agent + Foreman
foreman/
  SKILL.md
  toolbelt/
  templates/

01  Read the playbook
02  Describe your project
03  Review the brief
04  Build with your agent

Claude Code

Both lines, in this order. This adds the playbook and its four tools as slash commands.

/plugin marketplace add Turki-Sh/Foreman
/plugin install foreman@alshuaibi

If your Claude Code surface does not support /plugin, run these commands in your shell, then start a new session.

claude plugin marketplace add Turki-Sh/Foreman
claude plugin install foreman@alshuaibi

Update or remove

Update from your shell:

claude plugin marketplace update alshuaibi
claude plugin update foreman@alshuaibi
/plugin uninstall foreman@alshuaibi

Use it with your team.

Optional, for projects where Foreman is part of the shared workflow.

From the project directory, run:

claude plugin marketplace add Turki-Sh/Foreman
claude plugin install foreman@alshuaibi --scope project

This records Foreman in .claude/settings.json:

{
  "enabledPlugins": {
    "foreman@alshuaibi": true
  }
}

Keep existing settings and other plugin entries. Review the diff, then commit this file so collaborators receive the configuration. Each collaborator still runs the two commands once on their machine. Committing settings does not download the plugin for them.

For personal use, keep the default user-scope installation. Sharing is optional and works in private repositories too. Keep credentials and personal overrides out of the shared file.

Installation scopes · Shared settings

Claude apps

Download foreman.skill and upload it in the skills settings. The modes and the four tools are inside it. Ask for a tool in plain words, such as "run the punch list on my site".

Every other agent

Cursor, Windsurf, Codex, Copilot, Gemini CLI, Cline, or anything that reads skills or rules. Copy one folder.

git clone https://github.com/Turki-Sh/Foreman.git
cp -r Foreman/plugins/foreman/skills/foreman ~/.agents/skills/
ToolWhere the folder goes
Universal skills directory~/.agents/skills/foreman/
Cursor~/.cursor/rules/, or .cursor/rules/ in the project
Codex~/.codex/skills/foreman/, or reference it from AGENTS.md
GitHub Copilot.github/copilot-instructions.md, or point it at SKILL.md
Windsurf.windsurfrules, or the workspace rules directory
Gemini CLIGEMINI.md, or the extensions directory
Cline, Continue, RooThe custom instructions or rules field

Paths move as tools change. The rule that always works: put SKILL.md where your tool reads standing instructions, and keep references/, toolbelt/ and assets/ next to it. AGENTS.md has the latest table.

A chat with no skills support

Paste SKILL.md into the conversation and say "run this on me". The steps, the modes and the gates all work from that one file. The references only deepen them.

Check it loaded

Say help me build my portfolio. The first reply is this card, then nothing. If it starts writing HTML, it did not load.

         _____ ___  ____  _____ __  __    _    _   _
        |  ___/ _ \|  _ \| ____|  \/  |  / \  | \ | |
        | |_ | | | | |_) |  _| | |\/| | / _ \ |  \| |
        |  _|| |_| |  _ <| |___| |  | |/ ___ \| |\  |
        |_|   \___/|_| \_\_____|_|  |_/_/   \_\_| \_|

+--------------------------------------------------------------+
|                                                              |
|                        _______________                       |
|                    ___/               \___                   |
|                   /_________________________\                |
|                   \_________________________/                |
|                      |  .---.     .---.  |                   |
|                      |  | O |-----| O |  |                   |
|                      |  '---'     '---'  |                   |
|                      |         v         |                   |
|                      |     ~~~~~~~~~     |                   |
|                       \_________________/                    |
|                                                              |
|   PLAYBOOK  Foreman 3.0.1 by Turki Alshuaibi                 |
|   STATUS    Step 1 of 8 . Orient                             |
|   METHOD    Decide > Look > Brief > Build > Verify > Ship    |
|   MODE      Blueprint. Say survey or stress test to switch   |
|   RULE      No site code until you sign off the brief        |
|                                                              |
+--------------------------------------------------------------+
|   What are you building, and what do you already have?       |
+--------------------------------------------------------------+

Questions

Does it run anything on my machine? No. Foreman is markdown and fill-in templates. It ships no scripts, no hooks, no MCP servers and no network calls, and its CI fails if any appear. Your agent uses its own tools, with your permission, as it always does.

Does it need the internet? No. Survey mode and the board get better when your agent can browse, and say so in one line when it cannot.

Which models does it work with? Any capable model your agent runs. The recorded runs on this site used Claude Sonnet.

What does it cost? Nothing. MIT licensed.