aif-verify

Audit implemented tasks against the plan for completeness and quality.

2|Updated Sep 13, 2022

Search Tags:#implementation #verification #audit #build #quality #plan

Ready to run

npx skills add https://github.com/horizontalsystems/solana-kit-ios --skill aif-verify-horizontalsystems

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aif-verify
Source: https://github.com/horizontalsystems/solana-kit-ios/tree/main/.claude/skills/aif-verify
Command: npx skills add https://github.com/horizontalsystems/solana-kit-ios --skill aif-verify-horizontalsystems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify completed implementation against the plan, ensuring no tasks are missed, code compiles, tests pass, and quality standards are met.

Core Features & Use Cases

Plan-to-implementation validation: compares plan TaskList with actual code changes and outcomes.
Build, test, and quality checks: ensures code compiles, tests pass, and linting is clean.
Gap reporting and guidance: surfaces missing tasks, mismatches, and remediation suggestions.

Quick Start

Run the aif-verify after completing a plan with /aif-implement to confirm all tasks are complete and compliant.

Frequently Asked Questions about aif-verify

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

FAQPage Schema

How do I verify implemented code against a project plan?▼

To verify implemented code against a project plan, you audit completed tasks to ensure plan alignment, build health, passing tests, and documentation consistency. This validates completeness and correctness across multi-task codebases.

What is plan-to-implementation validation for multi-task codebases?▼

Plan-to-implementation validation compares the plan TaskList with actual code changes and outcomes. It surfaces missing tasks, mismatches, and remediation suggestions to ensure no requirements are missed during codebase execution.

How do I check build health, test results, and lint quality after implementation?▼

To check build health, test results, and lint quality after implementation, run end-to-end quality checks. This ensures code compiles, tests pass, and linting is clean across the implemented tasks.

Can I audit completed tasks for changelog and dependency consistency?▼

Yes, you can audit completed tasks to satisfy requirements for dependency validation and changelog synchronization. This ensures documentation consistency and verifies that all implemented changes match the original plan.

When should I run quality checks on my implemented plan?▼

You should run quality checks immediately after completing a plan with an implementation tool or upon user request. This confirms all tasks are complete, compliant, and free of gaps before finalizing changes.

What is the best way to find missing tasks in a codebase implementation?▼

The best way to find missing tasks is gap reporting, which compares implemented code against the original plan. It surfaces mismatches and provides remediation suggestions to resolve incomplete requirements.