release-notes-generatorlisted

Draft an evidence-backed per-release note and assess the kit's honest maturity ladder for a shipped roadmap slice in the Seshat BI repo. Use when someone asks to "generate the release notes", "what maturity level is the kit at", "assess the kit's maturity", or "record what became possible in this release". This is Maintenance Automation (F024): it runs as the conductor's post-milestone read, not per a per-run human trigger. It READS the F028 evidence pack + the F032 compatibility matrix + the roadmap ledger, DRAFTS the seven release-note blocks with every capability claim cited, ASSESSES the seven evidence-gated maturity rungs (L0..L6) by a BINARY evidence test each, reports the level as the highest all-evidence-present rung, and then STOPS for the named release owner. It emits NO numeric / maturity / confidence score (the ladder is milestones, not a score), re-measures NOTHING (no seshat check/validate, no DB, no powerbi/ read), self-approves NO release, self-confirms NO level, and publishes nothing.
Kemetra/Seshat-BI · ★ 2 · AI & Automation · score 68

Install: claude install-skill Kemetra/Seshat-BI

# release-notes-generator - **Roadmap feature:** F033 **On-disk spec:** `specs/027-release-maturity-management/` (dir 027 == F033; when the dir number and the F-number disagree, the roadmap F-number wins). - **Authority category:** Maintenance Automation (the F024 enumerated declaration -- see `docs/architecture/product-modules.md`). NO connectivity level and NO capability level: those sub-axes belong to Execution Adapters and Product Modules; Maintenance Automation carries neither (its boundary is prose). The kit ships in slices. Each slice changes WHAT THE KIT CAN DO, but the kit has no durable, reviewable record of "what became possible in this release, and how mature is the capability". Today that answer lives only in commit messages and the roadmap's delivered ledger. This skill is the record: it DRAFTS a per-release note (seven required blocks) and ASSESSES an evidence-gated maturity ladder. It composes evidence others already recorded; it originates none of it and owns no truth. A maturity claim is exactly where a tool is tempted to round "two worked examples" up to "production ready"; the kit's no-fake-confidence rule (hard rule #9) forbids that, so the ladder is an evidence-gated MILESTONE ladder -- not a score -- and the skill drafts-and-stops for a named release owner to approve. ## Authority declaration (F024) -- Maintenance Automation (no sub-axis) This skill declares EXACTLY ONE of the five F024 authority categories. Quoted verbatim from `docs/arc