Results for “task-verification”

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

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

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

Guides multi-step tasks by decomposing them into checkpoints, verifying results with concrete observations, and re-planning after surprises or failures.

Coordinates multiple AI agents working on a shared task list using Claude Code's native team tools, with task decomposition, staged execution, and verification.

Executes small ad-hoc tasks with GSD guarantees, spawning planner and executor agents, tracking tasks in .planning/quick/, and updating STATE.md. Supports composable flags for discussion, research, plan-checking, and verification.

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

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.

Use when about to claim work is complete, fixed, or passing, before committing, before reporting a task done, or before telling the evaluator the batch is ready. Requires running the verification command and reading its output in this turn before any success claim; evidence before assertions always.

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

Task Decomposition

Validate process JS files for correct SDK patterns, task definitions, syntax, and quality gate implementation.

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

Enforces running verification commands and confirming output before claiming work is complete, fixed, or passing, to prevent false success claims.

Executes commands, inspects git state, debugs CI or builds, makes narrow fixes, and reports exactly what changed and what was verified.

当用户已有确认过的开发任务清单（理想来自 split-task），要把它逐个落地成实现 + 测试 + 提交，并经验收确认真的做完时使用——如"执行任务、把 tasks 做掉、按任务清单开始编码、实现这些任务、推进开发"。不要用于：任务还没拆（先 split-task）、技术方案没定（先 make-design）、行为没钉死（先 write-spec）、想法还模糊（先 refine-idea）、只做单个改动的红绿闭环（那是 tdd）、只做一次代码审查（那是 review-changes）、单纯调试某个 bug、代码评审。

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

Executes terminal commands, inspects git state, debugs CI or builds, and makes narrow fixes with exact proof of what was executed and verified.

Validate built features through conversational UAT

Drives a PRD-based persistence loop that iterates on a task until all user stories pass and are reviewer-verified, with automatic retry and progress tracking.

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

Discovers and invokes agent skills by mapping tasks to development phases, with core operating behaviors for assumption surfacing, confusion management, and scope discipline.

Use this skill for browser verification, console/network errors, layout checks, user-flow QA, DevTools evidence. Trigger when the task involves qa work related to Browser Devtools Qa, production implementation, audits, debugging, strategy, or validation.

Orchestrate the full MoonSpec lifecycle from a preselected single-story feature request or active feature directory through specification, planning, TDD task generation, artifact alignment, implementation, and final verification. Use when the user asks for an end-to-end MoonSpec run and the input has already been routed to one independently testable story, or when Codex needs to coordinate `moonspec-specify`, `moonspec-plan`, `moonspec-tasks`, `moonspec-align`, `moonspec-implement`, and `moonspec-verify` without manual analyze/remediation prompts.

Write a 5-part mini spec (goal, constraints, acceptance criteria, verification, done gate) before starting any multi-step, externally-delivered, or risky task. Triggers when: a request has 3+ steps, touches external delivery, or is easy to declare done too early. NOT for: single lookups, one-line edits, routine acks, or simple factual answers.

Detects weak reverse engineering and tampering protections in mobile apps (Android/iOS). Trigger on: root detection bypass, jailbreak detection bypass, Frida detection, debugger detection, anti-debugging, ptrace, sysctl, emulator detection, code obfuscation absent, debug symbols present, get-task-allow, ProGuard disabled, R8 disabled, string encryption, integrity check, file tampering, repackaging, dynamic instrumentation, runtime hook, Magisk hide, Magisk, frida-server, objection bypass, signing verification, apk resign. Covers MASVS-RESILIENCE-1/2/3/4.