GitHub Issues backlog agent

The GitHub Issues backlog agent reads every open GitHub issue labelled agent-ready, implements the dbt™ models each one needs with tests and YAML docs, opens one PR per issue, and posts the link to Slack. One agent, one Bolt schedule: no custom Python, SDK glue, or orchestrator.

Prerequisites

Slack connected (the agent posts status updates to its configured channel via post_slack_message).
Your repository connected so the agent can branch, commit, and open PRs (it reads issues and opens PRs with the gh CLI).
Familiarity with programmable agents and running an agent with Bolt.
Issues to automate must be open and carry the label agent-ready.

Estimated time: 15 minutes.

Steps

Create the agent

In the Agent app, open Agents, select New agent, and start from the github-backlog-agent template (or Start from scratch). Fill in the builder fields with the content below. See Build an agent in the UI for a tour of the builder.Name: github-backlog-agentRole:

Analytics Engineer turning GitHub issues into well-scoped dbt model
PRs, using the gh CLI.

Goal:

For each open GitHub issue labelled "agent-ready" — or the specific
issue number in the trigger message: read it, implement the dbt models
it needs (staging, plus a mart where appropriate) with tests and YAML
docs on a new branch, open a PR that closes the issue, and post the PR
link to Slack. One branch and one PR per issue. Skip any issue that
already has an open PR.

Backstory:

You never invent a column that isn't in the source. When an issue is
ambiguous, you flag it under "Open questions" in the PR instead of
guessing. You follow the project's dinorules conventions and implement
everything yourself — no delegation.

Model: leave Auto selected.Allowed tools (everything else is refused, see the Tools Reference):

read_file, write_file, replace_in_file, search_files_and_directories, ripgrep_search
run_sql_query
run_terminal_command
post_slack_message

Output: set the Slack channel to #analytics-eng (or your team’s channel).

Deploy the agent

Select Deploy and choose where the agent lives:

Just here: saved to the workspace and live immediately, ideal while you tune the goal.
Open a pull request: committed to your repo as .dinoai/agents/github-backlog-agent.yml, so the agent is version-controlled and reviewed as code.

Both kinds appear in the Bolt agent picker. See Creating Agents in the App for the deploy options.

Run it with Bolt

On the Agents page, hover the agent card and select Schedule. This opens a new Bolt schedule with the Run Paradime DinoAI Agent command already added and the agent pre-selected. The command runs natively, so no API keys or environment variables are needed. Set the Task:

Find every open GitHub issue labelled agent-ready. For each one: read
it, implement the required dbt models with tests and YAML docs on a
new branch, open a PR with Closes #<number>.

See Run an agent with Bolt for the full walkthrough.

Choose a schedule frequency

Pick the cadence that matches how often your team labels new issues as agent-ready:

Cadence	Cron expression	When it runs
Every day at 9 AM	`0 9 * * *`	Monday–Sunday, 9:00 AM
Weekdays at 9 AM	`0 9 * * 1-5`	Monday–Friday, 9:00 AM
Once a week (Monday 9 AM)	`0 9 * * 1`	Every Monday, 9:00 AM
Twice a week (Mon & Thu)	`0 9 * * 1,4`	Monday and Thursday, 9:00 AM
Every 6 hours	`0 /6 * *`	12 AM, 6 AM, 12 PM, 6 PM

For most teams, weekdays at 9 AM (0 9 * * 1-5) is a good default. If there are no Agent Ready issues, the agent reports an empty backlog and the run completes cleanly.

After a run, each open agent-ready issue has one PR that closes it, and its link is posted to your Slack channel. When an issue already has an open PR, the agent skips it. Review the PRs, resolve any Open questions the agent flagged, and merge.

How it works

Bolt dispatches the agent natively on your chosen cadence with a task message telling it to process the agent-ready backlog. The agent lists the issues with the gh CLI, creates a branch and implements each one, pushes, opens a PR, then posts to Slack. Bolt blocks until the agent reaches a terminal state and inherits its success or failure, and the agent’s messages stream into the Bolt run logs.

Next steps

Linear backlog agent

The same pattern for a Linear backlog.

Jira backlog agent

The same pattern for a Jira backlog.

Run an agent with Bolt

Trigger agents from a Bolt schedule.

Programmable Agents reference

The agent schema, tools, and API.

Foundations

Automate with AI agents

Set up & configure

Orchestrate data pipelines

Migrate to Paradime

Develop in Paradime

Learn dbt™

GitHub Issues backlog agent

Steps

How it works

Next steps

Linear backlog agent

Jira backlog agent

Run an agent with Bolt

Programmable Agents reference

​Steps

​How it works

​Next steps

Linear backlog agent

Jira backlog agent

Run an agent with Bolt

Programmable Agents reference

Steps

How it works

Next steps