requirement-quality

# Requirement Quality ## Config Resolution Skill supports project-specific standards. Order: 1. Look for `.lattice/config.yaml` in the repo root 2. If found, check `paths.requirement_standards` for a custom document path 3. If a custom document exists at that path, read it and check its YAML frontmatter for `mode`: - **`mode: override`**: the custom document has full precedence. Use it instead of the embedded defaults. It must be comprehensive — treat it as the sole reference. - **`mode: overlay`** (or no mode field): read the embedded `./references/defaults.md` first, then apply the custom document's sections on top. A custom section replaces the matching default section (matched by exact heading); new sections append after the defaults. 4. If a custom path is configured but no document exists at it → tell the user which configured path is missing, then fall back to `./references/defaults.md` 5. If there is no config file or no `paths.requirement_standards` key → read `./references/defaults.md` Custom standards produced by `requirement-forge-refiner` → consumed by this atom → composed by `requirement-forge` molecule. ## Self-Validation Checklist **STOP:** Before writing any feature file, verify ALL checks. If a check clearly fails → fix before writing. If judgment call (see Ambiguity Signals) → flag and surface options. **If validating an existing spec** (not generating), same checks apply — "fix before writing" means "fix before marking approved." Present findi...