Acceptance Criteria

To define testable acceptance criteria before code execution, you use structured YAML templates to specify pass/fail conditions, assign validation responsibility to designated critic roles, and set measurable thresholds that must be met before proceeding.

Quality gates in CI/CD are pre-declared success conditions that block code changes from deploying. They use validator roles like code-critic and security-critic to evaluate predefined criteria, granting veto authority if the code fails to meet thresholds.

You set up validation roles for code review by assigning specific critic identities—such as code-critic, security-critic, and domain-critic—within your acceptance criteria templates to verify distinct quality aspects before execution.

Yes, you can reuse acceptance criteria templates across different projects. The skill provides template-driven reuse, allowing you to apply pre-built YAML structures and predefined gates consistently across various feature implementations and audits.

The best way to enforce pre-declared success conditions is to define explicit, measurable acceptance criteria before running tasks, ensuring your team agrees on what constitutes success and applying structured templates to guide validation.