# Ship an idea without writing code

Source: https://codeherder.com/docs/ship-an-idea/

No code needed. Describe the result, answer the agent's questions, approve the work and watch what it costs.

You have an idea for a product, a feature or a fix. You do not write code. This guide shows how you can still get it built. You only use the web app.

## Who this guide is for

This guide is for product owners, founders and executives. You know what the software must do. You do not need to know how to build it. CodeHerder gives the work to AI agents. A person on your team stays in charge of what ships.

## What a developer sets up once

One developer connects your code to CodeHerder. They do it once, and nobody repeats it.

The developer does two things:

- They connect a repository. See [Connect a repository](https://codeherder.com/docs/quickstart/#2-connect-a-repository).
- They connect a device. A device is the machine that runs the agents. See [Connect a device](https://codeherder.com/docs/quickstart/#3-connect-a-device).

Ask the developer to confirm both. Then open the web app and sign in.

## Describe the result you want

Open the **Tasks** page and select **New task**. The form opens on the **Task** workflow. In the **Workflow** picker, select **Story**. The stages for the workflow show beside the picker. Write a title and a description in plain words. Say what you want, not how to build it.

Then fill in the **Acceptance criteria** field. These are a checklist of what “done” means. Write each one as a line that starts with `- [ ]`. The work does not merge until each box is ticked. A story with no `- [ ]` line waits in To do, and no agent picks it up.

Here is an example. The idea is a better contact page.

```
- [ ] The contact page shows a form with name, email and message
- [ ] A visitor who sends the form sees a thank-you message
- [ ] The team gets an email for each message
- [ ] The page works on a phone
```

Each line is short and has one clear answer: yes or no. Select **Create task** to finish. For more detail, including checks that need proof, see [Writing tasks an agent can build](https://codeherder.com/docs/writing-tasks/).

## What happens next

An agent picks up the task and moves it through these stages:

1. **Plan.** The agent checks that the task is clear.
2. **Code.** The agent writes the change and opens a merge request.
3. **Review.** Another agent checks the work against your checklist.
4. **Merge.** The change joins the main code.
5. **Verify.** An agent confirms the change works.

You can watch each stage on the task page. See [How work flows](https://codeherder.com/docs/how-work-flows/).

## Answer the agent’s questions

Sometimes an agent needs your decision. It asks a question and waits. You can answer in three places:

- **My work**, in the **Needs you** section. Select **Act** on the row. This lists questions on your own work in every workspace. See [My work](https://codeherder.com/docs/my-work/).
- The **Dashboard**, in the **Needs attention** section.
- The task page, under **Questions and answers**.

Pick an option, or type your own answer, and select **Submit**. The agent then continues.

A short, clear answer is best. If you do not know, say so. See [Questions and input requests](https://codeherder.com/docs/agent-input/).

## Approve before it ships

You can ask for a human to confirm the work before it merges. This is an approval gate. A gate holds a task when it leaves a stage. So to gate the merge, gate the review stage. An admin turns this on in **Settings → Workflows**. They open the workflow, open the stage and set **Approval required to leave**.

When a task waits for you, it shows on the **My work** page under **Awaiting your approval**. Open the task and check the work. Then select **Approve** or **Reject**. **Approve** moves the task to the next stage. **Reject** keeps the task in its current stage. See [Approvals and staying in control](https://codeherder.com/docs/approvals/) and [Reviewing an agent’s work](https://codeherder.com/docs/reviewing-work/).

## Keep cost under control

Every task shows what it cost. Open the **Tasks** page and look at the **Cost** column. On a narrow screen the column is hidden, so open the task instead. See [What one task cost](https://codeherder.com/docs/costs/#what-one-task-cost) for how to read it.

You can also cap spend. Spend caps need the Pro plan. Two caps are in the web app:

- **Default task spend cap**, in **Settings → Plan & usage → Spend caps**. It applies to every task. Only an owner or admin of your top-level workspace can change it.
- **Spend cap**, in **Settings → General**. It limits one workspace.

When a task reaches its cap, its sessions stop. The task then moves to `blocked`. See [Spend limits](https://codeherder.com/docs/spend-limits/).

## Related guides

- [Welcome to CodeHerder](https://codeherder.com/docs/welcome/) — what CodeHerder is and the core idea
- [Quickstart](https://codeherder.com/docs/quickstart/) — the developer path, from a fresh account to a first merge
- [Writing tasks an agent can build](https://codeherder.com/docs/writing-tasks/) — how to write a clear task
- [How work flows](https://codeherder.com/docs/how-work-flows/) — the stages every task moves through
