survey
Skill35 starsChanged 52 days agoMITView on GitHub
Advanced surface, normally reached through the `foreman` entrance's Reconcile and pick mode, which hands it a near-term set of ids to scope the pass to. Ground-truths the roadmap's near-term candidates against the actual codebase — a read-only investigation checks whether each candidate's planned_touches/depends_on still match reality, then proposes a concrete, evidence-backed repair for every finding (hidden dependency, already-done, stale description or planned files), applies only the ones you approve, and persists them back into ROADMAP.jsonl so future sessions pick them up automatically. It costs materially more than a plain pick, which is why it is explicit: a fast pick or old roadmap alone does not trigger it.
23 other projects use a version of this.
Adopted by
Most recently taken up by
- Aquilo-Solution-S/tesla-valvetheir own version, first seen Nov 16, 2026
- quickchatai/quickreviewtheir own version, first seen Nov 15, 2026
- genkovich/sddtheir own version, first seen Oct 25, 2026
- PKU-DAIR/AutoScitheir own version, first seen Oct 25, 2026
- wheslleyrimar/BuildCLI-Agentstheir own version, first seen Oct 22, 2026
- LazyerIJ/self-clonetheir own version, first seen Oct 17, 2026
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.
LambenthanSkilldaily-arxiv
每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新
Also in 5 projects that use this
LambenthanSkillexp-eval
实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges
Also in 5 projects that use this
skyllwtSkillexp-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
skyllwtSkillexp-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
phanghonghaoSkillposter
HTML/CSS A4 海报生成。从沙龙/活动 Markdown 文件生成科技风 A4 海报 PDF/PNG。Use when user mentions: poster, 海报, 海报生成, make poster, generate poster, 活动海报, 沙龙海报.
Also in 4 projects that use this
- +6 more from Lambenthan
- +1 more from skyllwt
Other versions23 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 23
- skyllwt/OmegaWiki★ 1.7ksame name
- DAIR-AutoResearch/AutoSci★ 1.7ksame name
- PKU-DAIR/AutoSci★ 1.7ksame name
- skyllwt/AutoSci★ 1.7ksame name
- genkovich/sdd★ 187same name
- SNL-UCSB/literature-survey-skill★ 93same name
- Lambenthan/empiricalwiki★ 85same name
- spacedock-dev/spacedock★ 85same name
- jmylchreest/aide★ 19same name
- quickchatai/quickreview★ 9same name
13 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
- foremanSkill
- initSkill
- roadmapSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 1 is distinctive, and 5 are very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Use ${CLAUDE_PLUGIN_ROOT}/scripts/roadmap.js for all roadmap reads and mutations — never read or edit ROADMAP.jsonl directly — and run it …
- Very specific: line 25
Pre-check: if ROADMAP.jsonl doesn't exist at the project root, offer to set up the roadmap first (/foreman:init in Claude Code.
- Very specific: line 34
Read scope.md (${CLAUDE_PLUGIN_ROOT}/skills/survey/scope.md) and follow it.
- Very specific: line 40
Read investigate.md (${CLAUDE_PLUGIN_ROOT}/skills/survey/investigate.md) and follow it.
- Very specific: line 46
Read confirm.md (${CLAUDE_PLUGIN_ROOT}/skills/survey/confirm.md) and follow it.
- Distinctive: line 66
After each question interaction the user actually sees in this flow, one silent line:
“Common” is measured: kept by at least 6 in 10 of the 18 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:survey — ground-truth the roadmap's near-term candidates
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 is the advanced code investigation flow, the one Foreman flow that investigates the codebase against the roadmap. Fast pick does not run it: it reads more code and costs more than ranking stored tasks, so it runs only when someone asks for it.
Use ${CLAUDE_PLUGIN_ROOT}/scripts/roadmap.js for all roadmap reads and
mutations — never read or edit ROADMAP.jsonl directly — and run it as
roadmap.js <subcommand> --help (for example roadmap.js list --help) for
that subcommand's shape. Read the Fields section of
roadmap-schema.md
(${CLAUDE_PLUGIN_ROOT}/roadmap-schema.md) for field semantics.
Pre-check: if ROADMAP.jsonl doesn't exist at the project root, offer
to set up the roadmap first (/foreman:init in Claude Code; in
Codex, the init skill; /init in Antigravity) and stop
here.
1. Pick the scope
Read scope.md (${CLAUDE_PLUGIN_ROOT}/skills/survey/scope.md) and follow it.
2. Investigate each candidate in parallel
Read investigate.md (${CLAUDE_PLUGIN_ROOT}/skills/survey/investigate.md) and follow it.
3. Confirm before writing anything
Read confirm.md (${CLAUDE_PLUGIN_ROOT}/skills/survey/confirm.md) and follow it.
4. Report
Short summary: candidates surveyed (and how many were left unsurveyed, if any), verdicts, what got written. Separate the three outcomes in one line each: corrections applied, findings left unconfirmed as breadcrumbs, and proposals declined (declined ones exist only here — nothing about them was written). If no writes happened, say the roadmap is unchanged — this skill running is not itself news. For Reconcile and pick, return these results to the pick flow before it refreshes its menu; do not quietly continue on the old ranking.
<!-- [Foreman: 209] -->Trial log
After each question interaction the user actually sees in this flow, one silent line:
node ${CLAUDE_PLUGIN_ROOT}/scripts/trial-log.js question_asked '{"flow":"survey"}'One event per interaction, never one per question: 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.
A skipped question is never logged. 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.
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.

