Plan a feature: tasks, builders and checks

{{brand}} drafts the tasks and checks from the approved design. You choose who builds each task, then approve the plan.

In short

Once the design is approved, {{brand}} drafts the plan from it: the tasks to build and the checks that will prove the feature works. This draft uses no AI. You choose, for each task, whether an AI agent or a person builds it, then approve the plan. Approving makes the task cards.

Steps

Open the Feature card and its "Design & plan" tab. The plan is under the design.
Press "Plan it" if the plan is not drafted yet.
Under "Tasks", answer "Who builds each one?" for every task: "AI agent" or "A person".
Under "Checks", read each line. Switch off a check you do not want with its "Keep" box.
Press "Approve the plan", or "Choose builders and approve" from the next-step box.

Result: the status reads "Approved" and each task becomes a child card, such as "Open KEY-12".

Read the checks

{{brand}} finds the same API by method and path, the same table by schema and name, and the same journey by design and journey key.
"Not matched yet" or "Not in a connected project" means no connected project has it.
"Also used in 2 other projects" shows who else relies on that check. Their checks run when you may open them and are never changed. "and 1 you cannot open" counts hidden ones without naming them.
A staged check runs on the pull request only. Merging the pull request applies it. Cancelling the card discards it.

Good to know

With "Plan approved" set to Ask me, a person approves. With Automatic, {{brand}} approves the plan itself. Quick cards use Automatic.
A task given to the AI agent still waits for a person to give it to the agent. See /help/boards/build-a-feature.
If the design changes after the plan is approved, the plan waits for "Review the impact" before it updates.

If something goes wrong

"No plan yet" - the design is not approved yet.
"Waiting for the impact review" - accept or review the design change first.
A check shows no project - connect an API Tester, SQL Tester or UI Tester record under "Connected to the product flow".