verify
verify is a quality assurance auditor that gates feature work at three checkpoints: proposal readiness, dev doc completeness, and implementation verification. It searches for placeholder content, traceability gaps, missing acceptance criteria, and specification drift, then either passes the gate or blocks with exact findings. Designed to be adversarial—assuming work is incomplete until proven otherwise.
verify audits feature proposals and dev docs for completeness, catching gaps in requirements, acceptance criteria, and specification before approval gates.
AI-generated summary based on this skill's SKILL.md
Install
olehsvyrydov/AI-development-team/verify · repository language: Shell
git clone https://github.com/olehsvyrydov/AI-development-team
cp -r AI-development-team/claude/skills/quality/verify ~/.claude/skills/verifynpx skillfed install olehsvyrydov/AI-development-team/verifyFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What does verify do as a QA auditor for feature proposals and code?
verify is a quality assurance auditor that gates feature work at three checkpoints: proposal readiness, dev doc completeness, and implementation verification. It searches for placeholder content, traceability gaps, missing acceptance criteria, and specification drift, then either passes the gate or blocks with exact findings. Designed to be adversarial—assuming work is incomplete until proven otherwise.
How does verify detect placeholder content in specifications?
verify scans dev documents and feature proposals for incomplete sections, TODO markers, stub text, and gaps in acceptance criteria. It flags inconsistencies between specification language and actual implementation, then reports exact locations and types of placeholder content found so teams can address them before approval.
Can verify check traceability between requirements and tests?
Yes. verify builds traceability matrices linking goals through scenarios to test cases, ensuring every acceptance criterion has corresponding test coverage. It detects missing or orphaned tests and specification drift—cases where code no longer matches the original requirements—and reports gaps in the chain of evidence.
How does verify verify code matches spec and all tests pass?
verify compares implementation against specification and acceptance criteria, confirming test suites pass and coverage is complete. It acts as an adversarial reviewer, assuming work is incomplete until proven otherwise, and blocks shipping if tests fail, criteria are unmet, or implementation deviates from approved spec.
What gates does verify enforce in the approval workflow?
verify enforces three workflow gates: proposal readiness (completeness and clarity), dev doc validation (no placeholders, full traceability), and implementation verification (code matches spec, all tests pass). It blocks incomplete work from shipping and provides exact findings so teams know what to fix before resubmission.
Is verify open source and what license does it use?
Yes, verify is open source under the MIT license, making it freely available for commercial and private use with minimal restrictions.
SKILL.md
rendered from the published skill — quoted content, verbatim
Verification & Completion Auditor
Context
You are a Quality Assurance Auditor — meticulous, skeptical, adversarial, and thorough. You assume everything is incomplete until you personally verify it. You do NOT try to be helpful or agreeable — you find gaps. You are the agent that prevents bad work from shipping.
Gate Check (workflow)
Consult the workflow-engine skill first — it decides which gates this ticket requires. verify is the auditor for two hard gates, and sets each only from its matching checkpoint:
APPROVAL_GATE(hard) — from/verify proposal/devdoc, before implementation. Confirm the ticket is ready: behavioral AC present, no placeholder content, and the hard
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 6 files
claude/skills/quality/verify/SKILL.md
claude/skills/quality/verify/references/checkpoint-1-proposal.md
claude/skills/quality/verify/references/checkpoint-2-devdoc.md
claude/skills/quality/verify/references/checkpoint-3-implementation.md
claude/skills/quality/verify/references/placeholder-patterns.md
claude/skills/quality/verify/references/traceability-template.md