aif-verify

Verifies completed implementation against project plan via build, test, lint checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures that implemented code accurately reflects the project plan, is free of errors, and meets quality standards, preventing regressions and missed requirements.

Core Features & Use Cases

  • Task Audit: Verifies each task from the plan has been fully implemented.
  • Code Quality Check: Compiles code, runs tests, and checks for linting errors.
  • Consistency Checks: Identifies drift between the plan and the code, and flags leftover artifacts.
  • Use Case: After implementing a new feature, run this Skill to automatically confirm all acceptance criteria are met, the code builds successfully, tests pass, and no TODOs remain before merging.

Quick Start

Run this skill to verify the completed implementation against the project 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 my code implementation against a project plan?

Verify code implementation against a project plan by running an audit that checks task completion, compiles code, runs tests, and checks linting to ensure all requirements are fully met without regressions.

What does plan adherence verification check for in a completed feature?

Plan adherence verification checks for consistency between the project plan and code, identifies drift, flags leftover artifacts, and ensures no TODOs remain before merging a completed feature.

How do I check code quality and task completion before merging?

Check code quality and task completion before merging by running automated build, test, and lint checks to confirm acceptance criteria are met and code compiles successfully without errors.

Can I use strict verification mode to enforce plan adherence?

Yes, you can use strict verification mode to enforce plan adherence, which ensures all tasks are fully implemented and meets quality standards by analyzing task completion and consistency between plan and code.

What is the best way to audit code for leftover artifacts and plan drift?

The best way to audit code for leftover artifacts and plan drift is to perform consistency checks that compare implemented code directly against the project plan to identify any missing requirements or unremoved TODOs.

Why does my code pass tests but fail plan adherence checks?

Code can pass tests but fail plan adherence checks when there is drift between the plan and the code, tasks are not fully implemented, or leftover artifacts remain that violate quality standards.