bigeasyfreeman/specificity-judge

Specificity Judge

Run this at Eval Council Gate 0 after schema validation succeeds.

Inputs

For each task provide:

• artifact_type
• acceptance criteria list
• decision_contract
• reference_impl
• files_to_modify
• files_to_create
• tech_debt_boundaries
• compatibility_contract
• evidence_responsibilities
• definition_of_done
• dependencies
• verifier target from verification_spec.primary_verifier
• verifier target_files and expected_failure_mode

Output

{
  "task_id": "TASK-001",
  "score": 0.74,
  "rationale": "The task names files and a verifier, but the acceptance criteria still leave rollback evidence implicit.",
  "failing_signals": ["missing_compatibility_contract", "ambiguous_user_path"]
}

Thresholds

• score >= 0.8 -> pass
• 0.6 <= score < 0.8 -> warn
• score < 0.6 -> revise with low_specificity

Rules

• Specificity means a cold-start coding agent can execute without guessing and can close the work with production-grade evidence.
• Penalize missing file scope, vague acceptance criteria, absent reference paths, missing target_files, missing expected_failure_mode, and verifier targets that do not pin the intended behavior.
• Fail implementation tasks that carry decision_contract.status == unresolved or decision_contract.blocks_implementation == true. Those must be decision gates, not executable tasks.
• Fail tasks whose dependencies are unresolved aliases instead of Build Brief artifact IDs or already-emitted target artifact IDs.
• Fail parent/child duplicate scope: a scope_lock_epic may lock context, but an implementation task must own the executable work. The same behavior should not be executable in both.
• Fail implementation tasks that do not say what existing primitive, schema, service, helper, or workflow they extend, unless they explicitly prove no existing primitive can absorb the change.
• Fail tasks missing tech_debt_boundaries, compatibility_contract, evidence_responsibilities, or definition_of_done; these are one-shot production readiness fields, not optional prose.
• Validation tasks must cover verifier execution, evidence capture, compatibility checks, and final readiness proof. Penalize decomposition sets that lack automatic validation tasks.
• Do not count checklist items mechanically. Judge whether the task is executable.
• If fast_judge is unavailable for the active runtime, emit stuck with reason specificity_judge_unavailable.

Failing Signal Catalog

• unresolved_type1_in_implementation
• missing_artifact_type
• parent_child_duplicate_scope
• unresolved_dependency_alias
• missing_reference_impl
• missing_target_files
• missing_expected_failure_mode
• missing_tech_debt_boundaries
• missing_compatibility_contract
• missing_evidence_responsibilities
• missing_definition_of_done
• missing_validation_task
• ambiguous_user_path
• ambiguous_failure_mode