triangulate-spec-review

Review and improve architecture specs, ADRs, plugin or agent directory proposals, and other design documents by running multiple independent AI reviewers such as Claude, Qoder, Codex, or Cursor Agent against the same artifact, normalizing P1/P2/P3 findings, and iterating only on blocking or high-risk issues.

Jump to install

Repository: QoderAI/better-harness
Last source activity: July 27, 2026 at 08:18
Detected SKILL.md language: English
Stars: 1,903
Forks: 158

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/QoderAI/better-harness --skill triangulate-spec-review

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

3 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

generate-harness-dsl

Generate, revise, or review complete Harness as Code `.harness` files when a coding-agent workflow, agent role, skill, tool contract, MCP connection, runtime, or deployment must be compiler-valid and resolvable with `@qoder-ai/harness`.

2026-08-17

handoff

Prepare a bounded handoff.

2026-08-05

verify

Verify one bounded change.

2026-08-05

View all from this repository

Triangulate Spec Review

Use independent AI reviewers as an evaluation surface for specs. The lead agent owns synthesis, edits, validation, and the final recommendation.

Workflow

Resolve the target spec path and the acceptance gate. If the user did not name dimensions, default to complexity, convenience, and evolution.

Read the target spec and nearby repo instructions. Do not pass your suspected fixes or conclusions to reviewers.

Use the same read-only prompt for every reviewer. Ask for structured P1/P2/P3 findings and a p1_p2_clear boolean.

Run at least two reviewers; prefer three when available. Use scripts/run-triad-review.mjs for repeatable local runs.

Normalize findings. Treat reviewers as evidence, not authority: fix convergent P1/P2 issues first, challenge weak or contradictory findings, and leave P3 as backlog unless it is cheap and clarifying.

If the user asked for edits, patch only the owning spec or directly related helper docs. Keep unrelated refactors out of the review loop.

Run local validation such as git diff --check, relevant tests, and targeted rg checks for renamed concepts or stale paths.

Repeat the reviewer pass until every requested reviewer reports no P1 or P2, or until the user stops the loop.

Resources

Read references/review-loop.md for the prompt contract, severity rubric, command matrix, and iteration patterns.

Run this skill's scripts/run-triad-review.mjs --target <path> script, resolved relative to the triangulate-spec-review skill directory, to execute a read-only review round and write normalized JSON output.

Guardrails

Pass raw artifacts and task-local context to reviewers, not intended answers.

Keep every reviewer prompt materially identical unless a tool requires command syntax changes.

Do not let reviewers edit files. The lead agent applies changes after comparing findings.

Do not declare acceptance from an average score. Acceptance requires no P1/P2 findings from the required review surface.