cxavireh/hotz-skills/update-project-skill

Update Project Knowledge

Keep the existing project skill as a compact map of stable facts and evidence. Age alone does not mean it is stale. Resolve the project knowledge entrypoint from existing project instructions; do not create a new global skill.

Collect bounded facts with <plugin-root>/scripts/project_snapshot.py --root <project> and read the source files relevant to the actual change. Apply a focused update within the authorized task, preserving accurate lessons and linking to source code, results, and experiment IDs. When no existing entrypoint exists, identify a suitable documentation destination; create a project skill only if requested.

Update a local changelog or pipeline timestamp only when the project already uses it. Do not copy directory trees, transient tasks, or full logs into the skill. Do not synchronize another application's skills. For PRISM, follow ../../references/execution-boundaries.md when validating remote evidence.