grimoire-check

Installation
SKILL.md

Compare implementation with user intent and acceptance criteria, not literal adherence to a plan. Plans are design guidance; code and relevant execution evidence establish behavior. Tickets, specs, and applicable ADRs refine constraints.

Under orchestration, the caller's execution contract takes precedence over this skill's standalone defaults.

Standalone, remain read-only: report findings without changing Spec, Ticket, or other artifact statuses. Update statuses only with explicit user authorization or permission from the caller's execution contract; evidence alone is not write permission. Fix code only when implementation is also authorized.

Compare outcomes

Accept a plan, ticket, spec, acceptance criteria, or clear conversation goal; no formal plan is required. Derive the behavior-and-constraint checklist from original requirements before comparing implementation summaries or tests, so their omissions do not define the audit scope. Retain a source reference for each scoped outcome, including required error paths and constraints. If original sources are unavailable, disclose the limit rather than treating a summary as exhaustive. Ask only when competing interpretations would change the verdict; otherwise bound assumptions.

Read source artifacts, applicable ADRs, actual implementation, relevant tests/configuration, and available runtime evidence. Separate intent from optional design choices. Inspect related changes for scope expansion; do not infer behavior from filenames.

Each outcome must have evidence or an explicit evidence gap:

  • match — evidence establishes required behavior and constraints.
  • gap — evidence demonstrates required behavior or a binding contract is missing or unmet.
  • deviation — implementation materially differs from design guidance; acceptable when requirements and constraints still hold.
  • extra — related behavior exceeds the authorized scope, not merely an omitted plan detail.
  • needs-verification — evidence is insufficient to establish satisfaction or violation. Absence of evidence is not evidence of missing behavior.
Installs
18
GitHub Stars
3
First Seen
Jul 23, 2026