Antescript for teams building with coding agents

The notes before the code.

For people who build with Claude Code, Cursor or another coding assistant. Write the spec your agent works from, and let it write back into the same page while your team edits it.

A spec your agent can work from

Start from the Spec template: the problem, the goals, the proposal and the open questions, as headings to write under. Your coding assistant reads the page as markdown, heading by heading, so “implement the Rollout section of the checkout spec” points at something exact, and the spec stays the one place the plan lives instead of a file that drifts from it.

It writes where your team writes

Ask it to rewrite one section and it changes that section alone, while anyone else on the page keeps typing; nothing is pasted back by hand. Its writes land live under its own name, with a short glow on what it added, and the page’s History lists them in Activity beside people’s edits. It can also add to the end of a page, file it into a group, and tell you what changed since a time, as a diff.

Diagrams that stay editable

Ask for the flow or the architecture and it draws a design: boxes, connectors and screen mockups on a canvas that you then move and relabel by hand, and that it can change again by element. Type /design on any page to show one as a figure; edit the design once and every page that shows it follows.

Review in the margin

Select a line and choose Add comment. Mention your assistant with @ and it finds the question the next time it looks, answers in the thread and fixes the line. It can open threads of its own beside the text it means, for you to answer.

Connect yours