update

Update Skill

Update existing processed document with new info, corrections, or re-verification against updated sources. Every update ends with mandatory CLI-grounding pass on changed content - no silent skip - any content change can introduce ungrounded claim.

Pre-flight install (MANDATORY - run every session, no asking)

python3 -m pip install --user --upgrade stellars-claude-code-plugins 2>&1 | tail -1
LIB=$(python3 -c "import importlib.metadata as m;print(m.version('stellars-claude-code-plugins'))" 2>/dev/null) || { echo "FATAL: toolkit unavailable"; exit 1; }
PLUG=$(grep -m1 '"version"' "${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json" 2>/dev/null | cut -d'"' -f4)
OLDER=$(printf '%s\n%s\n' "$LIB" "$PLUG" | sort -V | head -1)
[ -n "$PLUG" ] && [ "$LIB" != "$PLUG" ] && [ "$OLDER" = "$LIB" ] && { echo "STALE: library $LIB older than plugin $PLUG - refusing to run on an outdated CLI; re-run the upgrade"; exit 1; }
echo "toolkit $LIB"

Run the CLI without touching the caller's project. The gate above puts it on PATH, so the bare command name is the whole invocation. uv run instead resolves whatever project the working directory sits in and writes uv.lock and .venv into it, so if you reach for uv pass --no-project (uv run --no-project <cli> ...) - it skips project discovery, leaves the tree untouched and still finds the same PATH binary. --no-sync and --frozen are not substitutes; both still create .venv.

The upgrade always runs; a version mismatch blocks. Never ask - just run the line.

When to use

• New source document added to 1-input/ - re-run affected sections
• User found errors in 3-output/ document - correct and re-verify
• Grounding audit failed - fix unconfirmed claims
• Uniformization rules changed - re-apply to existing output
• Additional context available - enrich existing document

Steps

1. Identify what exists: Read 3-output/ for the current document, 2-wip/ for the processing history, INSTRUCTIONS.md and BENCHMARK.md for the original program.