What problem does it solve? When the Tandem PM kit ships improvements, installed projects fall behind, but upgrading risks overwriting the operator's own plans, decisions, and work folders. This Skill applies kit updates non-destructively, refreshing only kit-owned files while leaving user artefacts byte-identical. ## Core Features & Use Cases - Non-destructive refresh: Updates only ownership:kit content (templates, standards, PM-folder CLAUDE.md, and the 93-Scripts/ tooling) and never writes user-owned paths like PROJECT-CONTEXT.md, MONITOR.md, or epic/story folders. - Preview-before-apply workflow: Runs update.js --dry-run to show the exact diff of files that would change plus the kitVersion bump, then applies only after operator confirmation. - Drift detection: Works with npm run pm:doctor, which reports update available when the installed kit version is behind the shipped one. - Use Case: After pulling a new Tandem plugin release, ask to update the kit; the Skill shows which templates and scripts would refresh, waits for your confirmation, applies the update, and reports the new kitVersion and regenerated dashboard path. ## Quick Start Ask the assistant to update the Tandem kit in this project, review the dry-run diff it shows, and confirm to apply the refresh.