TWISTEdBRACKETS

Skill

Conformance Check

Audit docs/technical/ against the codebase: missing tests, orphan tests, locked stack violations, contract drift.

// workflow;

Behaviour

What it does

  • Loads requirements, locked tech-stack choices, contracts, and engineering guidelines
  • Scans tests and source for REQ-ID traceability and orphan coverage
  • Finds drift in both directions: docs the code does not satisfy, code with no spec
  • Reports findings by severity before suggesting fixes
  • Writes a conformance report to docs/plans/
  • Hands off to refining-docs (doc gaps) or reconciling-changes (code behind spec)

When to use

Good fits

Before impact analysis on an existing app

After a delta build, to confirm code matches the updated spec

When you ask whether code still matches the documentation

When planning a brownfield change and you need to know existing drift

Development harness

Step 3 of 8 · Change control

Part of the design-to-ship pipeline: brainstorming → technical-documentation → conformance-check → reconciling-changes → planning → project-setup → executing-plans → shipping. Install the full set for structured feature work.

Install

Get this skill

Uses Agent Kit via npx; no global install required.

Quick install

sh
npx @levi-putna/agent-kit@latest add levi-putna/skills --skill conformance-check

Global (Cursor)

sh
npx @levi-putna/agent-kit@latest add levi-putna/skills --skill conformance-check --global --agent cursor

Global (Claude)

sh
npx @levi-putna/agent-kit@latest add levi-putna/skills --skill conformance-check --global --agent claude

Project install

sh
npx @levi-putna/agent-kit@latest add levi-putna/skills --skill conformance-check --project

Interactive install

sh
npx @levi-putna/agent-kit@latest add levi-putna/skills

Uninstall

sh
npx @levi-putna/agent-kit@latest remove conformance-check

Example

Example prompt

Conformance Check

Run a conformance check: do our tests cover every REQ in requirements.md?

Flow

How the skill works

  1. Load the spec side from docs/technical/
  2. Scan tests, source, and config on the code side
  3. Run requirement coverage, test traceability, and locked-decision checks
  4. Write a conformance report to docs/plans/
  5. Hand off to refining-docs or reconciling-changes based on findings