Results for “task-verification”

Self-referential loop until task completion with architect verification

Provides a repeatable, auditable workflow for large coding tasks by initializing repo-local task artifacts, installing subagent templates, and running a spec-freeze → build → evidence → verify → fix loop with fresh-session verification.

Self-referential loop until task completion with architect verification

Self-referential loop until task completion with configurable verification reviewer

Automate Postgrid Verify address verification tasks through Composio's toolkit via Rube MCP.

Structured task planning with clear breakdowns, dependencies, and verification criteria.

Automate Kickbox email verification and validation tasks through Composio's toolkit via Rube MCP.

Automate email verification and validation tasks using the Emailable API through Composio's Rube MCP integration.

Automate Identitycheck identity verification tasks through Composio's toolkit via Rube MCP, with dynamic tool discovery and connection management.

Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).

Automate Clearout email verification and data cleaning tasks through the Rube MCP interface using Composio's Clearout toolkit.

Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).

Automates email list verification tasks through Composio's Emaillistverify toolkit via Rube MCP, including tool discovery, connection management, and execution.

Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.

Verify that a change really works before you claim completion

Verify whether an online bounty, freelance task, agent marketplace job, hackathon prize, or crypto work offer is actually open, accessible, and credibly funded. Use when evaluating task URLs, payout claims, escrow or treasury evidence, eligibility restrictions, payment history, expected value, or whether a claimed amount may be counted as real revenue.

Persists through implement-verify-fix loops until a task is fully completed and verified, overriding default stopping behavior.

Verification-before-completion discipline ensuring all success criteria are met, tests pass, and reviews complete before declaring work done.

Verify the accuracy of claims and statements by extracting individual assertions, identifying authoritative sources, cross-referencing evidence, and assigning confidence-scored verdicts. Use when the user requests fact checking or provides relevant inputs for this workflow.

Verify code changes work by running them. Proves through execution, not just inspection.

Verify project behavior anchors — compilation, tests, and interaction checks after autonomous runs. NOT the Claude Code built-in /verify (which runs the app to observe a single change working) — this one walks the CLAUDE.md "Features (Behavior Anchors)" list.

Verify implemented work meets acceptance criteria — run tests, check PHPCS, validate Blade output, lando phpunit, lando phpcs, lando yarn test, Playwright tests, accessibility check, post-implementation verification, done criteria validation, checklist review, verification phase

Automate Mailcheck email verification tasks through Composio's Mailcheck toolkit via Rube MCP, with tool discovery and connection management.

Verifica la reproducibilidad y consistencia de un análisis de datos antes de presentarlo, validando contra la pregunta original y documentando limitaciones.

Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

Enforces a verification gate before any completion claim, requiring fresh command output as evidence.

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.

Testing Verification Skill