Specs aren’t just documentation anymore.

Spectagon brings peer review to the specs your agents build from.

Specs belong in the code.

We’ve said “docs should live with the code” for decades. But Google Docs and wikis were easier to collaborate on, so that’s where specs ended up.

That changed when agents started building from specs.

Now the spec lives in the repo — and because it’s what actually gets built, it doesn’t go stale.

But reviewing specs in git is terrible.

GitHub’s review experience was built for code — diffs, line numbers, side-by-side views.

So you paste the spec into Notion or Google Docs for review — and the two versions drift out of sync immediately.

Peer review for technical specs.

Structured feedback, inline comments, and clear approvals — all connected to your existing workflow.

Feedback that follows your rewrites.

When you revise a section — by hand or with an agent — comments intelligently re‑anchor to the content they’re about.

A lens on your GitHub PR.

Spectagon reads your markdown through the GitHub API and adds a review layer on top. The link gets posted right on your PR. Your specs stay in git where they belong.

Comments & suggestions.

Inline comments, threaded discussions, and suggest mode — propose specific text edits that authors accept with one click.

Rendered for reading.

Mermaid diagrams, syntax-highlighted code blocks, clean typography. Your markdown looks like a published document, not a raw file.

Approval flow.

Approve, merge, and track review status without leaving Spectagon. Status check posted to your PR.

Your specs never leave GitHub.

Spectagon is a read-only lens. If you stop using Spectagon, your documents are exactly where they always were, with all review activity preserved on the PR.

The spec is where humans shape the outcome.

With Spec-Driven Development, agents implement the spec literally — every ambiguity, overlooked edge case, and gap gets faithfully reproduced.