verify-milestone

Name: verify-milestone
Availability: InStock
Author: mckissinger

Verifies completed software milestones against specifications and acceptance criteria before code acceptance.

1|Updated Jun 29, 2026

Search Tags:#software delivery #autonomous development #spec compliance #code validation #ci workflow #milestone verification

Ready to run

npx skills add https://github.com/mckissinger/keel --skill verify-milestone

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify-milestone
Source: https://github.com/mckissinger/keel/tree/main/skills/verify-milestone
Command: npx skills add https://github.com/mckissinger/keel --skill verify-milestone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents unverified software milestones from being accepted by independently checking implementation results against specifications, runtime requirements, and evidence-based completion criteria.

Core Features & Use Cases

Independent Verification: Validates completed milestones in a fresh session using the project's declared verification method and ground truth.
Evidence-Based Gating: Checks automated suites, runtime behavior, tracked files, discrepancies, and commit-pinned verification records before acceptance.
Use Case: A development team finishing a major feature milestone can use this Skill to confirm the merged code matches the specification and create a durable verification record before opening a PR.

Quick Start

Run the verify-milestone skill for the completed milestone to independently validate its requirements and create a verified record if all checks pass.

Frequently Asked Questions about verify-milestone

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

FAQPage Schema

How do I verify software milestones against specifications before merging code?▼

Milestone verification independently validates completed implementation results against specifications and acceptance criteria. It checks automated tests, runtime conditions, evidence records, and commit-pinned proof to ensure verified code matches merged code before acceptance.

What is the best way to enforce spec compliance in an autonomous development workflow?▼

Spec compliance in autonomous development workflows is enforced by independently validating completed milestones against ground truth. This evidence-based gating checks automated suites, runtime behavior, tracked files, and commit-pinned verification records before code acceptance.

How do I create a durable verification record for a completed feature delivery pipeline?▼

Create a durable verification record for feature delivery pipelines by running milestone verification against automated suites and runtime conditions. If all checks pass, it generates a commit-pinned proof record confirming the merged code matches the verified implementation.

Does milestone verification work with my existing CI workflow and automated tests?▼

Milestone verification works with existing CI workflows by applying the project's declared verification method to validate automated tests and runtime conditions. It gates code acceptance by checking evidence records and commit-pinned proof before opening a pull request.

Why should I use independent validation for code acceptance instead of relying on test runs?▼

Independent validation for code acceptance prevents unverified milestones from passing by checking implementation results in a fresh session against ground truth. Unlike relying solely on test runs, it verifies runtime conditions, evidence records, and commit-pinned proof that verified code matches merged code.