speckit-rubric-score

You validate release readiness by applying a rubric score to post-commit self-check evidence and branch state. This structured evaluation checks stage compliance, applies hard gates, and outputs a clear pass or block decision for branch completion.

Rubric-based branch readiness scoring evaluates L1 through L5 against required evidence and weighted totals. It applies hard-gate validation to self-acceptance, retrospective completion, commit validation, and evidence sufficiency before allowing branch completion.

Yes, hard-gate validation explicitly checks self-acceptance, retrospective completion, commit validation, and evidence sufficiency. It also confirms stage order, artifact readiness, and context governance to ensure spec-kit delivery workflow compliance before allowing branch completion.

To calculate the final Spec Kit rubric score, you submit final post-commit self-check evidence for review. The evaluation applies weighted totals across L1 through L5 stages, applies hard gates, and produces the rubric score with deductions, blockers, and a complete-branch decision.

A spec-kit branch can be blocked due to failing hard-gate validation on retrospective completion, commit validation, or evidence sufficiency. The rubric score also checks stage order, artifact readiness, and context governance, reporting specific blockers if any requirement is unmet.

No, spec-kit rubric scoring requires explicit evidence of scores, deductions, gate outcomes, and blocker or approval conclusions. Evidence sufficiency is a hard gate that must be passed before the evaluation can produce a complete-branch readiness decision.