Retain for engineers
For an engineer, Retain turns a design discussion into a design doc grounded in your code, and the doc into a build packet that your coding agent builds. This page walks through a week of that, and points to the articles for each step.
Record the design discussion
Record the meetings where a technical decision gets made, such as a design review or a talk about how to split a service. Retain transcribes them with speakers. See meeting types for what each type produces.
Get a design doc grounded in your code
After the discussion, ask Retain for a technical design document. It leads with the decision you reached, then lists what exists in the code that the decision touches, the approach, the risks that could stop the work, and the open questions. Anything the sources do not confirm is marked unverified.
With a codebase connected, Retain asks your coding agent questions about the code and cites what it finds, so the "what exists" section points at real files. From a meeting to a design doc shows the steps, and grounding a design in your codebase covers the connection.
You can also start in your coding agent: /retain:explore thinks a change through with your code open, and /retain:design writes it up as a packet.
Build the packet
A build packet is one change to your code, from the reason for it to the pull request that ships it. Open the packet, select the Build tab, and copy what it shows into your coding agent, for example /retain:apply followed by the packet name. The agent writes requirements and tasks against your code, then builds. /retain:next lets Retain pick the next packet to build.
Track the pull requests and what waits on what
The Build tab lists the packet's pull requests with their number and whether each is a draft, open or merged. A packet that builds on another shows it under Depends on, and the packets waiting on it are under Needed by. A dependency counts as ready once it has an open pull request.
Building shows on the Work list as a count such as Building 12/25.
Read next
- Build packets explains the parts of a packet and the states it moves through.
- The Build tab shows how to start a build and watch it.
- Packet dependencies covers building one change on top of another.
Need help?
Can't find what you're looking for? Contact our support team for a quick reply.
Contact Support