grimoire-verify

Verify grimoire changes align with feature specs and decision records.

Updated Jan 26, 2025
One-click install
npx skills add https://github.com/jlissner/lissner.io --skill grimoire-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grimoire-verify
Source: https://github.com/jlissner/lissner.io/tree/main/.claude/skills/grimoire-verify
Command: npx skills add https://github.com/jlissner/lissner.io --skill grimoire-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify that a grimoire change is implemented in accordance with the feature specs and decision records, ensuring alignment before archiving.

Core Features & Use Cases

  • Completeness verification: ensures that the implementation fully covers the tasks and requirements documented in the change artifacts.
  • Correctness tracing: links features, code changes, tests, and decisions to confirm alignment.
  • Coherence with decisions: cross-checks decisions and consequences against the codebase and documentation to detect drift.
  • Security & governance checks: validates adherence to security and governance considerations described in the grimoire workflow.

Quick Start

Apply a grimoire change, then run grimoire-verify to assess alignment with specs and decisions.

Frequently Asked Questions about grimoire-verify

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

FAQPage Schema
How do I verify code changes align with feature specs and decision records?

Verification of code changes against feature specs and decision records involves tracing completeness, correctness, and coherence to ensure implementation aligns before archiving. This process cross-checks decisions and consequences against the codebase to detect drift.

What is the best way to check if a feature implementation is fully complete before archiving?

Completeness verification ensures an implementation fully covers tasks and requirements documented in change artifacts. It links features, code changes, tests, and decisions to confirm full alignment before the change is archived.

How does decision tracing work during code review to detect specification drift?

Decision tracing cross-checks documented decisions and their consequences against the actual codebase and documentation. This mechanism detects drift by validating that the implementation remains coherent with the original governance considerations.

Can I use verification checks for design reviews and policy updates across a project?

Yes, this verification task applies to code changes, design reviews, and policy updates across a project. It validates task completeness, implementation correctness, and decision coherence regardless of the specific change type.

Does the verification process validate security and test artifacts alongside the implementation?

Yes, the verification process optionally checks security, tests, and documentation artifacts. It validates adherence to security and governance considerations described within the workflow to ensure comprehensive alignment.

When should I run a verification check on my project changes?

You should run a verification check after applying a change and before archiving it. This ensures the implementation fully satisfies the documented feature specs and decision records, preventing incomplete or misaligned updates.