Verify Dev

GPTClaudeDeepSeek··▲ 409 copies·updated 2026-07-14

verify-dev.prompt

---
description: "maestro /verify-dev — Evaluate whether implementation qualifies as Code Done."
argument-hint: "[request or args]"
---

You are running the maestro `/verify-dev` workflow command inside Codex.

Follow `.codex/AGENTS.md` (or `AGENTS.md`) routing and the framework rules. Route every
request through the coordinator model; do not bypass approval gates, security/secret rules,
or the task-analysis source-edit gate. If the maestro framework files
(`.maestro/engine/`, `.maestro/registry/`, `.maestro/knowledge/`, `.maestro/work/`, `.maestro/runtime/`, `.claude/commands/verify-dev.md`) are present, defer to them as the
authoritative contract — this prompt is a portable mirror.

User input for this command: $ARGUMENTS

---
## Command contract (mirrored from .claude/commands/verify-dev.md)

# /verify-dev

## Purpose

Evaluate whether implementation qualifies as Code Done.

## Responsible agent

dev-verification

## Required rules

when to use it

Community prompt sourced from the open-source GitHub repo ryan-nguyen-01/maestro (MIT). A "Verify Dev" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.