review-fix-speclisted

# review-fix-spec Fixed document type: SPEC. Users must not pass type. This entry skill always treats the target as a `SPEC` for requirements, product behavior, API behavior, feature definition, and acceptance documents. Invocation syntax: ```text review-fix-spec <path> [ref=<path>...] [read-only|review-and-fix] [strict|normal] [assurance=practical|strict-verified|advisory] [guard=git|snapshot] [resume|reset] [rounds=<n>] [ledger=<target-local path>] [root=<project-root>] [debug] ``` Full form: `review-fix-spec target=<path> ...`. A bare path is shorthand for `target=<path>`. Valid target invocations may omit mode. Codex and Claude Code generated routes select `review-and-fix assurance=practical` by default when mode and assurance are omitted; missing mode selects `review-and-fix` and missing assurance selects `practical`. Explicit `assurance=advisory` without mode selects `read-only` on Codex and Claude Code. Gemini generated routes select `read-only assurance=advisory` by default. Help-style or invalid invocations explain usage only and do not read files, run workflow commands, run probes, create state, or declare review results. Reference Conformance: `ref=` documents are consistency sources, not mandatory upstream chains. This route checks whether the target conflicts with references or invents unsupported reference-backed claims; it does not require coverage tables, stable IDs, `Design Coverage Import`, or `SPEC-to-task mapping` unless the target explicitly claims