define-validation

Define AI validation criteria with defaults and custom requirements.

6|Updated Oct 7, 2025
One-click install
npx skills add https://github.com/rjroy/vibe-garden --skill define-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: define-validation
Source: https://github.com/rjroy/vibe-garden/tree/main/lore-development/skills/define-validation
Command: npx skills add https://github.com/rjroy/vibe-garden --skill define-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill defines AI validation criteria for work in progress, enabling explicit verification standards when a spec or plan lacks clear validation.

Core Features & Use Cases

  • Default validation checklist: Introduces the standard validation items (mocked time, mocked network, mocked filesystem, mocked LLM calls, 90%+ code coverage, and code review) to ensure consistent quality.
  • Custom validation prompts: Allows adding feature-specific verification requirements beyond the defaults.
  • Standalone and appendable outputs: Provides options to append to an existing spec/plan or save as a standalone lore document in .lore/validation/[feature-or-work].md.
  • Context-rich guidance: Keeps a trace of how the criteria were derived for future audits.

Quick Start

Use this skill to generate AI validation criteria for your current work item. If a spec/plan exists, offer to append the AI Validation section; if not, save as a standalone document in .lore/validation/[feature-or-work].md.

Frequently Asked Questions about define-validation

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

FAQPage Schema
How do I define AI validation criteria for a spec that lacks testing requirements?

Defining AI validation criteria for a spec involves applying default checks like unit tests with mocked network and filesystem dependencies, 90%+ code coverage, and code review. You can append these to an existing spec or save them as a standalone lore document.

What are the default validation checks applied to work in progress without formal criteria?

Default validation checks for work in progress include unit tests with mocked time, network, filesystem, and LLM calls, alongside 90%+ code coverage and a mandatory code review to ensure consistent quality.

Can I add custom verification requirements beyond the default unit test and coverage checklist?

Custom verification requirements can be added beyond the default checklist, allowing you to specify feature-specific validation prompts tailored to your current work item's needs.

Where should I save validation criteria if I am starting work without an existing plan?

Saving validation criteria without an existing plan should be done as a standalone lore document in the .lore/validation/[feature-or-work].md path, preserving a trace of how the criteria were derived for future audits.

When do I need to generate AI validation criteria for my documentation?

Generating AI validation criteria is needed when a spec or plan exists but lacks explicit verification standards, or when starting work without formal criteria, ensuring explicit verification standards are established.