---
title: "Hand context to a builder"
url: "https://docs.alisx.com/how-to/ideate/hand-context-to-build/"
---
# Hand context to a builder

Start building with Alis Build DBD from what a project has captured, so that whoever builds the thing starts from what was actually said rather than from a summary of it. There are two ways in, depending on who is building.

## Prerequisites

- A project whose context has settled: no **Still settling** note in `alis ideate context <project>`, and no stale outputs you intend to build from.
- For the CLI routes, `alis` installed and signed in, with Build access on your active account.

## Give a coding agent the project

A coding agent working through the CLI reads the project the same way you do:

1. Hand the agent the project reference, `ideas/<id>`, in your prompt.
2. The agent runs `alis ideate context <id>` first, then reads the outputs and contributions that matter with `alis ideate artifacts read` and `alis ideate contribution`.
3. It then proceeds with Define, Build and Deploy for the product; see [Ship your first service](https://docs.alisx.com/tutorials/first-build-service.md) and [Work with a coding agent](https://docs.alisx.com/tutorials/work-with-a-coding-agent.md).

`alis docs ideate` and `alis docs` tell the agent to do exactly this.

## Take an artifact to an external tool

Two output types made before artifacts are written to be pasted into other tools rather than into Build:

- **UI design brief** opens in a design tool of your choice: the menu beside **Copy page** lists the tools it targets under **Open in**, and **Copy markdown** copies the brief.
- **AI prototype prompt** does the same for prototyping tools and coding assistants.

## Related

- [Create and review artifacts](https://docs.alisx.com/how-to/ideate/generate-and-review-outputs.md)
- [Read project context from the CLI](https://docs.alisx.com/how-to/ideate/read-project-context-from-the-cli.md)
- Why the handover works this way: [Ideate](https://docs.alisx.com/explanation/ideate.md)