tc-tracker

# TC Tracker Track every code change with structured JSON records, an enforced state machine, and a session handoff format that lets a new AI session resume work cleanly when a previous one expires. ## Overview A Technical Change (TC) is a structured record that captures **what** changed, **why** it changed, **who** changed it, **when** it changed, **how it was tested**, and **where work stands** for the next session. Records live as JSON in `docs/TC/` inside the target project, validated against a strict schema and a state machine. **Use this skill when the user:** - Asks to "track this change" or wants an audit trail for code modifications - Wants to hand off in-progress work to a future AI session - Needs structured release notes that go beyond commit messages - Onboards an existing project and wants retroactive change documentation - Asks for `/tc init`, `/tc create`, `/tc update`, `/tc status`, `/tc resume`, or `/tc close` **Do NOT use this skill when:** - The user only wants a changelog from git history (use `engineering/changelog-generator`) - The user only wants to track tech debt items (use `engineering/tech-debt-tracker`) - The change is trivial (typo, formatting) and won't affect behavior ## Storage Layout Each project stores TCs at `{project_root}/docs/TC/`: ``` docs/TC/ ├── tc_config.json # Project settings ├── tc_registry.json # Master index + statistics ├── records/ │ └── TC-001-04-05-26-user-auth/ │ └── tc_record.json # Source ...