skill-comply

Topics in the source

• skill-comply: Automated Compliance Measurement
• Supported Targets
• When to Activate
• Usage
• Key Concept: Prompt Independence
• Report Contents
• Advanced (optional)

Measures whether coding agents actually follow skills, rules, or agent definitions by: 1. Auto-generating expected behavioral sequences (specs) from any .md file 2. Auto-generating scenarios with decreasing prompt strictness (supportive → neutral → competing) 3. Running claude -p and capturing tool call traces via stream-json 4. Classifying tool calls against spec steps using LLM (not regex) 5. Checking temporal ordering deterministically 6. Generating self-contained reports with spec, prompts, and timelines Skills (skills//SKILL.md): Workflow skills like search-first, TDD guides Rules (rules/common/.md): Mandatory rules like testing.md, security.md, git-workflow.md Agent definitions (agents/.md): Whether an agent gets invoked when expected (internal workflow verification not yet supported) User runs /skill-comply User asks "is this rule actually being followed?" After adding new rules/skills, to verify agent compliance Periodically as part of quality maintenance Measures whether a skill/rule is followed even when the prompt doesn't explicitly support it. Reports are self-contained and include: 1. Expected behavioral sequence (auto-generated spec) 2. Scenario prompts (what was aske

This is an excerpt. Refer to the complete source and its current requirements.