---
name: triangulate-spec-review
description: 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.
title: triangulate-spec-review
canonical_url: https://skilld.dev/gh/qoderai/better-harness/triangulate-spec-review
last_updated: 2026-10-07T00:09:43.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/review-loop.md](https://skilld.dev/api/skills-raw/qoderai/better-harness/triangulate-spec-review/references/review-loop.md), [scripts/run-triad-review.mjs](https://skilld.dev/api/skills-raw/qoderai/better-harness/triangulate-spec-review/scripts/run-triad-review.mjs).
>
> If the user asked to install this Skill, run `npx skilld install qoderai/better-harness/triangulate-spec-review`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/triangulate-spec-review`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/qoderai/better-harness/triangulate-spec-review) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/triangulate-spec-review`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/triangulate-spec-review --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/triangulate-spec-review --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# 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

1. Resolve the target spec path and the acceptance gate. If the user did not
   name dimensions, default to `complexity`, `convenience`, and `evolution`.
2. Read the target spec and nearby repo instructions. Do not pass your suspected
   fixes or conclusions to reviewers.
3. Use the same read-only prompt for every reviewer. Ask for structured
   `P1`/`P2`/`P3` findings and a `p1_p2_clear` boolean.
4. Run at least two reviewers; prefer three when available. Use
   `scripts/run-triad-review.mjs` for repeatable local runs.
5. 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.
6. If the user asked for edits, patch only the owning spec or directly related
   helper docs. Keep unrelated refactors out of the review loop.
7. Run local validation such as `git diff --check`, relevant tests, and targeted
   `rg` checks for renamed concepts or stale paths.
8. 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.
