kd

Use when creating, grooming, or working a persistent improvement backlog — adding or triaging an item, refuting a candidate, deciding where a long-lived task should live, or grooming stale entries. For this repo the backlog is the git-tracked docs/backlog.md. Reach for this skill whenever you are about to write down a future task, a tech-debt note, or a "we should eventually…" item, even if the user doesn't say the word "backlog" — durable tasks belong here, not in throwaway scratch. Pairs with the improvement-cycle skill, which discovers and ships the items this skill files.

Use when doing self-directed, iterative improvement of this codebase — "improve the UX", "find things to improve", "keep improving X", run improvement cycles, or generate/work a backlog. Encodes how to DISCOVER improvement points yourself (by investigating source code and the web), adversarially VERIFY them against the real code, and IMPLEMENT them one verified cycle at a time. Tuned for kd's UI/UX work but the loop is general.

Use when cutting a kd release — publishing a new version of the kd app and/or its Helm chart, or when the user says "release X.Y.Z", "tag a release", "ship a new version", or "publish the chart". Encodes the two independent semver tracks (app `vX.Y.Z` → GoReleaser; chart `chart-vX.Y.Z` → helm push), the exact order of operations, the pre-flight gates, and the traps that fail a release half-published. Reach for this whenever a git tag is about to trigger a public artifact.