Project version requirements management and command-line suggestions for change log generation

[clay-good]

Note

Moved from issue #386, originally opened by @hermer on 2025-12-22. Continuing the conversation here in Discussions — the original issue thread (including any comments) stays available at #386 for the record.

---

The desired workflow is to implement an automated mechanism that integrates version planning, to-do lists, proposal discussions, and implementation records, automatically generating a version changelog after release.

The expected workflow is as follows:
Version Planning Management: Maintain a requirements list for each version in the project files (e.g., VERSIONS.md).

# Version Planning
## 1.0.0 (Under Development)

- [ ] Feature A: xxxx (Associated with Issue #1)

- [ ] Feature B: xxxx (Associated with Issue #2)

## 1.1.0 (Planned)

- [ ] Feature C: xxx

- [ ] Feature D: xxx

Automated Task Status: When a requirement or task is completed, its status is automatically updated to "Completed".

Changelog Generation: When a version is released, automatically or semi-automatically generate a changelog for that version, based on completed tasks/Issues.

Desired Features: Command-driven, managing status and generation via simple CLI commands.