Change Specify

Use when a change rationale just emerged — a revert, hotfix, fix chain, workaround, or abandoned approach — and you want guided facilitation (options, consequences, provenance) before it becomes a ChDR. Not for mining git history (/change-init) or reviewing drafts (/change-clarify); class boots only suggest this skill, they never write drafts.

tikalk Updated 145 repo stars

File contents

tikalk/adlc-team-skills commit 978cb1f936

Frequently asked questions

npx get-skill add tikalk/change-specify