Decommission Validated System

Decommission a validated computerized system at end-of-life. Covers data retention assessment by regulation, data migration validation (mapping, transformation, reconciliation), archival strategy, access revocation, documentation archival, and stakeholder notification. Use when a validated system is being replaced, reaching end-of-life without replacement, vendor support is discontinued, multiple systems are consolidating, or regulatory changes render a system obsolete.

45 stars 4 forksWriting & Content

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add pjt222/agent-almanac --skill decommission-validated-system
Manual install
git clone --depth 1 https://github.com/pjt222/agent-almanac.git /tmp/agent-almanac
mkdir -p ~/.claude/skills
cp -r /tmp/agent-almanac/i18n/caveman-lite/skills/decommission-validated-system ~/.claude/skills/decommission-validated-system

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Decommission Validated System

Plan and execute the controlled retirement of a validated computerized system while preserving data integrity and meeting regulatory retention requirements.

## When to Use

- A validated system is being replaced by a new system
- A system is reaching end-of-life with no replacement (business process eliminated)
- Vendor discontinues support for a validated product
- Consolidation of multiple systems into a single platform
- Regulatory or business changes render a system obsolete

## Inputs

- **Required**: System to be decommissioned (name, version, validation status)
- **Required**: Data retention requirements by regulation (21 CFR Part 11, GLP, GCP)
- **Required**: Replacement system (if applicable) and migration scope
- **Optional**: Current validation documentation package
- **Optional**: Data volume and format inventory
- **Optional**: Business owner and stakeholder list

## Procedure

### Step 1: Assess Data Retention Requirements

Determine how long data must be retained and in what form:
Read the full skill on GitHub

Details

Skill name
decommission-validated-system
Path
i18n/caveman-lite/skills/decommission-validated-system/SKILL.md
License
MIT
Repo updated
18 November 2026

FAQ

What does the Decommission Validated System skill do?

Decommission a validated computerized system at end-of-life. Covers data retention assessment by regulation, data migration validation (mapping, transformation, reconciliation), archival strategy, access revocation, documentation archival, and stakeholder notification. Use when a validated system is being replaced, reaching end-of-life without replacement, vendor support is discontinued, multiple systems are consolidating, or regulatory changes render a system obsolete.

How do I install the Decommission Validated System skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add pjt222/agent-almanac --skill decommission-validated-system. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Decommission Validated System popular?

It lives in pjt222/agent-almanac, which has 45 GitHub stars and 4 forks, and is included in 1 curated skill list.

Related skills

Adapt Architecture

45

pjt222/agent-almanac

Execute structural metamorphosis using strangler fig migration, chrysalis phases, and interface preservation. Covers transformation planning, parallel running, progressive cutover, rollback design, and post-metamorphosis stabilization for system architecture evolution. Use when assess-form has classified the system as READY for transformation, when migrating from monolith to microservices, when replacing a core subsystem while dependents continue operating, or when any architectural change must be gradual rather than big-bang.

Software DevelopmentIn 1 list

Adaptic

45

pjt222/agent-almanac

Master skill composing the 5-step synoptic cycle for panoramic synthesis across multiple domains. Orchestrates meditate, expand-awareness, observe, awareness, integrate-gestalt, and express-insight into a coherent process that produces unified understanding rather than sequential compromise. Use when a problem genuinely spans 3+ domains and the interactions between domains matter more than depth in any one, when sequential analysis feels like compromise rather than integration, or before major architectural decisions affecting multiple stakeholders.

OtherIn 1 list

Add Puzzle Type

45

pjt222/agent-almanac

Scaffold a new puzzle type across all 10+ pipeline integration points in jigsawR. Creates the core puzzle module, wires it into the unified pipeline (generation, positioning, rendering, adjacency), adds ggpuzzle geom/stat layers, updates DESCRIPTION and config.yml, extends the Shiny app, and creates a comprehensive test suite. Use when adding a completely new puzzle type to the package or following the 10-point integration checklist to ensure nothing is missed end-to-end.

Testing & QAIn 1 list

Design Logic Circuit

45

pjt222/agent-almanac

Design combinational logic circuits from a functional specification through gate-level implementation. Covers AND, OR, NOT, XOR, NAND, NOR gates; NAND/NOR universality conversions; and standard building blocks including multiplexers, decoders, half/full adders, and ripple-carry adders. Use when translating a Boolean function or truth table into a hardware-realizable gate network and verifying it by exhaustive simulation.

Writing & ContentIn 1 list

Construct Geometric Figure

45

pjt222/agent-almanac

Perform a ruler-and-compass construction with step-by-step justification for each operation, producing a constructible geometric figure from given elements. Covers classical Euclidean constructions including perpendicular bisectors, angle bisectors, parallel lines, regular polygons, and tangent lines. Use when given geometric elements (points, segments, angles) and asked to produce a Euclidean construction, verify constructibility, or generate ordered construction steps for educational or documentation purposes.

Writing & ContentIn 1 list

Evolve Skill

45

pjt222/agent-almanac

Evolve an existing skill by refining its content in-place or creating an advanced variant. Covers assessing the current skill, gathering evolution requirements, choosing scope (refinement vs. variant), applying changes, updating version metadata, and synchronizing the registry and cross-references. Use when a skill's procedure steps are outdated, user feedback reveals gaps, a skill needs a complexity upgrade, an advanced variant is needed alongside the original, or related skills are added and cross-references are stale.

Writing & ContentIn 1 list

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.