skills.rest
peterbamuhigire
peterbamuhigireCOMMUNITY
Explore all skills by this author →
Website𝕏@peterbamuGitHub

validation-contract

Declare seven evidence categories and map artefacts to the Release Evidence Bundle template.

1|Updated Apr 25, 2026
Search Tags:#documentation#specification#validation#evidence#contract#release-bundle
One-click install
npx skills add https://github.com/peterbamuhigire/digital-research-skills --skill validation-contract
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validation-contract
Source: https://github.com/peterbamuhigire/digital-research-skills/tree/main/skills/validation-contract
Command: npx skills add https://github.com/peterbamuhigire/digital-research-skills --skill validation-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes a standard, ship-ready validation framework for specialist skills by centralising the seven evidence categories and canonical Release Evidence Bundle templates, reducing ambiguity and enabling consistent governance.

Core Features & Use Cases

  • Defines the seven canonical evidence categories (Correctness, Security, Data safety, Performance, Operability, UX quality, Release evidence) and explains how to map skill artefacts to them.
  • Provides a standard Outputs contract (the "Evidence Produced" section) and a canonical Release Evidence Bundle template to capture ship-readiness artifacts.
  • Serves as a normalisation tool for authoring new skills or updating existing ones to the repository's house style and governance.

Quick Start

Create a SKILL.md that declares the seven evidence categories and attaches the Release Evidence Bundle template to enable ship readiness checks.

Frequently Asked Questions about validation-contract

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

FAQPage Schema
What are the seven evidence categories required for a validation contract?▼

A validation contract requires mapping artefacts to seven evidence categories: Correctness, Security, Data safety, Performance, Operability, UX quality, and Release evidence to ensure ship-readiness.

How do I standardize skill artefact mapping for a release bundle?▼

You standardize skill artefact mapping by applying a canonical Release Evidence Bundle template that declares the seven evidence categories, ensuring your release bundle aligns with governance requirements.

When do I need to use a formal validation framework for feature shipping?▼

A formal validation framework is needed when authoring or updating specialist skills to a repository's house style, requiring artefact-to-category mapping to prove feature shipping readiness.

Does a validation contract require external dependencies to declare evidence?▼

No, declaring evidence requires no external dependencies; it uses a standard Outputs contract within your SKILL.md to attach the canonical Release Evidence Bundle template for validation.

What is the best way to normalize new skills to repository house style?▼

The best way to normalize new skills is using a centralized validation framework that enforces the seven evidence categories and canonical templates, reducing ambiguity and enabling consistent governance.

Related Skills

Explore More Software Engineering Skills→
refactory-langrefactory-lang

speckit-workflows.baseline

Generate baseline-spec.md and current-state.md from codebase and git history.

Official
Advanced
bravekingzhangbravekingzhang
29

acp-release-check

Classify release risk and verify evidence for operational readiness.

Community
Advanced
hgflimahgflima
1

code-review-and-quality

Review code across correctness, readability, architecture, security, and performance.

Community
Advanced
blackpwnguinblackpwnguin
1

Createskill

Generate canonical skill structures with SKILL.md, workflows, tools, and references.

Community
Advanced