aif-verify

# Verify — Post-Implementation Quality Check 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. --- ## Step 0: Load Context ### 0.0 Load config.yaml **FIRST:** Read `.ai-factory/config.yaml` if it exists to resolve: - **Paths:** `paths.description`, `paths.architecture`, `paths.rules_file`, `paths.roadmap`, `paths.plan`, `paths.plans`, `paths.fix_plan`, `paths.specs`, and `paths.rules` - **verify_mode:** default verification strictness (`strict` | `normal` | `lenient`) - **Git:** `git.enabled`, `git.base_branch`, `git.create_branches` - **Rules hierarchy:** the resolved RULES.md path + `rules.base` + named `rules.<area>` entries - **Workflow:** `workflow.plan_id_format` (default: `slug`) — used by branch-based plan discovery in Step 0.2. Active values: `slug` and `sequential`. When `sequential`, the resolver globs `<paths.plans>/[0-9]{4}_<branch_stem>.md` first and falls back to `<paths.plans>/<branch_stem>.md` only if no numbered match is found. `timestamp` and `uuid` are **reserved values** and currently behave like `slug`. Treat any unknown value as `slug`. **verify_mode priority:** 1. `--strict` CLI flag → always use `strict` 2. config.yaml `workflow.verify_mode` → use configured value 3. Default → `normal` If config.yaml doesn't exist, use defaults: - Paths: `.ai-factory/` for all artifact...