agentleFS
V-SongbirdV-Songbird/foreman/skills/init/SKILL.md

init

Skill35 starsChanged 52 days agoMITView on GitHub

Bootstraps a project's ROADMAP.jsonl and .foreman/config.json from the user's goals and the repository, or appends to an existing roadmap. Asks only what the request leaves open — what the project is, its near-term goals, and whether an inferred draft looks right — then writes and commits only the files it changes, leaving every optional behavior at its built-in default. Checkpoint policy is never asked here; it is asked the first time it could actually matter. Use for Foreman setup or an explicitly requested reinitialization; existing history and settings are preserved unless replacement was authorized.

147 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use daily-arxiv, exp-eval and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • LambenthanSkill

    daily-arxiv

    每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新

    Also in 5 projects that use this

  • LambenthanSkill

    exp-eval

    实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges

    Also in 5 projects that use this

  • skyllwtSkill

    exp-pilot-eval

    Pilot result evaluation — read pilot results, apply success criteria, update idea page (pilot_result, failure_reason if failed), generate PILOT_VERDICT_REPORT. Called by /ideate Phase 5 after /exp-pilot-run.

    Also in 4 projects that use this

  • skyllwtSkill

    exp-pilot-run

    Pilot experiment execution — read Pilot Spec YAML, write pilot code, run experiment(Confirm with the user before operation and require the applicant to conduct manual inspection), return results. Called by /ideate Phase 5. Does NOT modify wiki pages or judge pass/fail.

    Also in 4 projects that use this

  • gaebalaiSkill

    codex-system

    PROACTIVELY consult Codex CLI, your highly capable supporter with exceptional reasoning and task completion abilities. Codex is a trusted expert you should ALWAYS consult BEFORE making decisions on: design choices, implementation approaches, debugging strategies, refactoring plans, or any non-trivial problem. When uncertain, consult Codex. Don't hesitate - Codex provides better analysis. Explicit triggers: "think deeper", "analyze", "second opinion", "consult codex".

    Also in 3 projects that use this

  • +6 more from Lambenthan
  • +1 more from skyllwt

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 0 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 134 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If ROADMAP.jsonl already exists at the project root, an explicit user instruction to append or to replace selects that branch.

    line 58
  2. Very specific:

    Keep, add to it → continue to Call 1 and append new entries instead of replacing.

    line 71
  3. Very specific:

    Read call-1.md (${CLAUDE_PLUGIN_ROOT}/skills/init/call-1.md) and follow it.

    line 79
  4. Very specific:

    Every optional behavior already has a safe default in the code that reads it, so init writes .foreman/config.json as an empty object {} and …

    line 86
  5. Very specific:

    Read draft.md (${CLAUDE_PLUGIN_ROOT}/skills/init/draft.md) and follow it.

    line 104
  6. Very specific:

    Read write.md (${CLAUDE_PLUGIN_ROOT}/skills/init/write.md) and follow it.

    line 116

“Common” is measured: kept by at least 6 in 10 of the 134 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

foreman:init — bootstrap a project roadmap

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.

Creates ROADMAP.jsonl and .foreman/config.json at the project root. Both are committed to git — they're a shared project artifact, not personal state — unless the project git-ignores them to keep a private roadmap; then init writes both and commits neither (step 4 of the write phase). All reads/writes go through ${CLAUDE_PLUGIN_ROOT}/scripts/roadmap.js (see "Write phase" below) — it enforces the write invariants (id computation, parse-before/after-write) mechanically, so you don't have to. Run it as roadmap.js <subcommand> --help (for example roadmap.js add --help) for that subcommand's shape; read the Fields section of the schema (${CLAUDE_PLUGIN_ROOT}/roadmap-schema.md) if you need field semantics beyond what's obvious from the names (why/what/depends_on/planned_touches).


<!-- [Foreman: 209] -->

Trial log. Setup is one of the flows no script can see from outside, so these lines are the only record it left. A valid call records nothing unless the project set trialLog, so it needs no check first; a malformed one fails in every project. Either way it never blocks the flow.

At the first question actually put to the user — or as the write phase starts, when no question is asked — one line:

node ${CLAUDE_PLUGIN_ROOT}/scripts/trial-log.js init_started '{}'

and, after each question interaction the user actually sees — one AskUserQuestion call in Claude Code, however many questions it batches; one picker call or one plain-text question in Codex; one ask_question call in Antigravity — one event:

node ${CLAUDE_PLUGIN_ROOT}/scripts/trial-log.js question_asked '{"flow":"init"}'

A skipped question is never logged. A cancelled or blocked setup leaves an init_started with no init_completed. That is the correct record of an unfinished setup, not a gap to paper over.


Pre-check

If ROADMAP.jsonl already exists at the project root, an explicit user instruction to append or to replace selects that branch. Otherwise ask before doing anything else — AskUserQuestion in Claude Code; in Codex, the picker in questions.md. With no usable question tool, ask each question in this skill as one self-contained plain-text question.

Q1 — "ROADMAP.jsonl already exists. What do you want to do?" Options: Overwrite it (start fresh — discards done entries and their accumulated notes), Keep it, just add to it, Cancel

  • Overwrite → continue to Call 1; the write phase snapshots the old file before replacing it.
  • Keep, add to it → continue to Call 1 and append new entries instead of replacing; don't touch .foreman/config.json if it already exists.
  • Cancel → stop here and change nothing.

Call 1 — project and goals

Read call-1.md (${CLAUDE_PLUGIN_ROOT}/skills/init/call-1.md) and follow it.


Defaults — never asked, never written

There is no policy interview, and there is no settings file to compose. Every optional behavior already has a safe default in the code that reads it, so init writes .foreman/config.json as an empty object {} and lets those defaults stand: finished work waits for the user's confirmation, nothing blocks a task's completion, handoffs open with a persona sentence, and no prompt section is omitted.

Writing those values out would only create a second copy that can drift from the readers. Checkpoint policy stays absent for a second reason too: an absent key is the record that the user was never asked, so it gets asked once, the first time it could matter, at the first split run.

Any of it can be set by hand later — see the README's settings table.


Draft phase (no question)

Read draft.md (${CLAUDE_PLUGIN_ROOT}/skills/init/draft.md) and follow it.


Call 2 — approval

Read call-2.md (${CLAUDE_PLUGIN_ROOT}/skills/init/call-2.md) and follow it.


Write phase

Read write.md (${CLAUDE_PLUGIN_ROOT}/skills/init/write.md) and follow it.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.