tessl-eval-demo

Use when an engineering task must be carried to a verified, reviewed, PR-ready local change: an approved ticket or requirements, a feature, or a bug fix, including a failing test, a crash, or a bug a user reported.

Carries a code change through to a tested, verified and reviewed local change, loading the stage skill for each step: planning, test-first implementation, debugging, verification and review. Use when a request asks for code to change, whether it arrives as an approved ticket or a one-line message: a bug fix, a failing test or crash, a small feature or flag, a behavior change, or review comments to fix. Not for questions about the code, for merging or deleting a finished branch, or for deciding which review comments to accept without changing code. Use it whenever the work will change code, even when the user does not mention tests, review or a pull request.

Carries a code change through to a tested, verified and reviewed local change, loading the stage skill for each step: planning, test-first implementation, debugging, verification and review. Use when a request asks for code to change, whether it arrives as an approved ticket or a one-line message: a bug fix, a failing test or crash, a small feature or flag, a behavior change, or review comments to fix. Not for questions about the code, for merging or deleting a finished branch, or for deciding which review comments to accept without changing code. Use it whenever the work will change code, even when the user does not mention tests, review or a pull request.

Carries a code change through to a tested, verified and reviewed local change, loading the stage skill for each step: planning, test-first implementation, debugging, verification and review. Use when a request asks for code to change, whether it arrives as an approved ticket or a one-line message: a bug fix, a failing test or crash, a small feature or flag, a behavior change, or review comments to fix. Not for questions about the code, for merging or deleting a finished branch, or for deciding which review comments to accept without changing code. Use it whenever the work will change code, even when the user does not mention tests, review or a pull request.

Use when an engineering task must be carried to a verified, reviewed, PR-ready local change: an approved ticket or requirements, a feature, or a bug fix, including a failing test, a crash, or a bug a user reported.

Executes a written multi-step implementation plan end to end - loads the plan, reviews it critically for gaps, works through each task with its verification steps, and reports when everything is done. This is the execution stage inside the delivery-flow workflow, entered by requests like "implement this plan", "run the plan", "execute the plan", or "work through these tasks" once delivery-flow has produced a written plan. Do not activate directly for a standalone request that has not gone through delivery-flow first.

Executes a written multi-step implementation plan end to end - loads the plan, reviews it critically for gaps, works through each task with its verification steps, and reports when everything is done. This is the execution stage inside the delivery-flow workflow, entered by requests like "implement this plan", "run the plan", "execute the plan", or "work through these tasks" once delivery-flow has produced a written plan. Do not activate directly for a standalone request that has not gone through delivery-flow first.

Executes a written multi-step implementation plan end to end - loads the plan, reviews it critically for gaps, works through each task with its verification steps, and reports when everything is done. This is the execution stage inside the delivery-flow workflow, entered by requests like "implement this plan", "run the plan", "execute the plan", or "work through these tasks" once delivery-flow has produced a written plan. Do not activate directly for a standalone request that has not gone through delivery-flow first.

Executes a written multi-step implementation plan end to end - loads the plan, reviews it critically for gaps, works through each task with its verification steps, and reports when everything is done. This is the execution stage inside the delivery-flow workflow, entered by requests like "implement this plan", "run the plan", "execute the plan", or "work through these tasks" once delivery-flow has produced a written plan. Do not activate directly for a standalone request that has not gone through delivery-flow first.

Executes a written multi-step implementation plan end to end - loads the plan, reviews it critically for gaps, works through each task with its verification steps, and reports when everything is done. This is the execution stage inside the delivery-flow workflow, entered by requests like "implement this plan", "run the plan", "execute the plan", or "work through these tasks" once delivery-flow has produced a written plan. Do not activate directly for a standalone request that has not gone through delivery-flow first.

Executes a written multi-step implementation plan end to end - loads the plan, reviews it critically for gaps, works through each task with its verification steps, and reports when everything is done. This is the execution stage inside the delivery-flow workflow, entered by requests like "implement this plan", "run the plan", "execute the plan", or "work through these tasks" once delivery-flow has produced a written plan. Do not activate directly for a standalone request that has not gone through delivery-flow first.

Executes a written multi-step implementation plan end to end - loads the plan, reviews it critically for gaps, works through each task with its verification steps, and reports when everything is done. This is the execution stage inside the delivery-flow workflow, entered by requests like "implement this plan", "run the plan", "execute the plan", or "work through these tasks" once delivery-flow has produced a written plan. Do not activate directly for a standalone request that has not gone through delivery-flow first.

Executes a written multi-step implementation plan end to end - loads the plan, reviews it critically for gaps, works through each task with its verification steps, and reports when everything is done. This is the execution stage inside the delivery-flow workflow, entered by requests like "implement this plan", "run the plan", "execute the plan", or "work through these tasks" once delivery-flow has produced a written plan. Do not activate directly for a standalone request that has not gone through delivery-flow first.

Executes a written multi-step implementation plan end to end - loads the plan, reviews it critically for gaps, works through each task with its verification steps, and reports when everything is done. This is the execution stage inside the delivery-flow workflow, entered by requests like "implement this plan", "run the plan", "execute the plan", or "work through these tasks" once delivery-flow has produced a written plan. Do not activate directly for a standalone request that has not gone through delivery-flow first.

Executes a written multi-step implementation plan end to end - loads the plan, reviews it critically for gaps, works through each task with its verification steps, and reports when everything is done. This is the execution stage inside the delivery-flow workflow, entered by requests like "implement this plan", "run the plan", "execute the plan", or "work through these tasks" once delivery-flow has produced a written plan. Do not activate directly for a standalone request that has not gone through delivery-flow first.

Executes a written multi-step implementation plan end to end - loads the plan, reviews it critically for gaps, works through each task with its verification steps, and reports when everything is done. This is the execution stage inside the delivery-flow workflow, entered by requests like "implement this plan", "run the plan", "execute the plan", or "work through these tasks" once delivery-flow has produced a written plan. Do not activate directly for a standalone request that has not gone through delivery-flow first.

Executes a written multi-step implementation plan end to end - loads the plan, reviews it critically for gaps, works through each task with its verification steps, and reports when everything is done. This is the execution stage inside the delivery-flow workflow, entered by requests like "implement this plan", "run the plan", "execute the plan", or "work through these tasks" once delivery-flow has produced a written plan. Do not activate directly for a standalone request that has not gone through delivery-flow first.

Executes a written multi-step implementation plan end to end - loads the plan, reviews it critically for gaps, works through each task with its verification steps, and reports when everything is done. This is the execution stage inside the delivery-flow workflow, entered by requests like "implement this plan", "run the plan", "execute the plan", or "work through these tasks" once delivery-flow has produced a written plan. Do not activate directly for a standalone request that has not gone through delivery-flow first.

Executes a written multi-step implementation plan end to end - loads the plan, reviews it critically for gaps, works through each task with its verification steps, and reports when everything is done. This is the execution stage inside the delivery-flow workflow, entered by requests like "implement this plan", "run the plan", "execute the plan", or "work through these tasks" once delivery-flow has produced a written plan. Do not activate directly for a standalone request that has not gone through delivery-flow first.

Executes a written multi-step implementation plan end to end - loads the plan, reviews it critically for gaps, works through each task with its verification steps, and reports when everything is done. This is the execution stage inside the delivery-flow workflow, entered by requests like "implement this plan", "run the plan", "execute the plan", or "work through these tasks" once delivery-flow has produced a written plan. Do not activate directly for a standalone request that has not gone through delivery-flow first.