Recommended Free Tools
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Jeel Vankhede’s one-off fix for an unverified task-queue payload grew into a staged AI-agent workflow: classify the request first, create durable artifacts at each phase, and pause for human review before later work proceeds. It is a practical design for steering agent-assisted software work, not proof that the workflow improves speed or reliability.
What changed when a one-task fix became a workflow?
In the ninth and final part of his series “The Contract,” Lead Full Stack Engineer Jeel Vankhede describes starting with a specific problem: a queue whose payload contract had not been verified. The response expanded into reusable instructions, skills, and checkpoints for handling software-engineering requests. The series installment appeared on Hashnode and as a DEV Community cross-post on August 11, 2026: Hashnode article and DEV Community cross-post.
The central shift is from asking an agent to complete a task in one conversational run to asking it to produce a chain of inspectable work products. Instructions and outputs persist between phases, so decisions are recorded in artifacts rather than left only in chat history.
How does the workflow decide what happens next?
A short instruction file at the repository root classifies each incoming request before work starts. Vankhede says trivial tasks are handled inline, while standard or complex requests—including spikes and longer or cross-cutting work—go through a fuller process. The root instructions sit above seven skill files, which support work at different phases.
#1 Best Overall
That classification is a routing decision, not an independently validated measure of task complexity. Vankhede identifies the gap himself: agreement between him and the agent does not show that a classification is objectively correct. A team adopting this pattern would need to decide what evidence or review could reveal misclassification, rather than treating agreement as proof.
What artifacts make the process inspectable?
For work that enters the full sequence, a slug groups the files for one work item. A requirement manifest separates what the requester explicitly asked for from what the agent inferred. Each phase reads the previous artifact, preserving a traceable handoff rather than depending on conversational memory alone.
- Exit gate: checks the artifacts for a phase before the next phase begins.
- Waiver: records when a phase is skipped, so an omission is visible rather than silently disappearing.
- Requirement manifest: keeps stated requirements distinguishable from inferred ones, which matters when reviewing scope and deciding what counts as complete.
These mechanisms make the process legible in principle; they do not, by themselves, guarantee that an artifact is correct. The value depends on the quality of the evidence in each file and on a person actually reviewing the consequential decisions.
Rank #2
What are the stages for standard or complex work?
Vankhede describes the following sequence. Each stage produces or checks an artifact that informs what follows:
- Brief: establish the work to be done and provide an early point for approval or return.
- Risk register: identify risks before implementation.
- Plan: lay out the approach for review before the build begins.
- Build: implement the approved approach.
- Requirement-by-requirement review: inspect the result against the manifest, including requirements that may be only partially met.
- Test matrix: record the testing considered across the work.
- Rollback plan: describe how to reverse the change if needed.
- Retrospective: capture what was learned after the work.
The article’s practical emphasis is not merely the number of stages, but where a person can intervene. A reviewer can approve or return the brief, examine the plan before implementation, and decide what to do about requirements marked partial. That creates a middle ground between writing every line oneself and inspecting only the finished result.
Where should a human review the work?
The design places review points before subsequent work makes a mistaken assumption more costly to correct. In a team adapting it, the useful question is what decision each checkpoint is meant to support—not whether every task needs every phase. A brief review can catch a misunderstanding of the request; a plan review can catch an unsuitable approach; a requirement review can expose incomplete delivery.
Rank #3
Those checkpoints only help when the artifacts are specific enough to judge. A manifest should preserve the distinction between explicit and inferred requirements; a review should identify partial items rather than obscure them; and a phase waiver should make skipped work visible. The author describes the structure and his use of it, but does not report measured outcomes establishing that it reduces errors or effort.
What has—and has not—been demonstrated?
Vankhede’s account is qualitative. He says the chain ran through one person, on one task, with that person approving each handoff. It therefore does not establish that another person would assign the same weight to the artifacts, or that the workflow generalizes across projects and teams. Nor does the article report performance statistics, time savings, reliability improvements, or broad adoption.
Those limits matter when deciding how to use the idea. The described workflow is a concrete way to make agent work reviewable; it is not evidence that its complexity classification is objectively right or that its gates produce better software. Teams can treat it as a process design to adapt and evaluate, not as a validated standard.
Rank #4
Where can readers see the original workflow?
Vankhede calls a compact guide a GitHub Gist and describes agentsmyth as the complete version. The article does not establish commercial terms for either resource. The original account and its cross-post are available at Hashnode and DEV Community.
“That is the actual product of nine parts. Not a more obedient agent. A place for me to stand while it works.” — Jeel Vankhede
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsSpecial offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.Quick Recap
SaleBestseller No. 2SaleBestseller No. 3
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
