fsl-deliverylisted

# FSL Delivery ## Overview Use this skill as the lifecycle coordinator for FSL-based delivery. It does not replace the layer-specific skills; it routes work to them, preserves the layer boundaries, and keeps proof, refinement, and implementation-conformance claims separate. FSL is the checkable contract spine, not the entire product process — but that spine is broad by default: a spec replaces the prose business/requirements/design doc you would write anyway, so wide coverage across those layers needs no per-feature verification-ROI case. Natural language discovery, UI/API design, coding, and testing still happen in their normal tools; FSL supplies the machine-checkable contracts and counterexamples that constrain those artifacts. The resulting spec corpus is the project's living single source of truth: each layer is re-verified on every change (regression, drift, and cross-layer change-impact via `refine`), and it doubles as onboarding context for humans and AI approaching the flow it documents. ## Routing Before authoring a layer, read and follow the corresponding skill: - Business process, As-Is/To-Be, controls, KPIs, goals: `../fsl-business/SKILL.md` - PM/PdM requirements, acceptance criteria, forbidden flows, NFR/SLA: `../fsl-requirements/SKILL.md` - Engineering design, internal state/actions, refinement mapping, testgen/replay handoff: `../fsl-design/SKILL.md` - Design review, variants, substitutability, SOLID/LSP/OCP judgment: `../fsl-design-review/SKILL.m