User guide release notes checklist (engineering)

Operational reminder for whoever ships user-visible enhancements:

:::info Engineering-only housekeeping

Readers do not submit these notes—engineering updates this page or linked docs when narratives shift.

:::

When you ship materially user-visible Skilladder behaviours:

Step	Prompt
1	Decide whether Slack summary suffices vs editing guide articles—bias toward documenting navigation deltas + roles impacted.
2	Date-stamp succinct bullet snippets optionally linking Linear ticket IDs for auditing (internal audience only).
3	Tag CS leadership if externally visible promises shift (elevator pitch tweaks).

This file intentionally stays lightweight—a future iteration may adopt automated feeds.