ntent
Find what your client hasn't told you, and get the answer before you build.
Software delivery teams build from documents they did not write: RFPs, scope workbooks, and call transcripts. Every brief contains unstated assumptions and contradictions. When those gaps reach implementation unresolved, both human developers and coding agents fill them with guesses.
ntent runs before implementation begins. It parses client source documents into a structured model, isolates undecided rules and conflicts as multiple-choice questions, collects stakeholder answers via a single web link, and exports a verified brief to coding agents and issue trackers.


Origin
ntent started as an internal set of repository validation scripts for coding agents. While applying those scripts to client delivery projects, we found that most defects originated upstream in the requirements documents rather than in code generation.
On a client portal build, we extracted 55 open questions from the RFP and workshop notes and sent them to the client on a single web link. Three stakeholders answered 52 questions asynchronously in 45 minutes. Nine answers directly changed project scope: one screen moved out of v1, authentication shifted to a later phase, and offline storage and data retention rules received explicit numerical limits. Two answers surfaced direct contradictions between the commercial workbook and the workshop transcript.
We packaged that workflow into ntent. Rather than competing with coding agents like Claude Code, Cursor, or Lovable, ntent supplies them with a verified specification.
The six-stage workspace
Each project progresses left to right across six tabs: Sources, Model, Questions, Sets, Review, and Versions. Live badge counts on each tab show how many items await ingestion, stakeholder replies, or team sign-off.


When source documents are uploaded, Claude extracts a structured five-part model: actors and roles, user journeys, business rules, data entities, and screens. Every item in the model carries 1 to 3 supporting quotes from the uploaded documents. The backend verifies each quote character-for-character against the source text and records its exact character offsets. Any quote that fails substring verification is flagged as unverified, preventing fabricated rules from being marked as confirmed facts.


Structured questions for fast stakeholder replies
Every open item or cross-document conflict in the model generates a structured question. Each question specifies the target stakeholder role, a plain-English prompt capped at 20 words (enforced by an automated length check), a context line quoting the source document, 2 to 5 closed multiple-choice options, and an explicit “We do not know” option.
In controlled trials comparing this format against traditional open-ended prose questions, completion time dropped from 42 minutes to 20 minutes, and total words typed by stakeholders dropped from 1,407 to 177.


One link, no account required
The delivery team groups questions into a shareable set and sends a single URL or QR code to the client. Stakeholders enter their name once and tap through the options; every selection saves immediately. Responses stream back to the delivery team’s workspace within a minute, grouped by question and respondent.


Human-gated review
Stakeholder answers never mutate the specification automatically. In the Review tab, each incoming response is paired with the model rule it affects and sorted by priority:
- Conflicts: Two stakeholders selected different answers for the same question.
- Needs a reply: A stakeholder selected “We do not know” and the question must be re-routed.
- Model updates: Agreed answers ready to be merged into the specification.
Claude drafts the proposed rule update from the stakeholder’s answer, and the delivery lead commits one of three actions: Apply to model, Keep current rule, or Send follow-up on the same client link.


Version snapshots, exports, and MCP integration
Locking a version records an immutable snapshot with a SHA-256 content hash and attribution for the client stakeholder who signed off. Each locked version exports to six formats:
INTENT.mdfor repository root context- An
AGENTS.mdrules block intent.json(typed machine-readable schema)- Lovable project knowledge format
- CSV for importing stories into Jira or Linear
- A formatted Word/Markdown requirements document for client sign-off


Any question that has not yet been answered by the client is exported with an explicit status: "open" marker. In a 90-run benchmark comparing prose briefs against exported ntent models across 20 stated facts and 10 unstated gaps, coding agents reading prose silently invented behavior that contradicted the client in 13 of 30 runs (43%). When reading the ntent export where those same gaps were marked open, agents contradicted the client in 0 of 30 runs.
Coding agents also connect directly to ntent over the Model Context Protocol (MCP). Agents read the latest locked version and, when they encounter an unstated edge case during implementation, post a structured question back into the delivery team’s Question queue rather than guessing.


Core product rules
- Zero friction on the client link. Stakeholders never see the internal model or create an account. They open one URL, type their name, and tap answers on their phone.
- “We do not know” is a first-class answer. Giving stakeholders an honest opt-out prevents guessed answers and lets the team route the question to the domain owner who actually knows.
- Humans approve every spec change. AI drafts the model and proposes updates from client answers; a person on the delivery team approves every mutation.
- Unanswered gaps stay visibly open. Undecided rules ship marked
openin every export so downstream builders pause and ask instead of inventing defaults. - Fit existing toolchains. Exports drop directly into Claude Code, Cursor, Lovable, Jira, and Linear without custom plugins.
ntent is live at ntent.app, built with Next.js, Supabase with row-level security, and the @ntent/tokens design system across light and dark modes.