Criteria

A tool belongs in the Software Delegate directory when it can take a software task and return work that a human can inspect, test, and accept.

What qualifies for inclusion

The tool must let a user delegate work. A user should be able to assign work through an issue, prompt, ticket, pull request comment, IDE action, command line session, or another similar entry point.

The tool must stay within a limited scope. It should be able to inspect a codebase and carry out at least one implementation action, such as editing files, running tests, pushing a branch, opening a pull request, or preparing a patch.

The tool must return a reviewable artifact. A chat answer does not meet the requirement. The output should be a diff, branch, pull request, test summary, log, or another artifact that can enter an engineering review workflow.

Acceptance must stay with a human or a separately governed workflow. A software delegate can prepare the work. It should not silently become the release authority.

Exclusions

Autocomplete, code search, static analysis, lint fixes, and general coding chat are not enough on their own. They may become part of a delegated workflow. The directory tracks tools that can carry a scoped work package.

Review schedule

Review entries against public documentation at least monthly while the category is moving quickly. Each entry should show when the documentation was last checked.