gather-context
Skill1 starsChanged 5 months agoMITView on GitHub
Before working on a task, pull the relevant slices of the project's ground truth from the manifest, write a short context brief, and confirm it with the human in one batch. Re-run at each phase boundary, not just at the start.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- dmzoneill/skillstheir own version, first seen Oct 24, 2026
- lucastosetto/dev-skillstheir own version, first seen Oct 15, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- dmzoneill/skills★ 2same name
- lucastosetto/dev-skills★ 0same name
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 repository8 other files it gives its agents.
- close-the-booksSkill
- expert-panelSkill
- scan-projectSkill
- scope-watchSkill
- seal-planSkill
- servo-flowSkill
- servo-gateSkill
- shape-specSkill
The file
Files
gather-context
Load the ground truth a task needs before touching it — and again whenever the work has moved the ground. Context decays over a long session and drifts as the work changes state; the slice of truth that matters before writing a plan is not the same one that mattered before the brainstorm. So this is a recurring ritual, not a one-time setup.
The failure this prevents: an agent re-deriving facts that already exist (in the manifest's oracles), or asking the human to re-feed context the project already records.
Procedure
- Read the manifest.
.servo/manifest.yamllists the project'soracles(where ground truth lives) andexperts(the domains). If there is no manifest, runscan-projectfirst. - Pull only the relevant slices. For the task at hand, decide which oracles matter (scope of the work, invariants it could break, prior art that already exists, known footguns) and read those sources — and only those. Do not ingest everything; pull the slice the task needs.
- Write a short context brief. A few lines: what the task is, what it must not break (invariants), what already exists (prior art), which footguns apply, which experts are relevant. Cite the oracle each fact came from.
- Confirm in one batch — not one question at a time. Where the brief has gaps or assumptions, ask the human all the open questions at once, with proposed answers pre-filled from the context. The human is the CEO/client seat here: they own the intent. Their answers are input to pressure-test, not orders to execute blindly.
- Carry the brief forward — it is the cache. The brief is read ONCE here and then consumed by the downstream phases (the expert panel, the gates). Hand subagents the brief instead of having each one re-read the raw oracles; a subagent only goes back to a raw source when it genuinely needs to go deeper than the brief. Reading the same vault notes and specs eleven times, once per subagent, is the main avoidable cost in the flow. At the next phase boundary, re-run this skill on the slice that now matters.
Rule
Ground in what the project already records before asking the human or re-deriving. The manifest exists so you know where to look.
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.