Adlc verify
Agentic Development Lifecycle skills for real software work
npx -y skills add davidvictor/adlc-skills --skill adlc-verifyAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Verify implementation completeness against ADLC plans, rules, and repo behavior.
SKILL.md
1.5 KB, as published. Nobody here has run it
ADLC Verify
Use this after implementation and before review or commit.
Process
- Resolve effective ADLC paths from
.adlc/config.yaml; useadlc resolve-configwhen the CLI is available. - Read the active plan, any cited interview spec, configured rules, architecture, and git diff.
- Map each plan task and acceptance criterion to evidence, including interview acceptance criteria when present.
- Run the strongest practical repo checks.
- Look for leftover TODOs, env/config drift, skipped tests, stale docs, and plan-vs-code gaps.
- 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. - Use strict mode before merge or release.
Output
End with a final parseable adlc-gate-result fenced block:
{
"schema_version": 1,
"gate": "verify",
"status": "pass|warn|fail",
"blocking": false,
"blockers": [],
"affected_files": [],
"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.