Validate acceptance criteria and feature completion. Use when checking if features pass, validating test results, verifying acceptance criteria, or determining feature completion status.
npx skills add https://github.com/majiayu000/claude-skill-registry --skill ac-criteria-validator
Validate acceptance criteria and determine feature completion.
Validates that implemented features meet their acceptance criteria, determining when passes can transition from false to true.
from scripts.criteria_validator import CriteriaValidator
validator = CriteriaValidator(project_dir)
result = await validator.validate_feature("auth-001")
print(result.passes) # True/False
print(result.criteria_results)
{
"feature_id": "auth-001",
"passes": true,
"criteria_results": [
{
"criterion": "Valid registration creates user",
"passed": true,
"evidence": "test_valid_registration passed",
"method": "test_execution"
},
{
"criterion": "Invalid email shows error",
"passed": true,
"evidence": "test_invalid_email passed",
"method": "test_execution"
}
],
"test_summary": {
"total": 5,
"passed": 5,
"failed": 0,
"coverage": 87.5
},
"validated_at": "2024-01-15T10:30:00Z"
}
validation:
require_all_tests_pass: true
minimum_coverage: 80
require_no_lint_errors: true
require_type_checks: true
custom_rules:
- name: "no_console_logs"
pattern: "console\\.log"
severity: "warning"
CRITICAL: passes can ONLY transition false → true
Before validation:
{"passes": false, "status": "in_progress"}
After successful validation:
{"passes": true, "status": "completed"}
NEVER:
{"passes": true} → {"passes": false}
ac-state-trackerac-test-generator test filesSee scripts/criteria_validator.py for full implementation.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when implementing any feature or bugfix, before writing implementation code
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.
Cloud laboratory platform for automated protein testing and validation. Use when designing proteins and needing experimental validation including binding assays, expression testing, thermostability measurements, enzyme activity assays, or protein sequence optimization. Also use for submitting experiments via API, tracking experiment status, downloading results, optimizing protein sequences for better expression using computational tools (NetSolP, SoluProt, SolubleMPNN, ESM), or managing protein design workflows with wet-lab validation.
This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.
Take majiayu000/ac-criteria-validator from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.