document-changeslisted

# Document Changes Review everything that changed in a project since its last release, then bring every documentation artifact into agreement with the code: the changelog, the internal version, and the per-feature `feature.json` records. Documentation must be comprehensive and written in natural, human-readable language; never raw diff or commit dumps. This skill **documents** existing change and then commits the documentation + tracked changes in logical bundles. It does not modify product code, and it does not push or tag. ## Usage ``` document-changes [app] ``` ## Inputs Resolve the target project: 1. If a path argument is given, use it. 2. Otherwise use the current working directory. The target must be a git repository. Read, if present: - The project's **version manifest** (see below) — authoritative; the version lives in the root manifest only - `VERSION`: plain-text version file (bump in lockstep with the manifest when both exist) - The project changelog (see detection order in Phase 1) - `.aidd/features/<id>/feature.json`: existing feature records - `docs/reference/feature-fields.md`: the feature.json field contract (read it if present; aidd has it) ### Version source **Applies to any project, whatever its stack.** Discover the version manifest by role rather than assuming one ecosystem. Check for these at the repository root, in order, and record which exist: | Manifest | Version field | | ------