qa-verifylisted

Ask the reviewer to QA the output of a completed execution against the original request — did the work actually meet the spec, or are there ignored constraints, off-by-one errors, hallucinated fields, or silent partial successes. Use when the user says "did this actually do what I asked," "verify my work with the reviewer," "QA check this," "sanity-check the output," "did the execution meet the spec," "did we actually complete the task," or "validate the result." Also offer this proactively when the active primary has just finished a complex multi-step execution (data transformation, large refactor, batched file edits, multi-API workflow, deploy script) and is about to report success — a QA pass with caller-verified independence before claim-of-completion catches the silent-success-with-missing-constraint failure mode that visual inspection often misses.
sumitake/agent-collab · ★ 0 · Data & Documents · score 63

Install: claude install-skill sumitake/agent-collab

## Unified runtime invocation Resolve the **plugin root** from this loaded file: `SKILL.md` is at `<plugin-root>/skills/<skill-name>/SKILL.md`. Invoke only `python3 "<plugin-root>/coordinator.py"` and send one bounded JSON routing request on EOF-delimited stdin, without a PTY. Use the Python invocation example in the **Routing request** section in `<plugin-root>/README.md` and the co-packaged manifest's signed `wire_contract`; never invent fields or provider actions. Supply one caller-defined work unit per independently useful deliverable, with this skill's logical action and a bounded opaque payload. Use `depends_on` only for actual dependencies. Honor an operator-named provider with `explicit_target`. For an authorized independent review or governance task without an operator-named provider, also use that field to bind the caller-verified distinct reviewer selected by the caller or designated by the workflow. Carry the same target into planning and live dispatch; verify returned native lineage before accepting independence. Otherwise use normal untargeted routing. Choose quality and effort for the workload; include context/output token estimates when known. Read the current manifest digest and actual cwd device/inode; do not copy example values. The runtime owns its timeout; do not wrap it in a shorter fixed timeout. Repository identity, source-head verification, disposable copies, patch capture, and cleanup remain caller-owned where applicable. The shim runs standalone fr