update

Refresh kit-owned templates, standards, and tooling in an installed Tandem project without touching user artefacts.

Updated May 25, 2026
One-click install
npx skills add https://github.com/DATA-AI-XYZ/Tandem --skill update-data-ai-xyz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update
Source: https://github.com/DATA-AI-XYZ/Tandem/tree/main/skills/update
Command: npx skills add https://github.com/DATA-AI-XYZ/Tandem --skill update-data-ai-xyz

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update the Tandem PM kit in an existing project?

Run npm run pm:update, or invoke the /tandem:update skill which previews the change diff first with update.js --dry-run and applies only after you confirm. It refreshes kit-owned templates, standards, and tooling while bumping the kitVersion.

Will updating Tandem overwrite my project plans and stories?

No. The update only writes ownership:kit files such as templates, standards, and the 93-Scripts tooling. User-owned paths like PROJECT-CONTEXT.md, MONITOR.md, settings.json, and all epic/story work folders remain byte-identical.

How do I check if my Tandem kit is out of date?

Run npm run pm:doctor, which compares your installed kitVersion against the shipped version and prints update available when you are behind. It is read-only and writes nothing, per ADR-0073.

Can I preview Tandem kit changes before applying them?

Yes. Run node _00-Project-Management/93-Scripts/update.js --dry-run to see exactly which kit files would refresh and the resulting kitVersion bump. The skill presents this diff and waits for confirmation before applying.

Why do I see hook errors after updating the Tandem plugin?

Transient hook errors referencing the old version's cache path are expected when the plugin itself was updated, until you restart your Claude Code session. The skill's final report reminds you to restart in that case.