upgrade

Diff last locked tseng review against architecture docs and generate a new open review.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/kagenti/humr --skill upgrade-kagenti
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: upgrade
Source: https://github.com/kagenti/humr/tree/main/.agents/skills/upgrade
Command: npx skills add https://github.com/kagenti/humr --skill upgrade-kagenti

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrade a previously bootstrapped or adopted project when the architecture evolves. Diffs the current architecture rules against the project's last locked review, identifies new or changed rules, and proposes incremental changes. Triggers on phrases like "upgrade my project", "sync with latest architecture", "update to new rules", "upgrade tseng", or "architecture changed, update my project". Also invocable via the /tseng:upgrade slash command.

Core Features & Use Cases

Upgrades architecture by diffing last locked reviews against architecture docs, generates a fresh checklist, and creates a new open review to guide incremental adoption across teams. It supports loading adoption state, auditing new/changed rules, and applying changes in a staged, tracked manner.

Quick Start

Invoke the upgrade by running /tseng:upgrade or selecting Upgrade in your UI.

Frequently Asked Questions about upgrade

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

FAQPage Schema
How do I automate architecture upgrades across multiple projects?

Automate architecture upgrades by diffing the last locked tseng review against the latest architecture docs to identify new rules, generate a checklist, and create an open review guiding incremental adoption.

What triggers an architecture upgrade review when project rules change?

Architecture upgrade reviews are triggered by user prompts like upgrade my project, sync with latest architecture, or the /tseng:upgrade slash command to start the version retrieval and diffing process.

How does diffing architecture rules against previous reviews work?

Diffing architecture rules compares the last locked tseng review with current architecture/index.md docs, identifying new or changed rules to propose incremental, staged changes.

Can I audit and apply new architecture rules incrementally across teams?

Yes, you can audit and apply architecture rules incrementally by loading the tseng/adoption.md state, generating a new open review, and tracking staged changes across teams.

Does the architecture upgrade process require a previously bootstrapped project?

Yes, the architecture upgrade process requires a previously bootstrapped or adopted project to load the existing adoption state and diff against the last locked tseng review.

What files are read to create a new architecture review checklist?

Creating a new architecture review checklist reads architecture/index.md, tseng/reviews, and tseng/adoption.md to load adoption state and guide auditing and applying changes.