Skip to content
Antoine Le LouëtIndependent senior developer (Home)
Back to the Journal

Workshop4 min read

ADE: scope an AI agent's work through to the pull request

Prepare repository context with AI Delivery Engine, define a verifiable task and organise checks before human review of a PR.

A brief passes through an approved scope, a checked change and human review. Repository context and rules accompany the work through to the pull request.
ADE formalises delivery stages. The chosen agent makes the change within the approved scope, then the PR goes to human review.

A request too broad to start coding

'Improve catalogue search' leaves many decisions open to an AI agent. Should it speed up responses, add filters or change the display? A PR may contain correct code and still be hard to accept if no one defined the expected result.

I am developing AI Delivery Engine, or ADE, to make those preparation and validation steps explicit. Its local foundation brings together repository context and review rules. The documented workflow then describes moving from a request to a change the team can examine. The team still chooses its development assistant.

Prepare a first repository

To try the local foundation, the documentation requires Node.js 22 or later. From a project's root, the following commands install ADE as a development dependency, create its configuration, generate context and run deterministic review.

Terminal · documented setup
npm install -D @alelouet/ai-delivery-engine
npx ade init
npx ade context generate
npx ade review

This sequence changes the project: review the created files and dependency changes. It shows ADE's documented starting process, not a test result on your application. The foundation works without a model API key. Context generation and deterministic review do not implicitly call an AI provider.

Before assigning a task to an agent, adapt ade.config.json to the repository paths and sensitive files. Shared working rules also belong in AGENTS.md. Generated context helps convey the project structure; acceptance criteria still need to be written for the specific request.

Write down what makes the task acceptable

Return to a fictional catalogue search. The team confirms that the requirement concerns retaining filters when moving to the next page. It can then prepare a limited task with cases the developer and reviewer can reproduce.

Fictional scope example
Objectif
Conserver le filtre de catégorie dans les liens de pagination.

Critères d’acceptation
- La page suivante conserve la catégorie sélectionnée.
- Changer de catégorie revient à la première page.
- Une URL partagée retrouve le filtre et la page demandés.

Hors périmètre
Pas de changement du moteur de recherche ni de nouvelle interface.

Vérification attendue
Tests des URL et parcours manuel avec retour arrière.

This text is a scoping example for discussion. It does not, by itself, represent the structured ADE handoff format. In the documented GitHub workflow, ADE first plans the request; development relies on an approved implementation handoff that sets, among other things, the scope and acceptance criteria. If a product decision is missing, it must be resolved before broadening the work.

Plan checks and understand what they cover

Once the change is implemented, npx ade review --staged targets changes staged for commit. The review checks configuration, context freshness and applicable rules, among other things. Project tools can be run with --run-tools when configured in ADE.

For the fictional pagination task, you still need to choose a test that actually detects the lost filter and navigate the interface. A rule report with no errors is not enough to demonstrate that navigation suits the user. Test and build commands remain those of the repository, to configure or run explicitly according to the chosen workflow.

ADE's delivery workflow also includes specialist reviews according to configured profiles, followed by bounded corrections if needed. Profile choices depend on the project. An access-rights change needs different checks from an article or pagination link.

Leave a clear decision in the PR

The PR should connect expected behaviour to the delivered change. In our example, its author can explain which link lost the filter, show the new behaviour and state the checks performed. Anything not verified must remain visible to the reviewer.

PR creation depends on integration: in local mode, the developer follows the repository's Git rules; in ADE Control Plane, the orchestrator owns Git and GitHub operations. The workflow retains human review and an explicit merge decision. Installing the CLI alone does not set up that entire orchestration.

To evaluate ADE, choose an upcoming short task and keep its record through review. Can the reviewer find the accepted scope and validation evidence without restarting the entire conversation with the agent? That question provides a concrete criterion for deciding what to retain or adjust in the process.

Sources and useful links

Share on LinkedIn (new tab)

Keep reading
All articles in this category