Turn an existing brief into a proposal you can review

You already described the feature in a ticket, a PRD, or a message to an engineer. Use that request as the starting point. The coding agent drafts the proposal from the request and the repository; you review whether it understood what you meant.

The input

The original text for one upcoming change, access to the repository, and someone who runs the coding agent. A relevant PRD excerpt or rough notes are enough to begin. Keep uncertainties visible instead of filling gaps with invented evidence.

The flow

1. Create or join your workspace. Sign up, then connect the coding agent yourself or choose Invite a teammate. If you were invited, accept the invitation to join that workspace. You can prepare a brief while your teammate handles the repository connection.

2. Give the original request to the coding agent. Ask it to draft an IntentSpec from the request and the codebase, label its assumptions, and attach the original request to the connected proposal. Preserve your wording so you can compare the request with its interpretation.

3. Open the proposal in Pathmode. Read the original request alongside the proposed behavior. If the source text is missing, choose Attach the request, add its title and exact wording, and optionally link to the source document.

4. Correct what it misunderstood. Check What the agent understood. Use Correct on a behavior that differs from your intent. Where Pathmode offers a recommendation, you can use its wording or describe another behavior, then review and submit the correction. Explain the result you need and why it matters.

5. Return for the revised proposal. The repository agent applies the correction or reports why it cannot. Once applied, review the changed behavior and the rest of the proposal. Authorize implementation only when that revision expresses the change you want built.

The output

• The original request available to the reviewer, with its wording preserved.
• A proposal that makes the agent's interpretation and assumptions visible.
• A correction the repository agent can act on, followed by a revision you can inspect.
• Your explicit authorization of the proposal the engineer will implement.

An attached request records what was asked. It does not, by itself, prove a claim about users. Link relevant observations or research when they help you judge the proposal.

Try it with your next feature

Choose a request whose meaning could be lost in a small detail: which customers an export includes, who keeps access after a teammate leaves, or what a user sees when a payment times out. Compare the proposed behavior with the original request before implementation starts.

For a worked example, follow Review and correct an agent's proposal before it builds. For setup through verification, see Your First Intent in Pathmode.