Inclusion Criteria

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

Inclusion requirements

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

The tool must stay focused on a limited scope. It can 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 is not acceptable. The output is a diff, branch, pull request, test summary, log, or another artifact that fits an engineering review workflow.

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

Excluded tools

Autocomplete, code search, static analysis, lint fixes, and general coding chat do not meet the bar on their own. They can still be part of a delegated workflow. The directory tracks tools that can carry a scoped work package.

Documentation review schedule

Entries are reviewed against public documentation at least monthly when the category is moving quickly. Each entry shows when the documentation was last checked.