aif-verify

Compare implemented work against a plan and generate a structured verification report.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verification ensures that an implemented plan matches the planned tasks, validating completeness, build success, tests, and quality standards.

Core Features & Use Cases

  • End-to-end plan alignment: compare implemented work against the plan and surface drift or gaps.
  • Quality gate: run builds, tests, lint, and static analysis to guarantee production readiness.
  • Reporting: generate a structured verification report with actionable remediation notes.

Quick Start

Run the verification after completing an implementation to confirm completeness, build success, tests passing, and quality conformance.

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 implementation matches the original plan and check for gaps?

End-to-end verification compares implemented work against the plan to surface drift or gaps. It assesses overall completion by verifying all tasks are fully satisfied and returning a structured report tagging issues for remediation.

What is the best way to run build, test, and quality checks for production readiness?

Apply build, test, and quality checks to ensure code compiles, tests pass, and standards are met. This quality gate runs builds, tests, lint, and static analysis to guarantee production readiness across the project.

How do I generate a structured verification report after completing a software implementation?

Generate a structured verification report by running end-to-end checks after completing an implementation. The report highlights any gaps, drift, or dependencies detected and provides actionable remediation notes.

Can I use automated verification to detect plan drift in my software project?

Automated verification detects plan drift by comparing implemented work against the original plan. It surfaces gaps and dependencies, ensuring overall completion is assessed and all tasks are fully satisfied.

When do I need end-to-end verification for my implementation?

End-to-end verification is needed after completing an implementation to confirm completeness, build success, tests passing, and quality conformance. It ensures the implemented plan matches planned tasks and validates production readiness.

Does aif-verify work without external dependencies for build and test automation?

aif-verify operates without external dependencies to apply build, test, and quality checks. It compares implemented work against the plan and returns a structured verification report highlighting gaps and remediation notes.