readmedaddy

Use when writing or improving a README — thin, stub, outdated, a wall of text, unscannable, or missing; a new repo needs a front page; no quickstart, install, badges, or examples; broken instructions or AI slop. Triggers include "write me a README", "make this README better", "the readme sucks", "polish the readme", "readme.md", "project front page", "documentation landing". Works for any repo: CLI, library, framework, app/SaaS, infra, data/ML, agent skill, research, monorepo, internal tool. Yields to user and project instructions; never invents facts about the code.

Use when a release is being cut and the CHANGELOG is empty, stale, or out of sync with the commits since the last tag; when commit messages need to be turned into human-readable release notes grouped by type; or when asked to "update the changelog", "write release notes", or "what changed since the last release". Not a version bumper and not a tag/publisher; yields to an existing changelog format already in the repo.