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
SKILL.mdskills/sdlc-router/skills/delivery-flow/SKILL.md
GitHubDelivery 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.
- Load
writing-planswhen the task spans multiple meaningful implementation units. For a narrow task, record a concise working plan instead. - Load
executing-planswhen working from a written plan, and loadtest-driven-developmentbefore implementing any behavior change or bug fix. - Load
systematic-debuggingbefore 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. - Load
verification-before-completionbefore claiming completion or recording final verification evidence. - Load
requesting-code-reviewfor a requirements-driven review of the final diff. If it returns valid findings, loadreceiving-code-review, address them, and return to verification. - Load
finishing-a-development-branchonly 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.