PreCode

Proof layer for AI-built softwarePreCode

Turn messy product intent into structured plans, hand them to any coding agent, and get verifiable proof that what shipped matches what was agreed, posted where your team already reviews.

Join the waitlistSee the proof trail
  • Intent to proof
  • Agent-neutral
  • CI-verified delivery

The problem

AI agents ship code fast. But "done" is still self-reported: no link from customer intent to what actually merged, no acceptance criteria that compile into checks, no proof in the pull request or ticket where review already happens. Trust breaks when founders, clients, and stakeholders cannot see what was verified and what was assumed.

Process

Five acts.
One proof trail.

01 - 05
01

Capture intent

Start with the idea, the user, and the evidence behind it: customer notes, tickets, or plain English. PreCode keeps signal attached so nothing gets lost in translation.

InputEvidence + intake
02

Structure the plan

A guided interview turns ambiguity into scope, requirements, architecture, tasks, and acceptance criteria: linked docs with provenance, not a one-shot prompt.

Engine11-doc package + trace
03

Hand to your agent

Export a build-ready package and connect @precode/mcp in Cursor, Claude Code, Codex, or any MCP host. Any agent builds; PreCode stays the source of truth.

Handoff.precode/ + MCP loop
04

Verify the build

Acceptance criteria compile into checks. Delivery tickets bind to PRs. PreCode reads CI verdicts against what merged, not what the agent claims locally.

GateChecks + CI verdict
05

Deliver proof

A proof report lands in the PR, ticket, or status check: evidence to spec to acceptance to bound PR to CI to what was verified. One artifact stakeholders can read.

ProofPROOF.md + trace/proof.json
What you walk away with
11 linked docs + trace + verification scaffolds

Not a prompt.
A proof-ready system.

Human-readable specs, execution docs, acceptance matrices, and machine-readable trace files. Together they give your agent the full picture, and give PreCode enough structure to verify what ships against what was agreed.

  • PRODUCT_BRIEF.mdscope
  • REQUIREMENTS.mdrequirements
  • ARCHITECTURE.mdarchitecture
  • TASK_GRAPH.mdtasks
  • ACCEPTANCE_MATRIX.mdacceptance
  • trace/acceptance.jsonchecks
  • PROOF.mdproof
precode-output / ACCEPTANCE_MATRIX.md
# AC-12 · Login redirect
───────────────────────
Given: authenticated user on /login
When: form submits successfully
Then: redirect to /app (not /)
───────────────────────
# Bound check
test: e2e/auth-login.spec.ts
compile: scaffold → runnable gate
───────────────────────
# Delivery link
ticket: DEL-042 → PR #118
ci: pending until merge █

Planning is the setup. Proof is the product.

Verification

One trail from intent to CI.

PreCode binds evidence to requirements, requirements to acceptance checks, checks to delivery tickets, tickets to merged changes, and CI verdicts to what shipped, then posts proof where review already happens.

  1. 01

    Intent

    Evidence and requirements stay linked

  2. 02

    Acceptance

    Criteria compile into runnable checks

  3. 03

    Delivery

    Tickets bind to the PR that built them

  4. 04

    CI verdict

    Verification reads what actually merged

  5. 05

    Proof

    Report posted to PR / ticket / check

trace/proof.json · excerpt
feature: user-auth
evidence → REQ-12 → DEL-042
acceptance: AC-12, AC-13
pr: #118 merged @ a3f9c2
ci: typecheck ✓ e2e ✓ proof ✓
verified: 2/2 acceptance items
→ posted: PR / ticket comment
need_met: pending review

Your agent builds. PreCode verifies.

PreCode MCP

Checks run. Proof gets delivered.

@precode/mcp on npm runs the build-and-verify loop: one task, real checks, delivery binding, CI verdict, and proof posted where review already happens. Works with any spec format; optimized for PreCode packages.

Bind

Links each delivery ticket to the PR that implements it.

Verify

Reads CI verdicts and acceptance coverage for what merged.

Deliver

Posts proof into the PR, ticket, or status check.

precode-mcp / verify

Example verify_delivery run: bind a delivery record, run CI checks, fix acceptance gaps, post proof to the PR, ticket, or status check.

$ precode verify_delivery
█
precode-mcp / install
$ npm i -g @precode/mcp
.cursor/mcp.json
{
  "mcpServers": {
    "precode": {
      "command": "precode-mcp",
      "env": {
        "PRECODE_TELEMETRY_DISABLED": "1"
      }
    }
  }
}

Read MCP docs

Works with

Any agent. Any delivery stack you already use.

PreCode is agent-neutral through MCP and tool-neutral through provider adapters: GitHub, GitLab, Linear, Jira, or a manual summary when you need it.

Waitlist

Join the waitlist

Tell us how you want to use PreCode - planning, agent handoff, or delivery verification. We'll use this to prioritize onboarding and follow up when it's your turn.

Join the waitlist

We store your email with this request. No payment info.

Start here

Get on the list
before we open the doors.

Join the waitlist and we'll reach out when it's your turn.

Join the waitlist