Checklists

requirements.md

Specification Quality Checklist: Write-Surface Coherence

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

Content Quality

  • ✅ No implementation details (languages, frameworks, APIs) — exception: this is an internal architecture/refactor mission; named surfaces/functions are the requirement substance, not incidental HOW. The stakeholders are the dev team + operator.
  • ✅ Focused on user value and business needs (operator can plan a mission without manual coord-worktree steps)
  • ✅ Written for the relevant stakeholders (dev team + operator)
  • ✅ 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 where the outcome allows (SC-001/003 are operator-observable; SC-002/004 are guard-test counts)
  • ✅ All acceptance scenarios are defined
  • ✅ Edge cases are identified (protected primary; already-split missions)
  • ✅ Scope is clearly bounded (Out of Scope section)
  • ✅ Dependencies and assumptions identified

Feature Readiness

  • ✅ All functional requirements have clear acceptance criteria (via Success Criteria + scenarios)
  • ✅ User scenarios cover primary flows (happy path + exception + edge)
  • ✅ Feature meets measurable outcomes defined in Success Criteria
  • ✅ No incidental implementation details leak (named surfaces are the requirement substance for an infra mission)

Notes

  • The two design crux decisions (planning-on-primary all shapes / status-on-coordination; forward-only) were operator-confirmed 2026-06-23 — recorded in the Summary and Constraints, no open markers.
  • Standing practice: run the post-spec adversarial consistency squad before /spec-kitty.plan.