PreCode

Planning layer - before the first line of code

PreCode

PreCode

Most founders start building before the idea is clear. PreCode slows that first step down, turns the mess into structure, and gives your coding tools something real to follow.

Join the waitlistSee the output
  • Guided interview
  • Traceable package
  • Works with your tools
The problem

AI coding tools are extraordinary. But they depend on you knowing what to build, and most founders don't. Bad architecture isn't a code problem. It's a thinking problem that shows up later, six rewrites deep, wondering where it all went wrong.

Process

Four acts.
One foundation.

01 - 04
01

Capture the idea

Name the product, who it's for, and the problem it solves. Every later answer builds on this.

InputRough idea in plain English
02

Answer the right questions

A structured interview across scope, roles, data, auth, and edge cases - the questions engineers know to ask.

EngineGuided interview framework
03

Export the blueprint

A Markdown documentation package, machine-readable and agent-ready. Drop it into Cursor, Claude Code, or Codex.

OutputStructured doc package
04

Build and verify

Hand the package to @precode/mcp on npm. It builds in phases, checks each one against the spec, fixes what drifted, and tells you what is left for you.

LoopBuild, check, fix, repeat
What you walk away with
11 linked docs / one build-ready system

Not a prompt.
A package.

Human-readable specs, execution docs, trace files, and a compact MCP handoff. Together they give your coding agent the full picture: scope, requirements, architecture, tasks, acceptance, and verification - before a single component is written.

  • PRODUCT_BRIEF.mdscope
  • REQUIREMENTS.mdrequirements
  • ARCHITECTURE.mdarchitecture
  • UX_FLOW.mdui
  • DATA_AND_API.mddata
  • TASK_GRAPH.mdtasks
  • ACCEPTANCE_MATRIX.mdverify
precode-output / REQUIREMENTS.md
# MVP scope
───────────────────────
Auth: email/password (MVP)
Roles: Creator, Buyer
───────────────────────
# Core flow
Creator → uploads template
Buyer → browses + purchases
───────────────────────
# Out of scope
- Subscriptions (later)
- Mobile app (later)
───────────────────────
# Agent instructions
Build server actions first.
Match schema in schema.sql.
Do not add Stripe yet. █

You have the docs. Now hand them to the loop.

PreCode MCP

It builds. Then it checks its own work.

@precode/mcp is on npm for the build loop: one task, one check, one fix at a time. Works with any spec format; optimized for PreCode documentation packages.

Task

Reads the plan and gives the agent one focused build step.

Check

Runs the project checks before anything gets marked done.

Ledger

Records finished work, drift, and anything human-only.

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

Bring the package to the tools you already build with.

Bring Markdown docs into the tools you already build with. PreCode stays upstream - your build process stays yours.

Waitlist

Join the waitlist

Tell us how you want to use PreCode. 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