code60

A compile step for your specifications

See how it works Join the waitlist

How it works.

  1. Connect your specifications.

    Connect the GitHub repository that holds your specifications. code60 will extract your requirements regardless of format: user stories, E.A.R.S., Gherkin, an in-house specification format, or unstructured natural language.

  2. Compile your specifications

    Invoke the compiler with your preferred workflow. Trigger code60 manually from the Web UI, through MCP via an agent, or from your GitHub Actions pipeline using the official CLI tool.

    code60 groups related requirements through semantic clustering, identifies duplicates, and flags ambiguous wording that needs clarification.

    It then applies logical checks and deterministic constraint solvers to test whether the modeled rules can hold together, exposing contradictions and impossible outcomes.

  3. Correct your specifications

    Review findings in the web UI, route them through webhooks, or send them straight to your coding agent through Model Context Protocol (MCP).

    Clarify the specs, resolve conflicts, and give your agent better requirements to build from.

See an example

Example

code60 finds three requirements related to refunds in the repository's specs:
custom-orders.md
Once production starts, custom orders are non-refundable.
refunds.md
Every cancelled order must receive a full refund.
cancellation.md
Customers may cancel any order before it ships.
code60 constructs an example to test the requirement:

“A customer cancels a custom order after production starts, but before it ships”

The example shows that the requirements conflict. code60 proposes two possible solutions:

Option A

You must refund this order.

Option B

You must not refund this order.

code60 sends you the options via MCP. You modify cancellation.md to fix the issue:
Customers may cancel orders before shipment, except custom orders whose production has started.