drift-maintenance

Update file path, PRD section, and commit hash references in existing tickets.

2|1|Updated Apr 7, 2026

Search Tags:#codebase drift #ADLC integration #ticket maintenance #reference refresh #ticket accuracy

Ready to run

npx skills add https://github.com/bigeasyfreeman/adlc --skill drift-maintenance

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: drift-maintenance
Source: https://github.com/bigeasyfreeman/adlc/tree/main/skills/drift-maintenance
Command: npx skills add https://github.com/bigeasyfreeman/adlc --skill drift-maintenance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Ensures that the references to paths, PRD sections, and commits in existing tickets remain accurate and up-to-date as the codebase evolves, preventing the slow drift that makes ticket scope references fictional over time.

Core Features & Use Cases

Prevents Drift: Updates path references, PRD sections, and commit hashes in tickets when the codebase changes.
Ticket Refresh: Triggered during work-item emitter operations on existing tickets.
Error Handling: Skips tickets without adlc:source_context and handles workspace path issues, PRD version determination failures, and Git operations failures.

Quick Start

Use the drift-maintenance skill to refresh the references in the ticket with ID '12345'.

Frequently Asked Questions about drift-maintenance

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

FAQPage Schema

How do I keep ticket references accurate as the codebase evolves?▼

To keep ticket references accurate as the codebase evolves, you need to update file paths, PRD sections, and commit hashes within existing tickets. This prevents slow drift that makes ticket scope references fictional over time.

What is codebase drift in ticket maintenance?▼

Codebase drift in ticket maintenance occurs when references to paths, PRD sections, and commits in existing tickets become outdated and inaccurate as the codebase changes. Regular reference refreshes prevent this drift.

How do I update PRD sections and commit hashes in existing tickets?▼

To update PRD sections and commit hashes in existing tickets, trigger a refresh during work-item emitter operations. The maintenance process operates within the ADLC framework to handle these specific reference updates.

Do I need git and ADLC integration to maintain ticket accuracy?▼

Yes, you need git and ADLC integration to maintain ticket accuracy. The drift-maintenance process requires git for commit hash operations and access to product documentation for PRD version determination.

What happens to tickets without adlc:source_context during reference refresh?▼

Tickets without adlc:source_context are skipped during reference refresh. The error handling also manages workspace path issues, PRD version determination failures, and Git operations failures gracefully.

When should I refresh ticket references to prevent codebase drift?▼

You should refresh ticket references to prevent codebase drift when triggered during work-item emitter operations on existing tickets. This ensures path, PRD, and commit references remain accurate as the codebase evolves.