Checklists

requirements.md

Specification Quality Checklist: Terminus Projection Driver-Replay Attribution

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

Content Quality

  • ✅ No implementation details (languages, frameworks, APIs) — core-infra spec necessarily names merge seams; kept to behavior/outcome level per requirement
  • ✅ Focused on user value and business needs (operator/merge-agent value: no false-REFUSE, floor preserved)
  • ✅ Written for the merge-workflow stakeholder
  • ✅ All mandatory sections completed

Requirement Completeness

  • ✅ No [NEEDS CLARIFICATION] markers remain (decision verify: clean)
  • ✅ Requirements are testable and unambiguous
  • ✅ Requirement types are separated (Functional / Non-Functional / Constraints)
  • ✅ IDs are unique across FR-###, NFR-###, and C-### entries
  • ✅ All requirement rows include a non-empty Status value
  • ✅ Non-functional requirements include measurable thresholds
  • ✅ Success criteria are measurable
  • ✅ Success criteria are technology-agnostic (outcome-oriented: test flips, floor holds, 0 regressions)
  • ✅ All acceptance scenarios are defined
  • ✅ Edge cases are identified (non-driver path, non-diverged subset, idempotent replay)
  • ✅ Scope is clearly bounded (#5021-r2 doc-only, #4997 out)
  • ✅ Dependencies and assumptions identified

Feature Readiness

  • ✅ All functional requirements have clear acceptance criteria
  • ✅ User scenarios cover primary flows (fix, floor, residual disposition)
  • ✅ Feature meets measurable outcomes defined in Success Criteria
  • ✅ No implementation details leak into specification beyond the necessary seam naming

Notes

  • Grounded in Phase R (3 opus lenses). Operator ruled Option B (DM-01M3EC2FMWKCKGSBX1QHC7GFCJ).
  • All items pass — ready for /spec-kitty.plan.