aif-verify

Audit plan tasks against code, tests, and quality gates.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/mind-systems/mind_context --skill aif-verify-mind-systems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-verify
Source: https://github.com/mind-systems/mind_context/tree/main/.claude/skills/aif-verify
Command: npx skills add https://github.com/mind-systems/mind_context --skill aif-verify-mind-systems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify completed implementation matches the plan, ensuring no tasks are forgotten, code builds, tests pass, and quality standards are met.

Core Features & Use Cases

  • End-to-end plan-to-code audit that validates each task is implemented according to plan and meets acceptance criteria.
  • Automated checks against the repository state (build, tests, lint) with a clear PASS/FAIL report and suggested remediation.
  • Use Case: After finishing /aif-implement, run this skill to confirm every task is complete and aligned with project goals.

Quick Start

Run this verification after the implementation completes to confirm all tasks are fully implemented and meet quality standards.

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 matches the project plan?

To verify your code implementation matches the project plan, run an end-to-end plan-to-code audit that cross-checks code, tests, and quality gates. This reports complete, partial, or missing work and evaluates build, tests, lint, and dependencies to surface actionable issues before merging.

What is an automated plan audit for code review?

An automated plan audit for code review is a process that identifies and audits every task in your current plan to ensure complete implementation. It cross-checks repository state to confirm no tasks are forgotten and that quality standards are met.

How do I check repository state for build, tests, and lint issues before merging?

To check repository state for build, tests, and lint issues before merging, execute automated quality gate evaluations. This surfaces actionable issues with a clear PASS or FAIL report and suggested remediation based on the evaluated code and dependencies.

Can I confirm acceptance criteria are fully met after finishing implementation?

Yes, you can confirm acceptance criteria are fully met by validating each task implemented according to plan. This verification evaluates build, tests, lint, and dependencies to ensure everything is complete and aligned with project goals before merging.

What's the best way to surface partial or missing work in a repository?

The best way to surface partial or missing work in a repository is performing an end-to-end plan-to-code audit. It cross-checks code, tests, and dependencies against the current plan, providing a clear PASS or FAIL report with suggested remediation for any incomplete tasks.