Checklists

requirements.md

Specification Quality Checklist: Nightly suites green on main

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

Content Quality

  • ✅ No implementation details (languages, frameworks, APIs)
  • ✅ Focused on user value and business needs
  • ✅ Written for non-technical stakeholders
  • ✅ 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-###, C-### and SC-### entries, and match the requirement-ID grammar (optional lowercase letter suffix; <mission-slug>#<ID> only for another mission's ID)
  • ✅ All requirement rows include a non-empty Status value
  • ✅ Non-functional requirements include measurable thresholds
  • ✅ Every FR row and success criterion carries a delivery label and no-op mark
  • ✅ Success criteria are measurable
  • ✅ Success criteria are technology-agnostic (no implementation details)
  • ✅ All acceptance scenarios are defined
  • ✅ Edge cases are identified
  • ✅ Scope is clearly bounded
  • ✅ Dependencies and assumptions identified

Mission Readiness

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

Notes

  • The readers of this spec are the maintainers of a developer tool, so the "non-technical stakeholder" and "no implementation details" items are met at that audience's level: requirements state behaviour and name the seams that the operator rulings fixed (alias authority, moved gate), while file and line detail stays in research/code-grounding.md.
  • C-001 names one function in one file because the operator ruling of 2026-10-05 scoped an exception to it.