Accelint Archive Synthesis

Read backward across the entire archived-change history to check whether it still agrees with itself, check the running index itself against the live files it claims to summarize, and surface any capability whose accumulated relationships suggest it has outgrown its own boundaries. This is the "lint" operation in Karpathy's LLM Wiki pattern: ingest already exists as accelint-qrspi-archive, query already exists as artifact loading at propose/apply time, but nothing periodically re-reads the whole corpus to check it is still internally consistent. Every existing drift check in this stack, including accelint-qrspi-apply Step 5's own hub-doc refresh, is forward-looking and scoped to one change's own proposal and design. This skill is the only one that looks the other direction — and, since accelint-qrspi-archive moved to row-level index patching for its own efficiency, the only one that ever re-checks specs/INDEX.md against the spec.md files it summarizes at all.

That backward-looking scope is also what keeps this skill's footprint small and deliberate. It reads two indexes and, for genuine candidates only, a handful of design.md files and, for the reconciliation check, a lightweight top-of-file read of every spec.md. It never rewrites a hub doc directly, and every write it does make — on either index — is a single targeted line, gated behind an explicit human confirmation of that specific finding, and never runs on its own initiative. A human always decides which findings get acted on.

What This Skill Does

Automates: a periodic, corpus-wide consistency check across every archived OpenSpec change, surfacing contradictions between past decisions, flagging capabilities that have become structurally over-coupled, and flagging specs/INDEX.md rows that have drifted from the spec.md files they summarize. Scope: openspec/changes/archive/INDEX.md, openspec/specs/INDEX.md, and — for the reconciliation check only — a lightweight read of each spec.md's ## Purpose heading and related: frontmatter. This skill never originates a change, never implements a fix, and never edits a hub doc itself. Output: a CRITICAL / WARNING / SUGGESTION report in the same register as /opsx:verify, plus, only after a human confirms a specific finding, a Status column update on the relevant archive row, a single-row patch or removal on specs/INDEX.md, and/or an independent invocation of the affected writer skill(s) via the shared findings: interface — see Step 8 for which finding types get which. Does NOT: run automatically, run as a blocking step inside any other skill's workflow, rewrite any document directly, write any archive/INDEX.md column other than Status, write to specs/INDEX.md beyond a single confirmed row's patch or removal, introduce any severity or status state beyond CRITICAL/WARNING/SUGGESTION and current/superseded, or reconcile a contradiction on its own judgment without a human confirming which side of it stands.

Prerequisites