rune-constraint-check

Audits workflow conversations for compliance with skill HARD-GATEs and mandatory constraints.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/dangvu008/VietTruyen --skill rune-constraint-check-dangvu008
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rune-constraint-check
Source: https://github.com/dangvu008/VietTruyen/tree/main/.agents/skills/rune-constraint-check
Command: npx skills add https://github.com/dangvu008/VietTruyen --skill rune-constraint-check-dangvu008

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents often claim they followed mandatory workflow constraints (write tests first, get plan approval, run verification) without actually doing so. This Skill independently audits the conversation trail and tool call ordering to verify whether HARD-GATEs and constraints were genuinely followed, not just claimed. ## Core Features & Use Cases - HARD-GATE Auditing: Extracts mandatory constraints from each invoked skill's SKILL.md and checks them against actual tool call evidence. - Violation Classification: Distinguishes BLOCK-level HARD-GATE violations from WARN-level constraint violations and INFO-level best-practice skips. - Compliance Reporting: Produces a per-skill compliance summary table with specific evidence and remediation steps for each violation. - Use Case: After a cook workflow finishes, run a discipline audit to confirm tests were written before implementation code, plan approval was obtained, and verification output was actually captured. ## Quick Start Audit the current session for constraint compliance by asking the agent to run a constraint check on all skills invoked in this workflow.

Frequently Asked Questions about rune-constraint-check

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

FAQPage Schema
How do I verify an AI agent followed workflow constraints?

Run a constraint audit that extracts HARD-GATEs from each invoked skill's SKILL.md and checks them against tool call ordering and conversation evidence. Temporal constraints like test-before-code are verified by comparing Write/Edit timestamps, not agent self-reports.

What is the difference between a HARD-GATE violation and a constraint violation?

A HARD-GATE violation is classified as BLOCK, meaning the skill defines it as non-negotiable and the pipeline must halt. A constraint violation is a WARN, meaning the step is required but not fatal. Best-practice skips are logged as INFO.

Can this audit trust the agent's own compliance claims?

No. The audit explicitly rejects agent self-reports as evidence and independently checks tool call sequences, user approval messages, and captured stdout. This prevents agents from claiming verification steps that never occurred.

Which skills and gates does the constraint audit cover?

It audits every skill invoked in the session, including test (Iron Law test-first), cook (scout before plan), plan (test entries per phase), verification (evidence per claim), sentinel and preflight (BLOCK halts), and debug (no code changes, 3-fix escalation).

When should a constraint check be run in a workflow?

Run it at the end of a cook workflow as a discipline audit, during team workflows to verify stream agent compliance, or manually mid-session. It is read-only and makes no outbound calls, so it is safe to run at any checkpoint.