Checklists

requirements.md

Specification Quality Checklist: Corrupt per-mission state files fail closed, not crash

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) — internal CLI tool; error-type names are the domain contract, kept at requirement level
  • ✅ Focused on user value and business needs (operators + agent loop degrade gracefully)
  • ✅ Written for non-technical stakeholders (operator-facing outcomes lead)
  • ✅ 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 (Open)
  • ✅ Non-functional requirements include measurable thresholds (exit code, 0 tracebacks, complexity ≤15)
  • ✅ Success criteria are measurable
  • ✅ Success criteria are technology-agnostic (outcome-focused)
  • ✅ All acceptance scenarios are defined (Given/When/Then per story)
  • ✅ Edge cases are identified (non-UTF-8, wrong-shape, missing-file, broad-except, downstream escape)
  • ✅ Scope is clearly bounded (2 sites in; wps_manifest + audit deferred)
  • ✅ Dependencies and assumptions identified (ADR 2026-07-17-1; #4600 sibling; deferred mission)

Feature Readiness

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

Notes

  • Q1 (error presentation) resolved: unify on the fail-closed + run: spec-kitty doctor hint for both files.
  • All items pass on iteration 1.