aif-verify

Verify completed code implementation against a project plan.

2|Updated Aug 22, 2025

Search Tags:#code quality #testing #linting #verification #auditing #plan adherence

Ready to run

npx skills add https://github.com/drsapaev/final --skill aif-verify-drsapaev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aif-verify
Source: https://github.com/drsapaev/final/tree/main/.codex/skills/aif-verify
Command: npx skills add https://github.com/drsapaev/final --skill aif-verify-drsapaev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill guarantees that implemented code precisely matches the project plan, meets quality standards, and is production-ready, preventing costly errors and rework.

Core Features & Use Cases

Task Completion Audit: Verifies every requirement in the plan has been fully implemented.
Code Quality Checks: Assesses build status, test results, linting, and dependency integrity.
Consistency Verification: Detects drift between the plan and code, identifies leftover artifacts, and checks configuration documentation.
Use Case: After a developer completes a feature, run this Skill to automatically confirm all tasks are done, the code compiles, tests pass, and no TODO comments remain, before merging.

Quick Start

Run the aif-verify skill to check the completed implementation against the plan.

Frequently Asked Questions about aif-verify

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

FAQPage Schema

How do I verify code implementation against a project plan before merging?▼

Verifying code implementation against a project plan requires auditing task completion, checking build status, running tests, and performing linting. This ensures all requirements are fully met and detects drift between the plan and code.

What is plan adherence verification in software engineering?▼

Plan adherence verification confirms completed code matches the project plan by auditing task completion and performing consistency checks. It prevents costly errors and rework by detecting drift between the plan and implementation.

How do I check for leftover TODO comments and artifacts after feature implementation?▼

Checking for leftover TODO comments and artifacts involves running consistency verification to identify remaining items in the codebase. It ensures configuration documentation aligns with the actual implementation before merging.

Does code quality verification check build status, test results, and dependency integrity?▼

Code quality verification assesses build status, test results, linting, and dependency integrity to ensure implemented code meets quality standards. It confirms the codebase is production-ready and prevents costly rework.

When do I need to run a task completion audit?▼

You need to run a task completion audit after a developer completes a feature to verify every requirement in the project plan has been fully implemented. This prevents errors by ensuring no tasks are missed before merging.

What are the limitations of automated plan adherence checks?▼

Automated plan adherence checks verify task completion, build status, tests, and linting, but require a detailed project plan to function effectively. They detect drift and leftover artifacts but depend entirely on the plan's accuracy.