From a meeting to a design doc
When a technical discussion ends with "someone should write this up", Retain can write the design from what was said. You pick the direction, Retain reads the meetings and email behind it, and the result is a Technical Design Document you can revise and then build. This page covers where to start one, what Retain writes, and how to change it.
Start from a meeting, a Thread or Create New
Every route ends at the same place: a plan with one or more steps, where a step is one document Retain can write.
- From a meeting. Open the meeting and look under Potential actions. Items the meeting produced and the next steps of Threads that cite it are listed there.
- From a Thread. At the end of a Thread, Suggested and Other actions list what Retain proposes. The box under them, What do you want to do?, takes your own words, such as "design the retry queue we discussed". A Thread is Retain's running record of one matter across meetings and email; see Threads and what's owed.
- From Create New on the Mac. Choose Document, type what needs doing in one line, and press Return to plan it.
For work on software, systems, data or infrastructure, Retain plans a Design step unless the sources point to another kind of document. If a step came out as something else, open it and change Type to Design. A brief or an outline you already wrote can also be turned into a design from its menu: choose Rewrite as, then Design.
Set the direction, then write
Open the step. It shows what the step makes, which you can edit in place, and a few fields:
- Approach. Pick one of the options Retain proposes, or say what the design should do in your own words. Retain writes toward the direction you choose and does not reopen alternatives you ruled out. The Write button waits for this.
- Must include. Anything the result has to cover, one per line.
- Draws on. How many sources the design reads, such as meeting transcripts and email threads. Select it to see them.
- Codebase. On the Mac you can let the design read your code; see Grounding a design in your codebase.
Select Write. While it runs you can select Stop. What was written so far is kept as a draft, and Write again starts over.
What Retain writes
Without a codebase, you get one design document of roughly 600 to 900 words:
- Decision. The direction you chose, stated plainly.
- What exists. Only the parts of the current product, history or sources that the decision touches, each cited once.
- Approach. How the work fits into what exists.
- Risks that block. Only the risks that could stop or reverse the work.
- Open questions. What is undecided and who can decide it.
Anything Retain could not confirm is marked unverified instead of stated as fact. It leaves out a build order and a test plan; the agent that builds the change adds those against your code.
With a codebase connected, the same design is written as the first two parts of a build packet: a Proposal (Why, What Changes, Not Doing) and then the Design. Each part is checked against Retain's format and rewritten if it fails.
Revise it
- Edit it yourself. In a packet on the Mac, open the Proposal or Design tab and select Edit. You edit the whole file as markdown, then Save. A packet that is archived is read-only.
- Ask in the document chat. Select the sidebar button to show the AI chat beside the document and say what to change, such as "cut the rollout section" or "add the risk Sam raised". The chat's edits go to the Design.
What comes next
Once a packet is written it is ready to build. Open its Build tab for the command to give your coding agent, which writes the requirements and tasks against your code and then builds. Explore, design, apply covers that loop, and the Build tab shows what the tab reports while it runs.
Need help?
Can't find what you're looking for? Contact our support team for a quick reply.
Contact Support