How it works

From a goal to inspectable work.

Plan a change, watch each stage make a decision, and inspect the delivered result.

Last updatedSeptember 27, 2026

Describe the outcome

Start in Mission with a concrete user goal. ACP can ask clarifying questions and turn the accepted request into tickets. For interface work, Design can begin while the planner completes UI tickets.

The plan is a checkpoint: read it and resolve missing requirements before asking agents to implement it. A small first goal is easier to verify than an entire product brief.

Start your first app →

Watch work move through the pipeline

A builder commits a change. Testing and review then decide whether it can advance or needs another pass. Optional Browser Verify checks a running interface. A blocked ticket retains its evidence so you can identify the failed stage and next action.

The board shows the workflow and run output. It is a better place to judge progress than a single agent completion message.

Understand the pipeline →

Inspect the delivery

New Plan → Feature can collect all of its tickets on one shared branch and draft pull request. Standalone tickets can each produce a separate pull request. Mission Build or Change can use a direct project-main route. The chosen workflow determines which result to expect.

Read the diff, test evidence, and resulting behavior before merging or deploying. ACP supplies an accountable process; you remain the product owner.

Compare delivery routes →