role-worker

Consume GitHub issues from a backlog and execute the act-dev workflow.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/JuroOravec/agents --skill role-worker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: role-worker
Source: https://github.com/JuroOravec/agents/tree/main/.cursor/skills/role/worker
Command: npx skills add https://github.com/JuroOravec/agents --skill role-worker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates development work by continuously taking issues from a GitHub backlog pool, executing the full act-dev workflow, and closing each issue when complete.

Core Features & Use Cases

  • Parallel processing: multiple workers can take different issues from the same pool.
  • Full act-dev workflow: design, implement, test, validate, document, changelog, and PR.
  • Automatic issue closure: closes the GitHub issue via PR or explicit close if PR is skipped.

Quick Start

Provide a backlog of issues and say implement these issues to begin the end-to-end act-dev workflow.

Frequently Asked Questions about role-worker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub issue implementation from a backlog pool?

Automating GitHub issue implementation is done by consuming issues from a backlog pool and executing the full act-dev workflow to design, implement, test, document, and PR the work. Multiple workers can process different items in parallel.

Can multiple workers process GitHub issues in parallel?

Yes, parallel execution is supported. Multiple workers can take different issues from the same backlog pool simultaneously, with prioritized sequencing and dependency awareness to coordinate the development work.

What steps does the act-dev workflow cover for issue management?

The act-dev workflow covers end-to-end steps: design, implement, test, validate, document, create a changelog, and submit a PR. It automatically closes the GitHub issue via the PR or explicitly if the PR is skipped.

Do I need GitHub integration to automate issue closure with act-dev?

Yes, GitHub integration is required. The Skill requires integration with GitHub issues to view, claim, and close them, ensuring that completed work is tracked and the backlog is updated automatically.

How do I start parallel execution on a backlog of GitHub issues?

To start parallel execution, provide a backlog of GitHub issues and say implement these issues. This initiates the end-to-end act-dev workflow, where workers claim and process items continuously.

What happens if a PR is skipped during GitHub issue automation?

If a PR is skipped during GitHub issue automation, the Skill will explicitly close the GitHub issue instead of closing it automatically via the PR merge, ensuring the backlog item is still marked as complete.