Checklists

requirements.md

Specification Quality Checklist: move-task / approval-gate ergonomics

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

Content Quality

product surface itself, not implementation choices

  • ✅ No implementation details (languages, frameworks, APIs) — CLI flag/verdict names are the
  • ✅ Focused on user value and business needs (honest audit artifact, unsurprising workflow)
  • ✅ Written for stakeholders (operators/agents driving missions)
  • ✅ 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 (<200ms, <2s, 100%, 0)
  • ✅ Success criteria are measurable
  • ✅ Success criteria are technology-agnostic
  • ✅ All acceptance scenarios are defined
  • ✅ Edge cases are identified
  • ✅ Scope is clearly bounded (explicit out-of-scope: #4330 landed work, #2816, #3454 children)
  • ✅ Dependencies and assumptions identified (grounding verdict recorded in Context section)

Feature Readiness

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

Notes

DM-01M302SBM26BGHEX36GC8YFJME.

resolved Decision Moments.

already-landed items (#4330) and by-design behavior (#2816) explicitly excluded.

  • Verdict-value naming (not-applicable) confirmed by the operator via Decision Moment
  • Scope (both levers + ADR; all three ergonomics items) confirmed by the operator; recorded as
  • Grounding squad reproduced every sub-defect against main HEAD a9d3f4b747 before authoring;