Index of every page on this site: llms.txt
All skills
qoderai avatar

/triangulate-spec-review

@c6240a8
by qoderaiqoderai/better-harness2.5k stars
208
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/qoderai/better-harness/triangulate-spec-review

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈84 tokens for metadata: the name and description. ≈523 when used: this file. ≈654 more on demand in 1 file.

Description uses 4.2% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈335 characters, or 4.2%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning3mo3 checks · Risk MEDIUM
  • Gen Agent Trust Hub3mo

    The skill executes external CLI tools (claude, qodercli, agent, codex) with flags that bypass user permissions and trust prompts. It also contains logic that could allow local command execution via unsanitized arguments passed to child processes.

  • Socket3mo

    No alerts

  • Snyk3mo

    Risk: LOW · No issues

Signed by skilld at c6240a8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 4 months ago

README badge

README badge for qoderai/better-harness/triangulate-spec-review