Checklists

requirements.md

Specification Quality Checklist: Common Docs Convergence

Purpose: Validate specification completeness and quality before proceeding to planning Created: 2026-08-10 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

charter authority paths) is intentional: for a documentation-infrastructure mission these are the domain objects and the acceptance gates, not an implementation choice. They are framed as outcomes/gates, not as a prescribed technology stack.

plan time per DIRECTIVE_035 (path/link renames across many files).

still requiring inbound link-target fixes from plans pages to moved files.

era-README collapse) and #2887 (ADR date-sequence); coordinates #3024, #2358, #3147.

Material corrections: FR-001 uses the EXISTING docs/context/audience/ catalog (not copy built-in); FR-002/003/004 formalize+migrate+test the existing audience field (non-vacuous); FR-009 audience-based how-to routing (contributor→development/, user→guides/); FR-019 repairs all 3 dead authority paths; FR-021/C-010/NFR-010 corrected redirect tooling model (derived map, immutable baseline, own cumulative occurrence-map spine); FR-017 adds a pre-merge DocFX build job; FR-023 extends the lint so NFR-003 is non-vacuous; FR-014/NFR-009 bound + fact-guard the rewrites; C-011 single-threads shared surfaces. Sanctioned section set / root allowlist / in-scope now closed enumerations in Definitions.

  • Naming a few environment surfaces (DocFX site, structural-lint asset, terminology guard,
  • change_mode: bulk_edit is set in meta.json; an occurrence_map.yaml will be produced at
  • Scope boundary (C-001) explicitly excludes the docs/plans/ triage (follow-on mission), while
  • Issue #3273 (docs-IA subdivision residual, epic #2314) is folded; also folds #2215 (arch
  • Spec REVISED post-spec adversarial squad (2026-08-10, 5 lenses) — see reviews/post-spec-squad.md.