aif-verify

Verify completed software implementations against project plans before merge.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/marinkobabic/dario-shop --skill aif-verify-marinkobabic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-verify
Source: https://github.com/marinkobabic/dario-shop/tree/main/.claude/skills/aif-verify
Command: npx skills add https://github.com/marinkobabic/dario-shop --skill aif-verify-marinkobabic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

After implementing a feature or plan, it is common to miss requirements, leave incomplete code, or introduce quality issues that only surface later. This Skill automates the verification process to ensure every task was fully implemented, the code compiles, tests pass, and quality standards are met before merging.

Core Features & Use Cases

  • Task Completion Audit: Scans the implementation against the original plan to confirm all requirements were met, flagging partial or missing work with clear status indicators.
  • Code Quality Checks: Detects the project build system and runs compilation, test, and lint commands to catch errors and style violations in changed files.
  • Consistency Validation: Identifies plan-to-code drift, leftover debug artifacts, undocumented environment variables, and architecture boundary violations.
  • Use Case: After running /aif-implement to build a new authentication system, use this Skill to verify that all planned endpoints exist, password reset email logic is complete, and no TODO comments remain.

Quick Start

Use the aif-verify skill to check the current implementation against the active plan and generate a comprehensive quality report.

Frequently Asked Questions about aif-verify

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

FAQPage Schema
How do I verify implementation completeness against a project plan?

Build validation checks compilation, tests, and linting by detecting the project build system and running the appropriate commands. It catches errors and style violations specifically in changed files, ensuring code quality standards are met before merge.

How do I check for plan-to-code drift after feature implementation?

To run post-development code audits, you need access to git history, build tools, and test runners. The process also requires project context files including DESCRIPTION.md, ARCHITECTURE.md, and RULES.md to validate architectural compliance and task coverage.

What is the best way to ensure production readiness before merging code?

Code audit verification requires project context files including DESCRIPTION.md, ARCHITECTURE.md, and RULES.md, along with access to git history, build tools, and test runners. These provide the necessary plan details and architectural rules to validate implementation completeness.

How do I detect leftover debug artifacts and architecture violations in changed files?

Code audit verification requires project context files including DESCRIPTION.md, ARCHITECTURE.md, and RULES.md, along with access to git history, build tools, and test runners to validate task completion, test coverage, and architectural compliance comprehensively.