Speccy

Could someone build this without coming back to ask what you meant? Speccy reviews your markdown specs and answers with one verdict, Build Ready or Not Build Ready.

From a blank page to a build packet Review docs you already have

Speccy is one binary: the app, the CLI, the terminal UI and an MCP server. Models find the problems, and a pure function decides the verdict. A doc is Build Ready only when no MUST finding is open.

curl -fsSL https://raw.githubusercontent.com/alternayte/speccy/main/install.sh | sh
cd <the folder with your specs>
speccy

The install script checks the release against its published checksum. speccy opens the app on 127.0.0.1, with no account and no server.

The bundle screen: the control row with the verdict and the next action, the doc with its findings marked, and the findings rail

Finds ambiguity, not only gaps

Three independent readers answer the same build questions from your doc. Where they disagree, the doc is ambiguous. Where none of them finds an answer, the doc has a gap.

Checks the writing in under a second

Fixed rules find placeholders, missing sections, broken links, duplicate trace IDs, filler phrases and long sentences, on every save.

Keeps linked docs honest

An SDD must cover the requirements of the PRD it implements. It must not contradict the PRD, and it must not repeat it.

Verifies the build

After a builder takes the build packet, speccy verify reads the code. It says where each requirement lives and where the code contradicts it.

Where to go next

TutorialsOne doc from a blank page to Build Ready and a build packet, and a PRD with the SDD that implements it.

How-to guidesTasks: adopt a repo, close a coverage gap, ask for a waiver, hand a spec to a coding agent, keep the verdict in CI.

ConceptsHow the verdict, the review pipeline, profiles, waivers and traceability work, and why.

ReferenceEvery check, command, key, input, tool and API operation.