Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From code-coherence
Defines measurable acceptance criteria as pre-declared quality gates before code execution, using natural language, YAML, or templates for financial, security, and performance.
npx claudepluginhub reggiechan74/cc-plugins --plugin code-coherenceHow this skill is triggered — by the user, by Claude, or both
Slash command
/code-coherence:acceptance-criteriaThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Define specific, measurable acceptance criteria before any code execution, following test-driven development principles. Criteria serve as quality gates that critics evaluate with veto authority.
Creates concrete pass/fail criteria when no existing standards or tests exist. Guides teams to quantify correctness before execution.
Verifies features/stories meet Definition of Done criteria via checklists for functionality, code quality, testing, and security before completion.
Enforces proof-of-work validation with evidence, failing tests first, TDD iron laws, checklists, and red-flag checks before task completion. For acceptance criteria and done gates.
Share bugs, ideas, or general feedback.
Define specific, measurable acceptance criteria before any code execution, following test-driven development principles. Criteria serve as quality gates that critics evaluate with veto authority.
Must be:
/acceptance-criteria define for authentication refactoring:
- All existing tests must pass
- No OWASP Top 10 vulnerabilities
- Token storage uses httpOnly cookies
- Coverage maintains above 85%
Parsed automatically into structured format.
criteria:
- name: Test Pass Rate
description: All existing auth tests pass
validator: code-critic
threshold: 100%
- name: Security Compliance
description: No OWASP Top 10 vulnerabilities introduced
validator: security-critic
checklist: OWASP-2021
- name: Code Coverage
description: Maintain test coverage
validator: code-critic
threshold: ">= 85%"
/acceptance-criteria use template financial
Loads pre-built criteria set for financial calculations.
---
domain: financial
criteria:
- Decimal precision maintained (no float arithmetic)
- Banker's rounding applied (IEEE 754)
- All operations logged to audit trail
- Results formatted to 2 decimal places
- Currency conversion explicit (no implicit conversions)
validators:
- domain-critic (financial specialization)
- code-critic (logic verification)
---
---
domain: security
criteria:
- No SQL injection vectors (parameterized queries only)
- No XSS vulnerabilities (output escaping verified)
- Authentication bypass prevented (auth required on protected routes)
- HTTPS enforced (no plaintext transmission)
- Secrets not in code (environment variables used)
- Password hashing with bcrypt/argon2
validators:
- security-critic
- code-critic (implementation check)
---
---
domain: performance
criteria:
- API latency < 200ms (95th percentile)
- Database queries < 10ms
- No N+1 query patterns
- Memory usage < 512MB
- Caching implemented for expensive operations
validators:
- code-critic (performance checks)
- domain-critic (SLA validation)
---
Each criterion evaluated by assigned critic:
Code Critic checks:
Security Critic checks:
Domain Critic checks:
Update criteria based on lessons learned:
/acceptance-criteria add to financial template:
- Handle leap year calculations correctly
- Timezone conversions must be explicit
Criteria library grows with project experience.
templates/financial.yaml - Financial calculation standardstemplates/security.yaml - OWASP checklist and auth patternstemplates/performance.yaml - Latency SLAs and optimizationreferences/criteria-library.md - All available criteria sets