🚀 Now in Public Beta

Review AI-Assisted Code
Before Drift Reaches PR or Main.

SpecFact is an open-source CLI for developers and teams shipping with AI. Start with a zero-install review that checks code against contracts, tests, and policy gates. Add IDE prompts, project bundles, and CI enforcement when you want a deeper workflow — without moving to a new platform.

Run the 60-Second Review View GitHub README

Use uvx for a fast first run. Install with pip when you want a stable specfact command and AI IDE slash commands.

Zero-install review

# README quick start
uvx specfact-cli init --profile solo-developer
uvx specfact-cli code review run --path . --scope full

Installed CLI + AI IDE workflow

# Stable local CLI + slash commands
pip install specfact-cli
specfact init --profile solo-developer
specfact init ide --ide cursor --install-deps

# Then in your IDE chat
/specfact.01-import my-project

Same CLI. Two ways to engage.

SpecFact is open source and built for teams shipping with AI. Choose self-serve to move fast, or talk to us when you need contracts, NDAs, and a partnership for your workforce and AI fleet.

Start fast

Startups & smaller teams

For fast-moving teams that want to adopt SpecFact without procurement overhead.

  • Install in minutes, Apache 2.0, no vendor lock-in
  • Docs, GitHub, and community when you want answers
  • IDE slash commands and CI when you are ready to scale checks
Get started Read the docs GitHub Discussions
Enterprise partnership

Mid-market & enterprise

For organizations that need a formal relationship before rolling SpecFact out broadly. Most engagements start with a scoped proof of concept (PoC) or proof of value (PoV) before any larger commitment.

  • PoC and PoV engagements as the usual first step: validate fit on a real repo or team before fleet-wide rollout
  • NDAs, MSAs, and security reviews as part of how we work together
  • Partnership for AI governance, policy, and workforce-scale adoption
  • Roadmap input and support aligned to your compliance and procurement process
Discuss PoC, PoV, or partnership

Not sure? Start with the open-source CLI and docs. For enterprise, most teams begin with a PoC or PoV, then NDAs and broader rollout when it makes sense. Use Discuss PoC, PoV, or partnership to start that conversation.

Why SpecFact?

Developer-first by default: start with fast local review, then expand into project, backlog, and governance workflows when your team actually needs them. Works for new projects and existing code.

🔄

Everything Stays Aligned

Specs, tests, and code stay in sync; add backlog sync when you use that workflow. Works with GitHub, Azure DevOps, Jira, Linear. When you or AI change code, the rest stays aligned — so nothing breaks in production.

🏗️

New Projects & Existing Code

Starting from scratch or improving what you already have? Turn existing code into specs and automatic checks, or start from specs — your choice. No jargon, no lock-in.

🔒

Automatic Checks

What's built stays aligned with what was planned. Ready-for-sprint and definition-of-done style checks. Catch mismatches before they reach production.

👥

Grows from Solo to Team

Start as a developer with local review and validation. Add product, planning, and governance workflows later without replacing the core CLI path.

🤖

Where You Already Work

Runs in your AI IDE (Cursor, VS Code, Copilot) and in CI/CD. No new platform. One toolkit that fits into your stack.

🔗

Connects Your Tools

Specs (Spec-Kit, OpenSpec), backlogs (GitHub, Azure DevOps, Jira, Linear), and checks (Specmatic, OpenAPI). One toolkit, your tools.

⚡

Get Value in Minutes

Run one command and get a project bundle in under a minute. Or use slash commands in your AI IDE. No lengthy setup.

🔄

Fits Into CI/CD

GitHub Actions and other pipelines. Start in observe mode, then turn on enforcement. Roll out step by step with full visibility.

How It Works

Start with one fast review, then expand into IDE workflows, project bundles, and team gates only when you need them. The command path stays clear at every stage.

01

Start with a Scored Review

The fastest path is CLI-only: no pip install, no IDE setup, just a deterministic review on a real repo.

# Zero-install path
uvx specfact-cli init --profile solo-developer
uvx specfact-cli code review run --path . --scope full
02

Install Once for IDE Workflows

When you want a stable local command, project bundles, and AI IDE prompts, move to the installed CLI path.

# Stable local CLI + IDE prompts
pip install specfact-cli
specfact init --profile solo-developer
specfact init ide --ide cursor --install-deps
specfact code import my-project --repo .
specfact project health-check
03

Add Team Gates When Ready

Bring the same workflow into planning, sync, and CI without changing tools. Start light, then enforce more as confidence grows.

# Optional team and CI workflow
specfact module install nold-ai/specfact-backlog
specfact backlog verify-readiness --bundle my-project
specfact project sync bridge --adapter github --bundle my-project --mode export-only
specfact govern enforce stage --preset balanced
specfact code repro --verbose

One CLI, Two Clear Paths

Start with a zero-install review via uvx, or install the CLI when you want specfact, IDE slash commands, project bundles, and team workflows. Both paths stay local-first and fit into your existing IDE and CI/CD setup.

CLI-only quick start
uvx specfact-cli@latest --help
Installed CLI + IDE
pip install specfact-cli
Open Quickstart
Installed CLI examples
$ specfact init --profile solo-developer # Bootstrap the installed CLI path
$ specfact init ide --ide cursor --install-deps # Add slash commands and IDE prompt templates
$ specfact code import my-project --repo . # Analyze an existing repo into a project bundle
$ specfact project health-check # Summarize what the import discovered
$ specfact module install nold-ai/specfact-backlog # Add backlog workflows when your team needs them
$ specfact backlog verify-readiness --bundle my-project # Run readiness checks before planning or delivery
$ specfact project sync bridge --adapter github --bundle my-project --mode export-only # Sync outward to GitHub when you want bridge workflows
$ specfact govern enforce stage --preset balanced # Move from observe mode to stronger CI enforcement

Start in 60 Seconds

Start with the same two-line quick start used in the CLI README. No API keys, no hosted account, and no install ceremony just to see whether the review is useful on your codebase. 

uvx specfact-cli init --profile solo-developer
uvx specfact-cli code review run --path . --scope full
Open Quickstart Docs View GitHub README

What you can do next:

  • Start with `uvx`, then install with `pip` when you want a stable `specfact` command
  • Turn an existing repo into a project bundle with `specfact code import`
  • Run scored code review, health checks, and validation locally before PR
  • Add GitHub and CI workflows only when your team is ready
  • Use AI IDE slash commands in Cursor or VS Code after `specfact init ide`

Need enterprise support? Contact us