---
description: Add an entry to the [Unreleased] section of the current scope's CHANGELOG
argument-hint: "<added|changed|deprecated|removed|fixed|security> <text>"
---

The user wants to add a changelog entry. Arguments: **$ARGUMENTS**

First token is the section name (one of `added`, `changed`, `deprecated`,
`removed`, `fixed`, `security`). Everything after is the entry text.

Follow the cleepi SDD workflow (load `/skill:sdd` if you haven't):

1. **Resolve scope.** Determine which `CHANGELOG.md` to edit:
   - If the change only affects one package, target =
     `packages/<name>/CHANGELOG.md`.
   - If it's a repo-level event (tooling, conventions, new package), target =
     `/CHANGELOG.md` at the repo root.
   - If ambiguous, ask the user.

2. **Validate the section name.** Must be one of: `Added`, `Changed`,
   `Deprecated`, `Removed`, `Fixed`, `Security`. Capitalize properly.

3. **Read the target CHANGELOG.** Find the `## [Unreleased]` section. If it
   doesn't exist, add it at the top (just under the file header), then
   proceed. If the file doesn't exist at all, stop and ask the user — a
   missing CHANGELOG suggests a missing package or wrong scope.

4. **Find or create the subsection** (`### Added`, etc.) within `[Unreleased]`.
   Preserve the conventional ordering (Added, Changed, Deprecated, Removed,
   Fixed, Security) — insert new subsections in that order.

5. **Append the entry** as a bullet point. If the entry text references a
   spec the user mentioned, append a link in the form
   `(see [spec AC-NNN](docs/AC-NNN-slug/spec.md))`. ADRs are no longer a
   separate artifact — link to the spec whose `## Decision` section
   records the rationale instead.

6. **Report.** Tell the user which file you edited and show the new bullet.
   Do not modify any released version sections — those are frozen.