A Request is how you turn a rough idea or ask into concrete tasks. You describe what you want in plain language; DIJJI.ai breaks it down into ordered work items you can review, adjust, and then save as tasks. Requests live under the project’s Plan section, at Plan > Requests.
Each request is a thread
Every request you make is its own thread. You start one with + New Request, where you give it an optional title, optional notes describing what you want, and — if it helps — uploaded files or screenshots. Then you select Break it down, and DIJJI.ai reads your project and drafts the work items (you’ll see Breaking down your request… while it works). Unlike a Blueprint, you don’t pick a project type — DIJJI.ai works it out from your code.
A thread carries a status as it moves along: Generating, then Draft once the work items are ready, Committed after you’ve saved them as tasks, or Archived.
The work items
DIJJI.ai turns your request into a numbered, ordered list of work items — each a focused piece of work. A work item can carry:
- A size — S, M, or L, a rough sense of how big it is.
- A Depends on note — when one item needs another done first.
As with a Blueprint, each part tells you how sure DIJJI.ai is: fields are marked Filled, Assumption — confirm/change, or Question — answer, with a plain-language explanation and a Technical detail disclosure. Clear the assumptions and answer the questions until the breakdown is right. You can add input and regenerate to refine it, and earlier versions can be restored.
Saving work items as tasks
When the breakdown looks right, select Approve & save. The work items are saved to your task list as pending tasks — “{N} task(s) created” — and a View in Tasks link takes you to them.
Two things to know about what you get:
- No pull request. Unlike a Blueprint, a Request doesn’t touch your repository — it only creates tasks.
- Nothing runs automatically. The new tasks wait as Pending until you run them, the same as any other task. See Execute a task.
Requests vs. Blueprint
Blueprint and Requests both turn your input into something structured, but they produce different things:
- A Request produces tasks — work items saved to your task list, no pull request.
- A Blueprint produces design documents, written to your repository as a pull request.
Use Requests to describe work you want done; use a Blueprint to establish what the project is.
To create one step by step, see Create a request and save it as tasks.