Checklists

requirements.md

Specification Quality Checklist: Verdict-matrix RMW preservation (#4858 + #4868)

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

<!-- Terminology note: the canonical specify checklist template ships "Feature:" and "## Feature Readiness"; per the Terminology Canon this instance uses "Mission". Upstream gap to file against the shipped template in packs/built-in. -->

Content Quality

  • ✅ No implementation details (languages, frameworks, APIs) — behaviour-level; fix mechanisms (lock/atomic/read-source) expressed as constraints
  • ✅ Focused on user value and business needs — honest verdicts, no silent verdict loss
  • ✅ Written for non-technical stakeholders — Intent Summary + user stories are plain-language
  • ✅ 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
  • ✅ Success criteria are measurable
  • ✅ Success criteria are technology-agnostic
  • ✅ All acceptance scenarios are defined
  • ✅ Edge cases are identified (both roots)
  • ✅ Scope is clearly bounded — two roots in one class; #2482 excluded (C-005); non-verdict acceptance writers out of scope (C-010); no issue-matrix concurrency work
  • ✅ Dependencies and assumptions identified

Mission Readiness

  • ✅ All functional requirements have clear acceptance criteria
  • ✅ User scenarios cover primary flows (both roots + single-writer preservation)
  • ✅ Mission meets measurable outcomes defined in Success Criteria
  • ✅ No implementation details leak into specification

Notes

preservation" class. Operator's own #4868 triage routed it to this family.

FR-008, exact seam + one-shot reentrancy, disk-reload assertions, mid-point provenance, coord two-worktree-root drive, criterion-mode seam). See tracer-squad-findings.md.

read; fix = coord-aware read_dir into migrate_issue_matrix_to_json, write staging unchanged (C-011); integration red-first test mandatory (real write-seam). A focused post-spec squad pass on the #4868 half + combined coherence runs before plan.

  • Folded per operator decision (2026-09-21): #4868 joins #4858 as the "verdict-matrix RMW
  • #4858 half hardened by the post-spec adversarial squad (lock-acquisition spy FR-007, call-order
  • #4868 half grounded (research/grounding-4868.md): confirmed _migrate_if_needed wrong-source