lidr-requirements

Author and validate the requirements specification — Functional Requirements (RF) with BDD acceptance criteria, measurable Non-Functional Requirements (NFR), and the cross-validation / RTM that enforces Gate 2. BMad emits ONE unified PRD (FRs nested under features + cross-cutting and feature-specific NFRs in the SAME document) — this skill consumes that single PRD; it does NOT assume a separate "Functional PRD" and "Technical PRD". Fuses the former generate-rf + generate-nfr + validate-requirements into one workflow-driven skill with 5 modes across two phases: per-rf (atomic RFs from the PRD's functional scope — Gate-2 evidence, Phase 3), nfr (measurable NFRs from the PRD's NFR scope — Phase 3), validate (5-pass RTM + Gate-2 verdict; the /lidr-validate-requirements command delegates here — Phase 3), living-spec (consolidate a feature's current-state UJ/RF/NFR/AC into docs/features/<f>/spec.md — Phase 0/anytime, DTC), brownfield-audit (recover the spec from an existing system via bmad-document-project, then ha

By LIDR-IT schedule Updated 6/14/2026