AI recipes

These are requests you can copy and adapt. Try them in the in-app AI chat, or install the official plugin and connect through MCP to use your preferred AI app.

You do not need to name tools. Say which board to use and what work you want done. You can paste a board or task link instead of its name.

1. Turn meeting notes into tasks in bulk

On [board name], turn only the action items in these notes into tasks.
Show me the proposed tasks first and create them after I confirm.
If an assignee or due date is missing, note that it is undecided in the description.
Check for similar existing tasks before creating duplicates.
Report created tasks with links, and explain anything you could not create.

[Paste meeting notes here]

Reviewing what was left out helps catch missing actions and separate them from items shared for information only.

2. Write the morning standup summary

In [workspace name], summarize my day in three short groups:
- Tasks where I hold the ball and need to act next
- Tasks due today
- Tasks whose due date was before today

Include links to the tasks. Do not change anything.

Save the request as a reusable skill if you want to use it every morning.

3. Find what stopped moving

On [board name], check open tasks assigned to me or where I hold the ball.
Find those with no updates in the last 14 days.

Make a table with the last update date, what to check next, and a task link.
Separate confirmed facts from possible explanations. Do not change any tasks.

A lack of updates does not prove that no work happened. Use the result to start a conversation. The Risks view also helps you review the board.

4. Build the retro document

Summarize activity on [board name] from [start date] through [end date],
using [time zone]. Include the history of archived tasks.
Group the results into completed work, confirmed reopens or rework,
and open tasks with no updates during the period.

Check open tasks and their individual histories to identify the last group.
Give counts and links to representative examples.
State any limits on what you could check. Do not change anything.

A lane change alone does not prove rework. Look at the comments and history as well.

5. Gather the numbers for a realistic due date

On [board name], total the sizes of open tasks in [project name].
Exclude tasks without a size from the total. List their count and links separately.
Do not set or change due dates.

Use the total as an input to planning. Your team’s pace, availability, and review delays still need to be considered when setting a realistic date.

6. Start with requests that only read

Review [board name] without changing anything.
If something needs updating, show the proposed change and the reason only.

Summaries and reviews do not require permission to change tasks. You can also limit the MCP connection permissions to read-only access.

7. Be specific about what to change

For [task link], add this acceptance check to the description:
“A new user can follow every step successfully.”
Keep the existing description. Do not change assignees, labels, or dates.

For a lane move, name the destination. For a handoff, name the next ball holder. Ask the AI to check with you if the target is unclear.

8. Audit your recurring tasks

Review recurring tasks in [workspace name].
Check tasks created from [start date] through [end date] and identify where
unfinished work is accumulating.
If you cannot tell which recurring setup produced a task, say so.
Suggest what to review and why. Do not disable settings or archive tasks.

Use the result to check whether recurring tasks still have the right frequency and destination.

9. Allow board settings changes when needed

Changing board settings through an external AI requires additional permission at connection time. It is not needed for everyday task reviews and organization. See MCP connection settings.