Feature

Questions first,then code.

Adams stops a vague request from turning into the wrong build, by asking the few questions that change the result.

Pro
// the problem

What goes wrong

A guess looks like progressA short request leaves a lot open: who it is for, what is out of scope, what must not change. An AI fills each gap with a guess and keeps going. You find out an hour later.
Rework costs more than askingUndoing a wrong build means reading code you never wrote. A two minute question at the start is cheaper than an afternoon of reverse engineering.
// what adams does

What Adams does

Looks up what it canAdams reads your docs, code and config first. It asks only about decisions, taste, access and money, never about facts it can find.
One round, at most four questionsEach question carries a recommended answer and a one line reason, so a plain yes settles it.
Records what you settledThe answers become a short spec. Later steps are held to it, so the build matches what you agreed.
// worked example

An example

A request that is too short

Illustrative session. Wording differs by project.

~/project~/your-project · example
Add a way for customers to book a call
1. Paid or free calls? (recommended: free first)
2. Use your calendar or a simple form? (recommended: form)
3. Who gets the email when someone books?
✓ Spec saved, building to it
// faq

Questions

Does it ask on every message?

No. A clear, small, reversible task goes straight through with one stated assumption. It asks when a task has several readings or is costly to undo.

Can I skip the questions?

Yes. Answer yes to accept every recommendation, or type your own answer to any question.

Is this Lite or Pro?

Asking before building is a Pro feature. Lite keeps the secret, git and leak guards and the basic text check.

// related

Keep reading