manifold-m5-verify

Compare implementation, tests, docs, and operations against constraints to generate a verification matrix.

8|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/dhanesh/manifold --skill manifold-m5-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manifold-m5-verify
Source: https://github.com/dhanesh/manifold/tree/main/install/agents/codex/skills/manifold-m5-verify
Command: npx skills add https://github.com/dhanesh/manifold --skill manifold-m5-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates and communicates verification status by verifying ALL artifacts against ALL constraints, producing a comprehensive verification matrix that highlights coverage gaps and required actions.

Core Features & Use Cases

  • End-to-end constraint verification across code, tests, docs, and operations.
  • Generates a verification matrix with statuses (SATISFIED, PARTIAL, MISSING) and gap details.
  • Enforces explicit user invocation for phase transitions and supports evidence-based checks.

Quick Start

Run /m5-verify <feature-name> to generate the verification matrix and identify gaps.

Frequently Asked Questions about manifold-m5-verify

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

FAQPage Schema
How do I verify constraints across code, tests, docs, and deployment configurations?

Constraint verification compares implementation, tests, docs, and operations against defined constraints to identify coverage gaps. It generates a verification matrix with statuses like SATISFIED, PARTIAL, and MISSING to highlight required actions across all artifacts.

What is a verification matrix and how does it surface coverage gaps?

A verification matrix tracks artifact coverage by mapping all constraints against all artifacts. It surfaces gaps by assigning statuses such as SATISFIED, PARTIAL, or MISSING, providing actionable details for incomplete or missing evidence across codebases and operations.

How do I generate a verification matrix for a specific feature?

Generate a verification matrix by explicitly invoking the command against a feature name. This triggers an end-to-end verification workflow that compares all artifacts against defined constraints and outputs the matrix with detailed coverage gaps.

Can I use this for end-to-end verification across codebases and deployment configurations?

Yes, end-to-end verification applies to codebases, tests, docs, and deployment configurations. It coordinates verification status across all these artifacts to ensure constraints are met and to enforce evidence-based checks during phase transitions.

What's the best way to track missing evidence in implementation and operations artifacts?

Tracking missing evidence requires verifying all artifacts against defined constraints to produce a comprehensive matrix. This approach highlights MISSING and PARTIAL statuses, detailing exactly where coverage gaps exist and what actions are required to resolve them.