How AI reads your brief

Domain is inferred from the brief—no type picker. How to steer roadmap and tasks.

The AI project builder no longer asks you to pick a preset type. The model infers domain from the chat (SaaS, AI tool, content site, event, internal tool, and so on) and sizes the roadmap to the idea—typically a handful of phases, not a fixed ten-week template.

What still gets stored

Projects still have a projectType field for older rows and analytics. New AI setups store AI; blank boards store Manual. You do not need to manage this for good results.

Steering the model

Domain language comes from the conversation and later from the AI sidebar context (title, description, roadmap, tasks). To change direction:

Ask in the builder chat (“Lean more toward a developer tool than a marketing site”).
Edit the project description and roadmap on the board after create.
Tell the board assistant explicitly (it can call update_project for title, description, and roadmap phases).

When suggestions feel wrong

Symptoms:

Tasks are too marketing-heavy for a backend-heavy build, or vice versa.
Suggestions ignore compliance or accessibility when your domain needs them.

Fix by editing the roadmap/description, nudging via chat, or adding a clearer constraint to the next prompt. Stack and constraints belong in the brief—they are hints, not validators.