Verify completed implementation against the plan. Checks that all tasks were implemented, nothing was forgotten, code compiles, tests pass, and quality standards are met. Use after "/aif-implement" completes, or when user says "verify", "check work", "did we miss anything".
81%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Before mode routing or work, read existing files relative to the current project root in this order (reuse them if already loaded):
.ai-factory/skill-context/global-skill-context.md — all bundled skills..ai-factory/skill-context/build-skill-context.md — only fix, implement, plan, verify, improve..ai-factory/skill-context/aif-verify/SKILL.md — this skill.Missing files are skipped; an existing unreadable file stops dependent work with its path.
Precedence: individual > build (when applicable) > global > skill defaults; retain non-conflicting instructions and check all outputs against the effective rules.
These layers customize workflow; they do not replace the project's rules/architecture hierarchy or relax explicit requirements, ownership, scope, safety/privacy, validation, or approval boundaries. Report conflicts with those boundaries instead of overriding them.
global is a project-local layer, not home-directory configuration. Custom/extension skills do not automatically use it.
Verify that the completed implementation matches the plan, nothing was missed, and the code is production-ready.
This skill is optional — invoked after /aif-implement finishes all tasks, or manually at any time.
Apply this contract whenever the workflow asks the user to decide:
AskUserQuestion and Questions below describe the intended interaction, not a required tool name. Use only a question tool actually exposed and permitted in the current session/mode, with its advertised schema. Do not guess aliases, probe unavailable tools, or assume questionnaire exists. A frontmatter entry alone does not make a tool available.HANDOFF_MODE=1), do not prompt the user directly. Use declared defaults only for optional preferences within the authorized scope and report assumptions. If a required decision, approval, or material scope/behavior choice remains unresolved, stop dependent work and return the missing decision and options to the parent/caller using its existing blocked/failure contract. Never invent consent or select a new scope to avoid blocking.Resolve reference paths beside this installed entrypoint, including flat workflows. Read a reference in full only when its stated condition applies, before the dependent step; do not preload all references. If a selected reference is missing or unreadable, STOP before that step and report its path. The entrypoint dispatch and hard boundaries apply to every reference. Project skill-context overrides and managed extension injections retain their existing precedence. Keep managed aif-ext blocks in the entrypoint; never move them into references.
FIRST: Read .ai-factory/config.yaml if it exists to resolve:
paths.description, paths.architecture, paths.rules_file, paths.roadmap, paths.research, paths.plan, paths.plans, paths.fix_plan, paths.specs, paths.rules, and paths.archive; derive research_bundles_dir = <parent directory of paths.research>/research/strict | normal | lenient)git.enabled, git.base_branch, git.create_branchesrules.base + named rules.<area> entrieslanguage.ui for prompts, user-visible explanations, verification reports, context-gate summaries, issue remediation prompts, and next-step guidanceworkflow.plan_id_format (default: slug) — used by branch-based plan discovery in Step 0.2.
Active values: slug and sequential. Discovery treats root *.md files as
full plans except the resolved fast/fix paths, and direct child */index.md
files as ultra entrypoints only when they contain exactly one
<!-- aif:plan-mode:ultra -->. When
sequential, search both numbered shapes and choose the highest prefix.
timestamp and uuid are reserved values and currently behave like slug.
Treat any unknown value as slug.verify_mode priority:
--strict CLI flag → always use strictworkflow.verify_mode → use configured valuenormalIf config.yaml doesn't exist, use defaults:
.ai-factory/ for all artifacts.ai-factory/RESEARCH.mdnormalui_language: enworkflow.plan_id_format: slugResolved language value:
ui_language = language.ui || "en"All AskUserQuestion prompts, user-visible explanations, verification reports, context-gate summaries, issue remediation prompts, and next-step guidance MUST be written in ui_language.
Preserve machine-readable aif-gate-result JSON schema fields and enum values (pass, warn, fail) unchanged. Preserve WARN/ERROR gate labels, commands, paths, config keys, code identifiers, package names, API names, and raw command output unchanged.
references/CONTEXT-GATES-AND-OWNERSHIP.md first.references/GATE-RESULT-CONTRACT.md for the machine-readable quality gate summary.aif-commit/aif-review/aif-verify,Before selecting a plan or standalone verification target, read plan discovery. Scan configured active plan paths, preserve canonical branch stems and sequential IDs, and ignore unrelated directories. Ultra requires exactly one <!-- aif:plan-mode:ultra -->; missing plan context requires the existing standalone choice.
<!-- aif:plan-mode:ultra -->; ignore unrelated */index.md files.index.md. A missing/broken/escaping phase link is
a blocking plan-integrity failure because the committed specification is incomplete.Task N in index.md against exactly one matching
## Task N section in its linked phase file. Unmapped tasks, duplicate task
sections, and unlinked phase-*.md files are blocking plan-integrity failures.TaskList → get all tasks and their statuses.ai-factory/DESCRIPTION.md (use path from config) for project context (tech stack, conventions).ai-factory/ARCHITECTURE.md (use path from config) for dependency and boundary rules (if present)rules.api, rules.frontend).ai-factory/ROADMAP.md (use path from config) for milestone alignment checks (if present)## Original Request, treat it as useful original scope context. Use it to understand the user's starting intent, while the task list, committed ## Research Context, and ultra phase specifications remain the executable verification inputs.## Research Context, treat its embedded copy as the committed requirements snapshot. Parse the first Source: / Reference: line with canonical ^(?:Source|Reference):\s+\x60([^\x60]+)\x60\s+\( syntax; for older bare-path lines, fall back to ^(?:Source|Reference):\s+(.+?)\s+\(. Fall back to configured paths.research only when neither form identifies a usable path.research_bundles_dir, require its sibling INDEX.md to contain <!-- aif:research-mode:ultra --> exactly once and link that RESEARCH.md from ## Artifact Index; otherwise emit WARN [research-drift]. Sibling C4/ADR/dependency files remain rationale only.SHA256: is present, extract the current source text strictly between <!-- aif:active-summary:start --> and <!-- aif:active-summary:end -->, remove HTML comment blocks, preserve line order and leading whitespace, trim trailing spaces from every line, use LF endings, and end with one newline. Hash through stdin with shasum -a 256 or sha256sum; the digest is authoritative. Use Updated: only as a legacy fallback when SHA256: is absent. A missing/invalid source or revision mismatch emits WARN [research-drift]; verify against the embedded Research Context and do not expand scope unless the user explicitly requests a rebase/refinement. Skipping this drift check is a verification bug.WARN [research-drift] and
verify against the plan's embedded Research Context.Read .ai-factory/skill-context/aif-verify/SKILL.md — MANDATORY if the file exists.
This file contains project-specific rules accumulated by /aif-evolve from patches,
codebase conventions, and tech-stack analysis. These rules are tailored to the current project.
How to apply skill-context rules:
Enforcement: After generating any output artifact, verify it against all skill-context rules. If any rule is violated — fix the output before presenting it to the user.
# All files changed during this feature/plan
git diff --name-only <configured-base-branch>...HEAD
# Or if on the base branch / in no-git mode, check recent commits
git diff --name-only HEAD~$(number_of_tasks)..HEADIf git.enabled = false, skip branch diffing entirely and gather changed files from:
Store as CHANGED_FILES.
Before auditing implementation, read task completion and code quality checks. Verify every required task against real code, run applicable build/test/lint/dependency checks, and report skipped or failed checks honestly. Apply the plan's testing policy and strict-mode requirements; never treat missing evidence as a passing check.
Verify the full chain authoritative requirements → plan → implementation → verification evidence, not only plan-to-code agreement.
## Requirements Reconciliation, resolve citations to
the selected research source against the embedded ## Research Context; the
live research file remains drift-only unless the user explicitly rebases the
plan. Re-read other cited source passages. Otherwise use the Original Request,
committed Research Context, project rules, and authoritative sources they
explicitly reference.WARN [requirement-ambiguity] in normal or
lenient mode, and ERROR [requirement-ambiguity] in strict mode.ERROR [requirement-conflict] and blocks verification even
when the plan, code, and tests agree with one another.Respect the plan's testing setting. If tests were intentionally skipped, use static inspection plus the plan's runnable/manual verification evidence; report missing evidence as a warning in normal mode and a failure in strict mode.
Before evaluating code/configuration drift and context gates, read consistency checks and owner remediation. Apply the canonical ownership/gate contracts. Clear architecture/rule violations block; clear roadmap mismatch blocks in strict mode. Missing milestone linkage remains a warning even in strict mode. Context artifacts are read-only; route remediation to their owner commands.
Before rendering any result, read report format and follow-up procedures. Report task completion, code quality, requirement consistency, context gates, and unavailable evidence in ui_language. Unresolved blockers remain failures even when accepted or deferred; remediation requires the user's choice and owner commands.
Append exactly one final fenced aif-gate-result JSON block with "gate": "verify" and unchanged schema. Use pass only without warnings/blockers, warn for non-blocking limitations, and fail for blocking gaps. Keep blocking, blockers, affected_files, and suggested_next consistent with references/GATE-RESULT-CONTRACT.md. Nothing follows the final machine-readable block; any follow-up suggestions precede it.
When invoked with --strict:
/aif-verify --strictfeat/fix/perf is a warning even in strict modeStrict mode is recommended before merging to the configured base branch or creating a pull request.
Read report example only when a worked rendering is needed; use actual evidence rather than the example values.
Only when usage help is needed, read verification examples. Normal, strict, and standalone verification remain supported.
lee-to/ai-factory
eabdfe9
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.