Checklists
requirements.md
Specification Quality Checklist: Single planning-surface authority + worktree repair
Purpose: Validate specification completeness and quality before proceeding to planning Created: 2026-06-22 Feature: spec.md
Content Quality
- ✅ No implementation details (languages, frameworks, APIs) — resolver/command names are the domain surfaces under fix, not tech choices
- ✅ Focused on user value and business needs (operators stop hitting silent not-found / dead-end recovery)
- ✅ Written for non-technical stakeholders (scenarios are operator-facing)
- ✅ 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 (gate-green, zero-issue lint, complexity ≤15, live-repro)
- ✅ Success criteria are measurable (zero unmapped, all legs×handles PRIMARY, guard fails on planted phantom)
- ✅ Success criteria are technology-agnostic where user-facing
- ✅ All acceptance scenarios are defined
- ✅ Edge cases are identified (create-window, coord-deleted, legacy no-mid8, benign no-op repair)
- ✅ Scope is clearly bounded (#1890 + #1716 folding #2062/#2063/#2064; #1970 in-slice)
- ✅ Dependencies and assumptions identified
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
ARE the domain objects under fix, cited for precision; they are not premature implementation choices.
- This is a refactor/convergence mission: the named code surfaces (resolvers, commands)
- #1970 campsite directive is recorded as C-001 + FR-009..FR-013 per operator mandate.
- #2062 carries C-002 (no close without live repro) per the live-evidence rule.