feat: add technical-change-tracker for structured code change tracking (#459)

* feat: add technical-change-tracker for structured code change tracking

* docs: add README credit for technical change tracker

---------

Co-authored-by: sickn33 <sickn33@users.noreply.github.com>

README.md

@@ -284,6 +284,7 @@ This collection would not be possible without the incredible work of the Claude
 
 ### Community Contributors
 
+- **[Elkidogz/technical-change-skill](https://github.com/Elkidogz/technical-change-skill)**: Source for the Technical Change Tracker skill - structured JSON change records, session handoff, and accessible HTML dashboards for coding continuity.
 - **[rmyndharis/antigravity-skills](https://github.com/rmyndharis/antigravity-skills)**: For the massive contribution of 300+ Enterprise skills and the catalog generation logic.
 - **[amartelr/antigravity-workspace-manager](https://github.com/amartelr/antigravity-workspace-manager)**: Workspace Manager CLI companion to dynamically auto-provision subsets of skills across local development environments.
 - **[obra/superpowers](https://github.com/obra/superpowers)**: The original "Superpowers" by Jesse Vincent.

skills/technical-change-tracker/SKILL.md

@@ -0,0 +1,60 @@
+---
+name: technical-change-tracker
+description: "Track code changes with structured JSON records, state machine enforcement, and AI session handoff for bot continuity"
+category: development
+risk: safe
+source: community
+source_repo: Elkidogz/technical-change-skill
+source_type: community
+date_added: "2026-04-05"
+author: Elkidogz
+tags: [change-tracking, session-handoff, documentation, accessibility, state-machine]
+tools: [claude, cursor, gemini, codex]
+---
+
+# Technical Change Tracker
+
+## Overview
+
+Track every code change with structured JSON records and accessible HTML output. Ensures AI bot sessions can resume seamlessly when previous sessions expire or are abandoned.
+
+## When to Use This Skill
+
+- Use when you need structured change tracking across AI coding sessions
+- Use when a bot session expires mid-task and the next session needs full context to resume
+- Use when onboarding a project with undocumented change history
+
+## How It Works
+
+### State Machine
+
+```
+planned -> in_progress -> implemented -> tested -> deployed
+             |
+             +-> blocked
+```
+
+### Commands
+
+`/tc init` | `/tc create` | `/tc update` | `/tc status` | `/tc resume` | `/tc close` | `/tc export` | `/tc dashboard` | `/tc retro`
+
+### Session Handoff
+
+Each TC stores: progress summary, next steps, blockers, key context, and files in progress — so the next bot session picks up exactly where the last left off.
+
+### Non-Blocking
+
+TC bookkeeping runs via background subagents. Never interrupts coding work.
+
+## Features
+
+- Structured JSON records with append-only revision history
+- Test cases with log snippet evidence
+- WCAG AA+ accessible HTML output (dark theme, rem-based fonts)
+- CSS-only dashboard with status filters
+- Python stdlib only — zero external dependencies
+- Retroactive bulk creation from git history via `/tc retro`
+
+## Full Repository
+
+https://github.com/Elkidogz/technical-change-skill — MIT License