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
Decision gist · record as of 2026-06-14
verify audits feature proposals and dev docs for completeness, catching gaps in requirements, acceptance criteria, and specification before approval gates. 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.
Use it when
- verify scans dev documents and feature proposals for incomplete sections, TODO markers, stub text, and gaps in acceptance criteria.
- Yes.
Verify before relying
Read SKILL.md below before installing (6 files). Open directory: indexed for reading, not audited.
Install
olehsvyrydov/AI-development-team/verify · repository language: Shell
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently 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)
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
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Audit feature proposals and dev docs for completeness before approval”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
doc-bdd translates EARS requirements into Layer 4 acceptance scenarios using structured YAML (not Gherkin), each with Given-When-Then phases, element-level trace links to upstream EARS, and forward mapping to SPEC sections. Use this after EARS is complete and before ADR/SPEC authoring; for batch generation across multiple documents, the autopilot skill handles orchestration.
doc-tdd generates Layer 7 TDD artifacts that translate component contracts into concrete test cases with quality thresholds. It maps BDD scenarios to unit, integration, functional, and end-to-end tests, establishes coverage targets per type, and sequences the Red-Green-Refactor workflow before implementation begins.
doc-adr captures a single architectural decision using the Context-Decision-Consequences pattern, positioned as Layer 5 in the specification-driven development flow. It records the rationale, chosen approach, evaluated alternatives, and accepted trade-offs for decisions that bridge container and component design.
Workflow Audit systematically reviews `.github/workflows/*.yml` files against security hardening, action version currency, and reliability standards. It discovers all workflow files, validates YAML syntax, runs a comprehensive checklist covering permissions, script injection, timeouts, and cross-workflow consistency, then reports findings sorted by severity with concrete fixes for each issue.
vc-generate-spec turns research findings and user intent into a reviewable requirements document written for stakeholders, not engineers. It captures what users want and why before any implementation approach is chosen, serving as the authoritative bridge between discovery and planning. The skill enforces structured sections—from user stories through acceptance criteria—ensuring specs remain focused on observable outcomes and user-facing behavior.
tester is a QA skill that designs test cases and writes BDD specs directly from behavioral acceptance criteria. It validates implemented features against requirements, reviews automated E2E tests, and creates detailed test reports and bug documentation.
More skills update-deps (MIT) · e2e-tester (MIT)