How it works
From a request to a live release, step by step
Here is the whole journey of one change. The steps marked with a person are decisions a human makes. Nothing moves past them on its own.
1. A user asks, inside your product
Who: Business user
From any screen, a user opens a feature request or reports a problem. They write in plain language and can attach screenshots and files. A bug report captures useful context, such as the page and the app version, only with the user's consent.
2. An AI analyst works with them
Who: AI analyst agent
The project's business analyst asks follow-up questions until the need is clear, then writes a specification with fixed headings. For a bug, the intake assistant asks what happened and writes the report.
3. The requester sends it to development
Person decidesWho: Business user
The requester reads the specification, edits it if needed and sends it. Every version is kept. A technical analyst agent can add a technical analysis for the developers.
4. An issue is filed in your tracker
Who: Maestro
The request becomes a GitHub issue with the specification and the technical analysis. Its status is mirrored back into your product, so the requester always knows where it stands.
5. Your team approves it for development
Person decidesWho: Product owner or engineering lead
Approval is a label on the issue. Only approved issues can become development runs.
6. A development run builds it
Who: Coding agent
Maestro starts a run, by an operator's click or automatically on approval if the project allows it. The agent works on its own branch, implements the change with tests and opens a pull request that names the issue.
7. Review, CI and merge
Person decidesWho: Your reviewers
Maestro follows the pull request: reviews, checks and changes requested. The agent answers review comments and failing checks. The merge is done by a person, or automatically once CI is green and the required human approvals are on the pull request. Each project chooses.
8. The release goes live
Who: Your deploy
Your deploy reports the release it shipped. Maestro links it to the run, the pull request and the issue.
9. Users hear about it, and test it
Person decidesWho: Business users and operators
A plain-language article appears in What's New and the requester is told the change is live. Users try it and say whether it works. An operator approves the article as released, and that approval can be the gate for promoting a release to production.
Bring your product team into the loop
Maestro is ready to deploy on your product. Tell us about your product and your team, and we will show you how Maestro runs it.
Your product's AI team and delivery pipeline, with people at every gate.
Maestro is part of the TALOS MaiND family.