Checklists

requirements.md

Specification Quality Checklist: CI Terminal-Cancel Verdict (infra-error)

Purpose: Validate specification completeness and quality before planning Created: 2026-09-16 Feature: spec.md

Content Quality

  • ✅ No implementation details beyond necessary infra anchors (deliverable IS CI code; requirements framed as testable outcomes)
  • ✅ Focused on release-authority honesty (a cancellation must never silently wedge a head)
  • ✅ Written for the maintainer / release-authority stakeholder
  • ✅ All mandatory sections completed

Requirement Completeness

  • ✅ No [NEEDS CLARIFICATION] markers remain
  • ✅ Requirements testable and unambiguous
  • ✅ Types separated (FR / NFR / C)
  • ✅ IDs unique
  • ✅ Every row has a Status
  • ✅ NFRs have measurable thresholds (0 false-green; INV-2 both cases; 100% branch coverage; idempotent re-run)
  • ✅ Success criteria measurable
  • ✅ Success criteria outcome-framed (verdict/head-release, not tool internals)
  • ✅ Acceptance scenarios defined (classify precedence + report() release + sweep)
  • ✅ Edge cases identified (cancel-among-pending, failure+cancel, timed_out vs cancelled, cancelled reporter, idempotency)
  • ✅ Scope bounded (4a + 4b in; router_gate classify + Stage-1 levers + dedup out)
  • ✅ Dependencies/assumptions identified (Stage 1/2 merged; #4430 closed-but-unfixed; 4b surface/host settled in plan)

Feature Readiness

  • ✅ All FRs have acceptance criteria
  • ✅ User scenarios cover primary flows (release / never-green / sweep / non-fakeable proof)
  • ✅ Meets measurable outcomes in Success Criteria
  • ✅ No implementation leak beyond necessary anchors

Notes

  • Classify precedence is settled by the pre-spec squad (reviewer-renata caught the premature-fire flaw in the orchestrator's first default; corrected to gate on all present completed).
  • The one open design area (4b surface + host) is a deliberate plan determination, recorded as an Assumption, ADR-constrained to "surface as a watch item, do not auto-release."