Shape it in your first workshop
A workshop turns an idea into two things: the documents that describe your product, and a pipeline of versions ready to build.
In the appWorkshops
A workshop turns an idea into two things: the documents that describe your product, and a pipeline of versions ready to build.
Creating a project drops you straight into an Untitled workshop. That is not a detour: it is step two.
A workshop is a conversation with an agent that turns an idea into two things. Documents that describe what you are building, and a pipeline of versions ready to build, in order. You get both from talking, not from filling in a form.
Describe your idea
An empty session. The prompt is on the left, and the panel on the right says what you will walk out with: product requirements, technical requirements, and versions.
Take the prompt literally. A few lines beat a specification you sweated over alone. Speaking is faster than typing, so use the voice input, and attach any document you already have.
Answer the questions
This is the part that does the work. The agent reads what you wrote, tells you what it understood, then asks.
You send a few lines. The agent replies with what it understood, then asks question 1 of 3.
Questions arrive as cards you answer in place, not as prose you have to reply to. A card carries its position in the run (1 of 3), and the answer type fits the question: one choice when something has to be settled, checkboxes when several answers hold together, free text for the rest. Arrow keys move, Enter selects, and Skip is always there when the question does not apply.
Skipping is a real answer: the agent assumes a sensible default and says so rather than blocking. But every question you do answer is a version you will not have to rebuild.
When the run ends, the whole exchange is summarised back to you as a question-and-answer block, so what the agent is about to write from is visible rather than implied.
Connect what it needs
Some answers imply an external service. When that happens the agent does not guess in silence: it asks, in the chat, naming the secrets it needs.
The run summarised, then a request: without these keys, that part of the plan stays a guess.
The card names the service, the step that needs it, the environment it applies to, and the secrets by name. It also states the cost of saying no, in plain terms: I have no Jira secrets on this environment, so I can only guess the API shape and the annex stays unverified.
Set up Jira opens the secrets form inside the card itself. You do not leave the workshop: the conversation stays right behind it.
The form opens in the card, in the thread. Nobody sends you off to a settings screen somewhere else.
Each secret is named and described, and How to obtain points at the provider's documentation when there is one. Save and verify stores them on the project, the card flips to connected, and the agent picks up again on its own with what it was missing. Not now carries on without it. Either is fine; what matters is that you know which one you picked. See Connect a third-party integration.
Correct what it writes
The agent drafts as you talk, and everything it produces lands in the Documents tab: product requirements, technical requirements, epics, sprints, and the technical decisions it took along the way.
Open one and read it. The Comments button in the document toolbar opens a panel on the right, and there are two ways to leave one.
Comment on a passage and a numbered marker ties it to that exact line. Comment on the whole document when it is not about one line.
Select text and Comment on this selection pins a numbered marker to that passage. Add a general comment attaches a note to the whole artifact. Both land in the Open tab and go nowhere until you send them, so you can read three documents and mark everything before you commit to a turn.
Then tick what you want and send. The agent receives them as refine instructions and they move to Sent. This is the cheap moment: a wrong assumption costs a comment here and a rebuilt version later.
Get the right people to read it
A comment is not a private notepad. Anyone with access to the project opens the same document, comments on the same passage, and replies in the same thread. Every message carries its author, and the discussion sits under the line it is about.
This is the moment to pull in the people who know: whoever owns the process, whoever knows the business rules, whoever will have to live with it. A disagreement settled here costs three replies in a thread. The same disagreement found after the build costs a version.
When the thread has landed, send it. The agent receives the whole discussion, not just the last sentence, so the reasoning behind the decision travels with it. Select several comments to send them in one go, and wait for the agent to finish its turn: sending is blocked while it is working.
Get your pipeline
Once the documents hold, the workshop slices the work into versions and queues them in the Roadmap tab, each priced in production units before anything runs.
That list is the plan. Versions run one at a time, in order, and you can still edit the brief of any of them before it starts.
Launch one version, or arm a batch and let the agent chain them.
One workshop per subject. A session that covers supplier onboarding and the spend dashboard produces a muddled roadmap. Two sessions produce two clean ones, and you can run their versions back to back anyway.
Next
The pipeline is ready. Now you launch it: see Launch your first batch.
Workshops are not only a first step. You will open one again to plan the next slice of work, to break a big review down, or to think through a change before building it. Run a workshop covers the workspace in full.