Checklists

requirements.md

Specification Quality Checklist: Coord/lane actor-identity representation cluster

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

Content Quality

  • ✅ No implementation details (languages, frameworks, APIs) — spec describes observable claim/verdict/ownership behavior; file:line internals are deferred to plan
  • ✅ Focused on user value and business needs (agents/operators completing claim, review, and hand-off honestly)
  • ✅ Written for non-technical stakeholders (purpose + user stories are workflow-level)
  • ✅ 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 (all Open)
  • ✅ Non-functional requirements include measurable thresholds (NFR-002 ≥4 matrix cases; NFR-003 red-before/green-after; NFR-004 zero new suppressions, complexity ≤15)
  • ✅ Success criteria are measurable (SC-001..004)
  • ✅ Success criteria are technology-agnostic (verdict attribution, one-invocation completion, zero force overrides)
  • ✅ All acceptance scenarios are defined (each user story)
  • ✅ Edge cases are identified (same-tool-two-roles, generic-actor allowance, rejection release, immutable history)
  • ✅ Scope is clearly bounded (four issues; #3029 representation-half only; adjacent issues explicitly separate)
  • ✅ Dependencies and assumptions identified (Assumptions section; C-001 upstream boundary)

Feature Readiness

  • ✅ All functional requirements have clear acceptance criteria
  • ✅ User scenarios cover primary flows (claim, review verdict, fix-mode ownership, move-task persistence)
  • ✅ Feature meets measurable outcomes defined in Success Criteria
  • ✅ No implementation details leak into specification

Notes

surfaced must-fix items that were all folded: NFR-002 was re-pinned to the correct seam (impl-claim key is tool-scoped/role-blind; role distinctness on the review-claim role channel); NFR-003 baseline reconciled to 0f5973a639 and carved out #3029's already-green case; SC-003/FR-007 hedged on live re-verification (C-001); FR-010 added to protect the generic-actor allowance; C-006 added for the three ownership authorities; C-002/C-005 rewritten so reconciliation lives in the CLI-local comparison layer and the shared projection stays byte-identical; SC-005 added for FR-009; ACs sharpened (rejection attribution, evidence retention, slot-named assertions, artifact-based #3029 close).

is a dependency, not an unresolved clarification.

  • Initial validation passed, then a post-spec adversarial squad (two lenses, code-verified)
  • C-001 records an out-of-repo boundary (shared reducer) that constrains #4673's scope; this