Checklists

requirements.md

Specification Quality Checklist: Merge/Git Destructive-Operation Safety

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

Content Quality

  • ✅ No implementation details (languages, frameworks, APIs) — file/symbol refs confined to Constraints as fix-boundary guidance, not FRs
  • ✅ Focused on user value and business needs (operator/implementer data safety)
  • ✅ Written for non-technical stakeholders (scenarios are plain-language data-loss narratives)
  • ✅ 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 (residue false-positive, atomic refusal, resume parity)
  • ✅ Scope is clearly bounded (three sites + two coupled folds; branch -D deferred)
  • ✅ Dependencies and assumptions identified

Feature Readiness

  • ✅ All functional requirements have clear acceptance criteria
  • ✅ User scenarios cover primary flows (one per issue)
  • ✅ Feature meets measurable outcomes defined in Success Criteria
  • ✅ No implementation details leak into specification requirements

Notes

the plan phase inherits the grounding squad's canonical-seam guidance.

  • Guard-strategy (unify) and adjacent-surface scope recorded as resolved Decision Moments.
  • Fix-boundary file/symbol references are intentionally captured in Constraints so