What is speckit.testreview?

A read-only review command for checking whether feature specifications can be tested effectively.

Use it after a complete task plan exists to review specification, plan, and task files, following the project's constitution and reporting issues without editing files.

It finds vague acceptance criteria, missing test coverage, and fixtures or contracts that may be impractical before implementation begins.

How unbound-force/gaze configures Claude Code and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to unbound-force/gaze. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/unbound-force/gaze/main/.opencode/commands/speckit.testreview.md

Clone the repo

git clone --depth 1 https://github.com/unbound-force/gaze

Made for: Claude Code, OpenCode.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/unbound-force/gaze/speckit.testreview/github.svg)](https://agentmods.dev/commands/unbound-force/gaze/speckit.testreview)

Your own site

<a href="https://agentmods.dev/commands/unbound-force/gaze/speckit.testreview"><img src="https://agentmods.dev/badge/commands/unbound-force/gaze/speckit.testreview/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/unbound-force/gaze/speckit.testreview"><img src="https://agentmods.dev/badge/commands/unbound-force/gaze/speckit.testreview.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,228 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00025	$0.01228
Opus 5.5	$0.00010	$0.00491
Sonnet 5.5	$0.00005	$0.00246
Haiku 4.5	$0.00003	$0.00123

Measured 6d ago against content hash 7a5c931ae3e0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

speckit.testreview scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.opencode/commands/speckit.testreview.md · 140 lines

How it starts

The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Goal

Assess the testability of feature specification artifacts (spec.md, plan.md, tasks.md) through a dedicated testing lens. This command identifies vague acceptance criteria, missing coverage strategy, undefined contract surfaces, and infeasible fixture requirements — issues that cause rework if discovered only during implementation. This command MUST run only after /speckit.tasks has successfully produced a complete tasks.md.

Operating Constraints

STRICTLY READ-ONLY: Do not modify any files. Output a structured testability analysis report. Offer an optional remediation plan (user must explicitly approve before any follow-up editing commands would be invoked manually).

Constitution Authority: The project constitution (.specify/memory/constitution.md) is non-negotiable within this analysis scope. Constitution Principle IV (Testability) violations are automatically CRITICAL. Missing coverage strategy is CRITICAL. These require adjustment of the spec, plan, or tasks — not dilution of the principle.

Execution Steps

1. Initialize Analysis Context

Run .specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks once from repo root and parse JSON for FEATURE_DIR and AVAILABLE_DOCS. Derive absolute paths:

SPEC = FEATURE_DIR/spec.md
PLAN = FEATURE_DIR/plan.md
TASKS = FEATURE_DIR/tasks.md

Abort with an error message if any required file is missing. Instruct the user to run /speckit.tasks first if tasks.md is absent, or /speckit.specify if spec.md is absent.

For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot").

2. Load Artifacts (Progressive Disclosure)

Load only the minimal necessary context from each artifact:

From spec.md:

User Stories with acceptance scenarios
Functional Requirements (FR-xxx)
Success Criteria (SC-xxx)
Edge Cases
Assumptions

Read the full file on GitHub · 140 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

6d ago Changed · -1 lines · +2 tokens per session 7a5c931ae3e0
1mo ago Changed · +1 lines 47ca27e0721e
2mo ago First seen · 140 lines · 23 tokens per session scan A 1d078f54f3fd

Subscribe to this mod's changes

speckit.testreview is a command published in the GitHub repository unbound-force/gaze (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 25 tokens to every session and 1,228 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Testing

speckit.testreview next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
speckit.testreviewunbound-force/gaze	Command	4	yesterday	Apache-2.0	A	25	Claude Code, OpenCode
prototypegrainulation/grainulator	Command	86	yesterday	MIT	A	0	Claude Code
qa-changesOpenHands/extensions	Command	176	yesterday	MIT	A	63	Claude Code
verifycloudnative-co/claude-code-starter-kit	Command	153	25d ago	MIT	A	9	Claude Code
modernize-transformfuxicodex/Fuxi	Command	3.2k	17d ago	none	A	17	Claude Code
constraintsvinvcn/addyosmani-agent-skills-zh	Command	46	17d ago	MIT	A	20	Claude Code
check-devpunt-labs/z-spec	Command	5	yesterday	MIT	A	7	Claude Code

gaze: Command for Claude Code