tessl-eval-demo
github.com/tesslio/tessl-eval-demo
| Skill | Added | Review |
|---|---|---|
test-driven-development 02-mutation/versions/record-red/sdlc-implementation/skills/test-driven-development/SKILL.md Implements a feature or bug fix test-first: write one failing test, run it and watch it fail, write the minimal code to pass, then refactor with the tests green. Use when a change alters code behavior: a new feature, a bug fix, or a behavior change, whether the request comes alone or through delivery-flow. | 71 71 Impact — No eval scenarios have been run Securityby  Passed No findings from the security scan Version: 5cb6fa3 | |
test-driven-development 02-mutation/versions/action-order/sdlc-implementation/skills/test-driven-development/SKILL.md Implements a feature or bug fix test-first: write one failing test, run it and watch it fail, write the minimal code to pass, then refactor with the tests green. Use when a change alters code behavior: a new feature, a bug fix, or a behavior change, whether the request comes alone or through delivery-flow. | 68 68 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 5cb6fa3 | |
test-driven-development 03-ablation/versions/no-cycle/sdlc-implementation/skills/test-driven-development/SKILL.md Implements a feature or bug fix test-first: write one failing test, run it and watch it fail, write the minimal code to pass, then refactor with the tests green. Use when a change alters code behavior: a new feature, a bug fix, or a behavior change, whether the request comes alone or through delivery-flow. | 73 73 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 5cb6fa3 | |
test-driven-development 02-mutation/versions/current-stubbed/sdlc-implementation/skills/test-driven-development/SKILL.md Implements a feature or bug fix test-first: write one failing test, run it and watch it fail, write the minimal code to pass, then refactor with the tests green. Use when a change alters code behavior: a new feature, a bug fix, or a behavior change, whether the request comes alone or through delivery-flow. | 55 55 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 5cb6fa3 | |
test-driven-development 03-ablation/versions/no-rules/sdlc-implementation/skills/test-driven-development/SKILL.md Implements a feature or bug fix test-first: write one failing test, run it and watch it fail, write the minimal code to pass, then refactor with the tests green. Use when a change alters code behavior: a new feature, a bug fix, or a behavior change, whether the request comes alone or through delivery-flow. | 73 73 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 5cb6fa3 | |
test-driven-development skills/sdlc-implementation/skills/test-driven-development/SKILL.md Implements a feature or bug fix test-first: write one failing test, run it and watch it fail, write the minimal code to pass, then refactor with the tests green. Use when a change alters code behavior: a new feature, a bug fix, or a behavior change, whether the request comes alone or through delivery-flow. | 73 73 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 5cb6fa3 | |
test-driven-development 06-regression/versions/old-description/sdlc-implementation/skills/test-driven-development/SKILL.md 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. | 75 75 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 5cb6fa3 | |
test-driven-development 06-regression/versions/no-cycle/sdlc-implementation/skills/test-driven-development/SKILL.md Implements a feature or bug fix test-first: write one failing test, run it and watch it fail, write the minimal code to pass, then refactor with the tests green. Use when a change alters code behavior: a new feature, a bug fix, or a behavior change, whether the request comes alone or through delivery-flow. | 76 76 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 5cb6fa3 | |
test-driven-development 02-mutation/versions/current/sdlc-implementation/skills/test-driven-development/SKILL.md Implements a feature or bug fix test-first: write one failing test, run it and watch it fail, write the minimal code to pass, then refactor with the tests green. Use when a change alters code behavior: a new feature, a bug fix, or a behavior change, whether the request comes alone or through delivery-flow. | 71 71 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 5cb6fa3 | |
test-driven-development 06-regression/versions/baseline/sdlc-implementation/skills/test-driven-development/SKILL.md Implements a feature or bug fix test-first: write one failing test, run it and watch it fail, write the minimal code to pass, then refactor with the tests green. Use when a change alters code behavior: a new feature, a bug fix, or a behavior change, whether the request comes alone or through delivery-flow. | 72 72 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 5cb6fa3 | |
test-driven-development 00-activation-testing/after/plugins/sdlc-implementation/skills/test-driven-development/SKILL.md 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. | 71 71 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 5cb6fa3 | |
verification-before-completion 00-activation-testing/before/plugins/sdlc-assurance/skills/verification-before-completion/SKILL.md 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. | 61 61 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 5cb6fa3 | |
verification-before-completion skills/sdlc-assurance/skills/verification-before-completion/SKILL.md 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. | 61 61 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 5cb6fa3 | |
verification-before-completion 00-activation-testing/after/plugins/sdlc-assurance/skills/verification-before-completion/SKILL.md 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. | 61 61 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 5cb6fa3 | |
writing-plans skills/sdlc-planning/skills/writing-plans/SKILL.md 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. | 73 73 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 5cb6fa3 | |
writing-plans 00-activation-testing/before/plugins/sdlc-planning/skills/writing-plans/SKILL.md 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. | 73 73 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 5cb6fa3 | |
writing-plans 00-activation-testing/after/plugins/sdlc-planning/skills/writing-plans/SKILL.md 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. | 73 73 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 5cb6fa3 |