requirement-quality

# Requirement Quality ## Config Resolution Skill supports project-specific standards. Order: 1. Look for `.lattice/config.yaml` in repo root 2. If found, check `paths.requirement_standards` for custom doc path 3. If custom path exists, read doc and check YAML frontmatter for `mode`: - **`mode: override`** (or no mode): Custom doc full precedence. Use instead of embedded defaults. Must be comprehensive — sole reference. - **`mode: overlay`**: Read embedded `./references/defaults.md` first, then apply custom doc sections on top. Custom sections replace matching sections in defaults (matched by heading). New sections appended after. 4. If no config/path/file, read `./references/defaults.md` Defaults ship with skill. Opinionated best practice. Work out of the box. Override only when team has different standards. Custom standards produced by `requirement-forge-refiner` → consumed by this atom → composed by `requirement-forge` molecule. Run refiner once per project. Re-run when standards evolve. ## Self-Validation Checklist STOP before writing any feature file. Verify ALL checks. If 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 findings as a quality report with severity. **Draft vs approved enforcement**: For `status: draft` — items 1, 2, 10 are required (core framin...