Individual skill
validation-first
Validation-first design for AI agent output — every spec requirement must be automatically verifiable. Covers the 6-gate validation pipeline, phase gates between Hunt phases, merge protocol, completion signals, and acceptance criteria design patterns. Trigger phrases: "validation gates", "quality gates", "validation-first design", "how to validate agent output", "acceptance criteria design"
plugins/JuliusBrussee/blueprint/skills/validation-first/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,531
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- design Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Validation-First Design
## Core Principle: If an Agent Cannot Validate It, It Will Not Be Met
Every spec requirement must include testable acceptance criteria that an agent can automatically verify. This is not optional — it is the foundation that makes SDD work.
**Why?** AI agents are non-deterministic. Without automated validation, there is no way to know whether an agent's output is correct. Validation gates turn "the agent generated some code" into "the agent generated code that provably meets the specification."
The validation-first rule applies at every level:
- **Spec requirements** must have testable acceptance criteria
- **Plans** must define which gates verify each task
- **Implementation** must pass all applicable gates before being considered complete
- **Iterations** must show measurable progress through gates
