Implementing Features

Azent can implement new features end-to-end: it reads the work item, creates a branch, writes code, validates, and opens a pull request.

How to trigger

Go to a work item and add a comment:

What the agent does

1. Reads the work item title, description, and acceptance criteria
2. Reads your comment for any additional instructions
3. Clones the repository and creates a new branch from the default branch
4. Analyzes the codebase to understand architecture, patterns, and conventions
5. Implements the feature across the necessary files
6. Runs the validation pipeline (if configured)
7. If validation fails, reads the logs, fixes the issues, and retries
8. Opens a pull request linked to the work item
9. Posts a status summary comment on the work item

An example, end to end

The screenshots below are a real example: a work item asking Azent to fix an OAuth state-validation gap, and the pull request Azent opened in response.

1. The work item

The ticket describes the bug, points at the exact files and lines, and lists acceptance criteria. A single @mention in the discussion is enough — the agent reads the description, picks up the request, and posts back a status comment while it works:

2. The pull request Azent created

Azent opened a PR linked back to the work item, with a description that summarises the change and the steps it took. The branch is named after the work item, and the linked work item is shown in the right sidebar:

Tips for best results

• •Write clear acceptance criteria in the work item — the more specific, the better the result
• •Include technical hints in your comment if you know where the change should go (e.g. "add a new endpoint in the OrdersController")
• •Use the preprompt to tell the agent about your project's architecture and conventions
• •Set up a validation pipeline to catch issues before the PR is opened
• •For complex features, consider breaking down the work item first, then implementing each sub-task separately