Use Composer to Build with User Stories

This page explains how to use the Board tab in the Build view to track and execute user stories with Composer.

About the Board tab

The Board tab becomes available when you click START BUILDING in the Plan view to move from planning to building. The board populates with the user stories you defined in the Stories tab, so the board is empty until you start building.

Once populated, the board organizes user stories by development status, giving you a visual way to track development progress. Accessing the Board tab requires Editor or Administrator permission for the application.

Scroll or drag to pan · ⌘+/⌘− to zoom · Esc to close

From the board, Composer can generate dependency-ordered tasks for each story and executes them in sequence. Because Composer has full context from your plan—including story descriptions, acceptance criteria, and existing application objects—it produces more predictable results than using Composer to build without a plan. This story-driven approach gives you a structured, repeatable workflow from requirements to working design objects.

Stories on the Board tab

A story is a unit of work on the board. Each user story from the Stories tab appears as a card in a status column, carrying all its planning context—description, acceptance criteria, type, and persona—from the Plan view into the Build view, where you implement it.

Story statuses

The board organizes user stories into four status columns:

Column	Description
To Do	User stories that have not started development. User stories moved from the Plan view appear with this status by default.
In Progress	User stories actively being developed.
In Review	User stories with completed development that are awaiting review.
Done	User stories with completed and reviewed development.

Story card information

Each story card on the board displays the following details.

Scroll or drag to pan · ⌘+/⌘− to zoom · Esc to close

#	Description
1	The name of the user story.
2	The parent activity the user story is associated with in the story map. For example, if the activity is "Onboard Employee" and the story name is "Submit Onboarding Form," the card displays both so you can identify which part of the plan the story belongs to.
3	The icon representing the user story's action type. For example, AI Process, Automated Process, or User Action.
4	A unique identifier for the user story, combining the application prefix and a sequential number. For example, HR-1, HR-2, HR-3.
5	A progress indicator showing the number of completed tasks out of the total tasks for the user story. This icon only appears if the user story has tasks.
6	The user assigned to the story. When you have Composer execute tasks from a story, it executes using your username.

Manage stories on the Board

User stories contain all the planning context from the Plan view, plus additional fields for tracking development progress. You can view and edit the user story details, delete stories, and change their status.

View story details

The story detail view shows a user story's planning context plus fields for tracking development.

To view user story details:

1. In the Build view, go to the Board tab.

2. Click a user story.

   The story detail view displays the following fields:

   Field	Description
   Description	A detailed explanation of what the story accomplishes.
   Acceptance criteria	The conditions that must be met for the story to be considered complete.
   Assignee	The developer responsible for implementing the story.
   Priority	The designated build priority (High, Medium, Low).
   Story points	The estimated effort for the story.
   Status	The current development state (To Do, In Progress, In Review, Done).
   Type	The action type from the Plan view.
   Persona	The user role associated with the story.
   Tasks	The task breakdown for implementing the story. You can generate tasks or manually create tasks. If the story already has tasks, click RUN TASKS to execute tasks with Composer.

3. Click Board to return to the full list of user stories.

Edit a story

You can edit a user story in two ways: prompt Composer in the chat pane to make changes conversationally, or edit the fields manually. Use Composer when you want to describe a change in plain language or update several fields at once. Edit manually when you want direct control over a single field.

To edit a story using Composer:

1. In the Build view, go to the Board tab.
2. Open the user story.
3. Enter your request in the chat. For example, "Set the priority to High and add an acceptance criterion for mobile support." Composer applies the change directly, so you don't need to save.

To edit a story manually:

1. In the Build view, go to the Board tab.
2. Hover over a story and click .
3. Update any of the story fields.
4. Click SAVE CHANGES.
5. Click Board to return to see the full list of user stories.

Update story status with drag and drop

To change a story's status, drag the story card from one column to another on the board. The card's position updates immediately to reflect the new status.

Scroll or drag to pan · ⌘+/⌘− to zoom · Esc to close

Delete a story

To delete a story:

1. In the Build view, go to the Board tab.
2. Hover over a story and click .
3. Click DELETE.

Manage tasks

Tasks represent the implementation plan for a story. When you review the story details, you can see all tasks associated with it. Each task displays a tag indicating whether it creates a new design object or updates an existing one.

The task list follows a sequence. Each task must be completed before the next task in the sequence can start, because later tasks depend on design objects created in earlier tasks. Composer generates tasks in the correct dependency order, but you can rearrange the sequence by dragging and dropping tasks within the task list. The new order determines the execution sequence.

Scroll or drag to pan · ⌘+/⌘− to zoom · Esc to close

Generate tasks

Before Composer can start working on a user story, it needs to understand the tasks involved in the user story. Composer can generate a task list, analyzing the user story against existing application objects, so it produces a dependency-ordered task list.

To generate tasks:

1. In the Build view, click BOARD.
2. Click a user story to open the story detail view.

3. In the Tasks section, click GENERATE TASKS. Composer creates a plan to generate the tasks.

   

   Scroll or drag to pan · ⌘+/⌘− to zoom · Esc to close

4. Click Begin Execution in the chat pane.

The tasks appear as Composer creates them.

Regenerate tasks

You can regenerate the task list for a story if your requirements have changed or you want a fresh plan.

To regenerate tasks for a story:

1. In the Build view, click BOARD.
2. Click a user story to open the story detail view.
3. In the Tasks section, click REGENERATE TASKS.
4. In the confirmation dialog, click REGENERATE.

