Checklists

requirements.md

Specification Quality Checklist: Mission-Type Doctrine Authority

Purpose: Validate specification completeness and quality before proceeding to planning Created: 2026-07-14 Feature: 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-###, 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 (no implementation details)
  • ✅ All acceptance scenarios are defined
  • ✅ Edge cases are identified
  • ✅ Scope is clearly bounded
  • ✅ 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

(MissionType artefact, governance-profile.yaml, doctrine reference graph) is the product's own canonical terminology, not implementation leakage. Requirements are stated at the behaviour/outcome level; the mechanism is fixed by ADR 2026-07-14-2 and elaborated in the plan phase.

Assumptions), not left as [NEEDS CLARIFICATION]: the software-dev-only denylist membership and the per-entry degrade behaviour for mission-less callers.

planner-priti): added FR-003a (mission-less degrade), FR-012 (canonicalizer / dossier-path leak closure), FR-013 (URN-normalized cross-grain disjointness guard), NFR-007 (deterministic ordering); disambiguated FR-003; softened FR-007/NFR-004/SC-005 to the detachable/deferrable dossier lane; tightened NFR-006 (URN denylist + shared-action non-vacuity); added SC-007 (steps) and the #883 partial-close note.

  • This is an internal platform/doctrine mission, so the domain vocabulary
  • Two decisions are deliberately deferred to their work packages (recorded in
  • Revised after a 3-lens post-spec review squad (reviewer-renata / architect-alphonso /