kiro-verify-completion

Name: kiro-verify-completion
Availability: InStock
Author: miyamo2

Verify completion claims using canonical validation commands and fresh outputs.

Updated Jan 26, 2026

Search Tags:#verification #governance #evidence #claims #build-quality

Ready to run

npx skills add https://github.com/miyamo2/braider --skill kiro-verify-completion-miyamo2

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kiro-verify-completion
Source: https://github.com/miyamo2/braider/tree/main/.gemini/skills/kiro-verify-completion
Command: npx skills add https://github.com/miyamo2/braider --skill kiro-verify-completion-miyamo2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents false completion claims by requiring fresh evidence that matches the scope of the claim.

Core Features & Use Cases

Gate-based verification: requires canonical validation commands, fresh outputs, and scoped evidence to support a claim.
Evidence-driven decisions: links verification results to specific task ids, requirements, and design refs to avoid scope drift.
Manual and automated verification support: supports automated checks and manual review when automation is insufficient.

Quick Start

Run the canonical validation command for your task, capture fresh outputs, and report the result to the verifier.

Frequently Asked Questions about kiro-verify-completion

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

FAQPage Schema

How do I verify completion claims with fresh evidence before a feature go-live?▼

To verify completion claims, run canonical validation commands for your task, capture fresh outputs, and report the results to enforce a gate that prevents premature feature go decisions.

What is evidence-driven verification in software development workflows?▼

Evidence-driven verification links validation results to specific task IDs, requirements, and design references to avoid scope drift. It requires fresh outputs matching the claim scope before approving task, fix, test, or build completions.

How do I prevent false completion claims and premature go decisions in task tracking?▼

Prevent false completion claims by enforcing a verification gate that demands canonical validation commands and fresh outputs. This ensures completion proof matches the actual task scope before any go decision is made.

Does verification support manual review when automated checks are insufficient?▼

Yes, verification supports both automated checks and manual review. When automation is insufficient for validating completion claims, manual review processes can enforce the gate using fresh evidence and scoped outputs.

When do I need to require fresh outputs for build quality verification?▼

You need fresh outputs for build quality verification whenever declaring task, fix, test, or feature completion. Requiring fresh evidence ensures the validation results directly match the claim scope and prevent premature approvals.