aif-verify

Audit completed work against a project plan for task completion and quality checks.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/batFormat/sancrm-docs --skill aif-verify-batformat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-verify
Source: https://github.com/batFormat/sancrm-docs/tree/main/.claude/skills/aif-verify
Command: npx skills add https://github.com/batFormat/sancrm-docs --skill aif-verify-batformat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill guarantees that implemented code meets all requirements, passes quality checks, and aligns with the original plan, preventing bugs and ensuring production readiness.

Core Features & Use Cases

  • Task Completion Audit: Verifies that every task defined in the plan has been fully implemented.
  • Code Quality Checks: Assesses build status, test results, linting, and dependency integrity.
  • Consistency Checks: Identifies drift between the plan and code, leftover artifacts, and configuration issues.
  • Use Case: After a developer uses /aif-implement to add a new feature, they can run /aif-verify to automatically confirm that all planned user stories are coded, the application compiles, tests pass, and no TODO comments were left behind.

Quick Start

Run the aif-verify skill to check the current 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?

To verify code implementation against a project plan, run a post-implementation audit that checks task completion, code compilation, test execution, and linting adherence to ensure the final work aligns with project specifications.

What is a post-implementation code audit?

A post-implementation code audit is a comprehensive verification process that assesses completed work against a project plan, checking build status, test results, linting, and dependency integrity to prevent bugs and ensure production readiness.

How do I check for leftover TODO comments and code drift after a feature implementation?

Checking for leftover artifacts and configuration drift requires running consistency checks that identify gaps between the project plan and code, ensuring all planned user stories are fully coded without leftover TODO comments.

Can I use strict mode for pre-merge quality assurance checks?

Yes, you can use strict mode for pre-merge quality assurance to enforce comprehensive verification of task completion, code compilation, and test execution before merging implemented features.

What does a task completion audit check for in software engineering?

A task completion audit verifies that every task defined in a project plan has been fully implemented, checking for build status, test results, linting adherence, and consistency with project specifications.

Why does my code pass tests but fail the project specification review?

Code can pass tests but fail specification review due to configuration drift, leftover artifacts, or incomplete implementation of planned user stories that a comprehensive post-implementation audit detects.