speckit-acceptance-rubric

To generate acceptance rubrics from requirements, you input your test plans and quality goals to produce self-contained rubric rows containing criteria, evidence requirements, pass conditions, and pitfall guards for verifying implementation.

An AI self-acceptance gate uses acceptance rubrics to verify implementation quality by matching criteria rows against required evidence and pass conditions, ensuring software changes meet defined quality expectations before review.

You create test planning criteria by converting requirements and quality vision into rubric rows that specify essential checks, required evidence, pass conditions, weighting, and pitfall guards for human-review checkpoints.

Yes, acceptance rubrics support workflow compliance by including stage order checks, blockers, retrospective readiness, and delivery-state checks to ensure software changes follow governance rules.

Yes, the generated acceptance rubric requires Chinese-first output formatting to ensure localized delivery and review readiness for teams using Chinese as their primary documentation language.

To generate pitfall guards for quality gates, your requirements and test plans should capture essential checks and important quality expectations, which the rubric translates into rows with source risks and stage compliance checks.