Neura Market
prompt logo

prompt

Free

Autonomous workflow orchestrator for issue-tracker-driven agent execution

FreeFree tier
Type
Open Source
Visit Website GitHub (40 stars)

About prompt

The Symphony Workflow Orchestrator Architect is a prompt template designed to create an autonomous AI agent that orchestrates long-running automation services. It continuously reads work items from an issue tracker, creates isolated workspaces for each issue, and runs coding-agent sessions inside those workspaces without requiring engineers to micromanage every step. The workflow policy lives in-repo as a version-controlled WORKFLOW.md file, ensuring runtime behavior changes ship through the same PR review process as code changes. Core responsibilities include designing the WORKFLOW.md contract with YAML front matter (defining tracker, polling, workspace, hooks, and agent configuration), enabling per-issue workspace isolation, bounded concurrency, exponential backoff retry, and reconciliation without a persistent database. The thesis is to turn project work into isolated, repeatable implementation runs so teams manage work at a higher level while agents handle implementation.

Key Features

Designs a self-contained, version-controlled WORKFLOW.md contract with YAML front matter for orchestrator configuration
Enables per-issue workspace isolation to prevent command leakage across issue boundaries
Reads work from issue trackers (e.g., Linear) and polls for updates
Configurable hooks (after_create, before_run, after_run, before_remove) as shell scripts with timeout
Supports bounded concurrency, exponential backoff retry, and reconciliation without a persistent database

Pros & Cons

Pros
  • Reduces need for engineers to micromanage every coding step by automating workflow execution
  • Provides strong isolation between issues, preventing cross-contamination of agent commands
  • Workflow configuration is version-controlled and shipped through normal code review processes
  • Designed for reliability with exponential backoff retry and no dependency on a persistent database
Cons
  • Requires careful initial setup of the issue tracker integration and WORKFLOW.md configuration
  • Depends on the quality and capability of the underlying coding agent being invoked
  • May introduce complexity in debugging workflow behavior when hooks or agent sessions fail

Best For

Automating software development tasks by converting issue tracker items into isolated agent implementation runsEnabling teams to manage work at a higher level while AI agents handle hands-on codingBuilding a multi-agent orchestration system where each issue gets its own agent session

FAQ

How does the orchestrator discover work?
It reads from an issue tracker defined in the WORKFLOW.md YAML front matter (e.g., Linear, endpoint, API key, project slug) and polls for issues in active states at a configurable interval (default 30 seconds).
What is the WORKFLOW.md file?
It is a repository-owned, version-controlled contract that defines how the orchestrator discovers work, configures the agent, and renders per-issue prompts. It includes YAML front matter for settings and optionally shell script hooks.
Does this require a database?
No. The system is designed for reconciliation without a persistent database, using isolated workspaces and exponential backoff retry.