verify

Name: verify
Availability: InStock
Author: doodledood

Coordinate parallel automated verifiers to validate Manifest criteria.

70|9|Updated Jan 27, 2026

Search Tags:#automation #validation #quality #manifest #verify #invariants #acceptance-criteria

Ready to run

npx skills add https://github.com/doodledood/manifest-dev --skill verify-doodledood

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/doodledood/manifest-dev/tree/main/claude-plugins/manifest-dev/skills/verify
Command: npx skills add https://github.com/doodledood/manifest-dev --skill verify-doodledood

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manifest verification is essential to guarantee that all criteria are checked and the intended invariants are enforced. This Skill coordinates automated verifiers to run in parallel, ensuring comprehensive, deterministic validation of a Manifest during the /do workflow.

Core Features & Use Cases

Parallel verification orchestration: Launches all Global Invariant and Acceptance Criteria checks in a single coordination step.
Clear, grouped results: Reports failures by type (globals first, then deliverables) with location, expected vs actual, and fix hints.
Robust failure handling: Handles global invariant failures as task-level errors and surfaces actionable feedback for remediation.

Quick Start

Invoke /verify with the manifest and log paths to start a full verification cycle.

Frequently Asked Questions about verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate manifest validation for global invariants and acceptance criteria?▼

Manifest validation is automated by coordinating multiple verifiers in parallel to check all global invariants and acceptance criteria. This orchestration runs shell commands, code pattern checks, and external research in a single step, providing explicit success or failure signals.

What is the best way to run parallel verification checks across multiple deliverables?▼

Parallel verification checks across deliverables are executed by launching all global invariant and acceptance criteria tests in a single orchestration step. This approach groups failures by type, reporting location, expected versus actual results, and fix hints for immediate remediation.

How does parallel verification handle global invariant failures during manifest checks?▼

Global invariant failures are handled as task-level errors during manifest checks. The verification process halts to surface actionable feedback, providing specific location details, expected versus actual values, and remediation hints to address the failed invariants.

Can I use automated checks for shell commands and code patterns in a single verification step?▼

Automated checks for shell commands and code patterns can be run in a single verification step. The orchestration coordinates these checks alongside external research and manual escalation, ensuring comprehensive validation of all manifest criteria.

When do I need to use a manifest verification orchestration workflow?▼

Manifest verification orchestration is needed when a manifest contains global invariants and acceptance criteria across deliverables. It ensures deterministic, comprehensive validation by coordinating parallel checks, replacing manual review with automated shell commands and code pattern matching.

Why does my manifest verification report grouped failures by globals and deliverables?▼

Manifest verification reports grouped failures by globals and deliverables to prioritize remediation. Global invariant failures are reported first as task-level errors, followed by deliverable-specific acceptance criteria failures, each with location, expected versus actual data, and fix hints.