Creating tasks with AI from a technical specification

Under the saved technical specification of a project or stage in PRO-dela, a button «Create tasks with AI» has appeared. It opens a modal window and immediately starts parsing: the AI returns from one to 50 draft tasks with titles and descriptions, assembled from the text of your specification.

Nothing is created automatically. The proposed list is an editable draft: you can adjust the wording and order, delete unnecessary items, and only then the entire set is confirmed with one button and created as regular project tasks.

Why turn a specification into a task list

The technical specification in PRO-dela is already stored in the system — in the text field of the project or stage. But to start working on it, you have to manually transfer the structure into tasks: read item by item and re-enter the title and description for each.

The feature closes exactly this step. It does not read the specification for you and does not make decisions for you — it offers a draft set of tasks based on the saved text, which you need to review, adjust if necessary, and confirm. The final work structure is still determined by a human, not by the model.

What the AI takes into account and what it does not

The source is exactly one — the saved text field of the project or stage specification. An unsaved draft in the editor is not passed to the request: if you edited the specification and did not save the changes, the button will suggest saving them first. Empty markup without meaningful text is considered an empty specification and does not trigger generation.

If files are attached to the specification, the AI does not read them — only the main text is analyzed. In this case, the preview will show a warning that only the saved text was taken into account, not the contents of the attachments.

The list of existing tasks, subtasks, and stages of the project is also not passed to the request. The feature does not look for semantic duplicates and does not warn about overlaps with already created tasks — you should do this check yourself before confirming.

How AI decomposition works

The model receives the task to cover the content of the specification as fully as the text itself allows: highlight individual verifiable results, give them short and action-oriented titles, and transfer into the description only what is actually in the specification — without invented performers, deadlines, technologies, or requirements. Tasks are returned in a logical order of execution and in the language of the original specification. If there are ambiguities or parts that are difficult to turn into a separate task, the model puts them into a list of warnings rather than making them up itself.

If the specification would result in more than 50 tasks, the AI consolidates closely related work into one item — the final set always consists of 1–50 tasks. This is not a soft limit: if the model still returns more than 50 suggestions, the entire response is rejected as a whole, PRO-dela does not truncate or merge it on its own, and no preview is created.

The task title is mandatory and, after cleaning extra spaces, must contain from 3 to 255 characters; the description is optional and is returned as plain text. Up to 180 seconds are allotted for the generation itself: if the AI did not respond in time or sent incorrect data, the draft is not saved, and you can run the generation again.

A preview that can be edited

Generation starts immediately after opening the window, without additional settings. While parsing is in progress, a progress indicator and elapsed time are visible; if something goes wrong, the window will show an error and suggest retrying.

Until the draft is confirmed, these are not yet tasks: the project, stage, real-time task list, and user notifications do not change. With each proposed item, you can do three things:

• edit the title and description;
• delete the item if it is not needed;
• move it up or down, setting the order manually.

You cannot add a new row to the preview that the AI did not suggest — for that, the usual manual task creation scenario remains. Only a valid set can be confirmed: at least one task must remain, and each must have a non-empty title. The order of items at the moment of confirmation will become the order of the created tasks.

You can close the window during generation, but this is a separate action with confirmation: the visible result will be lost, although the already sent request to the AI may finish on the server. But during the actual creation of tasks, the window cannot be closed — this is worth understanding for the next section.

The draft itself is valid for a limited time — about an hour. If you return to it later or the saved specification has changed in the meantime, PRO-dela will ask you to run the generation again rather than confirm an outdated result.

Creating tasks: all at once or nothing

The confirmed set is created in one operation: either all tasks or none. Each new task gets the original project, you as the author, the initial status «Pending» according to the usual task lifecycle, and a sequential place at the end of the current list. The assignee, category, deadline, and priority remain empty — they can be filled in after creation, as with any other task.

If the source was a project specification, tasks are created without linking to a stage — PRO-dela does not try to guess which stage they belong to and does not distribute them automatically. If the source was a stage specification, each task in the same operation is attached to that specific stage.

