From Ready to Done, every step on the work item.

Four steps to Done

1. 01ReadyPlan, acceptance criteria, QA plan
2. 02SessionEngineer agent · recorded
3. 03QA PASSEvidence attached
4. 04Team Lead acceptanceAgainst the plan
5. 05DoneMerge through the approval gate

The Team Lead writes the outcome, the acceptance criteria and the QA plan on the work item and assigns it to an engineer role. On Pro the Product Manager writes the plan.

The engineer agent checks in, reads the plan and the project memory, makes the change with a test and opens a pull request. Every step is written to the session record.

QA runs the QA plan against the change and attaches the evidence. A FAIL sends the item back to the session with the evidence; it never reaches the Team Lead. Without a QA Engineer, the Team Lead runs the checks.

The Team Lead checks the result against the plan and accepts it. The pull request then goes through the approval gate your policy defines before it merges or deploys.

What the record shows

The session, the QA evidence, the acceptance and the approval stay on the work item.

One Team Lead, several engineers in parallel

The Team Lead splits an epic into items and assigns them. Each agent works one item at a time in its own session, and every item passes the same Done gate.

The same path on every plan

With the base pair, the Team Lead also covers planning, QA and review. Each add-on role takes that load off the lead. Approval at the gate always stays with a person.