review-invariants

Walks maintainers through deferred invariant blocks and registers approved rules in the specs ledger.

Updated Jul 13, 2026
One-click install
npx skills add https://github.com/docktermj/senzing-bootcamp-claude-plugin-development --skill review-invariants-docktermj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-invariants
Source: https://github.com/docktermj/senzing-bootcamp-claude-plugin-development/tree/main/.claude/skills/review-invariants
Command: npx skills add https://github.com/docktermj/senzing-bootcamp-claude-plugin-development --skill review-invariants-docktermj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deferred invariant blocks in specs/IMPLEMENTED.md accumulate as rules that already ship in the plugin but are recorded in no invariant, and deciding them by hand produces silent errors: miscounted queues, re-presented held decisions, missed citation sites, and unverified rule quotes. ## Core Features & Use Cases - Computed review queue: pending_invariants.py lists pending and held DEFERRED INVARIANT blocks separately, with the next free INV ID, so held decisions are never re-offered. - Quote verification: the check subcommand confirms every rule quote appears verbatim in the file it names, reporting checked, mismatched, unresolved, and no-prose-site counts. - Citation site discovery: the sites subcommand separates deferral-named sites, prose-named sites, and scan candidates so no shipping location is missed. - Use Case: A maintainer of the Senzing Bootcamp Claude Plugin runs the skill to review eleven deferred invariants one at a time, registering approved wording with citations, recording holds with revisit conditions, and writing a dated session record. ## Quick Start Ask the assistant to review the pending deferred invariants in specs/IMPLEMENTED.md one at a time using the review-invariants skill.

Frequently Asked Questions about review-invariants

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review deferred invariants in the Senzing Bootcamp plugin?▼

Run pending_invariants.py list to see the numbered pending queue and held blocks, then use show and sites for each block. Present one invariant at a time, ask the maintainer for a register, hold, or amend verdict, and carry out only that decision.

What is a deferred invariant in a spec-driven workflow?▼

A deferred invariant is a rule already shipping in the plugin and guarded by a test, but recorded in no invariant because minting invariants is reserved for the maintainer. Implementation skills write DEFERRED INVARIANT blocks, and this review skill resolves them.

Can this skill approve or sign off an invariant itself?▼

No. The skill never signs off an invariant; it presents the shipping rules, drafted wording, and citation sites, then waits for the maintainer's verdict. A decision the maintainer did not give is never applied as a default.

Why does the check command report unresolved and no-prose-site counts?▼

Unresolved means a named path does not exist, so that rule's quote is unverified and the check is not clean. No-prose-site means the rule is encoded in code or tests rather than prose, which is legitimate and requires nothing.

Does review-invariants ship to bootcamp users?▼

No. The skill lives under .claude/, which propagate.sh does not mirror to the public repo. It is a maintainer-only development tool and is never invoked during a bootcamp session.