Checklists

requirements.md

Specification Quality Checklist: Nightly Suites Green — coord & charter rework fallout

Purpose: Validate specification completeness and quality before proceeding to planning Created: 2026-10-10 Mission: spec.md

Content Quality

  • ✅ No implementation details leak into product-level sections (code anchors are confined to requirement traceability, appropriate for a test-remediation mission)
  • ✅ Focused on the release-gate value (honest green nightly) and the owned-checkout boundary
  • ✅ Written so a maintainer can judge scope without reading code
  • ✅ All mandatory sections completed

Requirement Completeness

  • ✅ No [NEEDS CLARIFICATION] markers remain
  • ✅ Requirements are testable and unambiguous (each cites its suite/test and root cause)
  • ✅ Requirement types are separated (Functional / Non-Functional / Constraints)
  • ✅ IDs are unique across FR/NFR/C/SC and match the grammar
  • ✅ All requirement rows include a non-empty Status value
  • ✅ Non-functional requirements include measurable thresholds (28/28, ratio ≤ limit, zero new reds)
  • ✅ Every FR row and success criterion carries a delivery label and no-op mark
  • ✅ Success criteria are measurable
  • ✅ Success criteria are outcome-focused (green nightly, boundary holds, red-first proof)
  • ✅ All acceptance scenarios are defined
  • ✅ Edge cases are identified (basetemp-inside-repo; remote-live-but-local-absent coord branch; no-op budget bump)
  • ✅ Scope is clearly bounded (five issues; #5883 context-only; charter cutover explicitly out of scope)
  • ✅ Dependencies and assumptions identified

Mission Readiness

  • ✅ All functional requirements have clear acceptance criteria
  • ✅ User scenarios cover primary flows (code fix, CI/corpus artifacts, drift, perf)
  • ✅ Mission meets measurable outcomes defined in Success Criteria
  • ✅ Red-first / non-vacuity discipline encoded in NFR-004 and the no-op marks

Notes

  • FR-011 is no-op passable by itself (a bare limit bump); paired with FR-010's import-absence positive control so the budget cannot be green-washed.
  • C-001/C-002 encode the "fix at true root, never relax the check" rulings from the grounding squad.