Composer replaces all To Do tasks with a newly generated breakdown. Tasks that are Done remain unchanged.

Manually create a task

If you have a specific task in mind or an ad hoc request, you can create a task yourself.

To manually create a task for a story:

1. In the Build view, click BOARD.
2. Click a user story to open the story detail view.
3. In the Tasks section, click CREATE TASK.
4. In the Create Task dialog, enter the following details:
   • Name: A descriptive name for the task.
   • Status: The initial status (defaults to To Do).
   • Implementation Notes: A description of what the task should accomplish.
   • Design Object: Keep Create new selected to create a new object, or choose Select existing to link an existing object.
   • Object Type: Select the type of design object to create or use from the dropdown.
   • Object Name: Enter a name for the design object. This field is only available if you choose to create new objects.

5. Click CREATE to add the task.

   Tip:  Click CREATE ANOTHER to save a task and immediately create another one.

View task details

Once you've generated tasks or added your own, you can review the task details to better understand what action is being taken.

To view task details:

1. In the Build view, go to the Board tab.
2. Click a user story to open the story detail view.

3. In the Tasks section of the story, click the expand icon on a task. The expanded view shows:

   • Object Type: The type of design object (for example, record_type).
   • Object Name: The name of the object to create or modify (for example, T0 Document Type). Once the object is built, you can click the name to open the design object directly.
   • Notes: Implementation instructions describing what to build (for example, "Create a DATABASE-backed record type named 'T0 Document Type' with fields…").
   

   Scroll or drag to pan · ⌘+/⌘− to zoom · Esc to close

Edit a task

You can edit tasks that are in To Do status. Tasks in In Progress, In Review, or Done status cannot be edited.

To edit an existing task:

1. In the Build view, go to the Board tab.
2. Click a user story to open the story detail view.
3. In the Tasks section of the story, click .
4. Select Edit.
5. In the Edit Task dialog, edit the following fields as needed:
   • Name: The task name.
   • Status: The current status (To Do, In Progress, In Review, Done).
   • Implementation Notes: The description of what the task should accomplish.
   • Design Object: Select Create new or Select existing.
   • Object Type: The type of design object.
   • Object Name: The name of the design object.
6. Click SAVE CHANGES.

Delete a task

You can delete tasks that are in To Do status. Tasks in In Progress, In Review, or Done status cannot be deleted.

To delete a task:

1. In the Build view, go to the Board tab.
2. Click a user story to open the story detail view.
3. In the Tasks section of the story, click .
4. Select Delete.

Execute tasks with Composer

After your user story's tasks are generated and ready to go, Composer can execute them for you—creating design objects, configuring them based on the story's acceptance criteria and task notes, and connecting them across the application.

To execute a task with Composer:

1. In the Build view, go to the Board tab.
2. Click a story to open the story detail view.

3. In the Tasks section, click START TASK next to the task you want to execute.

   Note:  START TASK is disabled for AI & Automation tasks because Composer does not support execution of these object types. You must build these design objects manually using the implementation guidance provided in the task list.

When a task completes successfully, is replaced by a . The next task in the sequence becomes available for execution.

Use Composer guidance to build AI and automation objects

For user stories that involve AI agents, RPA robotic tasks, or AI skills, Composer generates a dependency-ordered task list with implementation guidance—but you must build these objects manually.

The task list includes guidance specific to each object type:

• AI skills: Inputs, output expectations, and an example prompt.
• AI agents: Inputs, outputs needed, a possible agent system prompt, and the tools and actions to provide to the agent (expression rules or process models from previous tasks).
• RPA robotic tasks: Prompts describing what the bot should do, system capabilities, and input variables.
• Knowledge bases: Folders with reference documents that the agent needs for context (for example, fraud indicators or compliance policies).

Example using Composer for an AI-focused story

The following example shows how Composer breaks down an AI-focused story into dependency-ordered tasks.

For a story called "Create an intelligent Claims Triage Agent," Composer generates the following tasks:

1. Create AI Skill: Document Data Extraction—The agent needs extracted claim data before classifying. Inputs: claim document. Outputs: structured claim fields. Includes an example prompt for extraction logic.
2. Create AI Skill: Fraud Risk Scoring—A distinct cognitive task, reusable across workflows. Inputs: claim data, fraud indicators. Outputs: risk score and flag.
3. Create knowledge base: Fraud Indicators Reference—A folder with reference documents containing fraud pattern data that the agent uses for context.
4. Create Agent: Claims Triage Agent—Connects the Document Data Extraction and Fraud Risk Scoring skills, defines classification logic, and sets limitations for escalation. Inputs: incoming claim. Outputs: routed claim with priority and risk assessment.
5. Modify Process Model: Claims Intake Workflow—Wire the agent into the existing workflow and add a routing gateway for escalation paths.

Limitations

The following limitations apply when using the Board tab and Composer for task execution:

• Sequential task execution: Tasks within a story must be executed in dependency order. Composer blocks execution of a task if its prerequisite tasks are not complete.
• Single-story execution: Composer breaks down and executes one story at a time. You cannot request a consolidated breakdown across multiple stories simultaneously.
• Automation execution: START TASKS is not available for automation tasks (AI Agents, AI Skills, RPA robotic tasks, and knowledge bases). You must implement automation tasks manually.
• Unrecognized object types: If a story references an object type that Composer does not recognize, Composer creates a breakdown using the object types it supports. You must fill in any gaps for unrecognized object types.

Feedback