infer-nfr-spec-from-code

What problem does it solve?

It prevents teams from guessing non-functional requirements by reconstructing what the shipped system already enforces, using evidence from scan-index outputs instead of inventing targets.

Core Features & Use Cases

• Grounded NFR Reconstruction: Builds a per-NFR contract of enforced targets by tracing signals (idioms, manifests, deploy config, CI) back to concrete evidence paths.
• Mechanism + Verification Pairing: For every inferred NFR entry, captures both the delivery mechanism (library, middleware, layer, deploy config block) and a verification method (test/CI/monitor signal).
• No-Invention Guardrails: Records missing or unsupported signals as knowledge gaps rather than fabricating thresholds or verification steps.
• Codify Pipeline Integration: Runs during /codify after quality and physical architecture/quality-profile proposals exist, producing architecture/nfr-spec.yaml in the expected STM location.

Quick Start

Ask the tech-architect agent to run infer-nfr-spec-from-code during /codify using scan-index.json and the prior quality, physical, and logical architecture proposal paths so it can generate architecture/nfr-spec.yaml with fully grounded evidence and resolution traces.