holdout-validation
CommunityEnforce holdout-based spec integrity.
System Documentation
What problem does it solve?
Structural separation of test authorship from code authorship. Produces behavioral acceptance scenarios that implementation agents cannot see, evaluated independently by Guardian. Use when designing acceptance criteria, validating implementations against intent, or enforcing holdout-set discipline. DO NOT USE FOR: unit test writing (use guardian), implementation (use implementer), verifying task completion (use verification-before-completion), or general test strategy.
Core Features & Use Cases
- Holdout scenario authoring: Architects define intent-level holdouts separate from code.
- Guardian review compatibility: Guardians evaluate implementations against holdout scenarios without access to the code.
- Workflow governance: Enforces structural separation to prevent model leakage and test gaming.
Quick Start
Architect writes 3–10 holdout scenarios per feature and stores them under .copilot/holdout/ with filenames like HOLDOUT.md.
Dependency Matrix
Required Modules
None requiredComponents
💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: holdout-validation Download link: https://github.com/karim-bhalwani/agentic-harness/archive/main.zip#holdout-validation Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.