Checklists

requirements.md

Specification Quality Checklist: Terminus Reconciliation Attribution Integrity

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

Content Quality

  • ✅ No implementation details (languages, frameworks, APIs) — FR/NFR/C describe gate behavior, not code; function names appear only as Key-Entity anchors
  • ✅ Focused on user value and business needs — the operator's ability to merge safely and completely
  • ✅ Written for non-technical stakeholders — Summary + user stories are plain-language; behavior-first
  • ✅ All mandatory sections completed

Requirement Completeness

  • ✅ No [NEEDS CLARIFICATION] markers remain
  • ✅ 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 (0 regressions, <2s, complexity ≤15)
  • ✅ Success criteria are measurable
  • ✅ Success criteria are technology-agnostic
  • ✅ All acceptance scenarios are defined
  • ✅ Edge cases are identified
  • ✅ Scope is clearly bounded (4 facets; 3-way explicitly out of scope)
  • ✅ Dependencies and assumptions identified (disjoint-write-scope invariant; parallel-safety with #4883)

Feature Readiness

  • ✅ All functional requirements have clear acceptance criteria (each FR maps to a User Story's scenarios + a Success Criterion)
  • ✅ User scenarios cover primary flows (one per facet, severity-ordered)
  • ✅ Feature meets measurable outcomes defined in Success Criteria
  • ✅ No implementation details leak into specification

Notes

  • Facets map: FR-001/002/003 → #5022 (WP1); FR-004/005 → #5018 (WP2); FR-006 → #5021 r1 (WP3); FR-007 → #5038 (WP4); FR-008 → #5021 r2 (kept honest xfail).
  • All items pass on first validation iteration.