Plans and acceptance criteria
Write a brief Ysra can turn into a scope, acceptance criteria and a plan, and approve or revise the plan before any change with Plan first.
On this page
Acceptance criteria are the checklist a Code task is checked against at the end; the scope is what you asked for, fixed when the task starts; the plan is the order Ysra works in. Read this page to understand why a task did or didn’t count as done, or to write a brief that gets checked the way you mean. How the checks run is on Review and verification.
The rule#
Your brief sets the scope, and only you can grow it. The plan can reorder work, and review can find defects, but neither can add deliverables; and “10 of 10 steps complete” means the work was done, not that it was proven.
| Built from | Controls | Can’t | |
|---|---|---|---|
| Scope | Your brief, your criteria, an approved spec | What to deliver, what to leave alone, required technology | Grow on its own. Review feedback can’t add deliverables. |
| Acceptance criteria | The scope, plus Ysra’s quality baseline | What the result is checked against | Rewrite your objective. |
| Plan | Ysra, while working | The order of steps | Change the scope. |
Scope#
The scope records your deliverables, what to leave alone, the parts of the repository the work applies to, and any technology choice you made explicit.
| You wrote | Ysra treats it as |
|---|---|
| “Don’t change the API” | A constraint that is checked, never a task |
| Nothing about a module | Not permission: the scope narrows to what the work touches |
| “Must be a Next.js app” | Binding |
| A technology mentioned in passing | Not a requirement |
| “A or B” | Still a choice |
Acceptance criteria#
| Field | Values |
|---|---|
| Source | Yours (from your brief or ticket), derived (inferred from your goal), or quality baseline (such as not breaking the build) |
| Applicability | Required, conditional, or not applicable |
| Severity | Blocker, major or minor |
| Proof required | A repository command, a unit or integration test, an API contract check, a browser workflow, a state check, a visual or accessibility check, a security scan, a deployment smoke test |
| Negative cases | What must not happen (“an invalid week number is rejected”) is tested, not assumed |
Proof is chosen by kind of work: a web criterion needs browser proof, an API criterion needs contract and integration checks, stored data needs a check of the stored state. An admin feature isn’t accepted because a page exists: it has to change something observable.
When you give criteria, Ysra reviews against yours, one by one. When a brief is too thin to yield any, Ysra still creates a meaningful one rather than passing an empty checklist.
Plans and deliverables#
The working plan is a numbered list of steps, each with its status. It is revised as Ysra learns; Ysra may complete, block or reorder its own steps, never add product scope.
Every requested deliverable is tracked separately as delivered, partial or not started. A task can’t be reported as successful while something you asked for was never started: you see an explicit gap instead.
Plan first#
With Plan first turned on (a switch in the thread's Access menu; see Access modes), Ysra writes a specification before changing anything: work items, their order and dependencies, the deliverables each covers, and anything it thinks you didn’t ask for. The plan is checked for overloaded items, missing deliverables and unrequested scope. Nothing changes until you approve; then the approved spec becomes the fixed scope.
Plan card states#
| State | What it means | What moves it on |
|---|---|---|
| Ready for review | The newest plan, waiting for you. | Approve & build, Approve only, or a reply |
| Approved | You approved it. | Work starts (with Approve & build) or waits for you to start it |
| Superseded | A newer version replaced it. It stays in the thread. | — |
The header’s badge (PLAN v1, PLAN v2…) counts the versions.
What the card holds#
| Part | Detail |
|---|---|
| Summary | What the plan delivers |
| Milestones | Numbered, each as title · N tasks, with its outcomes |
| N acceptance criteria | Folded |
| Blocking questions | Under “Blocking questions — reply below to resolve them:”. The plan can’t be approved until you answer. |
| N open questions (don't block approval) | Folded |
| Open as PDF | Saves the plan and opens it in your PDF viewer |
Answering a plan#
| You choose | What happens |
|---|---|
| Approve & build | Approves and starts the work (it reads Approving… meanwhile). |
| Approve only | Approves without starting. |
| A reply below (“…or reply below to revise it.”) | Becomes the input for the next version; the current one is Superseded. |
Only the newest plan has the buttons. See also Plan first in the desktop app. For work too large for one thread, see Projects.
Writing a brief Ysra can hold itself to#
| Do | Weak | Strong |
|---|---|---|
| Describe outcomes, not steps | “Add pagination.” | “Paginate the invoices page: 25 per page, archived invoices sorted last. Keep the URL shareable (?page=3). Existing filters must keep working. Add tests for the first page, the last page, and an empty result.” |
| Name what must not change | — | “Keep the public API unchanged”, “don’t touch the billing module”, “no backend” |
| Paste the criteria you have | — | The ticket’s acceptance criteria, as they are |
| Be explicit about technology when it matters | “maybe use DateRange” | “Use the existing DateRange type” |
| Attach what a person would need | — | A screenshot of the bug, the design, the error log, the API contract |
If it doesn’t work#
| Symptom | Why | What to do |
|---|---|---|
| Approve & build isn’t there | The plan has blocking questions, or it isn’t the newest version. | Answer the questions below it; use the newest card. |
| Ysra read the brief differently from what you meant | The brief left room for it. | Steer early and name what to leave alone; or use Plan first and reply to the plan. |
| “10 of 10 steps complete” but Didn't work | Plan progress isn’t proof. | Read what failed; see Review and verification. |
| A criterion is unproved | It needs proof that couldn’t be produced, such as browser proof. | Ask for that proof, or try it yourself. |
Related#
- Review and verification — how each criterion is proven.
- How a Code thread works — where the plan fits in a task.
- Steering and saved points — changing course mid-task.
- Projects — milestones and tasks for work too big for one thread.