upgrade-bundle

Migrates D2R prerequisite document bundles between methodology versions with per-doc deltas.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/gozonerd/shadow-ai-assessment --skill upgrade-bundle-gozonerd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: upgrade-bundle
Source: https://github.com/gozonerd/shadow-ai-assessment/tree/main/.claude/skills/upgrade-bundle
Command: npx skills add https://github.com/gozonerd/shadow-ai-assessment --skill upgrade-bundle-gozonerd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? D2R methodology versions evolve while real projects accumulate authored PRD/TRD/AVD/TQVCD/UXD/PSCAD bundles pinned to older versions, causing compatibility errors when downstream tools expect the current schema. This Skill walks an existing bundle through the required migration path without discarding authored content. ## Core Features & Use Cases - Version Detection and Path Planning: Reads each doc's methodology_version frontmatter, infers version from structure when absent, and generates a per-doc migration plan for user approval before any changes. - Version-Specific Section Migration: Applies additions such as UXD authoring for v0.1→v0.2, heading-prefix IDs and Amendment Protocol for v0.2→v0.3, TQCD→TQVCD rename cascade, and PSCAD addition for v0.3→v0.4, preserving authored content verbatim. - Cross-Doc Audit and Reporting: Runs the ASAE alignment audit after migration and produces an upgrade report with per-doc deltas, assigned IDs, and open questions. - Use Case: A project authored against methodology v0.2.x fails a CDCC compatibility check; run this Skill on the planning directory to migrate all five docs to v0.3.0 with a reviewable plan and final report. ## Quick Start Upgrade the D2R bundle in my planning directory from methodology v0.2.x to the current version and show me the migration plan first.

Frequently Asked Questions about upgrade-bundle

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

FAQPage Schema
How do I upgrade a D2R bundle to a newer methodology version?

Invoke the upgrade-bundle skill with the planning directory path containing your PRD/TRD/AVD/TQVCD/UXD docs. It detects each doc's methodology_version, generates a per-doc migration plan for your approval, then applies version-specific section additions while preserving authored content.

What migration paths does the D2R bundle upgrade support?

Supported paths include v0.1.x to v0.2.x (adds UXD), v0.2.x to v0.3.0 (IDs, Amendment Protocol, new sections), the TQCD to TQVCD rename cascade, v0.3.0 to v0.4.0 (adds PSCAD), and chained multi-step migrations across versions.

Does the migration overwrite my existing authored content?

No. The migration preserves authored content verbatim where compatible, moves old versions to a deprecated directory, and flags anything it cannot auto-translate as open questions for user review rather than resolving them silently.

When should I not use the bundle upgrade skill?

Do not use it for new projects with no existing bundle, bundles already at the current methodology version, or docs authored against retired methodology branches. It also refuses to bypass version compatibility checks.

What happens if a doc's methodology_version frontmatter is missing?

The skill infers the version from document structure, such as doc count, presence of PRD section 1.4, AVD Reversal Cost, or TQVCD naming. Docs that fail detection are escalated to the user instead of being auto-migrated.