# From Spec to Task --- The point of a session isn't the conversation — it's the **spec** that comes out of it. Once you've said you want something changed, the agent writes one up on the right and keeps it current as you talk. ## When a spec appears Only when you ask for a change. Questions get answers and nothing more — asking _"how does session expiry work?"_ won't produce a spec. Say _"let's make sessions expire after an hour"_ and one starts taking shape. It covers the goal, what "done" looks like, anything the agent assumed, what it's deliberately leaving out, and how big a job it thinks this is. At the top you'll see whether the agent considers it **vague**, **partial** or **ready** — useful as a nudge, though you can go ahead whenever you're happy with it. **To change the spec, talk to the agent.** Tell it what it's got wrong or what's missing and it rewrites it. There's no edit box, deliberately — the spec and the conversation stay in step. ## Turning it into a Task Click **Create task** under the spec. You'll see the goal and criteria one more time, and choose the **model** that should do the work. The default is picked for you based on how big the agent thinks the job is — bigger jobs get a more capable model. You can switch to a different agent here too, and change it again later. Click **Create Task**. ## What happens next **The Task goes to your backlog — it doesn't start running.** You'll land on the Tasks board with it open, ready to review. It carries over everything from the session: the spec becomes the Task's brief, along with the same repositories to work in. The session itself closes at this point. The spec stays on screen with a link through to the Task, so you can always see what was agreed. When you're happy, press **Start**. See [Creating and Running a Task](/docs/tasks/creating-and-running-a-task/). > Converting happens once. The Task doesn't stay linked to the session afterwards — it's a handover, not a live copy. --- Source: https://deployment.io/docs/assistant/from-spec-to-task/