The requirement clarification chat is the chat-first entry point of Ottili Coder. Instead of a free-text objective, you describe what you want and Coder asks only the questions that actually change the build, offers sensible defaults, persists your answers, and ends in a plan-ready mission.
What it does
- Asks only build-changing* questions (repository, auth, database, language, roles, deployment, acceptance criteria).
- Offers sensible defaults* as one-click options.
- Persists answers* across turns so revising an earlier answer just re-normalizes the mission.
- Ends in a plan-ready requirements contract* (
ready to build) — not endless chat.
Where it lives
Open New Build → Chat Intake* in the dashboard. The chat returns a mission card with intent, complexity, build mode, confidence, and clarifying questions; when nothing is missing it flips to Ready to build* with *Review technical plan* and *Start build*.
Full reference
The complete contract — endpoints, request/response schemas, the mission lifecycle, the question registry, examples, migration & rollback, limits, known issues and the release-acceptance checklist — is in the engineering reference:
[Requirement clarification chat — capability spec](/docs/ottili-coder)
Was this article helpful?