Spec versions & Amend

A spec your agent builds against has to hold still. CubeDot solves this with versions: publishing your committed gates freezes them into spec v1, and that frozen version is what the MCP server serves to your agent. You can keep thinking; the agent keeps building against something stable.

Update current sprint (Amend)

Plans change. When they do, you don’t edit the live spec field by field; you open Update current sprint from the project’s Overview page. That starts an amend session:

• Your changes accumulate as a draft changeset against the current version. Nothing your agent sees moves while the draft is open.
• You can adjust features, functionalities, stories, and the documents that depend on them, in one coherent batch.
• When you commit the amend, CubeDot re-renders every affected document and publishes everything atomically as the next version (v2, v3, and so on).

Because the commit is atomic, your agent never sees a half-updated spec: it reads v1 until the moment v2 exists, then reads v2.

Rules worth knowing

• Amend needs a published project. If you haven’t published a first version yet, keep working through the gates instead.
• Only one amend session can be open at a time. Finish or discard the open one before starting another.
• Amend is available on Trial and Pro plans (see Plans).

Versions and your team

On Trial and Pro, earlier versions stay browsable, so you can see what the spec said when a functionality was built. The Free plan keeps only the latest version visible.