critique

Source contract preview

This generated excerpt gives readers the beginning of the live primitive contract before they jump to GitHub.

Single-lens signal. Not a merge gate, not `/code-review`, not a parallel bench.

## Delegation Floor

This skill intentionally runs one focused critic lane. It does not satisfy the
full roster floor for substantive review, merge-readiness, or delivery claims;
route those to `/code-review`, `/deliver`, or the calling skill's roster
contract. If the critique itself requires broader judgment, probe the roster
and dispatch additional specialized provider lanes from the caller before
synthesizing.

Local lane guidance: The critique lane is specialized by lens and target. Keep
it read-only, artifact-only, and independent from author reasoning.

## Contract

- `--lenses` lists available lens names by reading
  `harnesses/shared/references/lenses.md`; do not hardcode the list here.
- `--lens <name>` resolves the matching `## <name>` block from that rubric.
  Unknown lens means stop and print the available names.
- `--target <path>` is required for a focused critique. Resolve it against the
  invoking repo and read only the files needed to answer.
- Never reference `agents/<lens>.md`. Lenses are rubrics, not static persona
  files.
- The critic is read-only. Do not edit, stage, commit, or emit a Ship verdict.

## Dispatch

Spawn one fresh read-only critic subagent with:

- role: critic
- objective: apply `<lens>` to `<target>` and find production-relevant design,
  correctness, test, or operability risks
- scope: target path, relevant nearby contracts, and the exact lens excerpt
- boundary: no edits, no broad review, no author reasoning trail
- output: structured findings only

If the harness cannot spawn a fresh subagent, the primary adopts the exact
lens text for one read-only pass and marks the header
`lens-adopted-by-primary`. This is a fallback, not fresh-context separation.
...