How to use AI composers in Vaiz

You know how your team wants to work. Describe it to Vaiz.

“Create a board for our product launch.” “Build an agent that spots work needing attention.” “Show active tasks grouped by stage, with urgent work first.”

Vaiz composers turn requests like these into a proposed setup. Describe the outcome, review what AI prepares, and make it yours. You can start in a dedicated composer, ask the built-in chat, or work through a compatible AI assistant connected to Vaiz MCP. You can also dictate your request.

What is a composer?

A composer is an AI-assisted way to configure part of your workspace using everyday language. You explain what you need; Vaiz translates that description into settings you can inspect and adjust.

A board composer prepares a structure for your work. An agent composer proposes instructions and operating settings. A view composer builds the filters, columns, sorting, and grouping that bring the right tasks into focus.

The useful starting point is your team’s workflow: what comes in, what happens next, and what a good result looks like.

Create a board from a description

Imagine a product team preparing a launch. Engineering tracks delivery on Launch Roadmap, while marketing needs a dedicated place for launch content.

Open Add board, choose Compose, and describe the board:

Create a Content Studio board for our product launch. Use stages Ideas, Writing, Design, Review, and Published. Include task types Article, Video, Newsletter, and Social Post. Add fields for Channel, Target audience, and Asset URL. Keep the setup focused and easy to scan.

Select Generate. Vaiz prepares a board configuration, including a name, groups, task types, and relevant custom fields.

Review the proposal before creating the board. Adjust a stage name or task type if your team uses different terminology, then select Create board and finish the access setup.

The same approach works for an Interview Pipeline in a Customer Discovery project, a Campaign Calendar for a marketing team, or a Client Delivery board for an agency. Describe the stages and information that matter to that team.

Create an agent around a clear job

An effective agent starts with a specific responsibility. Tell it what to inspect, when to run, and what result you expect.

Open Agents, start creating an agent, and choose Compose. For a launch briefing, try:

Create an agent named Launch Briefing for Product Launch. Run only when I request it manually. Review Launch Roadmap and summarize urgent work, upcoming deadlines, tasks waiting for review, and missing owners. Return a concise briefing with task links and three recommended next steps. Read-only: do not edit tasks, send messages, or contact external services.

Vaiz proposes an agent configuration. Review its instructions, trigger, scope, mode, and permitted actions. In this example, the proposal uses a manual trigger and a report-only setup scoped to Launch Roadmap.

Choose Edit manually to refine the settings, or Create to save the agent. The next screen offers a test of the saved configuration.

Be explicit about the level of autonomy you want. “Summarize and recommend” and “update the tasks” describe different jobs.

Ask for the view you need

A busy board can support several useful perspectives. A delivery lead wants active work. A reviewer wants the review queue. A contributor wants their own priorities.

Open a task list and select Compose view. Describe both the tasks and how you want to see them:

Show open tasks in In Progress and In Review. Group by status. Display task name, ID, assignee, priority, and due date. Sort by priority with urgent work first. Hide completed tasks.

Select Generate view. Vaiz applies the proposed view to the list. In our launch workspace, this brings 15 active tasks into a Launch Focus view, with the two stages separated and urgent work at the top.

The view composer handles the VDL settings behind the view. You can describe filters, visible columns, sort order, and grouping in one request, then inspect or adjust the result in View settings.

Try these perspectives on the same work:

You do not need to learn VDL syntax to get started. Describe the question your view should answer.

Use the built-in chat or Vaiz MCP

Composers are part of a broader way of working with Vaiz: ask for an outcome in the interface that fits the moment.

The built-in chat can help set up projects and boards and prepare tasks from a conversation. For example:

Set up a Customer Discovery project with an Interview Pipeline board. Add stages for recruiting, scheduling, interviews, synthesis, and validated insights. Include fields for customer segment and research theme.

Review the proposed structure and select Apply setup to create it.

Through Vaiz MCP, a compatible external AI assistant can also create and configure workspace structure using the tools and permissions available to its connection. Ask for the project, boards, and starter tasks in the same way you would describe them to a teammate.

The exact actions depend on the connected assistant and the tools it has access to. Your request still begins with what you want to accomplish.

Say it out loud

Board, agent, and view composers include Dictate. Use the microphone to turn your spoken description into a request, check the text, and generate the result.

Voice input is useful when the process is easier to explain than to type:

We need a content board. Ideas become drafts, then go through design and review before publishing. Track the channel and audience for each item.

You can also use voice input in the built-in chat. With an external MCP-connected assistant, use that assistant’s voice features where available.

Make your first request

A helpful request includes three things: the outcome, the relevant context, and the constraints.

“Create a board” is a starting point. “Create a content board for our product launch, with five stages, four content types, and fields for channel and audience” gives Vaiz a much clearer job.

Start with one board, one agent, or one useful view. Describe it, inspect the result, and refine it as your team works.

Ask, not configure.