Checklists

requirements.md

Specification Quality Checklist: Test-suite remediation: masked greens, harness and pin honesty

Purpose: Validate specification completeness and quality before proceeding to planning. Created: 2026-09-30 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
  • ✅ 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

  • Audience and implementation detail. In this Mission the product under change is the test suite, and its readers are maintainers. So naming test groups, "skip", "xfail", "exact count" and the "census gate" is domain language, not implementation detail. No production technology, framework or code structure is prescribed.
  • The one no-op-passable row. FR-008 is [ratchet] and marked no-op passable. It is paired with the planted-violation controls of FR-007 and FR-009 on the same fixtures, per tactic acceptance-criteria-non-vacuity.
  • Deferred to plan. Two inventories are fixed in the plan, not the spec: the exact list of recurring exact-count pins (FR-007), and the declared platform and tool guards that FR-004 exempts.
  • Validation. All items pass on the first iteration.