Verification Discipline

Enforce task-class-aware verification rules during code execution.

2|1|Updated Apr 7, 2026

Search Tags:#code quality #verification #task execution #task classification #verification enforcement

Ready to run

npx skills add https://github.com/bigeasyfreeman/adlc --skill verification-discipline-bigeasyfreeman

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Verification Discipline
Source: https://github.com/bigeasyfreeman/adlc/tree/main/skills/tdd-enforcement
Command: npx skills add https://github.com/bigeasyfreeman/adlc --skill verification-discipline-bigeasyfreeman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enforces task-class-aware verification during execution, ensuring that each task is verified according to its specific requirements, preventing false positives and improving code quality.

Core Features & Use Cases

Task-Class-Specific Verification: Verifies tasks based on their classification (e.g., feature, bugfix, build_validation, lint_cleanup).
Execution Time Verification: Operates at execution time, checking verification before task completion.
Fallback Rules: Applies fallback verification rules for refactor or infra tasks.
Integration with Codegen Context: Integrates with the codegen-context skill to provide detailed verification specifications.

Quick Start

Run the Verification Discipline skill to enforce verification rules for the current task.

Frequently Asked Questions about Verification Discipline

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

FAQPage Schema

How do I enforce task-specific verification rules during code execution?▼

Task-class-aware verification enforces specific verification rules during code execution by classifying tasks first, then applying tailored checks. It prevents false positives by ensuring each task type meets its exact requirements before completion.

What is task-class-aware verification and how does it improve code quality?▼

Task-class-aware verification categorizes tasks into classes like feature, bugfix, build_validation, or lint_cleanup, then applies specific verification rules to each. This targeted approach prevents false positives and improves overall code quality.

How do I apply fallback verification rules for refactor or infra tasks?▼

Fallback verification rules for refactor or infra tasks apply automatically when a task does not match a primary classification. A verification enforcement system triggers default checks, ensuring unclassified tasks still meet baseline quality standards.

Can I integrate task classification with codegen context for detailed verification specifications?▼

Task classification integrates with codegen context to provide detailed verification specifications. This integration allows the enforcement mechanism to use contextual code generation data to determine the exact verification rules required for each task class.

When do I need execution time verification for feature or bugfix tasks?▼

Execution time verification for feature or bugfix tasks is needed when you want to verify code quality before task completion. This approach checks verification rules at execution time, ensuring the specific requirements of the task class are met before finalizing.

Does verification enforcement work for lint cleanup and build validation tasks?▼

Verification enforcement works for lint cleanup and build validation tasks by applying task-class-specific verification rules. The system verifies these tasks based on their classification, ensuring the specific verification requirements for lint and build checks are enforced.