Technical Change Tracking and Session Handoffs
Track technical changes from intent to verified closure, with durable records, session handoffs, and changelog exports.
Before & after
Same prompt, same agent — the only difference is the skill.
Keeping track of technical changes across different parts of your system can be complicated. You might use comments in code or a document to track what changed and why. Version control history helps but can be scattered. You could create a change record to centralize information about a large migration. As work progresses across multiple services, keeping everyone informed about status becomes important. Handoffs between sessions or team members are easier if the change is well-documented. Closing out changes and archiving the information helps you build institutional knowledge.
TECHNICAL CHANGE RECORD: MULTI-SERVICE SCHEMA MIGRATION CHANGE INIT ID: TC-2026-0847 Title: User accounts table denormalization (email_verified, phone_verified) Owner: Platform team (Alice, Bob) Status: IN_PROGRESS Start date: 2026-07-22 Target completion: 2026-08-15 Risk level: MEDIUM (3 services affected, requires backfill) DESIGN PHASE Decision: Add columns user.email_verified_at, user.phone_verified_at (timestamps) Rationale: Avoid 3-table joins in auth checks; improve query performance Affected services: auth-service, notifications-service, admin-service Dependencies: Requires feature flag feature_phone_verification already live IMPLEMENTATION CHECKLIST ✓ Auth-service: Migration script written, tested on staging ✓ Backfill script: 2.1M user records (script complete, validation pending) ☐ Notifications-service: Update verification event listener ☐ Admin-service: Update user editing form to show verified_at timestamps ☐ Deployment: Rolling deploy across 5 datacenters (20percent at a time) HANDOFF NOTE (for next session) Last activity: Backfill validation started, expect completion in 4 hours Next steps: Monitor backfill for errors, then deploy notifications-service changes Config needed: Set FEATURE_FLAG=phone_verify_timestamps for staging env Contact if blocked: Reach out in #platform-eng Slack DEPLOYMENT LOG 2026-07-30 10:45 UTC: Auth-service v2.14.0 deployed to production 2026-07-30 11:30 UTC: Backfill job completed 2.1M records in 45 minutes 2026-07-31 09:00 UTC: Notifications-service changes awaiting review CLOSE-OUT (when done) Deployed: 2026-08-15 Validation: All queries within SLO, zero rollback events Post-mortem: Process review for next multi-service migration Archive: Link to deployment summary + metrics
About this skill
“The last session changed something, but I can't tell what's finished or what to do next.” This workflow turns technical work into a durable change record that separates intent, actual edits, verification evidence, and unfinished decisions. Resuming work starts by reconciling that record with the current code.
What it does
- Creates unique change records with bounded scope, acceptance checks, and explicit exclusions.
- Updates actual files, decisions, scope deviations, blockers, and verification results without erasing history.
- Lists active changes with age, last update, and the next concrete action.
- Reconciles a previous session's handoff against current repository state before implementation resumes.
- Gates closure on resolved questions and recorded acceptance evidence.
- Exports changelog entries that describe delivered behavior without implying a release or deployment occurred.
What you get
A compact Markdown record for each coherent change, plus a restart-ready handoff, status view, or changelog entry when requested. Records can be maintained in your existing tracking location or delivered directly in chat when file access is unavailable.
Best for
Developers and teams carrying implementation work across AI sessions, branches, or reviewers, especially when conversational history is no longer enough to explain what changed and why.
SKILL.md preview
---
name: technical-change-tracking-and-session-handoffs
description: Maintain technical change records from intent through closure, reconciling session handoffs against current repository evidence and preserving decisions, verification results, and next actions. Use when the user says "track this technical change", "create a TC record", "update TC-0091", "what changes are still open?", "resume the previous session", "close this change", "export a changelog entry", or "my AI sessions keep losing what changed".
---
# Technical Change Tracking and Session Handoffs
… (sign up to view the full skill)More development skills
View all Development skills →Performance Bottleneck Profiling: Node, Python, Go
Classifies a slowdown, gives exact profiler commands, reads the output, and proves the fix with same-conditions p95/p99 numbers.
Feature Scaffolding with Working Tests
Turn a short feature spec into code, runnable tests, and integration wiring that match your existing project.
Feature Flag Rollouts and Kill Switches
Design staged flag rollouts, verify rollback paths, and audit flag debt with explicit defaults, gates, and retirement plans.
Microcontroller Firmware and RTOS Engineering
Build and debug MCU firmware with bounded ISR/RTOS timing, safe DMA ownership, and measured power budgets.