tessl-eval-demo

Implements a feature or bug fix test-first - write one failing test, watch it fail, write the minimal code to pass, then refactor with tests green. This is the implementation stage inside the delivery-flow workflow, entered by requests like "implement this feature", "fix this bug", "write the code for this", or "add the tests and implement it" once delivery-flow is driving the change. Do not activate directly for a standalone request that has not gone through delivery-flow first.

Internal verification gate for delivery-flow. Use before delivery-flow claims work is complete, fixed, or passing; do not activate directly for a standalone user request.

Internal verification gate for delivery-flow. Use before delivery-flow claims work is complete, fixed, or passing; do not activate directly for a standalone user request.

Internal verification gate for delivery-flow. Use before delivery-flow claims work is complete, fixed, or passing; do not activate directly for a standalone user request.

Write a detailed implementation plan for a feature, spec, or ticket, breaking the work into bite-sized, testable tasks with exact file paths, code samples, and test commands an engineer can follow step by step. This is the internal planning stage of the delivery-flow workflow, run after delivery-flow splits the work into multiple meaningful implementation units. It is not a standalone entry point, so do not activate it directly for a one-off user request or a narrow change; use delivery-flow for those instead.

Write a detailed implementation plan for a feature, spec, or ticket, breaking the work into bite-sized, testable tasks with exact file paths, code samples, and test commands an engineer can follow step by step. This is the internal planning stage of the delivery-flow workflow, run after delivery-flow splits the work into multiple meaningful implementation units. It is not a standalone entry point, so do not activate it directly for a one-off user request or a narrow change; use delivery-flow for those instead.

Write a detailed implementation plan for a feature, spec, or ticket, breaking the work into bite-sized, testable tasks with exact file paths, code samples, and test commands an engineer can follow step by step. This is the internal planning stage of the delivery-flow workflow, run after delivery-flow splits the work into multiple meaningful implementation units. It is not a standalone entry point, so do not activate it directly for a one-off user request or a narrow change; use delivery-flow for those instead.