Skip to main content

Plan

Your agent reads the code, asks what only you can answer and writes one Plan. You approve it once, before any code is written.

A Plan in the App: one open decision with both paths drawn, beside the agent's conversationA Plan in the App: one open decision with both paths drawn, beside the agent's conversation
An example task in a fictional project.

Start a Plan​

Choose + › Task, describe the change and keep Plan with QualityLayer.

Answer the questions​

Your agent asks only about choices the code leaves open, each with a recommendation. A small change may get none.

  1. Pick a choice

    Your turn shows one question at a time. Choose a row, or write your own answer and press Send.

  2. Go faster

    Answer in any order from the numbered strip. Use all recommended takes every recommendation; Tell me more explains one.

  3. Change your mind

    Each answer reaches your agent at once. Change reopens it.
A Plan question in Your turn: the recommended choice open with its diagram, the other folded to one line, and your own answer belowA Plan question in Your turn: the recommended choice open with its diagram, the other folded to one line, and your own answer below
Tip
Your agent keeps reading the code while you answer. A new question comes only when an answer raises a new decision.

What the Plan shows​

SummaryWhat users get, the size of the build and what reviewed it.
Done meansThe numbered results you accept the change by. Verify shows each one as it ran.
DiagramsUp to three: before and after, a flow, a sequence or the architecture.
InterfaceOne clickable artifact per screen.
Note
Build notes for the agents are in agents/01-plan.md, under For agents in the Reader. qualitylayer plan export --out <folder> copies the Plan for readers without QualityLayer.

Approve​

  1. Settle your calls

    A choice only you can make shows as Your call. Approve stays locked until each one is answered and any second opinion has finished.

  2. Ask for changes

    Mark a passage, diagram or screen to open the quick feedback field. Write what should change and send it. The diff shows what changed.

  3. Approve

    Approve and build here builds in the planning session. Choose where to build, under the arrow, picks another agent or workspace.

Answering a question does not approve the Plan. Changes after approval show on Verify as amendments. To have the Plan reviewed on GitHub, Pull request in the header pushes it on its own branch and opens GitHub's page to create the pull request; an approving review there, by someone with write access, approves the Plan.

Other kinds of Plan​

The Plan finds the cause in the code first, then states the bug in four parts. Done means starts with a test that fails today. For example:

WhenSomeone opens /reports?page=2.
TodayThe page shows 49 of 50 rows.
ExpectedEvery page shows all of its rows.
Must keep workingPage size stays 50; the first page does not change.