Verify adoption criterion A8 (Planning Integration) in the current project. Reports fulfillment level 0–3.
QA agent: executes Epic AC (Acceptance Criteria) verification against an AC ticket or Epic. Runs all AC steps, classifies each as PASS/FAIL/MANUAL_REQUIRED/UNCERTAIN, and presents…
After a Sui build session, check what was built against .suiperpower/intent.md and flag drift. Use when the user wants to verify their build matches intent.
Lieferergebnisse validieren und Belegnachweise aufbauen, wenn Arbeit zwischen Agenten uebergeben wird.
Use FIRST when verifying any UI state on an Android emulator or device — checking that elements rendered, text appears, state is correct, or a fix landed.
Use when verifying an Android UI state requires a real screenshot — WebView content, animations, visual fidelity (color, font, image content, alignment), or finding an element by…
현재 접근 방식이 최신/올바른지 인터넷에서 검증. 구현 전 기술 선택이나 방법론 확인할 때 사용
Verify archive integrity with self-verifying SHA-256 checksums, generate VERIFY.md, and optionally create W3C PROV provenance
Round-trip fidelity test for a generated artifact. Generates the artifact, re-ingests it into a throwaway scratch vault, diffs against the originals, and reports a fidelity score…
Use when about to claim work is complete, fixed, or passing, before committing changes - requires running verification commands and confirming output before making any success…
Validate artifact against schema, acceptance criteria, and downstream readiness BEFORE marking a task complete.
Verify readiness criterion C2.1 (Setup Automation) in the current project. Reports fulfillment level 0–3.
Verify readiness criterion C4.1 (Requirements Access) in the current project. Reports fulfillment level 0–3.
Verify readiness criterion C5.1 (Runnability) in the current project. Reports fulfillment level 0–2.
Verify readiness criterion C5.2 (Unit Test Coverage) in the current project. Reports fulfillment level 0–3.
Verify readiness criterion C5.3 (Integration and E2E Coverage) in the current project. Reports fulfillment level 0–3.
Verify readiness criterion C6.1 (Static Analysis) in the current project. Reports fulfillment level 0–3.
Verify readiness criterion C7.1 (Test Isolation) in the current project. Reports fulfillment level 0–2.
Verify readiness criterion C8.1 (CI/CD Automation) in the current project. Reports fulfillment level 0–3.
Verify readiness criterion C8.2 (Observability) in the current project. Reports fulfillment level 0–3.
Use when claiming 'done', suggesting a commit, push, or PR — runs the evidence gate so completion claims come from fresh output in this message, not memory or earlier runs.
Record proof that a task works by capturing commands, pass/fail results, changed files, artifacts, risks, and the next safest task.
Use to audit the real implementation of a TODO ticket with senior code review rigor (backend/frontend/DB consistency, edge cases, dead code) and create correction tickets.
Verifica end-to-end di un endpoint REST della Todo API. Usa quando l'utente chiede di "testare", "verificare", "smoke test" o "provare" un endpoint Express del backend.
Verify changes using runtime observation instead of diff-reading or unit tests. Includes autoagent's failure taxonomy for diagnosing what went wrong when verification fails.
Uses Goss to express the expected state of a machine or container, then validates that reality still matches the contract.
Use before claiming a feature is done, before merging, and before running any finishing / release skill.
Spawn multiple children to verify implementation meets requirements from different angles
Interpret the output of `specgraph verify` and explain what each status means and what to do next.
Pattern for verifying your output matches required schema before completing. Use before writing final output to ensure validity.
Query OSS Rebuild attestations and rebuild metadata so an agent can verify whether a published package artifact matches a reproducible upstream rebuild.
Goal-backward phase verification + UAT conversational verification, consolidated. Use when checking phase achieves promised goal before milestone.
Verifies that features listed in a README (or similar documentation) are actually
Audit-only verification of manuscript references against PubMed and CrossRef. Detects fabricated or mismatched citations and writes qc/reference_audit.json.
For solution checking: independent verification that result is correct, separate from how it was computed.
End-to-end system health verification. Checks all containers, ports, endpoints, and pipelines (logging, email, auth, socket, worker).
Verify that a task's implementation meets its requirements and has adequate test coverage (happy path, sad path, edge cases). Use before /complete-task.
Create a verifying agent to check whether a working agent's task was completed successfully. Use after a working agent finishes (transitions to "done", "stopped", "waiting", or…
Use when the user wants to cross-check a CDC requirement with the TODO.md and the real code to detect gaps (false TODO, missing TODO, partial, KO).
For test co-location: tests in same file as code, run with main, tests as documentation and examples.
Drive a real browser against AI Atelie's running dev server to verify a change works, and capture screenshots + video as PR evidence.
Use when a worker has written its report and exit-file. This is the Critic step — re-run tests yourself, trust nothing.
Use when verifying any feature in a browser-based interactive runtime (three.js, canvas, WebGL, DOM game) where behavior depends on game state, render output, or user input — and…
Visually verifies Compose UI components by rendering @Composable/@Preview functions to images from the project's JVM runtime; STRONGLY PREFERRED for rapid UI iteration and visual…
Look up VeriGlow Agent Map for any website URL to discover its data functions, internal APIs, browser automation recipes, and agent reliability reports.
Expert-level Verilog and SystemVerilog knowledge following IEEE 1800 standards. Generates synthesizable RTL code with proper coding styles and constructs.
Verimi integration. Manage data, records, and automate workflows. Use when the user wants to interact with Verimi data.
Verimor API üzerinden SMS gönder, bakiye sorgula, rapor al, başlıkları listele ve kara liste yönet.
Veriphone integration. Manage data, records, and automate workflows. Use when the user wants to interact with Veriphone data.
Automate Veriphone tasks via Rube MCP (Composio). Always search tools first for current schemas.
Veritone integration. Manage data, records, and automate workflows. Use when the user wants to interact with Veritone data.
Unterstützt bei der rechtlichen Aufarbeitung von Verkehrsunfällen: Haftungsgrundlagen nach StVG und BGB, Direktanspruch nach § 115 VVG, Quotenbildung, vollständige…
Provides guidance for training LLMs with reinforcement learning using verl (Volcano Engine RL). Use when implementing RLHF, GRPO, PPO, or other RL algorithms for LLM post-training…
Verletzungs-Triage bei gewerblichen Schutzrechten und Wettbewerbsrecht: Marke (§ 14 MarkenG), Patent (§ 9 PatG), Urheberrecht (§ 97 UrhG), Wettbewerb (§ 8 UWG).
Unterstützt bei Erstellung, Prüfung und Aktualisierung des Vermögensverzeichnisses des Betreuers nach §§ 1835, 1839 BGB sowie der jährlichen Rechnungslegung nach § 1865 BGB.
Vero integration. Manage data, records, and automate workflows. Use when the user wants to interact with Vero data.
Automate Vero tasks via Rube MCP (Composio). Always search tools first for current schemas.
Redesigne eine blockweise Themen-Sequenz in einen verschränkten Plan mit gemischter Übung über verwandte Themen.
Print the currently-installed airc version (short git SHA, branch, commit subject, install dir). Use this to verify everyone in a mesh is on the same build.
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, npm publishing…