Adlc Verify

ADLC Verify

Use this after implementation and before review or commit.

Process

1. Resolve effective ADLC paths from .adlc/config.yaml; use adlc resolve-config when the CLI is available.
2. Read the active plan, any cited interview spec, configured rules, architecture, and git diff.
3. Map each plan task and acceptance criterion to evidence, including interview acceptance criteria when present.
4. Run the strongest practical repo checks.
5. Look for leftover TODOs, env/config drift, skipped tests, stale docs, and plan-vs-code gaps.
6. Classify failures as autonomous-fixable or human-gated. Code, docs, tests, rules, and security gaps should suggest adlc-fix; human-gated blockers are limited to explicit decisions, credentials or external accounts, destructive or production operations, legal/security sign-off, scope or product ambiguity, or user-requested approval points.
7. Use strict mode before merge or release.

Output

End with a final parseable adlc-gate-result fenced block:

```adlc-gate-result { "schemaversion": 1, "gate": "verify", "status": "pass|warn|fail", "blocking": false, "blockers": [], "affectedfiles": [], "suggested_next": { "command": "adlc-review|adlc-fix|null", "reason": "Short reason." } }

Use `suggested_next.command: "adlc-fix"` for autonomous-fixable blockers. Use `null` only when a human-gated blocker prevents the next autonomous gate.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [davidvictor](https://github.com/davidvictor)
- **Source:** [davidvictor/adlc-skills](https://github.com/davidvictor/adlc-skills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.