update

Update Skill — Evolve Tooling to Latest Best Practices

You are running the onboard update skill. This checks whether the project's Claude tooling is aligned with the latest best practices and offers targeted upgrades.

This is NOT a snapshot diff. It's a forward-looking check against current best practices.

---

Step 0: Initialize Phase Tracking

Runs first, before the Prerequisites Check. This wires the durable phase-task list that the rest of the flow transitions for in-session visibility.

First, read the contract: ../start/references/phase-tracking.md (the cross-skill source of truth — start is its worked example). It defines the task subjects, the pending → in_progress → completed (plus deleted) state machine, and the HARD GATE mapping. Follow it verbatim — do not re-derive its rules here. update runs on an already-onboarded project (an onboard-meta.json exists by the time the baseline check in Phase 0 passes), so it has no cross-session resume probe of its own; the task list here is in-session progress visibility, and the durable record lives in the on-disk artifacts the contract describes.

Create the 8 update phase tasks via TaskCreate, all status: "pending", one per ladder phase, using the update: subject prefix from the contract's § Other entry points table:

Subject	activeForm
update:verify-baseline	Verifying the onboard baseline
update:read-artifacts	Reading existing artifacts
update:reanalyze	Re-analyzing the codebase
update:best-practices-drift	Checking best practices & detecting drift
update:present-preview	Presenting findings & rendering preview
update:approve-gate	Awaiting approval of upgrades
update:apply	Applying approved updates
update:summary	Summarizing changes

Only this orchestrator touches the list. Every internal skill it later invokes (onboard:generate, onboard:research) is task-blind per the contract's § Ownership — when update invokes generate inside Phase 6, that does not create its own list; it runs inside this Phase-6 task. Routing note (per the contract's § Routing): if Phase 0 routes into adopt (missing-baseline branch), adopt owns its own adopt: list and marks it complete on handoff; the two lists coexist — this update list never touches adopt's tasks and vice versa.