End-to-end workflow

The normal standalone flow is:

1. Register a clean Git project.
2. Create a task from Dashboard, CLI, Telegram or Chat.
3. Prepare the task, which creates an isolated branch/worktree.
4. Start a Goal; the autopilot can also pick up queued work when enabled.
5. Execute planning, implementation, testing and review through available providers.
6. Validate the diff, project checks and secret scan.
7. Deliver a commit, pushed branch and draft pull request.
8. Review the evidence and choose approve, request changes or reject.

Maestro never writes directly to the project’s base branch for a task. The worktree, branch and original request form the durable unit of execution.

Feature plans

For coordinated larger work, a Feature Plan groups tasks, acceptance criteria, priorities and dependencies. Feature work has a distinct integration protocol: individual Work PRs remain draft evidence, and the consolidated Feature PR is the merge candidate. Do not treat a Feature Plan as a faster standalone task.

Autopilot

Autopilot is enabled by default and polls the queue. It respects dependency readiness and the configured maximum concurrent Goals. A Goal waiting for a provider does not consume the running capacity. Disable or tune it with the MAESTRO_AUTOPILOT_* settings in Configuration.