is the task — described inline, or pointing at the spec or set of tickets that holds it.

Told briefing held, build on the answers that came with the task and open step 1. Otherwise call the skill over this task, to settle three things:

Call the skill and hold its red → green loop, writing every test at the seams the briefing settled.

Name the project from its root marker, then pick the tools from the language of the code you are editing. A task that touches both sides of a Laravel project takes both Laravel rows.

artisan

pest-testing

artisan

pubspec.yaml

flutter test

flutter analyze

On every slice, run the one test file you are working on and the checks in the last column. Run the whole suite once, at the end.

When the build is done, review it on two sides, and carry the fixes yourself.

Both stop at a report and hand it back to you. Work each report to empty:

Call the skill to close.

Done when: the whole suite has run green, and every finding from step 2 is either fixed or standing in the debrief.