orch-confirm

Name: orch-confirm
Availability: InStock
Author: 180VRisLife

text goes here

Updated Aug 27, 2026

Search Tags:#automation #quality-assurance #e2e-testing #verify #cross-check #requirements-traceability #spec-completeness

Ready to run

npx skills add https://github.com/180VRisLife/.claude --skill orch-confirm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: orch-confirm
Source: https://github.com/180VRisLife/.claude/tree/main/skills/orc-confirm
Command: npx skills add https://github.com/180VRisLife/.claude --skill orch-confirm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Confirm spec completeness by cross-checking requirements, brainstorms, and plans against implemented features to prevent gaps between design and delivery.

Core Features & Use Cases

Parallel checks compare implementation against spec/brainstorm/plan to identify missing mappings
E2E coverage assessment maps acceptance criteria to existing tests and reports gaps
Blocking verify step validates agent claims before proceeding; non-blocking reporting surfaces gaps

Quick Start

Run the orch-confirm skill to assess spec completeness and report coverage gaps.

Frequently Asked Questions about orch-confirm

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

FAQPage Schema

How do I verify spec completeness and cross-check requirements against implemented features?▼

Spec completeness is verified by cross-checking formal requirements, brainstorms, and plans against implemented features to identify missing mappings. This process catches gaps between design and delivery before deployment.

What is the best way to assess end-to-end coverage for acceptance criteria?▼

End-to-end coverage assessment maps acceptance criteria to existing tests to report gaps. It evaluates whether your test suite fully covers the specified feature requirements.

How does a blocking verify step validate agent claims before proceeding?▼

A blocking verify step validates agent claims by running parallel checks against spec items before allowing progression. Non-blocking reporting simultaneously surfaces discovered coverage gaps without halting execution.

Do I need a formal spec and test suite to use automated requirements traceability?▼

Automated requirements traceability requires a project with a formal spec and test suite. The verification process performs parallel checks and aggregated coverage summaries against these existing artifacts.

What are the limitations of using blocking verification for spec compliance?▼

Blocking verification for spec compliance applies guardrails to agent results but is limited to projects with formal specs. Non-blocking reporting must be used separately to surface gaps without interrupting workflows.