Domain Config Planner: plans the build before anything is built
A request like "add a recruiting process" is not one thing. It needs models for candidates and applications, a page or two, maybe an automation. If a specialised agent starts building without a plan, you get duplicates, or things in the wrong order. Domain Config Planner is the step before. It reads your request, checks the structure you already have, and writes a short plan that the other agents then carry out.
It works inside the configuration assistant. This is how Worknano stays customisable with AI while keeping to core functionality: the result uses the same UI, UX and database as every other module, and it reuses what is there.
What it does
- Looks at the names of your existing models, pages and workflows before it interprets your request, so existing structure wins over assumptions.
- Reuses built-in features instead of duplicating them: comments, attachments, activities, approval, emails and call logs are model extensions, and parent-child lists use related models.
- Plans the smallest coherent set of tasks, each one create or edit, for models, pages and workflows, in that order, with dependencies between them.
- Marks tasks as optional when they are discretionary, and lists exactly which existing items each task needs as context.
- Asks for more context first if it cannot decide without reading one specific item.
- Asks one focused question, with two to four options and at most one recommendation, only when your answer would materially change the result.
When it helps
- A new process. You ask for an onboarding checklist with approvals. The plan says: one model, one page, one workflow, and approval reuses the built-in extension.
- Extending something that exists. You ask for a renewal date on contracts. The plan edits the existing contract model and page and creates nothing new.
- A request with a real fork. Should deals and quotes be one record or two? The planner asks that one question, with options that are possible in your configuration, and then continues.
How it works with your data
Domain Config Planner has no tools. It works from name lists of models, pages and workflows that the assistant supplies, plus the capabilities of your workspace. It never reads your records. It does not change anything: it returns a plan, and the specialised agents, such as Model Designer, Page Creator and Workflow Creator, produce proposals from it. You still review what they produce. Configuration changes are limited to the people allowed to edit configuration.
It uses a balanced model, because planning needs careful reading more than speed.
What it does not do
- It builds nothing. It plans.
- It does not ask about cosmetic choices or invent roles such as a specific approver.
- It will not ask you the same question twice. Answers you gave earlier in the conversation are binding.
Make it yours
Domain Config Planner is a record in the Agents module. You can adjust its instructions to match how your team plans, change the model or temperature, duplicate it, or start blank for your own planner.
Start with Build your own agent, read How to edit a page assistant and a reusable agent for the editor steps, or see the bigger picture in AI agents and AI assistants.