foreman
Skill35 starsChanged 52 days agoMITView on GitHub
The one entrance to Foreman, which keeps a project's plan and task history. Say what you want in plain language and this routes it to one of the six things Foreman does to a project: add work, show status, correct work, check the roadmap, pick work, or reconcile and pick. It owns no flow of its own. Use for Foreman or roadmap requests, not ordinary implementation work.
12 other projects use a version of this.
Adopted by
Most recently taken up by
- denysm/wiki-kittheir own version, first seen Nov 16, 2026
- mattvideoproductions/MVP-Promptstheir own version, first seen Nov 15, 2026
- lohi-ai/babysittheir own version, first seen Nov 14, 2026
- ilkemerol/foremantheir own version, first seen Nov 8, 2026
- MarioMagdy/foremantheir own version, first seen Nov 8, 2026
- sunjay-dev/skillstheir own version, first seen Nov 1, 2026
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- ilkemerol/foreman★ 38same name
- MarioMagdy/foreman★ 30same name
- mattvideoproductions/MVP-Prompts★ 5same name
- AIisNothing/foreman★ 3same name
- KodingDev/skills★ 2same name
- denysm/wiki-kit★ 1same name
- Pitcocy/skills★ 1same name
- rwshiraishi/foreman★ 1same name
- sifXt/claude-foreman★ 1same name
- lohi-ai/babysit★ 0same name
2 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- craft-promptSkill
- initSkill
- roadmapSkill
- surveySkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 59
When two intents fit and the distinction changes the work, ask one concise question naming the closest two intents in the user's own terms …
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
foreman — the one entrance
Foreman runs in Claude Code, Codex and Antigravity. Every step applies to every host unless it names one. Read the shared runtime first: it covers plugin paths, JSON payloads, questions and authorization for every host.
This skill routes. It does not add, pick, correct, or survey anything
itself, and it never reads or writes ROADMAP.jsonl. Every step
of every flow lives in the skill that owns it; duplicating any of it here
would give Foreman two versions of the same truth. Classify the request,
say in one short line which flow is taking it, then hand off and let that
skill run from its own first step.
The six intents
| The user says something like… | Intent | Route to |
| "add this", "put X on the roadmap", "we also need to…", "track this for later" | add work | foreman:roadmap → "Branch: Add a task" (add.md) |
| "where are we", "roadmap status", "what's left", "what's waiting on me" | show status | foreman:roadmap → "Branch: Review status" (status.md) |
| "that entry is wrong", "reword 003", "retarget 007 at the proxy", "its description is stale" | correct work | foreman:roadmap → "Branch: Correct a task" (correct.md) |
| "my roadmap is broken", "check the roadmap", "is the roadmap file healthy" | check the roadmap | foreman:roadmap → "Branch: Check the roadmap" (doctor.md) |
| "what's next", "pick a task", "something quick on auth", "give me work" | pick work | foreman:roadmap → "Branch: Pick the next task" (pick.md) |
| "is the roadmap still accurate — then give me something", "double-check the top tasks before I start", "audit it and pick" | reconcile and pick | foreman:roadmap → "Branch: Pick the next task", its reconcile path (pick.md, which runs survey first) |
Each route reads the roadmap skill and then the linked branch file.
Notes that change how a route is handed over:
- pick work is Fast pick, the default confidence mode and the sense of a bare "what's next": that branch deliberately does not investigate the codebase. Don't promote it to reconcile and pick because the roadmap looks old — the user asks for that or it doesn't happen.
- reconcile and pick is the other confidence mode, Reconcile and pick
— survey and pick in sequence, nothing new. The pick branch owns that
sequence: it takes the near-term set from its own menu, hands it to
foreman:survey, which ground-truths those entries and applies only the repairs the user authorizes, then picks from the repaired roadmap. Say up front that the reconcile half costs real tokens, since that is the whole difference from a plain pick. - check the roadmap is a structural check — is the file itself well
formed (duplicate ids, broken dependency edges, a stale schema version)
— not a check against the codebase. That's the difference from
reconcile and pick: this one never touches
foreman:surveyand never leads into a pick unless the user separately asks for one. - Four of the five roadmap intents can also be reached by the user picking
from
foreman:roadmap's own menu; check the roadmap is phrase-reached only. Route to the branch when the request already names one; hand over without a branch when it genuinely doesn't.
When the request fits two intents
When two intents fit and the distinction changes the work, ask one concise
question naming the closest two intents in the user's own terms —
AskUserQuestion in Claude Code, the picker in questions.md in
Codex. Never a menu of all six, and never a guess dressed up as a route. Then
hand off to the one they pick. Skip the question when the intent is clear.
The pairs worth expecting: "what's next" after describing new work (add work vs. pick work), "the plan looks off" (correct work vs. reconcile and pick), and "sort out what's next" (pick work vs. reconcile and pick).
Anything else is out of scope here
This entrance covers those six intents and nothing else. When a request falls outside them, name the skill that owns it in one line and stop — don't stretch a route to fit. If the user names a specialized skill, go straight to it.
- setting a project up for the first time, or re-initializing it —
foreman:init(init). - explicitly building or refining a handoff prompt for something that isn't a
roadmap entry —
foreman:craft-prompt(craft-prompt). - accepting, resuming, deferring, archiving, or restoring entries — those live
inside
foreman:roadmap's branches above; route to the intent that carries them rather than describing the mechanics here. - anything that isn't a Foreman request at all — this skill has no opinion on it and shouldn't have taken the turn.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