After creation, the task list updates in real time for everyone viewing it — just like with regular task creation. However, individual email, push, Telegram, and MAX notifications are not sent for this set. The tasks themselves are not marked as created by AI — after confirmation, they are regular tasks without any special marks.

If the creation request was interrupted due to a network error, pressing again is safe: PRO-dela will not create duplicates, but will either complete the creation once, or — if the tasks were already created — simply return the same result.

Access rights and when the button is unavailable

Preview and confirmation require access to the project or stage and the right to create tasks in the project. The right to edit the specification itself is not needed — the feature reads the saved text but does not edit it.

The button is shown in the specification viewing mode to a user with the right to create tasks. If the specification is still empty, the button is visible but inactive and explains that you need to fill in and save the text first. If there are unsaved changes in the editor or the specification is being saved, the button is also temporarily inactive with a hint to save changes. While generation or task creation is in progress, re-running from the same button is blocked.

Rights are additionally checked at the moment of confirmation: if access to the project or the right to create tasks is lost after the preview, PRO-dela will refuse to create and change nothing. If the previously obtained preview has not yet expired, disabling the AI feature itself or the provider after its creation does not prevent confirming it — at this step, the AI is not called again.

Project specification and stage specification — two independent features

«Creating tasks from a project specification» and «Creating tasks from a stage specification» are formally different platform features, and this is not a technical detail but a practical consequence: the PRO-dela administrator enables and configures them separately, each has its own provider, model, and prompt. You can, for example, keep only one of them enabled. How the management of the platform's AI features as a whole works, individual toggles, providers, and what happens if a feature is disabled or unavailable — in the article «AI features of PRO-dela». If the desired button is not displayed at all, rather than just inactive, this, as with other AI features of the platform, is a matter of current configuration, not a tariff or a bug.

Practical scenario

Suppose a stage specification contains a dozen work items: some are short and unambiguous, some are formulated generally. Instead of manually turning each item into a separate task, you open the stage specification and click «Create tasks with AI».

After a while, a draft appears: for example, seven tasks and one warning that one of the specification items is formulated too vaguely for a separate task. You refine the wording of two items, delete one that clearly duplicates another in meaning, swap the order of a couple of tasks — and confirm the list. All tasks are created in one operation and are immediately attached to this stage.

A good habit is to first read the warnings and compare the draft with the original specification, and only then confirm: the AI covers the content as fully as the text itself allows, but the decision about what exactly should become a task remains yours.

Frequently asked questions

Will the AI read files attached to the specification?

No. Only the saved text of the specification field is analyzed. If files are attached, the preview will separately warn that their contents were not taken into account.

What if the specification has far more than 50 logical items?

The AI consolidates closely related work to fit into 1–50 tasks. If the model's response still exceeds 50 items, it is rejected as a whole, not truncated — in this case, no preview is created, and you should try again.

Are existing tasks checked to avoid duplicates?

No, in the current version, the list of existing tasks, subtasks, and stages is not passed to the AI and is not compared with the proposed draft. You should do this check yourself before confirming.

Where will tasks created from a project specification go?

Into the project, without linking to any stage — PRO-dela does not distribute them among existing stages automatically. If you need linking to a specific stage, run the generation from that stage's specification.

Can I add my own task directly to the preview?

No, in the preview you can only edit, delete, and rearrange the items proposed by the AI. For manually adding a task that was not in the draft, use the regular task creation form.

What happens if task creation is interrupted midway?

Nothing partially applied remains: the set is created completely or not at all. If the result of the operation did not arrive due to a network error, you can safely repeat — PRO-dela will not create tasks again.

Turn your saved specification into tasks

Open the technical specification of the desired project or stage and make sure it is saved. If you see the button «Create tasks with AI» next to the text, click it, wait for the draft, compare it with the specification and warnings, make any necessary edits, and confirm the set. How statuses, participant rights, and the task lifecycle work in PRO-dela after a task is created — in the article «Tasks in PRO-dela».

If you don't have an account yet, register in PRO-dela, create a project with a technical specification, and check the feature's availability on the pricing page.