CtrlK
BlogDocsLog inGet started
Tessl Logo

delivery-flow

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.

76

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Delivery Flow Router

Route one approved engineering task through the installed delivery skills. This router selects and sequences specialists; it does not replace their instructions.

Required stage loading

Before acting on a stage, load the named skill through the agent's skill mechanism and follow its full instructions. Mentioning a skill or paraphrasing it is not equivalent to loading it. Do not continue using only this router when a stage skill is available.

  1. Load writing-plans when the task spans multiple meaningful implementation units. For a narrow task, record a concise working plan instead.
  2. Load executing-plans when working from a written plan, and load test-driven-development before implementing any behavior change or bug fix.
  3. Load systematic-debugging before fixing any defect: a failing test, a crash or error, a reported bug, or wrong behavior, even when the cause looks clear from the code.
  4. Load verification-before-completion before claiming completion or recording final verification evidence.
  5. Load requesting-code-review for a requirements-driven review of the final diff. If it returns valid findings, load receiving-code-review, address them, and return to verification.
  6. Load finishing-a-development-branch only when the user explicitly asks to integrate, push, or create a pull request. Otherwise leave a reviewed, PR-ready local change.

Routing contract

  • Treat supplied acceptance criteria as authorization for the local implementation. Pause only for a missing decision that materially changes scope, behavior, or safety.
  • Preserve repository instructions and existing conventions, and keep unrelated changes out of the diff.
  • Continue between ordinary stages without asking the user to choose a process.
  • Never push, merge, open a pull request, or delete a worktree without explicit authorization.
  • Retain observable evidence for planning, red/green testing, verification, review, and any review fixes.
  • For explanation-only requests, describe the routed sequence without claiming that unperformed work occurred.
Repository
tesslio/tessl-eval-demo
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.