Specs that live next to the work
Author a spec in CodePlans, give it a type and optional area, and link one document to the assets, plans and work items it governs. Plans declare whether they create, revise or reference it.
The Specs page separates current specs from those in review (including fresh imports waiting to be checked) and the archive.
Every revision kept, every change visible
Each change to the title or text is a new version with its full text retained. Open any earlier version read-only, or diff it against its predecessor. Activating, archiving or reclassifying a spec happens in place from the action bar at the top of the page: no new version, and approvals stay put.
When a capability was delivered against v1 and the spec moves to v2, the asset record shows both, without rewriting the delivery receipt.
Write specs in a proper editor
Edit slides a wide editor in from the side, with a toolbar for headings, lists, task lists, tables, code, links and Mermaid diagrams. Paste markdown from a README or a chat and it becomes formatting; switch to Markdown to edit the source directly.
Text is stored as clean markdown, the same text agents read over MCP. Saving creates the next version with an optional change summary; type and area save in place on the Details tab.
A wiki assembled from the work you already record
Open Wiki from the main navigation in its own tab. Read the architecture, documents, decisions and delivery history around every asset, with creator and editor attribution and import provenance. Missing metadata stays explicitly unknown.
Wiki screenshots are from a synthetic Atlas demo workspace.
Bring existing Markdown specs across
Apply the normal migrations, then preview the product-scoped legacy URL import. The importer deduplicates source URLs, puts imports in review, and keeps later native edits on reruns.