aidlc-verification-before-completion

Enforce evidence-based verification before AIDLC gate completion claims.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/CornFedKratos/s3-aidlc --skill aidlc-verification-before-completion-cornfedkratos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aidlc-verification-before-completion
Source: https://github.com/CornFedKratos/s3-aidlc/tree/main/plugins/s3-aidlc/skills/aidlc-verification-before-completion
Command: npx skills add https://github.com/CornFedKratos/s3-aidlc --skill aidlc-verification-before-completion-cornfedkratos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifying work completion with fresh, verifiable evidence to prevent dishonest or premature claims in AIDLC gate ceremonies.

Core Features & Use Cases

  • Enforces an evidence-before-claim policy across all Touchchain gates, ensuring every completion is backed by auditable artifacts.
  • Defines acceptable evidence types (command output, file diffs, validation script results, test outputs, and screenshots) and assigns ownership to the aidlc-cqo role.
  • Applies to gate ceremonies in aidlc-kickoff-touchchain and aidlc-dev-touchchain, including session-close checks and post-mission reviews.

Quick Start

In an active AIDLC session, enable this skill to enforce gate-verification at each completion checkpoint.

Frequently Asked Questions about aidlc-verification-before-completion

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

FAQPage Schema
How do I enforce evidence-based verification before claiming a gate close in AIDLC?

You can enforce evidence-based verification by enabling this skill in an active AIDLC session to validate gate completion claims. It requires predefined evidence types assigned to the aidlc-cqo role to ensure consistency and safety.

What is the evidence-before-claim policy in Touchchain workflow gates?

The evidence-before-claim policy in Touchchain gates requires that every work completion is backed by auditable artifacts. It prevents premature claims by validating predefined evidence types prior to completion in gate ceremonies.

What evidence types are acceptable for validating completion in AIDLC gate ceremonies?

Acceptable evidence types for validating completion in AIDLC gate ceremonies include command output, file diffs, validation script results, test outputs, and screenshots. The aidlc-cqo role maintains ownership of these artifacts.

Can I use this verification process for session-close checks and post-mission reviews in aidlc-dev-touchchain?

Yes, you can use this verification process for session-close checks and post-mission reviews within aidlc-dev-touchchain and aidlc-kickoff-touchchain. It applies to all gate closes in the Touchchain workflow to validate evidence.

Do I need the aidlc-cqo role to ensure consistency and safety during gate verification?

Yes, you need the aidlc-cqo role to ensure consistency and safety during gate verification. This role maintains line-of-sight ownership over the predefined evidence types required to authorize completion claims.