library-fitness-reviewlisted

Trigger a comprehensive whole-collection library-fitness review with a project-defined catalogue of persona reviewers when a documentation collection (the parent case is a governance/security documentation library) undergoes a major change or reaches its minimum review cadence, quarterly by default unless the adopting project records a different interval. The parent GRC library's major-change triggers are a new domain directory, a new document type, multiple governance rule additions, and a major restructure. Each invocation dispatches a fan-out of independent persona subagents (for example an executive reader, a security practitioner, an auditor, a newcomer) who review every page from a fresh-reader perspective without inheriting maintainer mental models. Catches comprehensibility, usability, logical-structure, standardization, domain quality, auditability, maintainability, and reader-experience gaps that per-change validation sweeps and mechanical audit gates do not detect. Surfaces prioritized recommendati
jposluns/grc_library · ★ 2 · Code & Development · score 68

Install: claude install-skill jposluns/grc_library

# Library Fitness Review ## Project wiring (the parent library's instantiation; adopters substitute their own) Portable procedure, concrete names. In the parent GRC library this skill runs with: - Persona catalogue and severity model: the activity convention document in the consuming project's working state (the persona briefs with per-persona scope and exclusions, the severity-model definitions, the per-run file format, and the operational guidance; the parent catalogue defines ten personas, labelled `A` through `J`). - Run-record path pattern: a dated per-run record in the consuming project's working state, one combined report per run, with `rN` the run ordinal that day. - History register: the fitness-review invocation history register in the consuming project's working state (the invocation history table, whose `Personas` column records the personas dispatched, written in the register as `A, B, C, D, E, F, G, H, I, J (all 10)` for a full dispatch, plus the open remediation backlog tracking table). - Remediation-backlog id scheme: `FR-N` (`FR-1`, `FR-2`, ...), carried into TODO entries and referenced from the CHANGELOG entry of each PR that closes an item. - Mechanical baseline command: `tools/run_all_audits.sh`, the parent library's full audit suite. - Citation-accuracy boundary: the corpus Citation Verification Specification (its §14 records that the library does not verify standard content against library interpretation), which bounds what a fitness