proof

Validate design, requirements, and runbook artifacts item-by-item with lifecycle tracking.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/ddaanet/edify-plugin --skill proof-ddaanet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: proof
Source: https://github.com/ddaanet/edify-plugin/tree/main/skills/proof
Command: npx skills add https://github.com/ddaanet/edify-plugin --skill proof-ddaanet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This tool enables structured artifact validation during design, runbook, and requirements review stages by enforcing a repeatable, item-by-item decision protocol.

Core Features & Use Cases

  • Item-by-item verdicts: Move beyond single-turn checks by collecting per-item approvals, revisions, kills, or skips.
  • Batch-apply and traceability: Apply all changes in one atomic pass and record lifecycle updates for auditability.
  • Hosting-skill integration: Seamlessly integrate with hosting skills like /design, /requirements, and /runbook to drive reviews.
  • Corrector coordination: Dispatch appropriate correctors when artifacts require modifications.

Quick Start

Invoke /proof during a hosting skill's review phase to begin the structured review loop.

Frequently Asked Questions about proof

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

FAQPage Schema
How do I automate artifact validation during project design reviews?

Automated artifact validation is handled by invoking this tool during a hosting skill's review phase to enforce a repeatable, item-by-item decision protocol. This moves beyond single-turn checks by collecting per-item approvals, revisions, or kills for structured verification.

What is the best way to perform item-by-item runbook reviews?

Item-by-item runbook reviews are best executed using a structured review loop that collects verdicts for each artifact. This process supports batch-apply of revise or kill decisions in one atomic pass and records lifecycle updates for full auditability.

How does task coordination work when artifacts require modifications?

Task coordination for artifact modifications works by dispatching appropriate correctors during the review loop. Correctors are triggered to apply necessary changes, which are then batch-applied in an atomic pass with lifecycle tracking for traceability.

Do I need formal frontmatter to start structured verification of requirements?

Formal frontmatter with a name and description is required to start structured verification of requirements. This prerequisite ensures the hosting skill can properly identify artifacts and apply the item-by-item validation protocol during the review phase.