메뉴
Use after ingesting or editing field-guide pages to attach living code/test anchors. Adds or refreshes fg-evidence metadata without trying to prove prose accuracy. Triggers include "update evidence", "wire evidence", "add evidence anchors", and "connect the wiki to code".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
| name | update-evidence |
| description | Use after ingesting or editing field-guide pages to attach living code/test anchors. Adds or refreshes fg-evidence metadata without trying to prove prose accuracy. Triggers include "update evidence", "wire evidence", "add evidence anchors", and "connect the wiki to code". |
Attach living implementation anchors to field-guide reference pages.
This is the mechanical pass between ingestion and semantic drift review:
ingest extracts durable knowledge from .lore/work/.update-evidence connects that knowledge to current code and tests.resolve-drift compares the prose against those anchors.Update indexed pages in .lore/reference/. Prefer .lore/reference/index.md; if it does not exist, read .lore/reference/index.html. Links may point to .md or .html pages.
Do not require fg-sources files to exist. Source artifacts are ingestion provenance and may be intentionally deleted after knowledge is extracted.
For Markdown pages, add or refresh YAML frontmatter:
fg-evidence:
code:
- src/core/model/types.ts
tests:
- src/core/tests/model.test.ts
symbols:
- CardEffect
For HTML pages, add or refresh meta tags in <head>:
<meta name="fg-evidence-code" content="src/core/model/types.ts">
<meta name="fg-evidence-tests" content="src/core/tests/model.test.ts">
<meta name="fg-evidence-symbols" content="CardEffect">
Read the page body and identify concrete implementation claims:
Search the repository for those anchors with rg. Evidence should point to files that would naturally change if the page became stale.
Good evidence:
Weak evidence:
.lore/work/package.json unless the page is specifically about tooling or stack choiceIf a page is mostly policy or product philosophy and has no honest living implementation anchor, leave it without evidence and report it as intentionally unanchored.
Report:
Do not rewrite page prose during this skill unless necessary to keep metadata valid. Semantic corrections belong in resolve-drift.
Use when checking whether field-guide reference pages still match current code and tests. Reads pages plus fg-evidence anchors, reports or fixes semantic drift, and can use sub-agents for parallel audit batches. Triggers include "resolve drift", "semantic drift", "check accuracy", "verify the reference against code", and "audit the wiki".
Use when extracting knowledge from .lore/ artifacts into the reference wiki. Converts work artifacts (retros, specs, plans, research, notes) into structured wiki pages grouped by knowledge type. Reads Markdown or HTML sources and writes Markdown by default. Triggers include "ingest this", "extract knowledge from", "add this to the wiki", "update the reference from", and "populate the field guide".
Use when setting up field-guide on a project for the first time, or to refresh the scheduled lint job after it expires. Triggers include "init field-guide", "set up field-guide", "refresh field-guide lint schedule", and "bootstrap the wiki".
This skill is used when the project wiki needs a health check. Triggers include 'lint the wiki', 'check wiki health', 'run field-guide lint', 'are there stale wiki pages', 'find orphaned pages', 'check for contradictions in the wiki'.
Use when asking questions about the project wiki, querying accumulated knowledge, searching project decisions or lessons. Triggers include "query the wiki", "what does the wiki say about", "search project knowledge", and natural language questions directed at the field-guide wiki.
Use when exploring before committing, thinking through trade-offs, or digesting sketches and diagrams. Triggers include "let's brainstorm", "what if we...", and "explore options". Bad ideas welcome, questions over answers, mistakes on purpose.