What description presets are
Description presets are board-scoped prompt templates for task descriptions. A preset has a short name, up to 30 characters, and a prompt body that tells CalmBoard AI how to shape the response. That prompt can define the response format, the tone, the sections you expect, and even an example output style.
Instead of starting every task with a blank textarea, your team can select a preset and generate a description that fits the current board's workflow. This is useful for product discovery, architecture-driven work, bug analysis, delivery planning, onboarding tasks, and repetitive operational tickets.
Why this matters
- Consistency: task descriptions stop changing shape from person to person.
- Faster task creation: the team starts from a strong draft instead of writing the same structure manually.
- Better board hygiene: clear sections, acceptance criteria, and context make execution easier.
- Board-level control: each board can define its own preset library based on the kind of work it handles.
- Flexible prompt design: users are not locked into one template; they can build their own response models.
If your team already uses CalmBoard AI agents for delivery insights, description presets extend that same idea into day-to-day task creation: less repetitive setup, more structured execution.
How the feature works
1. Define
Create a preset in Board Settings with a short name and a prompt template.
2. Select
Open a task and click Suggest from preset beside Suggest improvements.
3. Apply
Choose one preset, review the generated draft, and apply it to the description field.
Step by step: create a preset in Board Settings
Open the board and go to Board Settings. Expand the collapsible Task description presets section.
Add a preset name. Keep it short and specific so the team can recognize it quickly. Examples: Use case, Main tasks, Implementation plan.
Write the prompt template. This is where you define the output structure. You can ask for sections like context, objective, acceptance criteria, dependencies, validation steps, rollout notes, or examples.
Save the preset. It becomes available immediately for that board, so anyone creating or editing a task there can use it.
Visual aid: two example preset models
Preset: Use case from requirements
Create a task description as a use case. Include objective, actors, main flow, edge cases, acceptance criteria, and dependencies. Keep it concise and execution-ready.
Preset: Project main tasks
Turn this task into a project-level execution outline. Include scope, main workstreams, deliverables, assumptions, risks, and what done means for this task.
These are not hardcoded content types. They are just starting points. You can adapt them for QA test plans, architecture tickets, handoff documents, onboarding tasks, sprint-ready user stories, or anything else your board needs.
Step by step: use a preset while editing a task
- Open a task or create a new one.
- Go to the description area.
- Click Suggest from preset.
- Select one of the presets defined for that board.
- Let CalmBoard generate the suggestion using the selected preset and the current task context.
- Review the generated description and apply it if it fits.
The review step matters. CalmBoard AI suggests, humans approve. That keeps the workflow fast without silently changing user content. If you want a broader view of how AI fits into accountable delivery workflows, the article How to use AI agents to enhance your project management expands that operating model.
Best practices for better preset prompts
- Be explicit about structure. If you want sections, say which sections.
- Use examples when format matters. A short example can stabilize the output quality.
- Keep one purpose per preset. Avoid giant prompts that try to cover every task type.
- Name presets by use, not by author. Teams need to know when to choose one quickly.
- Review presets at the board level. The best preset library usually reflects the board's real workflow rather than abstract documentation ideals.
Teams using Scrum can combine description presets with the board-level reporting and planning flows described in Scrum board features in CalmBoard so tasks start with clearer execution detail and flow more cleanly into planning, review, and delivery reporting.
What this unlocks for teams
CalmBoard description presets are a small feature with a meaningful operational effect: they reduce prompt rewriting, reduce description inconsistency, and help boards encode their own documentation standards directly inside the workflow. The result is not just faster task creation. It is a cleaner system for turning intent into work that another person can actually execute.
If your team is already experimenting with AI-powered task management, this is one of the most practical ways to make those suggestions reusable instead of one-off. The board becomes the source of truth not only for tasks and status, but also for how good work should be described.